Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 1
744
| labels
stringlengths 4
574
| body
stringlengths 9
211k
| index
stringclasses 10
values | text_combine
stringlengths 96
211k
| label
stringclasses 2
values | text
stringlengths 96
188k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8,387
| 11,551,741,146
|
IssuesEvent
|
2020-02-19 02:31:13
|
googleapis/python-storage
|
https://api.github.com/repos/googleapis/python-storage
|
closed
|
Synthesis failed for python-storage
|
api: storage autosynth failure type: process
|
Hello! Autosynth couldn't regenerate python-storage. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
.coveragerc
.flake8
.github/CONTRIBUTING.md
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.gitignore
.kokoro/build.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/continuous.cfg
.kokoro/docs/common.cfg
.kokoro/docs/docs.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/presubmit.cfg
.kokoro/publish-docs.sh
.kokoro/release.sh
.kokoro/release/common.cfg
.kokoro/release/release.cfg
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.rst
LICENSE
MANIFEST.in
docs/_static/custom.css
docs/_templates/layout.html
docs/conf.py.j2
noxfile.py.j2
renovate.json
setup.cfg
Running session blacken
Creating virtual environment (virtualenv) using python3.6 in .nox/blacken
pip install black==19.3b0
Error: pip is not installed into the virtualenv, it is located at /tmpfs/src/git/autosynth/env/bin/pip. Pass external=True into run() to explicitly allow this.
Session blacken failed.
synthtool > Failed executing nox -s blacken:
None
synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 99, in <module>
main()
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 91, in main
spec.loader.exec_module(synth_module) # type: ignore
File "<frozen importlib._bootstrap_external>", line 678, in exec_module
File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
File "/tmpfs/src/git/autosynth/working_repo/synth.py", line 30, 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 39, in run
raise exc
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 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['nox', '-s', 'blacken']' returned non-zero exit status 1.
Synthesis failed
```
Google internal developers can see the full log [here](https://sponge/71791922-d263-4d09-a962-3c1472f71410).
|
1.0
|
Synthesis failed for python-storage - Hello! Autosynth couldn't regenerate python-storage. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
.coveragerc
.flake8
.github/CONTRIBUTING.md
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.gitignore
.kokoro/build.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/continuous.cfg
.kokoro/docs/common.cfg
.kokoro/docs/docs.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/presubmit.cfg
.kokoro/publish-docs.sh
.kokoro/release.sh
.kokoro/release/common.cfg
.kokoro/release/release.cfg
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.rst
LICENSE
MANIFEST.in
docs/_static/custom.css
docs/_templates/layout.html
docs/conf.py.j2
noxfile.py.j2
renovate.json
setup.cfg
Running session blacken
Creating virtual environment (virtualenv) using python3.6 in .nox/blacken
pip install black==19.3b0
Error: pip is not installed into the virtualenv, it is located at /tmpfs/src/git/autosynth/env/bin/pip. Pass external=True into run() to explicitly allow this.
Session blacken failed.
synthtool > Failed executing nox -s blacken:
None
synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 99, in <module>
main()
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 91, in main
spec.loader.exec_module(synth_module) # type: ignore
File "<frozen importlib._bootstrap_external>", line 678, in exec_module
File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
File "/tmpfs/src/git/autosynth/working_repo/synth.py", line 30, 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 39, in run
raise exc
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 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['nox', '-s', 'blacken']' returned non-zero exit status 1.
Synthesis failed
```
Google internal developers can see the full log [here](https://sponge/71791922-d263-4d09-a962-3c1472f71410).
|
process
|
synthesis failed for python storage hello autosynth couldn t regenerate python storage broken heart here s the output from running synth py cloning into working repo switched to branch autosynth running synthtool synthtool executing tmpfs src git autosynth working repo synth py coveragerc github contributing md github issue template bug report md github issue template feature request md github issue template support request md github pull request template md github release please yml gitignore kokoro build sh kokoro continuous common cfg kokoro continuous continuous cfg kokoro docs common cfg kokoro docs docs cfg kokoro presubmit common cfg kokoro presubmit presubmit cfg kokoro publish docs sh kokoro release sh kokoro release common cfg kokoro release release cfg kokoro trampoline sh code of conduct md contributing rst license manifest in docs static custom css docs templates layout html docs conf py noxfile py renovate json setup cfg running session blacken creating virtual environment virtualenv using in nox blacken pip install black error pip is not installed into the virtualenv it is located at tmpfs src git autosynth env bin pip pass external true into run to explicitly allow this session blacken failed synthtool failed executing nox s blacken none synthtool wrote metadata to synth metadata traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src git autosynth env lib site packages synthtool main py line in main file tmpfs src git autosynth env lib site packages click core py line in call return self main args kwargs file tmpfs src git autosynth env lib site packages click core py line in main rv self invoke ctx file tmpfs src git autosynth env lib site packages click core py line in invoke return ctx invoke self callback ctx params file tmpfs src git autosynth env lib site packages click core py line in invoke return callback args kwargs file tmpfs src git autosynth env lib site packages synthtool main py line in main spec loader exec module synth module type ignore file line in exec module file line in call with frames removed file tmpfs src git autosynth working repo 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 raise exc 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 output stdout stderr stderr subprocess calledprocesserror command returned non zero exit status synthesis failed google internal developers can see the full log
| 1
|
14,933
| 18,359,893,387
|
IssuesEvent
|
2021-10-09 03:13:23
|
edmobe/android-video-magnification
|
https://api.github.com/repos/edmobe/android-video-magnification
|
closed
|
OB-1002 El procesamiento de vídeo consume mucha memoria RAM
|
video-processing obstacle
|
El vídeo [`face.mp4`](http://people.csail.mit.edu/mrub/evm/video/face.mp4) disponible en la [página web del proyecto](http://people.csail.mit.edu/mrub/evm/#:~:text=%C2%A0-,Data,-All%20videos%20are) consumió más de 8GB de RAM.
|
1.0
|
OB-1002 El procesamiento de vídeo consume mucha memoria RAM - El vídeo [`face.mp4`](http://people.csail.mit.edu/mrub/evm/video/face.mp4) disponible en la [página web del proyecto](http://people.csail.mit.edu/mrub/evm/#:~:text=%C2%A0-,Data,-All%20videos%20are) consumió más de 8GB de RAM.
|
process
|
ob el procesamiento de vídeo consume mucha memoria ram el vídeo disponible en la consumió más de de ram
| 1
|
164,871
| 26,037,368,297
|
IssuesEvent
|
2022-12-22 07:01:44
|
beyondDevelops/AnimalTalk
|
https://api.github.com/repos/beyondDevelops/AnimalTalk
|
closed
|
[issue] 로그인 화면 구현
|
design markup component feat
|
## 👨💻 무엇을 하실 건지 설명해주세요!
- 로그인 화면 구현
## 🤔 구현방법 및 예상 동작
- 로그인 메인화면과 로그인을 하는 화면을 구현
## ⭐ 특이사항
- 없습니다
|
1.0
|
[issue] 로그인 화면 구현 - ## 👨💻 무엇을 하실 건지 설명해주세요!
- 로그인 화면 구현
## 🤔 구현방법 및 예상 동작
- 로그인 메인화면과 로그인을 하는 화면을 구현
## ⭐ 특이사항
- 없습니다
|
non_process
|
로그인 화면 구현 👨💻 무엇을 하실 건지 설명해주세요 로그인 화면 구현 🤔 구현방법 및 예상 동작 로그인 메인화면과 로그인을 하는 화면을 구현 ⭐ 특이사항 없습니다
| 0
|
60,493
| 3,129,971,043
|
IssuesEvent
|
2015-09-09 06:23:40
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
protein acetyltransferase activity grouping term
|
auto-migrated high priority PomBase
|
Could we have some structure under:
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0016407#term=children
I'd like a grouping term for protein acetyltransferases. This is primarily so that we can
group the protein acetyltransferases so we can have a "has_substrate/has_direct_input"
prompt for an extension for these terms in our curation tool
There is a term
id: GO:0034212
name: peptide N-acetyltransferase activity
namespace: molecular_function
def: "Catalysis of the acetylation of an amino acid residue of a peptide or protein, according to the reaction: acetyl-CoA + peptide = CoA + N-acetylpeptide." [GOC:mah]
is there any reason this can't be protein in the primary term name?
All of the protein acetyltransferases need grouping under the new parent, but some (for instance the histone lysine acetyltransferases also need to be under
id: GO:0034212
name: peptide N-acetyltransferase activity
and they are not currently.
I'm confused about some of the acetyltransferases which refer only to amino acids, are these always protein acetyltransferases, or can free amino acids be acetylated?
Reported by: ValWood
Original Ticket: [geneontology/ontology-requests/11815](https://sourceforge.net/p/geneontology/ontology-requests/11815)
|
1.0
|
protein acetyltransferase activity grouping term - Could we have some structure under:
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0016407#term=children
I'd like a grouping term for protein acetyltransferases. This is primarily so that we can
group the protein acetyltransferases so we can have a "has_substrate/has_direct_input"
prompt for an extension for these terms in our curation tool
There is a term
id: GO:0034212
name: peptide N-acetyltransferase activity
namespace: molecular_function
def: "Catalysis of the acetylation of an amino acid residue of a peptide or protein, according to the reaction: acetyl-CoA + peptide = CoA + N-acetylpeptide." [GOC:mah]
is there any reason this can't be protein in the primary term name?
All of the protein acetyltransferases need grouping under the new parent, but some (for instance the histone lysine acetyltransferases also need to be under
id: GO:0034212
name: peptide N-acetyltransferase activity
and they are not currently.
I'm confused about some of the acetyltransferases which refer only to amino acids, are these always protein acetyltransferases, or can free amino acids be acetylated?
Reported by: ValWood
Original Ticket: [geneontology/ontology-requests/11815](https://sourceforge.net/p/geneontology/ontology-requests/11815)
|
non_process
|
protein acetyltransferase activity grouping term could we have some structure under i d like a grouping term for protein acetyltransferases this is primarily so that we can group the protein acetyltransferases so we can have a has substrate has direct input prompt for an extension for these terms in our curation tool there is a term id go name peptide n acetyltransferase activity namespace molecular function def catalysis of the acetylation of an amino acid residue of a peptide or protein according to the reaction acetyl coa peptide coa n acetylpeptide is there any reason this can t be protein in the primary term name all of the protein acetyltransferases need grouping under the new parent but some for instance the histone lysine acetyltransferases also need to be under id go name peptide n acetyltransferase activity and they are not currently i m confused about some of the acetyltransferases which refer only to amino acids are these always protein acetyltransferases or can free amino acids be acetylated reported by valwood original ticket
| 0
|
12,546
| 14,975,769,048
|
IssuesEvent
|
2021-01-28 06:50:38
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
opened
|
Add automated rosetta integration tests to CI process
|
P2 enhancement process rosetta test
|
**Problem**
Rosetta module currently has unit tests that run locally and in CI
However, these do not cover E2E flows on a deployed instance
**Solution**
Add integration test coverage to CI process that runs tests against a deployed version of the Rosetta API
**Alternatives**
**Additional Context**
|
1.0
|
Add automated rosetta integration tests to CI process - **Problem**
Rosetta module currently has unit tests that run locally and in CI
However, these do not cover E2E flows on a deployed instance
**Solution**
Add integration test coverage to CI process that runs tests against a deployed version of the Rosetta API
**Alternatives**
**Additional Context**
|
process
|
add automated rosetta integration tests to ci process problem rosetta module currently has unit tests that run locally and in ci however these do not cover flows on a deployed instance solution add integration test coverage to ci process that runs tests against a deployed version of the rosetta api alternatives additional context
| 1
|
709,829
| 24,393,624,776
|
IssuesEvent
|
2022-10-04 17:13:02
|
yugabyte/yugabyte-db
|
https://api.github.com/repos/yugabyte/yugabyte-db
|
closed
|
[YSQL] CREATE DATABASE command timeouts in geo distributed/geo partitioned cluster
|
kind/bug area/ysql priority/critical jira-originated
|
Jira Link: [DB-3628](https://yugabyte.atlassian.net/browse/DB-3628)
|
1.0
|
[YSQL] CREATE DATABASE command timeouts in geo distributed/geo partitioned cluster - Jira Link: [DB-3628](https://yugabyte.atlassian.net/browse/DB-3628)
|
non_process
|
create database command timeouts in geo distributed geo partitioned cluster jira link
| 0
|
509
| 2,971,249,989
|
IssuesEvent
|
2015-07-14 04:45:19
|
aikuma/aikuma
|
https://api.github.com/repos/aikuma/aikuma
|
opened
|
Updating file properties
|
processing server
|
When a tag is added to an existing file, the properties of the file are updated (cf #455). In this case, the file exists in the central drive already, and needs its properties modified.
However, we have to check another condition: if the tag exists already and the file is added later (cf #463#issuecomment-113404101), we have to add the properties to the newly arrived file.
(NB. If a derivative file has been publicly shared before the source file is publicly shared, once the source file is shared, the derivative file cannot be accessed until the source is publicly shared.)
|
1.0
|
Updating file properties - When a tag is added to an existing file, the properties of the file are updated (cf #455). In this case, the file exists in the central drive already, and needs its properties modified.
However, we have to check another condition: if the tag exists already and the file is added later (cf #463#issuecomment-113404101), we have to add the properties to the newly arrived file.
(NB. If a derivative file has been publicly shared before the source file is publicly shared, once the source file is shared, the derivative file cannot be accessed until the source is publicly shared.)
|
process
|
updating file properties when a tag is added to an existing file the properties of the file are updated cf in this case the file exists in the central drive already and needs its properties modified however we have to check another condition if the tag exists already and the file is added later cf issuecomment we have to add the properties to the newly arrived file nb if a derivative file has been publicly shared before the source file is publicly shared once the source file is shared the derivative file cannot be accessed until the source is publicly shared
| 1
|
281,367
| 30,888,784,098
|
IssuesEvent
|
2023-08-04 01:49:27
|
nidhi7598/linux-4.1.15_CVE-2019-10220
|
https://api.github.com/repos/nidhi7598/linux-4.1.15_CVE-2019-10220
|
reopened
|
CVE-2016-4805 (High) detected in linuxlinux-4.4.302
|
Mend: dependency security vulnerability
|
## CVE-2016-4805 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</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/nidhi7598/linux-4.1.15_CVE-2019-10220/commit/6a0d304d962ca933d73f507ce02157ef2791851c">6a0d304d962ca933d73f507ce02157ef2791851c</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>/drivers/net/ppp/ppp_generic.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/ppp/ppp_generic.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unregister_channel functions.
<p>Publish Date: 2016-05-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-4805>CVE-2016-4805</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-4805">https://nvd.nist.gov/vuln/detail/CVE-2016-4805</a></p>
<p>Release Date: 2016-05-23</p>
<p>Fix Resolution: 4.5.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2016-4805 (High) detected in linuxlinux-4.4.302 - ## CVE-2016-4805 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</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/nidhi7598/linux-4.1.15_CVE-2019-10220/commit/6a0d304d962ca933d73f507ce02157ef2791851c">6a0d304d962ca933d73f507ce02157ef2791851c</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>/drivers/net/ppp/ppp_generic.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/ppp/ppp_generic.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unregister_channel functions.
<p>Publish Date: 2016-05-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-4805>CVE-2016-4805</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-4805">https://nvd.nist.gov/vuln/detail/CVE-2016-4805</a></p>
<p>Release Date: 2016-05-23</p>
<p>Fix Resolution: 4.5.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
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 drivers net ppp ppp generic c drivers net ppp ppp generic c vulnerability details use after free vulnerability in drivers net ppp ppp generic c in the linux kernel before allows local users to cause a denial of service memory corruption and system crash or spinlock or possibly have unspecified other impact by removing a network namespace related to the ppp register net channel and ppp unregister channel functions publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
16,227
| 20,763,955,915
|
IssuesEvent
|
2022-03-15 18:46:33
|
dotnet/fabricbot-config
|
https://api.github.com/repos/dotnet/fabricbot-config
|
opened
|
Determine how we want to track issues and PRs in auxiliary repositories
|
untriaged process
|
We have issues and PRs that our team members are responsible for across several other repositories where the responsibility doesn't align with area ownership and our area pods. We don't currently have a good approach for if or how to integrate those items into the area pod boards.
Example repositories:
1. roslyn-analyzers
2. sdk, arcade
3. iot
Should we create issue/pr boards for those ownerships? Should we include those issues/PRs into the team members' area pod boards? We're leaning toward having separate issue/PR boards for those auxiliary responsibilities that can be aligned to the team members/crews involved.
|
1.0
|
Determine how we want to track issues and PRs in auxiliary repositories - We have issues and PRs that our team members are responsible for across several other repositories where the responsibility doesn't align with area ownership and our area pods. We don't currently have a good approach for if or how to integrate those items into the area pod boards.
Example repositories:
1. roslyn-analyzers
2. sdk, arcade
3. iot
Should we create issue/pr boards for those ownerships? Should we include those issues/PRs into the team members' area pod boards? We're leaning toward having separate issue/PR boards for those auxiliary responsibilities that can be aligned to the team members/crews involved.
|
process
|
determine how we want to track issues and prs in auxiliary repositories we have issues and prs that our team members are responsible for across several other repositories where the responsibility doesn t align with area ownership and our area pods we don t currently have a good approach for if or how to integrate those items into the area pod boards example repositories roslyn analyzers sdk arcade iot should we create issue pr boards for those ownerships should we include those issues prs into the team members area pod boards we re leaning toward having separate issue pr boards for those auxiliary responsibilities that can be aligned to the team members crews involved
| 1
|
233,823
| 19,072,271,663
|
IssuesEvent
|
2021-11-27 05:01:44
|
istio/istio
|
https://api.github.com/repos/istio/istio
|
closed
|
Make tests runnable in parallel
|
area/test and release lifecycle/stale lifecycle/automatically-closed
|
To debug and fix flaky tests, it useful to run them many times in parallel (using `stress` usually). However, some tests break down when doing this.
This issue tracks updating all of our unit tests to support this
|
1.0
|
Make tests runnable in parallel - To debug and fix flaky tests, it useful to run them many times in parallel (using `stress` usually). However, some tests break down when doing this.
This issue tracks updating all of our unit tests to support this
|
non_process
|
make tests runnable in parallel to debug and fix flaky tests it useful to run them many times in parallel using stress usually however some tests break down when doing this this issue tracks updating all of our unit tests to support this
| 0
|
9,395
| 12,396,385,949
|
IssuesEvent
|
2020-05-20 20:26:21
|
w3c/aria-at
|
https://api.github.com/repos/w3c/aria-at
|
closed
|
More GitHub issue templates
|
process
|
Right now we have an [issue template for creating new test plans](https://github.com/w3c/aria-at/blob/master/.github/ISSUE_TEMPLATE/test-plan.md). Should we have other issue templates?
Issue templates can guide the user with what information to provide and also automatically apply the right labels.
|
1.0
|
More GitHub issue templates - Right now we have an [issue template for creating new test plans](https://github.com/w3c/aria-at/blob/master/.github/ISSUE_TEMPLATE/test-plan.md). Should we have other issue templates?
Issue templates can guide the user with what information to provide and also automatically apply the right labels.
|
process
|
more github issue templates right now we have an should we have other issue templates issue templates can guide the user with what information to provide and also automatically apply the right labels
| 1
|
7,995
| 11,187,954,512
|
IssuesEvent
|
2020-01-02 01:43:12
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Processing toolbox: r.reclass.area missing option for -d flag
|
Bug Processing
|
The processing toolbox invocation dialog is missing the ability to specify the `-d` flag ("Clump also diagonal cells?") for the GRASS algorithm `r.reclass.area`
I'm calling this a (small) bug rather than a feature request since it's an important flag that changes output, and since it is correctly included, as an "advanced parameter", in the analogous invocation dialog for `r.clump`. So I assume it has merely been forgotten here.
Thanks!
QGIS 3.10.1, OSGeo4W
|
1.0
|
Processing toolbox: r.reclass.area missing option for -d flag - The processing toolbox invocation dialog is missing the ability to specify the `-d` flag ("Clump also diagonal cells?") for the GRASS algorithm `r.reclass.area`
I'm calling this a (small) bug rather than a feature request since it's an important flag that changes output, and since it is correctly included, as an "advanced parameter", in the analogous invocation dialog for `r.clump`. So I assume it has merely been forgotten here.
Thanks!
QGIS 3.10.1, OSGeo4W
|
process
|
processing toolbox r reclass area missing option for d flag the processing toolbox invocation dialog is missing the ability to specify the d flag clump also diagonal cells for the grass algorithm r reclass area i m calling this a small bug rather than a feature request since it s an important flag that changes output and since it is correctly included as an advanced parameter in the analogous invocation dialog for r clump so i assume it has merely been forgotten here thanks qgis
| 1
|
19,750
| 26,112,521,631
|
IssuesEvent
|
2022-12-27 22:37:40
|
firebase/firebase-cpp-sdk
|
https://api.github.com/repos/firebase/firebase-cpp-sdk
|
closed
|
[C++] Nightly Integration Testing Report for Firestore
|
type: process nightly-testing
|
<hidden value="integration-test-status-comment"></hidden>
### [build against repo] Integration test with FLAKINESS (succeeded after retry)
Requested by @sunmou99 on commit 3095517de64f316fee6ad3e978163f584f91bb67
Last updated: Tue Dec 27 03:56 PST 2022
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/3786663580)**
| Failures | Configs |
|----------|---------|
| firestore | [TEST] [FLAKINESS] [Android] [1/3 os: windows] [1/4 android_device: android_target]<details><summary>(1 failed tests)</summary> CRASH/TIMEOUT</details> |
Add flaky tests to **[go/fpl-cpp-flake-tracker](http://go/fpl-cpp-flake-tracker)**
<hidden value="integration-test-status-comment"></hidden>
***
### ✅ [build against SDK] Integration test succeeded!
Requested by @firebase-workflow-trigger[bot] on commit 3095517de64f316fee6ad3e978163f584f91bb67
Last updated: Tue Dec 27 06:11 PST 2022
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/3787454076)**
|
1.0
|
[C++] Nightly Integration Testing Report for Firestore -
<hidden value="integration-test-status-comment"></hidden>
### [build against repo] Integration test with FLAKINESS (succeeded after retry)
Requested by @sunmou99 on commit 3095517de64f316fee6ad3e978163f584f91bb67
Last updated: Tue Dec 27 03:56 PST 2022
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/3786663580)**
| Failures | Configs |
|----------|---------|
| firestore | [TEST] [FLAKINESS] [Android] [1/3 os: windows] [1/4 android_device: android_target]<details><summary>(1 failed tests)</summary> CRASH/TIMEOUT</details> |
Add flaky tests to **[go/fpl-cpp-flake-tracker](http://go/fpl-cpp-flake-tracker)**
<hidden value="integration-test-status-comment"></hidden>
***
### ✅ [build against SDK] Integration test succeeded!
Requested by @firebase-workflow-trigger[bot] on commit 3095517de64f316fee6ad3e978163f584f91bb67
Last updated: Tue Dec 27 06:11 PST 2022
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/3787454076)**
|
process
|
nightly integration testing report for firestore integration test with flakiness succeeded after retry requested by on commit last updated tue dec pst failures configs firestore failed tests nbsp nbsp crash timeout add flaky tests to ✅ nbsp integration test succeeded requested by firebase workflow trigger on commit last updated tue dec pst
| 1
|
10,727
| 27,332,860,248
|
IssuesEvent
|
2023-02-25 21:13:06
|
gumyr/build123d
|
https://api.github.com/repos/gumyr/build123d
|
opened
|
Projection
|
architecture review
|
Currently the following projection methods exist in the direct_api:
1. `Vector.project_to_line(self, line: Vector) -> Vector:`
2. `Vector.project_to_plane(self, plane: Plane) -> Vector:`
3. `Mixin1D.project(self, face: Face, direction: VectorLike, closest: bool = True) -> Union[Mixin1D, list[Mixin1D]]:`
4. `Shape.project_faces(self, faces: Union[list[Face], Compound], path: Union[Wire, Edge], start: float = 0) -> Compound:`
5. `Edge.project_to_shape(self, target_object: Shape, direction: VectorLike = None, center: VectorLike = None) -> list[Edge]:`
6. `Face.project_to_shape(self, target_object: Shape, direction: VectorLike, taper: float = 0) -> ShapeList[Face]:`
7. `Wire.project_to_shape(self, target_object: Shape, direction: VectorLike = None, center: VectorLike = None) -> list[Wire]:`
This seems like too many and they aren't very consistent.
3 is limited to projecting on a Face while the ones that project onto a Shape can do this too. Here is an example of using `Face.project_to_shape` to project from one Face to another non-planar Face.
So I propose that 3 is eliminated.
4 .. 7 could potentially be collapsed to one. This new method could either be a Shape instance method where the target is self or a Shape class method where the target is a parameter. Preferences?
1 and 2 aren't really projections in the sense of the others. Should they be renamed as `intersect` methods? Something else?
|
1.0
|
Projection - Currently the following projection methods exist in the direct_api:
1. `Vector.project_to_line(self, line: Vector) -> Vector:`
2. `Vector.project_to_plane(self, plane: Plane) -> Vector:`
3. `Mixin1D.project(self, face: Face, direction: VectorLike, closest: bool = True) -> Union[Mixin1D, list[Mixin1D]]:`
4. `Shape.project_faces(self, faces: Union[list[Face], Compound], path: Union[Wire, Edge], start: float = 0) -> Compound:`
5. `Edge.project_to_shape(self, target_object: Shape, direction: VectorLike = None, center: VectorLike = None) -> list[Edge]:`
6. `Face.project_to_shape(self, target_object: Shape, direction: VectorLike, taper: float = 0) -> ShapeList[Face]:`
7. `Wire.project_to_shape(self, target_object: Shape, direction: VectorLike = None, center: VectorLike = None) -> list[Wire]:`
This seems like too many and they aren't very consistent.
3 is limited to projecting on a Face while the ones that project onto a Shape can do this too. Here is an example of using `Face.project_to_shape` to project from one Face to another non-planar Face.
So I propose that 3 is eliminated.
4 .. 7 could potentially be collapsed to one. This new method could either be a Shape instance method where the target is self or a Shape class method where the target is a parameter. Preferences?
1 and 2 aren't really projections in the sense of the others. Should they be renamed as `intersect` methods? Something else?
|
non_process
|
projection currently the following projection methods exist in the direct api vector project to line self line vector vector vector project to plane self plane plane vector project self face face direction vectorlike closest bool true union shape project faces self faces union compound path union start float compound edge project to shape self target object shape direction vectorlike none center vectorlike none list face project to shape self target object shape direction vectorlike taper float shapelist wire project to shape self target object shape direction vectorlike none center vectorlike none list this seems like too many and they aren t very consistent is limited to projecting on a face while the ones that project onto a shape can do this too here is an example of using face project to shape to project from one face to another non planar face so i propose that is eliminated could potentially be collapsed to one this new method could either be a shape instance method where the target is self or a shape class method where the target is a parameter preferences and aren t really projections in the sense of the others should they be renamed as intersect methods something else
| 0
|
21,732
| 30,245,608,712
|
IssuesEvent
|
2023-07-06 16:13:50
|
NationalSecurityAgency/ghidra
|
https://api.github.com/repos/NationalSecurityAgency/ghidra
|
closed
|
m68k andi instruction should only read memory once
|
Feature: Processor/68000 Status: Internal
|
Given code like:
```
andi.b #-0x2,(SOME_VOLATILE_MEM).l
```
this turns into the following pcode
```
VF = COPY 0:1
CF = COPY 0:1
*[ram]0xe00001:1 = INT_AND *[ram]0xe00001:1, 0xfe:1
NF = INT_SLESS *[ram]0xe00001:1, 0:1
ZF = INT_EQUAL *[ram]0xe00001:1, 0:1
```
and decompiles to:
```c
bVar1 = read_volatile_1(SOME_VOLATILE_MEM);
write_volatile_1(SOME_VOLATILE_MEM,bVar1 & 0xfe);
read_volatile(SOME_VOLATILE_MEM);
read_volatile(SOME_VOLATILE_MEM);
```
The memory read should only happen once and not for each flag being set.
|
1.0
|
m68k andi instruction should only read memory once - Given code like:
```
andi.b #-0x2,(SOME_VOLATILE_MEM).l
```
this turns into the following pcode
```
VF = COPY 0:1
CF = COPY 0:1
*[ram]0xe00001:1 = INT_AND *[ram]0xe00001:1, 0xfe:1
NF = INT_SLESS *[ram]0xe00001:1, 0:1
ZF = INT_EQUAL *[ram]0xe00001:1, 0:1
```
and decompiles to:
```c
bVar1 = read_volatile_1(SOME_VOLATILE_MEM);
write_volatile_1(SOME_VOLATILE_MEM,bVar1 & 0xfe);
read_volatile(SOME_VOLATILE_MEM);
read_volatile(SOME_VOLATILE_MEM);
```
The memory read should only happen once and not for each flag being set.
|
process
|
andi instruction should only read memory once given code like andi b some volatile mem l this turns into the following pcode vf copy cf copy int and nf int sless zf int equal and decompiles to c read volatile some volatile mem write volatile some volatile mem read volatile some volatile mem read volatile some volatile mem the memory read should only happen once and not for each flag being set
| 1
|
61,426
| 14,627,349,149
|
IssuesEvent
|
2020-12-23 12:06:29
|
shukia/ServletAlfrescoRepository
|
https://api.github.com/repos/shukia/ServletAlfrescoRepository
|
opened
|
CVE-2020-12648 (Medium) detected in multiple libraries
|
security vulnerability
|
## CVE-2020-12648 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advlink/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/example/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/save/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/insertdatetime/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/preview/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/template/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advhr/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/iespell/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/example/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/save/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/print/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/template/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/iespell/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advlink/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advhr/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/preview/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/print/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/insertdatetime/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/shukia/ServletAlfrescoRepository/commit/53019ef94e0bd9570f6d298f12cfbcfe3da234c2">53019ef94e0bd9570f6d298f12cfbcfe3da234c2</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A cross-site scripting (XSS) vulnerability in TinyMCE 5.2.1 and earlier allows remote attackers to inject arbitrary web script when configured in classic editing mode.
<p>Publish Date: 2020-08-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-12648>CVE-2020-12648</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12648">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12648</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 4.9.11,5.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-12648 (Medium) detected in multiple libraries - ## CVE-2020-12648 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b>, <b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advlink/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/example/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/save/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/insertdatetime/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/preview/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/template/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advhr/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/iespell/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/example/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/example/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/save/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/save/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/print/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/template/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/template/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/iespell/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/iespell/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advlink/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advlink/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/advhr/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/advhr/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/preview/editor_plugin.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/preview/editor_plugin.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/print/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/print/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<details><summary><b>editor_plugin_src-3.5.8.js</b></p></summary>
<p>TinyMCE rich text editor</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin_src.js">https://cdnjs.cloudflare.com/ajax/libs/tinymce/3.5.8/plugins/insertdatetime/editor_plugin_src.js</a></p>
<p>Path to vulnerable library: ServletAlfrescoRepository/src/test/resources/module/alfresco-4.2.c/scripts/tiny_mce/plugins/insertdatetime/editor_plugin_src.js</p>
<p>
Dependency Hierarchy:
- :x: **editor_plugin_src-3.5.8.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/shukia/ServletAlfrescoRepository/commit/53019ef94e0bd9570f6d298f12cfbcfe3da234c2">53019ef94e0bd9570f6d298f12cfbcfe3da234c2</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A cross-site scripting (XSS) vulnerability in TinyMCE 5.2.1 and earlier allows remote attackers to inject arbitrary web script when configured in classic editing mode.
<p>Publish Date: 2020-08-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-12648>CVE-2020-12648</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12648">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12648</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 4.9.11,5.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries editor plugin src js editor plugin src js editor plugin js editor plugin js editor plugin src js editor plugin js editor plugin src js editor plugin js editor plugin js editor plugin src js editor plugin js editor plugin src js editor plugin src js editor plugin js editor plugin js editor plugin js editor plugin src js editor plugin src js editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins advlink editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins example editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins save editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins insertdatetime editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins preview editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins template editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins advhr editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins iespell editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins example editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins save editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins print editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins template editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins iespell editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins advlink editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins advhr editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins preview editor plugin js dependency hierarchy x editor plugin js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins print editor plugin src js dependency hierarchy x editor plugin src js vulnerable library editor plugin src js tinymce rich text editor library home page a href path to vulnerable library servletalfrescorepository src test resources module alfresco c scripts tiny mce plugins insertdatetime editor plugin src js dependency hierarchy x editor plugin src js vulnerable library found in head commit a href found in base branch master vulnerability details a cross site scripting xss vulnerability in tinymce and earlier allows remote attackers to inject arbitrary web script when configured in classic editing mode publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
29,427
| 5,633,668,155
|
IssuesEvent
|
2017-04-05 19:26:54
|
emberjs/data
|
https://api.github.com/repos/emberjs/data
|
closed
|
urlForDeleteRecord doesn't appear in docs
|
Documentation
|
I would expect this method to appear in the docs here:
http://emberjs.com/api/data/classes/DS.RESTAdapter.html
It looks like maybe it's accidentally commented out in the version linked to from the docs.
https://github.com/emberjs/data/blob/v2.10.0/addon/-private/adapters/build-url-mixin.js#L363
It looks like it's fixed (not commented out) on master, - just the docs aren't updated to reflect this yet:
https://github.com/emberjs/data/blob/master/addon/-private/adapters/build-url-mixin.js#L363
|
1.0
|
urlForDeleteRecord doesn't appear in docs - I would expect this method to appear in the docs here:
http://emberjs.com/api/data/classes/DS.RESTAdapter.html
It looks like maybe it's accidentally commented out in the version linked to from the docs.
https://github.com/emberjs/data/blob/v2.10.0/addon/-private/adapters/build-url-mixin.js#L363
It looks like it's fixed (not commented out) on master, - just the docs aren't updated to reflect this yet:
https://github.com/emberjs/data/blob/master/addon/-private/adapters/build-url-mixin.js#L363
|
non_process
|
urlfordeleterecord doesn t appear in docs i would expect this method to appear in the docs here it looks like maybe it s accidentally commented out in the version linked to from the docs it looks like it s fixed not commented out on master just the docs aren t updated to reflect this yet
| 0
|
15,936
| 20,160,775,252
|
IssuesEvent
|
2022-02-09 21:16:44
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
DISABLED test_success (__main__.SpawnTest)
|
high priority triage review module: multiprocessing triaged module: flaky-tests skipped
|
This test has been flaky on CI for the past week or so: https://www.torch-ci.com/failure/test_success%2C%20SpawnTest
It fails with SIGBUS and errors sometimes
cc @ezyang @gchanan @zou3519 @VitalyFedyunin
|
1.0
|
DISABLED test_success (__main__.SpawnTest) - This test has been flaky on CI for the past week or so: https://www.torch-ci.com/failure/test_success%2C%20SpawnTest
It fails with SIGBUS and errors sometimes
cc @ezyang @gchanan @zou3519 @VitalyFedyunin
|
process
|
disabled test success main spawntest this test has been flaky on ci for the past week or so it fails with sigbus and errors sometimes cc ezyang gchanan vitalyfedyunin
| 1
|
397,925
| 27,181,649,208
|
IssuesEvent
|
2023-02-18 18:02:11
|
PalisadoesFoundation/talawa
|
https://api.github.com/repos/PalisadoesFoundation/talawa
|
closed
|
Feature request: Private Events
|
unapproved documentation feature request
|
**Is your feature request related to a problem? Please describe.**
The participants in all events are publicly visible to everyone. There needs to be options for more privacy.
**Describe the solution you'd like**
1. The ability to make events private where only participants can see who is attending
1. The optional ability to make private events invisible to persons not attending
**Describe alternatives you've considered**
N/A
**Approach to be followed (optional)**
N/A
**Additional context**
Tied to Issue https://github.com/PalisadoesFoundation/talawa-api/issues/354
|
1.0
|
Feature request: Private Events - **Is your feature request related to a problem? Please describe.**
The participants in all events are publicly visible to everyone. There needs to be options for more privacy.
**Describe the solution you'd like**
1. The ability to make events private where only participants can see who is attending
1. The optional ability to make private events invisible to persons not attending
**Describe alternatives you've considered**
N/A
**Approach to be followed (optional)**
N/A
**Additional context**
Tied to Issue https://github.com/PalisadoesFoundation/talawa-api/issues/354
|
non_process
|
feature request private events is your feature request related to a problem please describe the participants in all events are publicly visible to everyone there needs to be options for more privacy describe the solution you d like the ability to make events private where only participants can see who is attending the optional ability to make private events invisible to persons not attending describe alternatives you ve considered n a approach to be followed optional n a additional context tied to issue
| 0
|
13,920
| 16,676,623,519
|
IssuesEvent
|
2021-06-07 16:59:57
|
googleapis/google-cloud-cpp
|
https://api.github.com/repos/googleapis/google-cloud-cpp
|
closed
|
investigate using prow for cloud C++ repos
|
type: process
|
k8s has a system called [prow](https://github.com/kubernetes/test-infra/blob/master/prow/README.md) that does CI/CD, policy enforcement, and automatically merges PRs. let's investigate (not necessarily now, just noting this for future consideration) whether we should use it for our repos as well.
|
1.0
|
investigate using prow for cloud C++ repos - k8s has a system called [prow](https://github.com/kubernetes/test-infra/blob/master/prow/README.md) that does CI/CD, policy enforcement, and automatically merges PRs. let's investigate (not necessarily now, just noting this for future consideration) whether we should use it for our repos as well.
|
process
|
investigate using prow for cloud c repos has a system called that does ci cd policy enforcement and automatically merges prs let s investigate not necessarily now just noting this for future consideration whether we should use it for our repos as well
| 1
|
2,755
| 3,006,501,172
|
IssuesEvent
|
2015-07-27 10:49:55
|
Itseez/opencv
|
https://api.github.com/repos/Itseez/opencv
|
opened
|
Issues with shared library naming when using mangled paths
|
affected: master auto-transferred bug category: build/install priority: normal
|
Transferred from http://code.opencv.org/issues/3967
```
|| Gautier Minster on 2014-10-21 10:33
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: build/install
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: Any / Linux
```
Issues with shared library naming when using mangled paths
-----------
```
Hello,
When compiling OpenCV using mangled paths, using versions such as @3.0.0-dev@ or @3.0.0-alpha@, two problems arise:
1. The resulting pkg-config file (eg. @opencv-3.0.0-dev.pc@) refers to the shared libraries using the following format: <pre>libopencv_core.so.3.0.0-dev</pre>
This file does not exist however, the shared libraries are named without the "-dev": <pre>libopencv_core.so.3.0.0</pre>
This of course prevents pkg-config from working.
2. The namelinks of the shared libraries are set: on my system, with a working version of OpenCV 2.4.9, a symlink <pre>libopencv_core.so -> libopencv_core.so.2.4</pre> existed.
Upon installing OpenCV 3.0.0-dev, this symlink was replaced by <pre>libopencv_core.so -> libopencv_core.so.3.0</pre>, breaking OpenCV 2.4.9's pkg-config configuration.
Attached is a patch which:
- fixes the output name of the shared objects when using mangled paths, by adding the OPENCV_VERSION_STATUS to them
- adds the NAMELINK_SKIP flag to the CMake install of shared libraries when using mangled paths, so that already installed namelinks do not get overwritten
Do these 2 changes seem acceptable?
Kind regards,
--
Gautier
```
History
-------
##### Steven Puttemans on 2014-10-21 12:30
```
Personnally I would not change the use of the namelinks. Now it is fairly easy to build different OpenCV fixes, add a single `pkg-config opencv --libs` to your compiler settings and then just apply a `sudo make install` into the build folder you want to be running. This way you never have to adapt your OpenCV software projects to try out different installations.
```
##### Gautier Minster on 2014-10-23 06:17
```
You would not use mangled paths at all then, and simply install the specific build of OpenCV you want to use at this point? (since when using mangled paths, the pkg-config OpenCV configuration file has a mangled name too)
(note: i deleted the assignee, not sure if that was a mistake on my part or if it was auto-assigned at issue creation)
- Assignee deleted (Roman Donchenko)
```
|
1.0
|
Issues with shared library naming when using mangled paths - Transferred from http://code.opencv.org/issues/3967
```
|| Gautier Minster on 2014-10-21 10:33
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: build/install
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: Any / Linux
```
Issues with shared library naming when using mangled paths
-----------
```
Hello,
When compiling OpenCV using mangled paths, using versions such as @3.0.0-dev@ or @3.0.0-alpha@, two problems arise:
1. The resulting pkg-config file (eg. @opencv-3.0.0-dev.pc@) refers to the shared libraries using the following format: <pre>libopencv_core.so.3.0.0-dev</pre>
This file does not exist however, the shared libraries are named without the "-dev": <pre>libopencv_core.so.3.0.0</pre>
This of course prevents pkg-config from working.
2. The namelinks of the shared libraries are set: on my system, with a working version of OpenCV 2.4.9, a symlink <pre>libopencv_core.so -> libopencv_core.so.2.4</pre> existed.
Upon installing OpenCV 3.0.0-dev, this symlink was replaced by <pre>libopencv_core.so -> libopencv_core.so.3.0</pre>, breaking OpenCV 2.4.9's pkg-config configuration.
Attached is a patch which:
- fixes the output name of the shared objects when using mangled paths, by adding the OPENCV_VERSION_STATUS to them
- adds the NAMELINK_SKIP flag to the CMake install of shared libraries when using mangled paths, so that already installed namelinks do not get overwritten
Do these 2 changes seem acceptable?
Kind regards,
--
Gautier
```
History
-------
##### Steven Puttemans on 2014-10-21 12:30
```
Personnally I would not change the use of the namelinks. Now it is fairly easy to build different OpenCV fixes, add a single `pkg-config opencv --libs` to your compiler settings and then just apply a `sudo make install` into the build folder you want to be running. This way you never have to adapt your OpenCV software projects to try out different installations.
```
##### Gautier Minster on 2014-10-23 06:17
```
You would not use mangled paths at all then, and simply install the specific build of OpenCV you want to use at this point? (since when using mangled paths, the pkg-config OpenCV configuration file has a mangled name too)
(note: i deleted the assignee, not sure if that was a mistake on my part or if it was auto-assigned at issue creation)
- Assignee deleted (Roman Donchenko)
```
|
non_process
|
issues with shared library naming when using mangled paths transferred from gautier minster on priority normal affected branch master dev category build install tracker bug difficulty pr platform any linux issues with shared library naming when using mangled paths hello when compiling opencv using mangled paths using versions such as dev or alpha two problems arise the resulting pkg config file eg opencv dev pc refers to the shared libraries using the following format libopencv core so dev this file does not exist however the shared libraries are named without the dev libopencv core so this of course prevents pkg config from working the namelinks of the shared libraries are set on my system with a working version of opencv a symlink libopencv core so libopencv core so existed upon installing opencv dev this symlink was replaced by libopencv core so libopencv core so breaking opencv s pkg config configuration attached is a patch which fixes the output name of the shared objects when using mangled paths by adding the opencv version status to them adds the namelink skip flag to the cmake install of shared libraries when using mangled paths so that already installed namelinks do not get overwritten do these changes seem acceptable kind regards gautier history steven puttemans on personnally i would not change the use of the namelinks now it is fairly easy to build different opencv fixes add a single pkg config opencv libs to your compiler settings and then just apply a sudo make install into the build folder you want to be running this way you never have to adapt your opencv software projects to try out different installations gautier minster on you would not use mangled paths at all then and simply install the specific build of opencv you want to use at this point since when using mangled paths the pkg config opencv configuration file has a mangled name too note i deleted the assignee not sure if that was a mistake on my part or if it was auto assigned at issue creation assignee deleted roman donchenko
| 0
|
89,790
| 25,897,966,912
|
IssuesEvent
|
2022-12-15 01:08:42
|
google/xls
|
https://api.github.com/repos/google/xls
|
opened
|
Get a working `--incompatible_enable_cc_toolchain_resolution` build
|
build
|
We see failures in pybind11 plugin usage (i.e. in the fuzzer, which is the primary user of pybind11 plugins in the repo) due to differences in how RTTI works between GCC and LLVM in our (OSS builds) when enabling clang/LLVM with the `--incompatible_enable_cc_toolchain_resolution` flag on the bazel command line; i.e.:
`bazel test -c dbg --incompatible_enable_cc_toolchain_resolution //xls/fuzzer:sample_runner_test --test_filter=SampleRunnerTest.test_interpret_invalid_dslx --test_output=streamed`
Some of these were worked around by forcing [key methods](https://gcc.gnu.org/onlinedocs/gcc/Vague-Linkage.html) in source files for translation units in code under XLS control, but I have to imagine that's not generally viable -- we need some linkage scheme with LLVM builds that allows RTTI to be effectively common between Python plugin artifacts.
This SO question alludes to this thread on why we may be seeing a difference between GCC and LLVM build on this:
* https://stackoverflow.com/a/28827430
* https://lists.llvm.org/pipermail/llvm-dev/2014-June/073465.html
Was going to start digging into the details but wanted to document what we knew/suspected up front.
Getting this flag working will be quite nice to make more hermetic builds, and it's "nearly there".
Another option we talked about briefly was switching to a CFFI style model for Python (and other language) usage instead of pybind, but I think that would be more of an overhaul than is necessary at this point if a little linkage finagling/understanding can get the current model working. (Although having CFFI entry points would be nice from a "languages that are not Python in the future" perspective as reflected in the description in #108 ).
|
1.0
|
Get a working `--incompatible_enable_cc_toolchain_resolution` build - We see failures in pybind11 plugin usage (i.e. in the fuzzer, which is the primary user of pybind11 plugins in the repo) due to differences in how RTTI works between GCC and LLVM in our (OSS builds) when enabling clang/LLVM with the `--incompatible_enable_cc_toolchain_resolution` flag on the bazel command line; i.e.:
`bazel test -c dbg --incompatible_enable_cc_toolchain_resolution //xls/fuzzer:sample_runner_test --test_filter=SampleRunnerTest.test_interpret_invalid_dslx --test_output=streamed`
Some of these were worked around by forcing [key methods](https://gcc.gnu.org/onlinedocs/gcc/Vague-Linkage.html) in source files for translation units in code under XLS control, but I have to imagine that's not generally viable -- we need some linkage scheme with LLVM builds that allows RTTI to be effectively common between Python plugin artifacts.
This SO question alludes to this thread on why we may be seeing a difference between GCC and LLVM build on this:
* https://stackoverflow.com/a/28827430
* https://lists.llvm.org/pipermail/llvm-dev/2014-June/073465.html
Was going to start digging into the details but wanted to document what we knew/suspected up front.
Getting this flag working will be quite nice to make more hermetic builds, and it's "nearly there".
Another option we talked about briefly was switching to a CFFI style model for Python (and other language) usage instead of pybind, but I think that would be more of an overhaul than is necessary at this point if a little linkage finagling/understanding can get the current model working. (Although having CFFI entry points would be nice from a "languages that are not Python in the future" perspective as reflected in the description in #108 ).
|
non_process
|
get a working incompatible enable cc toolchain resolution build we see failures in plugin usage i e in the fuzzer which is the primary user of plugins in the repo due to differences in how rtti works between gcc and llvm in our oss builds when enabling clang llvm with the incompatible enable cc toolchain resolution flag on the bazel command line i e bazel test c dbg incompatible enable cc toolchain resolution xls fuzzer sample runner test test filter samplerunnertest test interpret invalid dslx test output streamed some of these were worked around by forcing in source files for translation units in code under xls control but i have to imagine that s not generally viable we need some linkage scheme with llvm builds that allows rtti to be effectively common between python plugin artifacts this so question alludes to this thread on why we may be seeing a difference between gcc and llvm build on this was going to start digging into the details but wanted to document what we knew suspected up front getting this flag working will be quite nice to make more hermetic builds and it s nearly there another option we talked about briefly was switching to a cffi style model for python and other language usage instead of pybind but i think that would be more of an overhaul than is necessary at this point if a little linkage finagling understanding can get the current model working although having cffi entry points would be nice from a languages that are not python in the future perspective as reflected in the description in
| 0
|
21,059
| 28,006,801,937
|
IssuesEvent
|
2023-03-27 15:44:54
|
data-liberation-project/epa-rmp-coordination
|
https://api.github.com/repos/data-liberation-project/epa-rmp-coordination
|
closed
|
Create first set of novice-friendly spreadsheets
|
data processing
|
From the [documentation draft](https://docs.google.com/document/d/1jrLXtv0knnACiPXJ1ZRFXR1GaPWCHJWWjin4rsthFbQ/edit), here are some spreadsheet typologies to aim for:
- [ ] One row per facility (providing its name, owners, date of latest RMP submission, chemicals reported in latest RMP, number of accidents reported in latest RMP, total impacts of those accidents), sorted by state, county, and name; submissions by state.
- [ ] One row per RMP (rather than one row per facility), with similar info as above.
- [ ] One row per facility-chemical (facility ID, name, state, chemical name, chemical quantity, program level).
- [ ] One row per accident reported.
- [ ] One row per data element withheld as Confidential Business Information.
Ideally, these would be defined as SQL queries, so that they could work both for spreadsheet generation *and* for [the Datasette instance](https://github.com/data-liberation-project/epa-rmp-datasette/). But if anyone would like to start cranking on this in Python/R/etc., that seems totally fine/reasonable for generating useful prototypes.
|
1.0
|
Create first set of novice-friendly spreadsheets - From the [documentation draft](https://docs.google.com/document/d/1jrLXtv0knnACiPXJ1ZRFXR1GaPWCHJWWjin4rsthFbQ/edit), here are some spreadsheet typologies to aim for:
- [ ] One row per facility (providing its name, owners, date of latest RMP submission, chemicals reported in latest RMP, number of accidents reported in latest RMP, total impacts of those accidents), sorted by state, county, and name; submissions by state.
- [ ] One row per RMP (rather than one row per facility), with similar info as above.
- [ ] One row per facility-chemical (facility ID, name, state, chemical name, chemical quantity, program level).
- [ ] One row per accident reported.
- [ ] One row per data element withheld as Confidential Business Information.
Ideally, these would be defined as SQL queries, so that they could work both for spreadsheet generation *and* for [the Datasette instance](https://github.com/data-liberation-project/epa-rmp-datasette/). But if anyone would like to start cranking on this in Python/R/etc., that seems totally fine/reasonable for generating useful prototypes.
|
process
|
create first set of novice friendly spreadsheets from the here are some spreadsheet typologies to aim for one row per facility providing its name owners date of latest rmp submission chemicals reported in latest rmp number of accidents reported in latest rmp total impacts of those accidents sorted by state county and name submissions by state one row per rmp rather than one row per facility with similar info as above one row per facility chemical facility id name state chemical name chemical quantity program level one row per accident reported one row per data element withheld as confidential business information ideally these would be defined as sql queries so that they could work both for spreadsheet generation and for but if anyone would like to start cranking on this in python r etc that seems totally fine reasonable for generating useful prototypes
| 1
|
76,679
| 3,490,861,821
|
IssuesEvent
|
2016-01-04 12:45:15
|
gama-platform/gama
|
https://api.github.com/repos/gama-platform/gama
|
opened
|
Enhancement: provide a way for developers to store and retrieve internal data
|
> Enhancement Affects Datafiles Concerns Development Concerns Persistence OS All Priority Low Version Git
|
While digging around trying to address Issue #1359 (which is on its way), I discovered that it is relatively easy and safe to store and retrieve data in the file system, within projects, using some of the facilities provided by the code generator included in XText.
This could be ported to the GAMA runtime, for example for storing and retrieving data intended to be persistent across simulations like shortest paths in graphs or results of database requests.
The idea would be to:
- [ ] create an invisible folder in projects called `.runtimedata` to which each model would have a limited access (the hierarchy of folders within the project could be recreated and each model have access to a folder named after its name, for instance).
- [ ] provide IScope with simple methods for storing and retrieving data: storeText(fileName, contents), storeBinary(fileName, outputStream), retrieveText(fileName), retrieveBinary(fileName), delete(fileName), exists(fileName)
Such an enhancement would advantageously replace the use of temporary directories and also ease the usage of disk caches in plugins.
Feel free to comment !
|
1.0
|
Enhancement: provide a way for developers to store and retrieve internal data - While digging around trying to address Issue #1359 (which is on its way), I discovered that it is relatively easy and safe to store and retrieve data in the file system, within projects, using some of the facilities provided by the code generator included in XText.
This could be ported to the GAMA runtime, for example for storing and retrieving data intended to be persistent across simulations like shortest paths in graphs or results of database requests.
The idea would be to:
- [ ] create an invisible folder in projects called `.runtimedata` to which each model would have a limited access (the hierarchy of folders within the project could be recreated and each model have access to a folder named after its name, for instance).
- [ ] provide IScope with simple methods for storing and retrieving data: storeText(fileName, contents), storeBinary(fileName, outputStream), retrieveText(fileName), retrieveBinary(fileName), delete(fileName), exists(fileName)
Such an enhancement would advantageously replace the use of temporary directories and also ease the usage of disk caches in plugins.
Feel free to comment !
|
non_process
|
enhancement provide a way for developers to store and retrieve internal data while digging around trying to address issue which is on its way i discovered that it is relatively easy and safe to store and retrieve data in the file system within projects using some of the facilities provided by the code generator included in xtext this could be ported to the gama runtime for example for storing and retrieving data intended to be persistent across simulations like shortest paths in graphs or results of database requests the idea would be to create an invisible folder in projects called runtimedata to which each model would have a limited access the hierarchy of folders within the project could be recreated and each model have access to a folder named after its name for instance provide iscope with simple methods for storing and retrieving data storetext filename contents storebinary filename outputstream retrievetext filename retrievebinary filename delete filename exists filename such an enhancement would advantageously replace the use of temporary directories and also ease the usage of disk caches in plugins feel free to comment
| 0
|
387,206
| 11,457,978,618
|
IssuesEvent
|
2020-02-07 01:37:55
|
wevote/WebApp
|
https://api.github.com/repos/wevote/WebApp
|
opened
|
Complete Your Profile (Step by Step)
|
Priority: 1
|
We are going to start with 8 items we are asking a voter to complete, like this for example (DESKTOP):
<img width="656" alt="desktop-one_example" src="https://user-images.githubusercontent.com/7756031/73993128-281f6900-4906-11ea-96fc-248f4af56eb8.png">
MOBILE:
<img width="407" alt="mobile-one_example" src="https://user-images.githubusercontent.com/7756031/73993150-37061b80-4906-11ea-81b5-f27ef9f71f5a.png">
Please start with one order, slides 1-8. For example:
1. Follow at least one value
2. Follow one organization or public figure
3. Our best guess for your location...
<img width="657" alt="desktop-three_examples" src="https://user-images.githubusercontent.com/7756031/73993247-7fbdd480-4906-11ea-814c-bd273ca2ddde.png">
As each item is completed, please move it in the left-to-right next and back order, to the far left of the slide order (so you can navigate back to slides you have completed by clicking the "Previous" arrow). So for example if you finish "Our best guess for your location..." first, the new order would be:
1. Our best guess for your location... (COMPLETED)
2. Follow at least one value
3. Follow one organization or public figure
For each completed step, show 1 “bar” across the top as a dark line, with all dark lines on the left.
When you first load the component, start by showing the next “to be completed” slide (light gray line) as the initial slide you show. (In the example order above, you would start on slide 2 ("Follow at least one value") when you returned to this component.
Dale will connect this component with the API server.
|
1.0
|
Complete Your Profile (Step by Step) - We are going to start with 8 items we are asking a voter to complete, like this for example (DESKTOP):
<img width="656" alt="desktop-one_example" src="https://user-images.githubusercontent.com/7756031/73993128-281f6900-4906-11ea-96fc-248f4af56eb8.png">
MOBILE:
<img width="407" alt="mobile-one_example" src="https://user-images.githubusercontent.com/7756031/73993150-37061b80-4906-11ea-81b5-f27ef9f71f5a.png">
Please start with one order, slides 1-8. For example:
1. Follow at least one value
2. Follow one organization or public figure
3. Our best guess for your location...
<img width="657" alt="desktop-three_examples" src="https://user-images.githubusercontent.com/7756031/73993247-7fbdd480-4906-11ea-814c-bd273ca2ddde.png">
As each item is completed, please move it in the left-to-right next and back order, to the far left of the slide order (so you can navigate back to slides you have completed by clicking the "Previous" arrow). So for example if you finish "Our best guess for your location..." first, the new order would be:
1. Our best guess for your location... (COMPLETED)
2. Follow at least one value
3. Follow one organization or public figure
For each completed step, show 1 “bar” across the top as a dark line, with all dark lines on the left.
When you first load the component, start by showing the next “to be completed” slide (light gray line) as the initial slide you show. (In the example order above, you would start on slide 2 ("Follow at least one value") when you returned to this component.
Dale will connect this component with the API server.
|
non_process
|
complete your profile step by step we are going to start with items we are asking a voter to complete like this for example desktop img width alt desktop one example src mobile img width alt mobile one example src please start with one order slides for example follow at least one value follow one organization or public figure our best guess for your location img width alt desktop three examples src as each item is completed please move it in the left to right next and back order to the far left of the slide order so you can navigate back to slides you have completed by clicking the previous arrow so for example if you finish our best guess for your location first the new order would be our best guess for your location completed follow at least one value follow one organization or public figure for each completed step show “bar” across the top as a dark line with all dark lines on the left when you first load the component start by showing the next “to be completed” slide light gray line as the initial slide you show in the example order above you would start on slide follow at least one value when you returned to this component dale will connect this component with the api server
| 0
|
828,436
| 31,828,733,079
|
IssuesEvent
|
2023-09-14 09:12:47
|
Deltares/tcBuildViewer
|
https://api.github.com/repos/Deltares/tcBuildViewer
|
closed
|
Treat 'default' (main/master/trunk/...) branch the same as no branch
|
bug enhancement priority needs refinement
|
TeamCity has a build:(defaultBranch) value that can be used for this.
|
1.0
|
Treat 'default' (main/master/trunk/...) branch the same as no branch - TeamCity has a build:(defaultBranch) value that can be used for this.
|
non_process
|
treat default main master trunk branch the same as no branch teamcity has a build defaultbranch value that can be used for this
| 0
|
942
| 3,409,392,704
|
IssuesEvent
|
2015-12-04 15:35:14
|
pwittchen/prefser
|
https://api.github.com/repos/pwittchen/prefser
|
closed
|
Release 2.0.3
|
release process
|
**Initial release notes**:
- added `@NonNull` Android support annotations
- updated Gson dependency to the newest version
- updated Target Android SDK version to 23
- removed Dagger 1 sample app, because it was outdated and too trivial
**Things to do**:
- [x] bump library version :arrow_right: PR #79
- [x] upload archives to Maven Central
- [x] close and release artifact on Maven Central
- [x] update `CHANGELOG.md` after Maven Sync
- [x] bump library version in `README.md`
- [x] create new GitHub release
|
1.0
|
Release 2.0.3 - **Initial release notes**:
- added `@NonNull` Android support annotations
- updated Gson dependency to the newest version
- updated Target Android SDK version to 23
- removed Dagger 1 sample app, because it was outdated and too trivial
**Things to do**:
- [x] bump library version :arrow_right: PR #79
- [x] upload archives to Maven Central
- [x] close and release artifact on Maven Central
- [x] update `CHANGELOG.md` after Maven Sync
- [x] bump library version in `README.md`
- [x] create new GitHub release
|
process
|
release initial release notes added nonnull android support annotations updated gson dependency to the newest version updated target android sdk version to removed dagger sample app because it was outdated and too trivial things to do bump library version arrow right pr upload archives to maven central close and release artifact on maven central update changelog md after maven sync bump library version in readme md create new github release
| 1
|
517,631
| 15,017,251,121
|
IssuesEvent
|
2021-02-01 10:36:28
|
threefoldfoundation/www_threefold_farming
|
https://api.github.com/repos/threefoldfoundation/www_threefold_farming
|
opened
|
Fix simple header on mobile
|
priority_major
|
On mobile view for some pages simple header works well on some pages it's off.
Can you please check and fix?
Tech and Token page is off for me:
p.s. same issue on threefold.tech website (see issue #52)
|
1.0
|
Fix simple header on mobile - On mobile view for some pages simple header works well on some pages it's off.
Can you please check and fix?
Tech and Token page is off for me:
p.s. same issue on threefold.tech website (see issue #52)
|
non_process
|
fix simple header on mobile on mobile view for some pages simple header works well on some pages it s off can you please check and fix tech and token page is off for me p s same issue on threefold tech website see issue
| 0
|
188,725
| 22,046,882,387
|
IssuesEvent
|
2022-05-30 03:29:00
|
panasalap/linux-4.1.15
|
https://api.github.com/repos/panasalap/linux-4.1.15
|
closed
|
CVE-2017-18202 (High) detected in linux-yocto-devv4.2.8 - autoclosed
|
security vulnerability
|
## CVE-2017-18202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-devv4.2.8</b></p></summary>
<p>
<p>Linux Embedded Kernel - tracks the next mainline release</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-dev>https://git.yoctoproject.org/git/linux-yocto-dev</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/mm/oom_kill.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/mm/oom_kill.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The __oom_reap_task_mm function in mm/oom_kill.c in the Linux kernel before 4.14.4 mishandles gather operations, which allows attackers to cause a denial of service (TLB entry leak or use-after-free) or possibly have unspecified other impact by triggering a copy_to_user call within a certain time window.
<p>Publish Date: 2018-02-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18202>CVE-2017-18202</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-18202">https://nvd.nist.gov/vuln/detail/CVE-2017-18202</a></p>
<p>Release Date: 2018-02-27</p>
<p>Fix Resolution: 4.14.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2017-18202 (High) detected in linux-yocto-devv4.2.8 - autoclosed - ## CVE-2017-18202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-devv4.2.8</b></p></summary>
<p>
<p>Linux Embedded Kernel - tracks the next mainline release</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-dev>https://git.yoctoproject.org/git/linux-yocto-dev</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/mm/oom_kill.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/mm/oom_kill.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The __oom_reap_task_mm function in mm/oom_kill.c in the Linux kernel before 4.14.4 mishandles gather operations, which allows attackers to cause a denial of service (TLB entry leak or use-after-free) or possibly have unspecified other impact by triggering a copy_to_user call within a certain time window.
<p>Publish Date: 2018-02-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18202>CVE-2017-18202</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-18202">https://nvd.nist.gov/vuln/detail/CVE-2017-18202</a></p>
<p>Release Date: 2018-02-27</p>
<p>Fix Resolution: 4.14.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in linux yocto autoclosed cve high severity vulnerability vulnerable library linux yocto linux embedded kernel tracks the next mainline release library home page a href found in head commit a href found in base branch master vulnerable source files mm oom kill c mm oom kill c vulnerability details the oom reap task mm function in mm oom kill c in the linux kernel before mishandles gather operations which allows attackers to cause a denial of service tlb entry leak or use after free or possibly have unspecified other impact by triggering a copy to user call within a certain time window publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
123
| 2,559,623,127
|
IssuesEvent
|
2015-02-05 02:44:51
|
queirozfcom/rachinations
|
https://api.github.com/repos/queirozfcom/rachinations
|
closed
|
Add a quick intro and lots of examples with DSL v1 to README.mkd
|
docs easy pick process Severity: HIGH
|
Make sure the examples have all needed instructions, e.g.: "save this into a file with extension `.rb` and then run it using `ruby ...`" if you don't have ruby installed, follow these instructions to install ruby for a)windows, b)linux etc etc.
|
1.0
|
Add a quick intro and lots of examples with DSL v1 to README.mkd - Make sure the examples have all needed instructions, e.g.: "save this into a file with extension `.rb` and then run it using `ruby ...`" if you don't have ruby installed, follow these instructions to install ruby for a)windows, b)linux etc etc.
|
process
|
add a quick intro and lots of examples with dsl to readme mkd make sure the examples have all needed instructions e g save this into a file with extension rb and then run it using ruby if you don t have ruby installed follow these instructions to install ruby for a windows b linux etc etc
| 1
|
10,795
| 13,609,184,750
|
IssuesEvent
|
2020-09-23 04:31:56
|
googleapis/java-grafeas
|
https://api.github.com/repos/googleapis/java-grafeas
|
closed
|
Dependency Dashboard
|
type: process
|
This issue contains a list of Renovate updates and their statuses.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/org.apache.maven.plugins-maven-project-info-reports-plugin-3.x -->build(deps): update dependency org.apache.maven.plugins:maven-project-info-reports-plugin to v3.1.1
- [ ] <!-- rebase-branch=renovate/com.puppycrawl.tools-checkstyle-8.x -->deps: update dependency com.puppycrawl.tools:checkstyle to v8.36.1
---
- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository
|
1.0
|
Dependency Dashboard - This issue contains a list of Renovate updates and their statuses.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/org.apache.maven.plugins-maven-project-info-reports-plugin-3.x -->build(deps): update dependency org.apache.maven.plugins:maven-project-info-reports-plugin to v3.1.1
- [ ] <!-- rebase-branch=renovate/com.puppycrawl.tools-checkstyle-8.x -->deps: update dependency com.puppycrawl.tools:checkstyle to v8.36.1
---
- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository
|
process
|
dependency dashboard this issue contains a list of renovate updates and their statuses open these updates have all been created already click a checkbox below to force a retry rebase of any build deps update dependency org apache maven plugins maven project info reports plugin to deps update dependency com puppycrawl tools checkstyle to check this box to trigger a request for renovate to run again on this repository
| 1
|
329,610
| 28,292,191,096
|
IssuesEvent
|
2023-04-09 10:56:08
|
Uuvana-Studios/longvinter-windows-client
|
https://api.github.com/repos/Uuvana-Studios/longvinter-windows-client
|
opened
|
a transparent bug
|
Bug Not Tested
|
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Keep the boat as close as possible to the door of the house
2. Move to seat 2 by boat (ctrl + 2)
3. Click on the house with the mouse to enter and exit (If you are sitting when you come out, you are successful. Click on the space bar to move to the boat)
4. If you look around Sirora or anywhere, it will be transparent
(Flying to a strange place when you're on a boat)
Personally, if you go around Shirora, it's the most transparent
This kind of writing is spreading Please check.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. Windows]
- Game Version [e.g. 1.0]
- Steam Version [e.g. 1.0]
**Additional context**
Add any other context about the problem here.
|
1.0
|
a transparent bug - **Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Keep the boat as close as possible to the door of the house
2. Move to seat 2 by boat (ctrl + 2)
3. Click on the house with the mouse to enter and exit (If you are sitting when you come out, you are successful. Click on the space bar to move to the boat)
4. If you look around Sirora or anywhere, it will be transparent
(Flying to a strange place when you're on a boat)
Personally, if you go around Shirora, it's the most transparent
This kind of writing is spreading Please check.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. Windows]
- Game Version [e.g. 1.0]
- Steam Version [e.g. 1.0]
**Additional context**
Add any other context about the problem here.
|
non_process
|
a transparent bug describe the bug a clear and concise description of what the bug is to reproduce steps to reproduce the behavior keep the boat as close as possible to the door of the house move to seat by boat ctrl click on the house with the mouse to enter and exit if you are sitting when you come out you are successful click on the space bar to move to the boat if you look around sirora or anywhere it will be transparent flying to a strange place when you re on a boat personally if you go around shirora it s the most transparent this kind of writing is spreading please check expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem desktop please complete the following information os game version steam version additional context add any other context about the problem here
| 0
|
3,728
| 3,226,996,996
|
IssuesEvent
|
2015-10-10 19:53:55
|
sstephenson/rbenv
|
https://api.github.com/repos/sstephenson/rbenv
|
closed
|
Error executing action `install` on resource 'rbenv_gem 2.1.5::
|
ruby-build uncofirmed
|
I am trying to install with chef. I get this error while running : Vagrant provison
```
Error executing action `install` on resource 'rbenv_gem[2.1.5::bundler (vagrant)] (vagrant)'
```
FULL log : https://gist.github.com/AlouaneMed/9212a27a9c40ccaabe1c
my cheffile:
```rb
cookbook 'apt'
cookbook 'build-essential'
cookbook 'postgresql'
cookbook 'database', '~> 2.3.0'
cookbook 'ruby_build'
cookbook 'nodejs', git: 'https://github.com/mdxp/nodejs-cookbook'
cookbook 'rbenv', :git => 'git://github.com/fnichol/chef-rbenv', :ref => 'v0.7.2'
cookbook 'vim'
```
Vagrantfile:
```rb
chef.json = {
rbenv: {
user_installs: [{
user: 'vagrant',
rubies: ["2.1.3"],
global: "2.1.3",
gems: {
"2.1.3" => [
{ name: "bundler" }
]
}
}]
},
:postgresql => {
:version => "9.3",
:listen_address => "*",
:password => {
:postgres => ""
}
},
}
end
end
```
|
1.0
|
Error executing action `install` on resource 'rbenv_gem 2.1.5:: - I am trying to install with chef. I get this error while running : Vagrant provison
```
Error executing action `install` on resource 'rbenv_gem[2.1.5::bundler (vagrant)] (vagrant)'
```
FULL log : https://gist.github.com/AlouaneMed/9212a27a9c40ccaabe1c
my cheffile:
```rb
cookbook 'apt'
cookbook 'build-essential'
cookbook 'postgresql'
cookbook 'database', '~> 2.3.0'
cookbook 'ruby_build'
cookbook 'nodejs', git: 'https://github.com/mdxp/nodejs-cookbook'
cookbook 'rbenv', :git => 'git://github.com/fnichol/chef-rbenv', :ref => 'v0.7.2'
cookbook 'vim'
```
Vagrantfile:
```rb
chef.json = {
rbenv: {
user_installs: [{
user: 'vagrant',
rubies: ["2.1.3"],
global: "2.1.3",
gems: {
"2.1.3" => [
{ name: "bundler" }
]
}
}]
},
:postgresql => {
:version => "9.3",
:listen_address => "*",
:password => {
:postgres => ""
}
},
}
end
end
```
|
non_process
|
error executing action install on resource rbenv gem i am trying to install with chef i get this error while running vagrant provison error executing action install on resource rbenv gem vagrant full log my cheffile rb cookbook apt cookbook build essential cookbook postgresql cookbook database cookbook ruby build cookbook nodejs git cookbook rbenv git git github com fnichol chef rbenv ref cookbook vim vagrantfile rb chef json rbenv user installs user vagrant rubies global gems name bundler postgresql version listen address password postgres end end
| 0
|
20,728
| 27,428,447,177
|
IssuesEvent
|
2023-03-01 22:24:58
|
RobertCraigie/prisma-client-py
|
https://api.github.com/repos/RobertCraigie/prisma-client-py
|
closed
|
Support default values for enum arrays
|
bug/1-repro-available kind/bug process/candidate priority/high topic: crash
|
<!--
Thanks for helping us improve Prisma Client Python! 🙏 Please follow the sections in the template and provide as much information as possible about your problem, e.g. by enabling additional logging output.
See https://prisma-client-py.readthedocs.io/en/stable/reference/logging/ for how to enable additional logging output.
-->
## Bug description
<!-- A clear and concise description of what the bug is. -->
Currently setting a default value for an `enum[]` field will cause the client to crash.
## How to reproduce
<!--
Steps to reproduce the behavior:
1. Go to '...'
2. Change '....'
3. Run '....'
4. See error
-->
https://discord.com/channels/933860922039099444/1080592482850586675/1080592482850586675
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
No crash
|
1.0
|
Support default values for enum arrays - <!--
Thanks for helping us improve Prisma Client Python! 🙏 Please follow the sections in the template and provide as much information as possible about your problem, e.g. by enabling additional logging output.
See https://prisma-client-py.readthedocs.io/en/stable/reference/logging/ for how to enable additional logging output.
-->
## Bug description
<!-- A clear and concise description of what the bug is. -->
Currently setting a default value for an `enum[]` field will cause the client to crash.
## How to reproduce
<!--
Steps to reproduce the behavior:
1. Go to '...'
2. Change '....'
3. Run '....'
4. See error
-->
https://discord.com/channels/933860922039099444/1080592482850586675/1080592482850586675
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
No crash
|
process
|
support default values for enum arrays thanks for helping us improve prisma client python 🙏 please follow the sections in the template and provide as much information as possible about your problem e g by enabling additional logging output see for how to enable additional logging output bug description currently setting a default value for an enum field will cause the client to crash how to reproduce steps to reproduce the behavior go to change run see error expected behavior no crash
| 1
|
316,937
| 9,658,902,233
|
IssuesEvent
|
2019-05-20 12:14:00
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
accounts.google.com - see bug description
|
browser-fenix engine-gecko priority-critical
|
<!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 5.1; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://accounts.google.com/signin/v2/sl/pwd?service=googleplay
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 5.1
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Can't touch "Next".
**Steps to Reproduce**:
I just typed my password and touched "Next" but nothing happened!
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
accounts.google.com - see bug description - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 5.1; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://accounts.google.com/signin/v2/sl/pwd?service=googleplay
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 5.1
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Can't touch "Next".
**Steps to Reproduce**:
I just typed my password and touched "Next" but nothing happened!
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_process
|
accounts google com see bug description url browser version firefox mobile operating system android tested another browser yes problem type something else description can t touch next steps to reproduce i just typed my password and touched next but nothing happened browser configuration none from with ❤️
| 0
|
8,611
| 11,768,437,106
|
IssuesEvent
|
2020-03-15 10:20:29
|
tueit/it_management
|
https://api.github.com/repos/tueit/it_management
|
closed
|
Customization Project in Sales Invoice
|
core enhancement process
|
When creating a Sales Invoice with a linked Project it will pull all open Time Sheets linked to the Project. When removing the Time Sheets from the List and hitting save it will re-pull all the Time Sheets. This makes it impossible to Invoice e.g. Hardware on an open project.
I think this should also go into core...
|
1.0
|
Customization Project in Sales Invoice - When creating a Sales Invoice with a linked Project it will pull all open Time Sheets linked to the Project. When removing the Time Sheets from the List and hitting save it will re-pull all the Time Sheets. This makes it impossible to Invoice e.g. Hardware on an open project.
I think this should also go into core...
|
process
|
customization project in sales invoice when creating a sales invoice with a linked project it will pull all open time sheets linked to the project when removing the time sheets from the list and hitting save it will re pull all the time sheets this makes it impossible to invoice e g hardware on an open project i think this should also go into core
| 1
|
9,540
| 12,507,537,284
|
IssuesEvent
|
2020-06-02 14:16:18
|
qgis/QGIS-Documentation
|
https://api.github.com/repos/qgis/QGIS-Documentation
|
closed
|
Request in QGIS ([feature][processing] Add Line density algorithm)
|
3.12 Processing Alg
|
### Request for documentation
From pull request QGIS/qgis#33525
Author: @root676
QGIS version:
**[feature][processing] Add Line density algorithm**
### PR Description:
## Description
This PR proposes a _Line density algorithm_ as it is implemented in [ESRI ArcGIS Spatial Analyst](https://desktop.arcgis.com/en/arcmap/latest/tools/spatial-analyst-toolbox/how-line-density-works.htm). The algorithm basically moves a circular search geometry from cell to cell and calculates the line density measure as proposed by Silverman (1986). The measure is a weighted sum of intersecting line lengths that are intersecting with the search geometry, which is then divided by the search geometry area. The figure below gives a rough example of the algorithms functionality.
The algorithm output for the road network of Vienna ([Data Source: Stadt Wien - data.wien.gv.at](https://www.data.gv.at/katalog/dataset/1039ed7e-97fb-435f-b6cc-f6a105ba5e09)) with randomly distributed weights between 1 and 3 looks like this:
Please feel free to review/comment/suggest improvements!
Literature:
- Silverman, B. W. Density Estimation for Statistics and Data Analysis. New York: Chapman and Hall, 1986.
## Checklist
<!-- Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.
-->
- [x] Commit messages are descriptive and explain the rationale for changes
- [x] Commits which fix bugs include `Fixes #11111` at the bottom of the commit message
- [x] I have read the [QGIS Coding Standards](https://docs.qgis.org/testing/en/docs/developers_guide/codingstandards.html) and this PR complies with them
- [x] New unit tests have been added for core changes
- [x] I have run [the `scripts/prepare-commit.sh` script](https://github.com/qgis/QGIS/blob/master/.github/CONTRIBUTING.md#contributing-to-qgis) before each commit
- [x] I have evaluated whether it is appropriate for this PR to be backported, backport requests are left as label or comment
### Commits tagged with [need-docs]
"[feature][processing] Add Line denisty algorithm"
|
1.0
|
Request in QGIS ([feature][processing] Add Line density algorithm) - ### Request for documentation
From pull request QGIS/qgis#33525
Author: @root676
QGIS version:
**[feature][processing] Add Line density algorithm**
### PR Description:
## Description
This PR proposes a _Line density algorithm_ as it is implemented in [ESRI ArcGIS Spatial Analyst](https://desktop.arcgis.com/en/arcmap/latest/tools/spatial-analyst-toolbox/how-line-density-works.htm). The algorithm basically moves a circular search geometry from cell to cell and calculates the line density measure as proposed by Silverman (1986). The measure is a weighted sum of intersecting line lengths that are intersecting with the search geometry, which is then divided by the search geometry area. The figure below gives a rough example of the algorithms functionality.
The algorithm output for the road network of Vienna ([Data Source: Stadt Wien - data.wien.gv.at](https://www.data.gv.at/katalog/dataset/1039ed7e-97fb-435f-b6cc-f6a105ba5e09)) with randomly distributed weights between 1 and 3 looks like this:
Please feel free to review/comment/suggest improvements!
Literature:
- Silverman, B. W. Density Estimation for Statistics and Data Analysis. New York: Chapman and Hall, 1986.
## Checklist
<!-- Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.
-->
- [x] Commit messages are descriptive and explain the rationale for changes
- [x] Commits which fix bugs include `Fixes #11111` at the bottom of the commit message
- [x] I have read the [QGIS Coding Standards](https://docs.qgis.org/testing/en/docs/developers_guide/codingstandards.html) and this PR complies with them
- [x] New unit tests have been added for core changes
- [x] I have run [the `scripts/prepare-commit.sh` script](https://github.com/qgis/QGIS/blob/master/.github/CONTRIBUTING.md#contributing-to-qgis) before each commit
- [x] I have evaluated whether it is appropriate for this PR to be backported, backport requests are left as label or comment
### Commits tagged with [need-docs]
"[feature][processing] Add Line denisty algorithm"
|
process
|
request in qgis add line density algorithm request for documentation from pull request qgis qgis author qgis version add line density algorithm pr description description this pr proposes a line density algorithm as it is implemented in the algorithm basically moves a circular search geometry from cell to cell and calculates the line density measure as proposed by silverman the measure is a weighted sum of intersecting line lengths that are intersecting with the search geometry which is then divided by the search geometry area the figure below gives a rough example of the algorithms functionality the algorithm output for the road network of vienna with randomly distributed weights between and looks like this please feel free to review comment suggest improvements literature silverman b w density estimation for statistics and data analysis new york chapman and hall checklist reviewing is a process done by project maintainers mostly on a volunteer basis we try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items feel free to ask in a comment if you have troubles with any of them commit messages are descriptive and explain the rationale for changes commits which fix bugs include fixes at the bottom of the commit message i have read the and this pr complies with them new unit tests have been added for core changes i have run before each commit i have evaluated whether it is appropriate for this pr to be backported backport requests are left as label or comment commits tagged with add line denisty algorithm
| 1
|
1,894
| 4,724,801,632
|
IssuesEvent
|
2016-10-18 02:31:55
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
test-child-process-fork-dgram Intermittent timeout on AIX
|
child_process dgram test
|
* **Version**: master
* **Platform**: AIX
* **Subsystem**: process
Noticed this failure in a recent AIX run when investigating intermittent addon issue:
https://ci.nodejs.org/job/node-test-commit-aix/472/->
test-child-process-fork-dgram failed with a timeout
```
not ok 55 parallel/test-child-process-fork-dgram
# TIMEOUT
```
Likely a pre-existing intermittent failure as nothing in the PR looks related to the failure.
|
1.0
|
test-child-process-fork-dgram Intermittent timeout on AIX - * **Version**: master
* **Platform**: AIX
* **Subsystem**: process
Noticed this failure in a recent AIX run when investigating intermittent addon issue:
https://ci.nodejs.org/job/node-test-commit-aix/472/->
test-child-process-fork-dgram failed with a timeout
```
not ok 55 parallel/test-child-process-fork-dgram
# TIMEOUT
```
Likely a pre-existing intermittent failure as nothing in the PR looks related to the failure.
|
process
|
test child process fork dgram intermittent timeout on aix version master platform aix subsystem process noticed this failure in a recent aix run when investigating intermittent addon issue test child process fork dgram failed with a timeout not ok parallel test child process fork dgram timeout likely a pre existing intermittent failure as nothing in the pr looks related to the failure
| 1
|
3,355
| 6,487,654,800
|
IssuesEvent
|
2017-08-20 10:03:01
|
Great-Hill-Corporation/quickBlocks
|
https://api.github.com/repos/Great-Hill-Corporation/quickBlocks
|
closed
|
blockScrape --deep --check
|
apps-blockScrape status-inprocess type-enhancement
|
Currently deep check only checks that each block has the correct list of transactions hashes. It should actually decend into the transactions and then into the receipts and then into the logs to check all data fields from QuickBlocks to the node.
From https://github.com/Great-Hill-Corporation/ethslurp/issues/140
|
1.0
|
blockScrape --deep --check - Currently deep check only checks that each block has the correct list of transactions hashes. It should actually decend into the transactions and then into the receipts and then into the logs to check all data fields from QuickBlocks to the node.
From https://github.com/Great-Hill-Corporation/ethslurp/issues/140
|
process
|
blockscrape deep check currently deep check only checks that each block has the correct list of transactions hashes it should actually decend into the transactions and then into the receipts and then into the logs to check all data fields from quickblocks to the node from
| 1
|
124,903
| 10,329,145,407
|
IssuesEvent
|
2019-09-02 11:24:25
|
bertvannuffelen/demo_oslodoc
|
https://api.github.com/repos/bertvannuffelen/demo_oslodoc
|
opened
|
Foutieve error output in CirceCI stap "Validate report"
|
Topic: testassociaties
|
Dit soort regels in de error output is verkeerd of op z'n minst verwarrend geformuleerd:
```
Property k08Arol without name in dutch, further processing this property will be incoherent
```
Het is niet de name tag die ontbreekt, wel de label-nl tag.
|
1.0
|
Foutieve error output in CirceCI stap "Validate report" - Dit soort regels in de error output is verkeerd of op z'n minst verwarrend geformuleerd:
```
Property k08Arol without name in dutch, further processing this property will be incoherent
```
Het is niet de name tag die ontbreekt, wel de label-nl tag.
|
non_process
|
foutieve error output in circeci stap validate report dit soort regels in de error output is verkeerd of op z n minst verwarrend geformuleerd property without name in dutch further processing this property will be incoherent het is niet de name tag die ontbreekt wel de label nl tag
| 0
|
16,588
| 21,636,686,270
|
IssuesEvent
|
2022-05-05 14:47:54
|
googleapis/cloud-debug-nodejs
|
https://api.github.com/repos/googleapis/cloud-debug-nodejs
|
opened
|
Firebase-backend branch: Re-enable unit tests related to ready state detection
|
type: process
|
https://github.com/googleapis/cloud-debug-nodejs/pull/1067 disabled some unit tests related to ready state detection. The refactors of the controller code have broken that functionality and must be repaired before the Firebase-backend branch can be merged into the main branch.
This is required as a part of developing https://github.com/googleapis/cloud-debug-nodejs/issues/1071
|
1.0
|
Firebase-backend branch: Re-enable unit tests related to ready state detection - https://github.com/googleapis/cloud-debug-nodejs/pull/1067 disabled some unit tests related to ready state detection. The refactors of the controller code have broken that functionality and must be repaired before the Firebase-backend branch can be merged into the main branch.
This is required as a part of developing https://github.com/googleapis/cloud-debug-nodejs/issues/1071
|
process
|
firebase backend branch re enable unit tests related to ready state detection disabled some unit tests related to ready state detection the refactors of the controller code have broken that functionality and must be repaired before the firebase backend branch can be merged into the main branch this is required as a part of developing
| 1
|
81,312
| 23,436,179,043
|
IssuesEvent
|
2022-08-15 10:05:17
|
appsmithorg/appsmith
|
https://api.github.com/repos/appsmithorg/appsmith
|
closed
|
[Feature]: Search for properties inside property pane
|
Enhancement Property Pane QA UI Builders Pod
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Summary
Based on [this](https://www.figma.com/file/hlOcM5LasxcRqEwHPXe5lm/UI-%7C-Content-Property-Pane?node-id=4489%3A94163) design, add a search bar to the property pane.
- [x] Search should work on content & style tab
- [x] It should work in the panels too (example: column properties in Table widget)
- [x] Search input should be focused when opening the property pane
### Why should this be worked on?
It will be helpful to quickly find the required property
|
1.0
|
[Feature]: Search for properties inside property pane - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Summary
Based on [this](https://www.figma.com/file/hlOcM5LasxcRqEwHPXe5lm/UI-%7C-Content-Property-Pane?node-id=4489%3A94163) design, add a search bar to the property pane.
- [x] Search should work on content & style tab
- [x] It should work in the panels too (example: column properties in Table widget)
- [x] Search input should be focused when opening the property pane
### Why should this be worked on?
It will be helpful to quickly find the required property
|
non_process
|
search for properties inside property pane is there an existing issue for this i have searched the existing issues summary based on design add a search bar to the property pane search should work on content style tab it should work in the panels too example column properties in table widget search input should be focused when opening the property pane why should this be worked on it will be helpful to quickly find the required property
| 0
|
433,604
| 12,507,600,703
|
IssuesEvent
|
2020-06-02 14:21:47
|
canonical-web-and-design/build.snapcraft.io
|
https://api.github.com/repos/canonical-web-and-design/build.snapcraft.io
|
closed
|
"Built, failed to release" on supertuxkart
|
Priority: Medium
|
## Summary
Supertuxkart successfully builds, but the UI reports "built, failed to release" for all architectures. This has been occurring for several weeks, to a couple months. This appears to currently happen with every build.
## Process
Manually trigger supertuxkart to build. Wait for the builds to finish and go through review. The reporting will state that the revisions are "failed to release" . This seems like a possible timeout issue, maybe due to the size of the supertuxkart snap.
## Current and expected result
The snap should correctly go through review and release, and the UI should then report the success.
## Screenshot
|
1.0
|
"Built, failed to release" on supertuxkart - ## Summary
Supertuxkart successfully builds, but the UI reports "built, failed to release" for all architectures. This has been occurring for several weeks, to a couple months. This appears to currently happen with every build.
## Process
Manually trigger supertuxkart to build. Wait for the builds to finish and go through review. The reporting will state that the revisions are "failed to release" . This seems like a possible timeout issue, maybe due to the size of the supertuxkart snap.
## Current and expected result
The snap should correctly go through review and release, and the UI should then report the success.
## Screenshot
|
non_process
|
built failed to release on supertuxkart summary supertuxkart successfully builds but the ui reports built failed to release for all architectures this has been occurring for several weeks to a couple months this appears to currently happen with every build process manually trigger supertuxkart to build wait for the builds to finish and go through review the reporting will state that the revisions are failed to release this seems like a possible timeout issue maybe due to the size of the supertuxkart snap current and expected result the snap should correctly go through review and release and the ui should then report the success screenshot
| 0
|
169,889
| 20,841,969,193
|
IssuesEvent
|
2022-03-21 01:59:05
|
Kites-Foundation/hello-munnar-frontend
|
https://api.github.com/repos/Kites-Foundation/hello-munnar-frontend
|
opened
|
CVE-2022-0691 (High) detected in url-parse-1.5.3.tgz
|
security vulnerability
|
## CVE-2022-0691 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.5.3.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.5.3.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.5.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.1.tgz (Root Library)
- webpack-dev-server-3.11.0.tgz
- sockjs-client-1.4.0.tgz
- :x: **url-parse-1.5.3.tgz** (Vulnerable Library)
<p>Found in base branch: <b>develop</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>
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.
<p>Publish Date: 2022-02-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0691>CVE-2022-0691</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-2022-0691">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0691</a></p>
<p>Release Date: 2022-02-21</p>
<p>Fix Resolution (url-parse): 1.5.9</p>
<p>Direct dependency fix Resolution (react-scripts): 4.0.2</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-0691 (High) detected in url-parse-1.5.3.tgz - ## CVE-2022-0691 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.5.3.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.5.3.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.5.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.1.tgz (Root Library)
- webpack-dev-server-3.11.0.tgz
- sockjs-client-1.4.0.tgz
- :x: **url-parse-1.5.3.tgz** (Vulnerable Library)
<p>Found in base branch: <b>develop</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>
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.
<p>Publish Date: 2022-02-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0691>CVE-2022-0691</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-2022-0691">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0691</a></p>
<p>Release Date: 2022-02-21</p>
<p>Fix Resolution (url-parse): 1.5.9</p>
<p>Direct dependency fix Resolution (react-scripts): 4.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in url parse tgz cve high severity vulnerability vulnerable library url parse tgz small footprint url parser that works seamlessly across node js and browser environments library home page a href path to dependency file package json path to vulnerable library node modules url parse package json dependency hierarchy react scripts tgz root library webpack dev server tgz sockjs client tgz x url parse tgz vulnerable library found in base branch develop vulnerability details authorization bypass through user controlled key in npm url parse prior to 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 url parse direct dependency fix resolution react scripts step up your open source security game with whitesource
| 0
|
111,094
| 9,498,951,468
|
IssuesEvent
|
2019-04-24 04:12:57
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
opened
|
Shields Panel drop downs are blank
|
QA/Test-Plan-Specified QA/Yes feature/shields feature/shields/panel regression
|
Follow up to https://github.com/brave/brave-browser/issues/2488
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean install
2. Open `interia.pl`
3. Open Shields Panel
4. Click on `3rd-party cookie blocked` to show drop down
OR
4. Click on `3rd-party recognition devices blocked` to show drop down
## Actual result:
<!--Please add screenshots if needed-->
Text in the drop down is not visible
Light theme:
Dark theme:
## Expected result:
Text in the drop down is visible
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easily reproduced
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Reproduced on
Brave | 0.64.60 Chromium: 74.0.3729.91 (Official Build) beta (64-bit)
-- | --
Revision | 03844ed83e02b8add3f4b9cb859a7108d55b2e4d-refs/branch-heads/3729@{#860}
OS | Windows 10 OS Build 17134.523
cc @brave/legacy_qa @cezaraugusto
|
1.0
|
Shields Panel drop downs are blank - Follow up to https://github.com/brave/brave-browser/issues/2488
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean install
2. Open `interia.pl`
3. Open Shields Panel
4. Click on `3rd-party cookie blocked` to show drop down
OR
4. Click on `3rd-party recognition devices blocked` to show drop down
## Actual result:
<!--Please add screenshots if needed-->
Text in the drop down is not visible
Light theme:
Dark theme:
## Expected result:
Text in the drop down is visible
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easily reproduced
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Reproduced on
Brave | 0.64.60 Chromium: 74.0.3729.91 (Official Build) beta (64-bit)
-- | --
Revision | 03844ed83e02b8add3f4b9cb859a7108d55b2e4d-refs/branch-heads/3729@{#860}
OS | Windows 10 OS Build 17134.523
cc @brave/legacy_qa @cezaraugusto
|
non_process
|
shields panel drop downs are blank follow up to steps to reproduce clean install open interia pl open shields panel click on party cookie blocked to show drop down or click on party recognition devices blocked to show drop down actual result text in the drop down is not visible light theme dark theme expected result text in the drop down is visible reproduces how often easily reproduced brave version brave version info reproduced on brave chromium official build beta bit revision refs branch heads os windows os build cc brave legacy qa cezaraugusto
| 0
|
798,494
| 28,281,561,517
|
IssuesEvent
|
2023-04-08 03:55:12
|
primaryodors/primarydock
|
https://api.github.com/repos/primaryodors/primarydock
|
closed
|
Side chain flexion probabilities.
|
high priority
|
As mentioned in #215 , too many side chain flexions are happening during dock, including one flexion of a phenylalanine residue into a position where it clashes with nearby protein atoms, causing false positives in the docking of ligands too big for the binding pocket.
Here are the flexion probabilities from the data in the cited https://pubmed.ncbi.nlm.nih.gov/10737948/ :
[flexion probabilities.ods](https://github.com/primaryodors/primarydock/files/11129710/flexion.probabilities.ods)
As you can see, the probability of any given Phe residue flexing in any real world protein-ligand binding is 0.015. This means about one and a half percent of dock poses for random selections of protein and ligand should include any flexion whatsoever of any Phe residue.
The probability of any given Arg flexing is 0.0635. Since we know Arg6.59 always flexes in OR51E* activations by SCFAs, 100% of all OR51E* docks with agonist SCFAs should flex Arg6.59.
|
1.0
|
Side chain flexion probabilities. - As mentioned in #215 , too many side chain flexions are happening during dock, including one flexion of a phenylalanine residue into a position where it clashes with nearby protein atoms, causing false positives in the docking of ligands too big for the binding pocket.
Here are the flexion probabilities from the data in the cited https://pubmed.ncbi.nlm.nih.gov/10737948/ :
[flexion probabilities.ods](https://github.com/primaryodors/primarydock/files/11129710/flexion.probabilities.ods)
As you can see, the probability of any given Phe residue flexing in any real world protein-ligand binding is 0.015. This means about one and a half percent of dock poses for random selections of protein and ligand should include any flexion whatsoever of any Phe residue.
The probability of any given Arg flexing is 0.0635. Since we know Arg6.59 always flexes in OR51E* activations by SCFAs, 100% of all OR51E* docks with agonist SCFAs should flex Arg6.59.
|
non_process
|
side chain flexion probabilities as mentioned in too many side chain flexions are happening during dock including one flexion of a phenylalanine residue into a position where it clashes with nearby protein atoms causing false positives in the docking of ligands too big for the binding pocket here are the flexion probabilities from the data in the cited as you can see the probability of any given phe residue flexing in any real world protein ligand binding is this means about one and a half percent of dock poses for random selections of protein and ligand should include any flexion whatsoever of any phe residue the probability of any given arg flexing is since we know always flexes in activations by scfas of all docks with agonist scfas should flex
| 0
|
29,122
| 7,058,321,611
|
IssuesEvent
|
2018-01-04 19:53:43
|
Microsoft/TypeScript
|
https://api.github.com/repos/Microsoft/TypeScript
|
closed
|
Code Helper using ~100% CPU
|
External VS Code Tracked
|
_From @coreh on December 9, 2017 0:26_
<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. -->
<!-- Use Help > Report Issues to prefill these. -->
- VSCode Version: 1.18.1
- OS Version: 10.12.6
I'm getting "Code Helper" stuck at ~100% CPU
<img width="815" alt="screen shot 2017-12-08 at 22 18 24" src="https://user-images.githubusercontent.com/418473/33790326-67568234-dc66-11e7-804a-17e67186907f.png">
```
ps a~ $ ps aux | grep 65462
coreh 65462 100.0 1.7 3492052 281544 ?? R 5:33PM 128:06.61 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart.js /Users/coreh/Projects/zimboli/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/m1/vk9trwwj3pz25vv0_jt7xtsc0000gn/T/vscode-tscancellation-da48568b3a6dd7891de0.sock* --locale en
```
Steps to Reproduce:
1. Use VS Code for a suficiently long time (say, several hours) on a large enough project.
2. A "Code Helper" process will start to use 100% CPU. Quitting VSCode does not terminate the Code Helper process, it needs to be killed from the Activity Monitor
<!-- Launch with `code --disable-extensions` to check. -->
Reproduces without extensions: _Probably_ not (?)
(It doesn't trigger immediately, or consistently, but rather after several hours using the App, and I haven't been able to conclude if it will not trigger without extensions. However the `ps` output seems to indicate that the offending file is `/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart.js`, so it's the built in TypeScript extension?)
Thanks in advance!
_Copied from original issue: Microsoft/vscode#39949_
|
1.0
|
Code Helper using ~100% CPU - _From @coreh on December 9, 2017 0:26_
<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. -->
<!-- Use Help > Report Issues to prefill these. -->
- VSCode Version: 1.18.1
- OS Version: 10.12.6
I'm getting "Code Helper" stuck at ~100% CPU
<img width="815" alt="screen shot 2017-12-08 at 22 18 24" src="https://user-images.githubusercontent.com/418473/33790326-67568234-dc66-11e7-804a-17e67186907f.png">
```
ps a~ $ ps aux | grep 65462
coreh 65462 100.0 1.7 3492052 281544 ?? R 5:33PM 128:06.61 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart.js /Users/coreh/Projects/zimboli/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/m1/vk9trwwj3pz25vv0_jt7xtsc0000gn/T/vscode-tscancellation-da48568b3a6dd7891de0.sock* --locale en
```
Steps to Reproduce:
1. Use VS Code for a suficiently long time (say, several hours) on a large enough project.
2. A "Code Helper" process will start to use 100% CPU. Quitting VSCode does not terminate the Code Helper process, it needs to be killed from the Activity Monitor
<!-- Launch with `code --disable-extensions` to check. -->
Reproduces without extensions: _Probably_ not (?)
(It doesn't trigger immediately, or consistently, but rather after several hours using the App, and I haven't been able to conclude if it will not trigger without extensions. However the `ps` output seems to indicate that the offending file is `/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart.js`, so it's the built in TypeScript extension?)
Thanks in advance!
_Copied from original issue: Microsoft/vscode#39949_
|
non_process
|
code helper using cpu from coreh on december report issues to prefill these vscode version os version i m getting code helper stuck at cpu img width alt screen shot at src ps a ps aux grep coreh r applications visual studio code app contents frameworks code helper app contents macos code helper applications visual studio code app contents resources app extensions typescript out utils electronforkstart js users coreh projects zimboli node modules typescript lib tsserver js useinferredprojectperprojectroot enabletelemetry cancellationpipename var folders t vscode tscancellation sock locale en steps to reproduce use vs code for a suficiently long time say several hours on a large enough project a code helper process will start to use cpu quitting vscode does not terminate the code helper process it needs to be killed from the activity monitor reproduces without extensions probably not it doesn t trigger immediately or consistently but rather after several hours using the app and i haven t been able to conclude if it will not trigger without extensions however the ps output seems to indicate that the offending file is applications visual studio code app contents resources app extensions typescript out utils electronforkstart js so it s the built in typescript extension thanks in advance copied from original issue microsoft vscode
| 0
|
84,174
| 24,252,133,648
|
IssuesEvent
|
2022-09-27 14:54:40
|
angular/angular
|
https://api.github.com/repos/angular/angular
|
closed
|
Error building project using artifacts created from angular source code build
|
comp: docs comp: build & ci
|
### Which @angular/* package(s) are the source of the bug?
Don't known / other
### Is this a regression?
No
### Description
In order to inestigate https://github.com/angular/angular/issues/13993, first I build angular-cli from source, then installed the tar balls and created a new angular project with it. This was done so that a new angular project is created with the correct dependencies.
Then I followed instructions at thttps://github.com/angular/angular/blob/main/docs/DEVELOPER.md
to copy angular build artifacts over to the newly created project using `yarn link`. Running "npm start" results in the above error.
I manually updated the javascript bundle where the issue was found and replaced ExternalExpr as suggested in the error message below. When I ran `npm start` again, I did not get error for `ExternalExpr` but similar error for another named export. Is there anything I am missing?
### Please provide a link to a minimal reproduction of the bug
_No response_
### Please provide the exception or error you saw
```true
An unhandled exception occurred: Named export 'ExternalExpr' not found. The requested module '@angular/compiler' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from '@angular/compiler';
const { ExternalExpr, ExternalReference, WrappedNodeExpr } = pkg;
```
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular CLI: 14.1.0-next.0
node: v14.17.0
```
### Anything else?
_No response_
|
1.0
|
Error building project using artifacts created from angular source code build - ### Which @angular/* package(s) are the source of the bug?
Don't known / other
### Is this a regression?
No
### Description
In order to inestigate https://github.com/angular/angular/issues/13993, first I build angular-cli from source, then installed the tar balls and created a new angular project with it. This was done so that a new angular project is created with the correct dependencies.
Then I followed instructions at thttps://github.com/angular/angular/blob/main/docs/DEVELOPER.md
to copy angular build artifacts over to the newly created project using `yarn link`. Running "npm start" results in the above error.
I manually updated the javascript bundle where the issue was found and replaced ExternalExpr as suggested in the error message below. When I ran `npm start` again, I did not get error for `ExternalExpr` but similar error for another named export. Is there anything I am missing?
### Please provide a link to a minimal reproduction of the bug
_No response_
### Please provide the exception or error you saw
```true
An unhandled exception occurred: Named export 'ExternalExpr' not found. The requested module '@angular/compiler' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from '@angular/compiler';
const { ExternalExpr, ExternalReference, WrappedNodeExpr } = pkg;
```
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular CLI: 14.1.0-next.0
node: v14.17.0
```
### Anything else?
_No response_
|
non_process
|
error building project using artifacts created from angular source code build which angular package s are the source of the bug don t known other is this a regression no description in order to inestigate first i build angular cli from source then installed the tar balls and created a new angular project with it this was done so that a new angular project is created with the correct dependencies then i followed instructions at t to copy angular build artifacts over to the newly created project using yarn link running npm start results in the above error i manually updated the javascript bundle where the issue was found and replaced externalexpr as suggested in the error message below when i ran npm start again i did not get error for externalexpr but similar error for another named export is there anything i am missing please provide a link to a minimal reproduction of the bug no response please provide the exception or error you saw true an unhandled exception occurred named export externalexpr not found the requested module angular compiler is a commonjs module which may not support all module exports as named exports commonjs modules can always be imported via the default export for example using import pkg from angular compiler const externalexpr externalreference wrappednodeexpr pkg please provide the environment you discovered this bug in run ng version true angular cli next node anything else no response
| 0
|
365
| 2,798,342,937
|
IssuesEvent
|
2015-05-12 18:08:58
|
pwittchen/NetworkEvents
|
https://api.github.com/repos/pwittchen/NetworkEvents
|
closed
|
Update README.md after merging PR #54 into master
|
release process
|
README.md should be updated after merging PR #54 into master.
|
1.0
|
Update README.md after merging PR #54 into master - README.md should be updated after merging PR #54 into master.
|
process
|
update readme md after merging pr into master readme md should be updated after merging pr into master
| 1
|
9,725
| 12,728,228,517
|
IssuesEvent
|
2020-06-25 01:52:40
|
allinurl/goaccess
|
https://api.github.com/repos/allinurl/goaccess
|
closed
|
Missing HTTP status code 308 support
|
add log-processing
|
Please, add also support for HTTP status code [308 Permanent Redirect](https://tools.ietf.org/html/rfc7538#section-3).
It is complementary to already supported 307 (Temporary Redirect). You know, it is the same as 301 – 302 pair.
```
goaccess-master/src/util.c
goaccess-master/src/labels.h
goaccess-master/po/…
```
|
1.0
|
Missing HTTP status code 308 support - Please, add also support for HTTP status code [308 Permanent Redirect](https://tools.ietf.org/html/rfc7538#section-3).
It is complementary to already supported 307 (Temporary Redirect). You know, it is the same as 301 – 302 pair.
```
goaccess-master/src/util.c
goaccess-master/src/labels.h
goaccess-master/po/…
```
|
process
|
missing http status code support please add also support for http status code it is complementary to already supported temporary redirect you know it is the same as – pair goaccess master src util c goaccess master src labels h goaccess master po …
| 1
|
21,495
| 29,660,307,021
|
IssuesEvent
|
2023-06-10 04:12:08
|
phuocduong-agilityio/internship-huy-dao
|
https://api.github.com/repos/phuocduong-agilityio/internship-huy-dao
|
closed
|
Create `Popover` Component
|
In-process
|
- [x] Make a button wrap block
- [x] Pass necessary props to button(`variant`, `size`,...)
- [x] Implement create 2 array contain image and text (`BRANDS`, `PRICES`)
- [x] Split into 2 popovers
- If `buttonType === image` the popover contains an image button
- Conversely, if `buttonType === text` then the popover contains the button text
- **NOTE**:
- The three component objects I create in the storybook will correspond to:
- See more details: [Link](https://docs.google.com/document/d/1iTrT9cdKrMCjUc6aDLS514gEk7BUFj-m2SCs2wCy2Lw/edit#heading=h.7t5pbcmau6ih)
|
1.0
|
Create `Popover` Component - - [x] Make a button wrap block
- [x] Pass necessary props to button(`variant`, `size`,...)
- [x] Implement create 2 array contain image and text (`BRANDS`, `PRICES`)
- [x] Split into 2 popovers
- If `buttonType === image` the popover contains an image button
- Conversely, if `buttonType === text` then the popover contains the button text
- **NOTE**:
- The three component objects I create in the storybook will correspond to:
- See more details: [Link](https://docs.google.com/document/d/1iTrT9cdKrMCjUc6aDLS514gEk7BUFj-m2SCs2wCy2Lw/edit#heading=h.7t5pbcmau6ih)
|
process
|
create popover component make a button wrap block pass necessary props to button variant size implement create array contain image and text brands prices split into popovers if buttontype image the popover contains an image button conversely if buttontype text then the popover contains the button text note the three component objects i create in the storybook will correspond to see more details
| 1
|
20,331
| 26,980,458,429
|
IssuesEvent
|
2023-02-09 12:44:46
|
ranchobiosciences/Data_Modeling_Issues_Templates
|
https://api.github.com/repos/ranchobiosciences/Data_Modeling_Issues_Templates
|
closed
|
[DM Request]: Use me to test Workbook Invalid (file format)
|
bug [SYSTEM] Processing
|
### Contact Details
joey@datamodel.com
### Description of changes
[wrong_file_format.csv](https://github.com/ranchobiosciences/Data_Modeling_Issues_Templates/files/10460352/wrong_file_format.csv)
|
1.0
|
[DM Request]: Use me to test Workbook Invalid (file format) - ### Contact Details
joey@datamodel.com
### Description of changes
[wrong_file_format.csv](https://github.com/ranchobiosciences/Data_Modeling_Issues_Templates/files/10460352/wrong_file_format.csv)
|
process
|
use me to test workbook invalid file format contact details joey datamodel com description of changes
| 1
|
2,697
| 5,541,396,336
|
IssuesEvent
|
2017-03-22 12:45:50
|
mathiasbynens/es-regexp-dotall-flag
|
https://api.github.com/repos/mathiasbynens/es-regexp-dotall-flag
|
closed
|
Advance to stage 2
|
process
|
Criteria taken from [the TC39 process document](https://tc39.github.io/process-document/) minus those from previous stages:
> - [x] Initial spec text
https://github.com/mathiasbynens/es-regexp-singleline-flag#specification
|
1.0
|
Advance to stage 2 - Criteria taken from [the TC39 process document](https://tc39.github.io/process-document/) minus those from previous stages:
> - [x] Initial spec text
https://github.com/mathiasbynens/es-regexp-singleline-flag#specification
|
process
|
advance to stage criteria taken from minus those from previous stages initial spec text
| 1
|
119,980
| 12,056,612,170
|
IssuesEvent
|
2020-04-15 14:42:01
|
luukvdmeer/sfnetworks
|
https://api.github.com/repos/luukvdmeer/sfnetworks
|
opened
|
Fine-tune pkgdown website
|
documentation improvement
|
- [ ] **Group functions on reference tab**
Group and describe `sfnetworks` functions accordingly. Reference [here](https://pkgdown.r-lib.org/articles/pkgdown.html#reference-1).
- [ ] **Check auto-linking to documentation**
Although `pkgdown` does this automatically, some links might not be working properly. Reference [here](https://pkgdown.r-lib.org/articles/linking.html).
- [ ] **Add news tab and changelog**
Add news tab to specify new features for each release. Reference [here](https://pkgdown.r-lib.org/articles/pkgdown.html#news-1).
|
1.0
|
Fine-tune pkgdown website - - [ ] **Group functions on reference tab**
Group and describe `sfnetworks` functions accordingly. Reference [here](https://pkgdown.r-lib.org/articles/pkgdown.html#reference-1).
- [ ] **Check auto-linking to documentation**
Although `pkgdown` does this automatically, some links might not be working properly. Reference [here](https://pkgdown.r-lib.org/articles/linking.html).
- [ ] **Add news tab and changelog**
Add news tab to specify new features for each release. Reference [here](https://pkgdown.r-lib.org/articles/pkgdown.html#news-1).
|
non_process
|
fine tune pkgdown website group functions on reference tab group and describe sfnetworks functions accordingly reference check auto linking to documentation although pkgdown does this automatically some links might not be working properly reference add news tab and changelog add news tab to specify new features for each release reference
| 0
|
2,101
| 4,938,011,191
|
IssuesEvent
|
2016-11-29 09:51:13
|
matz-e/lobster
|
https://api.github.com/repos/matz-e/lobster
|
closed
|
Caching datasets breaks with changing lumi mask
|
bug processing
|
When changing the lumi mask, datasets retrieved from the cache will always have the mask set from their first…
|
1.0
|
Caching datasets breaks with changing lumi mask - When changing the lumi mask, datasets retrieved from the cache will always have the mask set from their first…
|
process
|
caching datasets breaks with changing lumi mask when changing the lumi mask datasets retrieved from the cache will always have the mask set from their first…
| 1
|
8,257
| 11,423,777,886
|
IssuesEvent
|
2020-02-03 16:29:17
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
MP: GO:0099046 clearance of foreign intracellular nucleic acids
|
multi-species process quick fix
|
logically
GO:0099046 clearance of foreign intracellular nucleic acids
should be a descendant of
GO:0098542 defense response to other organism
?
|
1.0
|
MP: GO:0099046 clearance of foreign intracellular nucleic acids -
logically
GO:0099046 clearance of foreign intracellular nucleic acids
should be a descendant of
GO:0098542 defense response to other organism
?
|
process
|
mp go clearance of foreign intracellular nucleic acids logically go clearance of foreign intracellular nucleic acids should be a descendant of go defense response to other organism
| 1
|
285,393
| 31,154,500,972
|
IssuesEvent
|
2023-08-16 12:18:12
|
Trinadh465/linux-4.1.15_CVE-2018-5873
|
https://api.github.com/repos/Trinadh465/linux-4.1.15_CVE-2018-5873
|
opened
|
CVE-2016-2069 (High) detected in linuxlinux-4.1.52
|
Mend: dependency security vulnerability
|
## CVE-2016-2069 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.52</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/Trinadh465/linux-4.1.15_CVE-2018-5873/commit/32145daf0c96b012284199f23418243e0168269f">32145daf0c96b012284199f23418243e0168269f</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (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>
Race condition in arch/x86/mm/tlb.c in the Linux kernel before 4.4.1 allows local users to gain privileges by triggering access to a paging structure by a different CPU.
<p>Publish Date: 2016-04-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-2069>CVE-2016-2069</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- 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://nvd.nist.gov/vuln/detail/CVE-2016-2069">https://nvd.nist.gov/vuln/detail/CVE-2016-2069</a></p>
<p>Release Date: 2016-04-27</p>
<p>Fix Resolution: 4.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2016-2069 (High) detected in linuxlinux-4.1.52 - ## CVE-2016-2069 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.52</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/Trinadh465/linux-4.1.15_CVE-2018-5873/commit/32145daf0c96b012284199f23418243e0168269f">32145daf0c96b012284199f23418243e0168269f</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (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>
Race condition in arch/x86/mm/tlb.c in the Linux kernel before 4.4.1 allows local users to gain privileges by triggering access to a paging structure by a different CPU.
<p>Publish Date: 2016-04-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-2069>CVE-2016-2069</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- 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://nvd.nist.gov/vuln/detail/CVE-2016-2069">https://nvd.nist.gov/vuln/detail/CVE-2016-2069</a></p>
<p>Release Date: 2016-04-27</p>
<p>Fix Resolution: 4.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
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 main vulnerable source files vulnerability details race condition in arch mm tlb c in the linux kernel before allows local users to gain privileges by triggering access to a paging structure by a different cpu publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high 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 mend
| 0
|
70,381
| 23,148,912,248
|
IssuesEvent
|
2022-07-29 06:01:29
|
line/armeria
|
https://api.github.com/repos/line/armeria
|
closed
|
Test failure: `example.armeria.grpc.kotlin.HelloServiceTest`
|
defect
|
```
io.grpc.StatusException: UNKNOWN
at app//io.grpc.Status.asException(Status.java:550)
at app//io.grpc.kotlin.ClientCalls$rpcImpl$1$1$1.onClose(ClientCalls.kt:296)
at app//com.linecorp.armeria.internal.client.grpc.ArmeriaClientCall.close(ArmeriaClientCall.java:499)
at app//com.linecorp.armeria.internal.client.grpc.ArmeriaClientCall.transportReportStatus(ArmeriaClientCall.java:443)
at app//com.linecorp.armeria.internal.common.grpc.GrpcStatus.reportStatus(GrpcStatus.java:338)
at app//com.linecorp.armeria.internal.common.grpc.GrpcStatus.lambda$reportStatusLater$0(GrpcStatus.java:316)
at java.base@16.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
at java.base@16.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
at java.base@16.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at java.base@16.0.2/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2143)
at app//com.linecorp.armeria.common.stream.AbstractStreamMessage$CloseEvent.notifySubscriber(AbstractStreamMessage.java:259)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent0(DefaultStreamMessage.java:300)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent(DefaultStreamMessage.java:292)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.handleCloseEvent(DefaultStreamMessage.java:429)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber0(DefaultStreamMessage.java:372)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber(DefaultStreamMessage.java:328)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.addObjectOrEvent(DefaultStreamMessage.java:314)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.close(DefaultStreamMessage.java:436)
at app//com.linecorp.armeria.internal.common.stream.DecodedStreamMessage$DecodingSubscriber.onComplete(DecodedStreamMessage.java:288)
at app//com.linecorp.armeria.common.stream.AbstractStreamMessage$CloseEvent.notifySubscriber(AbstractStreamMessage.java:258)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent0(DefaultStreamMessage.java:300)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent(DefaultStreamMessage.java:292)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.handleCloseEvent(DefaultStreamMessage.java:429)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber0(DefaultStreamMessage.java:372)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber(DefaultStreamMessage.java:328)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.addObjectOrEvent(DefaultStreamMessage.java:314)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.close(DefaultStreamMessage.java:436)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.closeAction(HttpResponseDecoder.java:335)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.cancelTimeoutOrLog(HttpResponseDecoder.java:370)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.close(HttpResponseDecoder.java:318)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.close(HttpResponseDecoder.java:308)
at app//com.linecorp.armeria.client.Http2ResponseDecoder.onHeadersRead(Http2ResponseDecoder.java:216)
at app//com.linecorp.armeria.client.Http2ResponseDecoder.onHeadersRead(Http2ResponseDecoder.java:225)
at app//io.netty.handler.codec.http2.Http2FrameListenerDecorator.onHeadersRead(Http2FrameListenerDecorator.java:48)
at app//io.netty.handler.codec.http2.Http2EmptyDataFrameListener.onHeadersRead(Http2EmptyDataFrameListener.java:63)
at app//io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.onHeadersRead(DefaultHttp2ConnectionDecoder.java:409)
at app//io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.onHeadersRead(DefaultHttp2ConnectionDecoder.java:337)
at app//io.netty.handler.codec.http2.Http2InboundFrameLogger$1.onHeadersRead(Http2InboundFrameLogger.java:56)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader$2.processFragment(DefaultHttp2FrameReader.java:476)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader.readHeadersFrame(DefaultHttp2FrameReader.java:484)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader.processPayloadState(DefaultHttp2FrameReader.java:253)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader.readFrame(DefaultHttp2FrameReader.java:159)
at app//io.netty.handler.codec.http2.Http2InboundFrameLogger.readFrame(Http2InboundFrameLogger.java:41)
at app//io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder.decodeFrame(DefaultHttp2ConnectionDecoder.java:173)
at app//io.netty.handler.codec.http2.DecoratingHttp2ConnectionDecoder.decodeFrame(DecoratingHttp2ConnectionDecoder.java:63)
at app//io.netty.handler.codec.http2.Http2ConnectionHandler$FrameDecoder.decode(Http2ConnectionHandler.java:393)
at app//io.netty.handler.codec.http2.Http2ConnectionHandler.decode(Http2ConnectionHandler.java:453)
at app//io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510)
at app//io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449)
at app//io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:279)
at app//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at app//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at app//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at app//io.netty.handler.logging.LoggingHan
```
The cause of the error above seems suspicious.
```
Caused by: com.linecorp.armeria.common.grpc.StatusCauseException: java.lang.IllegalStateException: subscribed by other subscriber already
at com.linecorp.armeria.internal.common.stream.FixedStreamMessage.collect(FixedStreamMessage.java:189)
at com.linecorp.armeria.server.grpc.UnaryServerCall.startDeframing(UnaryServerCall.java:118)
at com.linecorp.armeria.server.grpc.FramedGrpcService.startCall(FramedGrpcService.java:316)
at com.linecorp.armeria.server.grpc.FramedGrpcService.lambda$startCall$3(FramedGrpcService.java:284)
at com.google.common.util.concurrent.SequentialExecutor$1.run(SequentialExecutor.java:123)
at com.google.common.util.concurrent.SequentialExecutor$QueueWorker.workOnQueue(SequentialExecutor.java:235)
at com.google.common.util.concurrent.SequentialExecutor$QueueWorker.run(SequentialExecutor.java:180)
at com.linecorp.armeria.common.RequestContext.lambda$makeContextAware$3(RequestContext.java:555)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
```
https://github.com/line/armeria/actions/runs/2738340617#summary-7516955221
|
1.0
|
Test failure: `example.armeria.grpc.kotlin.HelloServiceTest` - ```
io.grpc.StatusException: UNKNOWN
at app//io.grpc.Status.asException(Status.java:550)
at app//io.grpc.kotlin.ClientCalls$rpcImpl$1$1$1.onClose(ClientCalls.kt:296)
at app//com.linecorp.armeria.internal.client.grpc.ArmeriaClientCall.close(ArmeriaClientCall.java:499)
at app//com.linecorp.armeria.internal.client.grpc.ArmeriaClientCall.transportReportStatus(ArmeriaClientCall.java:443)
at app//com.linecorp.armeria.internal.common.grpc.GrpcStatus.reportStatus(GrpcStatus.java:338)
at app//com.linecorp.armeria.internal.common.grpc.GrpcStatus.lambda$reportStatusLater$0(GrpcStatus.java:316)
at java.base@16.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
at java.base@16.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
at java.base@16.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at java.base@16.0.2/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2143)
at app//com.linecorp.armeria.common.stream.AbstractStreamMessage$CloseEvent.notifySubscriber(AbstractStreamMessage.java:259)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent0(DefaultStreamMessage.java:300)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent(DefaultStreamMessage.java:292)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.handleCloseEvent(DefaultStreamMessage.java:429)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber0(DefaultStreamMessage.java:372)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber(DefaultStreamMessage.java:328)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.addObjectOrEvent(DefaultStreamMessage.java:314)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.close(DefaultStreamMessage.java:436)
at app//com.linecorp.armeria.internal.common.stream.DecodedStreamMessage$DecodingSubscriber.onComplete(DecodedStreamMessage.java:288)
at app//com.linecorp.armeria.common.stream.AbstractStreamMessage$CloseEvent.notifySubscriber(AbstractStreamMessage.java:258)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent0(DefaultStreamMessage.java:300)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriberOfCloseEvent(DefaultStreamMessage.java:292)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.handleCloseEvent(DefaultStreamMessage.java:429)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber0(DefaultStreamMessage.java:372)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.notifySubscriber(DefaultStreamMessage.java:328)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.addObjectOrEvent(DefaultStreamMessage.java:314)
at app//com.linecorp.armeria.common.stream.DefaultStreamMessage.close(DefaultStreamMessage.java:436)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.closeAction(HttpResponseDecoder.java:335)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.cancelTimeoutOrLog(HttpResponseDecoder.java:370)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.close(HttpResponseDecoder.java:318)
at app//com.linecorp.armeria.client.HttpResponseDecoder$HttpResponseWrapper.close(HttpResponseDecoder.java:308)
at app//com.linecorp.armeria.client.Http2ResponseDecoder.onHeadersRead(Http2ResponseDecoder.java:216)
at app//com.linecorp.armeria.client.Http2ResponseDecoder.onHeadersRead(Http2ResponseDecoder.java:225)
at app//io.netty.handler.codec.http2.Http2FrameListenerDecorator.onHeadersRead(Http2FrameListenerDecorator.java:48)
at app//io.netty.handler.codec.http2.Http2EmptyDataFrameListener.onHeadersRead(Http2EmptyDataFrameListener.java:63)
at app//io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.onHeadersRead(DefaultHttp2ConnectionDecoder.java:409)
at app//io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.onHeadersRead(DefaultHttp2ConnectionDecoder.java:337)
at app//io.netty.handler.codec.http2.Http2InboundFrameLogger$1.onHeadersRead(Http2InboundFrameLogger.java:56)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader$2.processFragment(DefaultHttp2FrameReader.java:476)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader.readHeadersFrame(DefaultHttp2FrameReader.java:484)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader.processPayloadState(DefaultHttp2FrameReader.java:253)
at app//io.netty.handler.codec.http2.DefaultHttp2FrameReader.readFrame(DefaultHttp2FrameReader.java:159)
at app//io.netty.handler.codec.http2.Http2InboundFrameLogger.readFrame(Http2InboundFrameLogger.java:41)
at app//io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder.decodeFrame(DefaultHttp2ConnectionDecoder.java:173)
at app//io.netty.handler.codec.http2.DecoratingHttp2ConnectionDecoder.decodeFrame(DecoratingHttp2ConnectionDecoder.java:63)
at app//io.netty.handler.codec.http2.Http2ConnectionHandler$FrameDecoder.decode(Http2ConnectionHandler.java:393)
at app//io.netty.handler.codec.http2.Http2ConnectionHandler.decode(Http2ConnectionHandler.java:453)
at app//io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510)
at app//io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449)
at app//io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:279)
at app//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at app//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at app//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at app//io.netty.handler.logging.LoggingHan
```
The cause of the error above seems suspicious.
```
Caused by: com.linecorp.armeria.common.grpc.StatusCauseException: java.lang.IllegalStateException: subscribed by other subscriber already
at com.linecorp.armeria.internal.common.stream.FixedStreamMessage.collect(FixedStreamMessage.java:189)
at com.linecorp.armeria.server.grpc.UnaryServerCall.startDeframing(UnaryServerCall.java:118)
at com.linecorp.armeria.server.grpc.FramedGrpcService.startCall(FramedGrpcService.java:316)
at com.linecorp.armeria.server.grpc.FramedGrpcService.lambda$startCall$3(FramedGrpcService.java:284)
at com.google.common.util.concurrent.SequentialExecutor$1.run(SequentialExecutor.java:123)
at com.google.common.util.concurrent.SequentialExecutor$QueueWorker.workOnQueue(SequentialExecutor.java:235)
at com.google.common.util.concurrent.SequentialExecutor$QueueWorker.run(SequentialExecutor.java:180)
at com.linecorp.armeria.common.RequestContext.lambda$makeContextAware$3(RequestContext.java:555)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
```
https://github.com/line/armeria/actions/runs/2738340617#summary-7516955221
|
non_process
|
test failure example armeria grpc kotlin helloservicetest io grpc statusexception unknown at app io grpc status asexception status java at app io grpc kotlin clientcalls rpcimpl onclose clientcalls kt at app com linecorp armeria internal client grpc armeriaclientcall close armeriaclientcall java at app com linecorp armeria internal client grpc armeriaclientcall transportreportstatus armeriaclientcall java at app com linecorp armeria internal common grpc grpcstatus reportstatus grpcstatus java at app com linecorp armeria internal common grpc grpcstatus lambda reportstatuslater grpcstatus java at java base java util concurrent completablefuture unihandle completablefuture java at java base java util concurrent completablefuture unihandle tryfire completablefuture java at java base java util concurrent completablefuture postcomplete completablefuture java at java base java util concurrent completablefuture complete completablefuture java at app com linecorp armeria common stream abstractstreammessage closeevent notifysubscriber abstractstreammessage java at app com linecorp armeria common stream defaultstreammessage defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage notifysubscriberofcloseevent defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage handlecloseevent defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage notifysubscriber defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage addobjectorevent defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage close defaultstreammessage java at app com linecorp armeria internal common stream decodedstreammessage decodingsubscriber oncomplete decodedstreammessage java at app com linecorp armeria common stream abstractstreammessage closeevent notifysubscriber abstractstreammessage java at app com linecorp armeria common stream defaultstreammessage defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage notifysubscriberofcloseevent defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage handlecloseevent defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage notifysubscriber defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage addobjectorevent defaultstreammessage java at app com linecorp armeria common stream defaultstreammessage close defaultstreammessage java at app com linecorp armeria client httpresponsedecoder httpresponsewrapper closeaction httpresponsedecoder java at app com linecorp armeria client httpresponsedecoder httpresponsewrapper canceltimeoutorlog httpresponsedecoder java at app com linecorp armeria client httpresponsedecoder httpresponsewrapper close httpresponsedecoder java at app com linecorp armeria client httpresponsedecoder httpresponsewrapper close httpresponsedecoder java at app com linecorp armeria client onheadersread java at app com linecorp armeria client onheadersread java at app io netty handler codec onheadersread java at app io netty handler codec onheadersread java at app io netty handler codec framereadlistener onheadersread java at app io netty handler codec framereadlistener onheadersread java at app io netty handler codec onheadersread java at app io netty handler codec processfragment java at app io netty handler codec readheadersframe java at app io netty handler codec processpayloadstate java at app io netty handler codec readframe java at app io netty handler codec readframe java at app io netty handler codec decodeframe java at app io netty handler codec decodeframe java at app io netty handler codec framedecoder decode java at app io netty handler codec decode java at app io netty handler codec bytetomessagedecoder decoderemovalreentryprotection bytetomessagedecoder java at app io netty handler codec bytetomessagedecoder calldecode bytetomessagedecoder java at app io netty handler codec bytetomessagedecoder channelread bytetomessagedecoder java at app io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at app io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at app io netty channel abstractchannelhandlercontext firechannelread abstractchannelhandlercontext java at app io netty handler logging logginghan the cause of the error above seems suspicious caused by com linecorp armeria common grpc statuscauseexception java lang illegalstateexception subscribed by other subscriber already at com linecorp armeria internal common stream fixedstreammessage collect fixedstreammessage java at com linecorp armeria server grpc unaryservercall startdeframing unaryservercall java at com linecorp armeria server grpc framedgrpcservice startcall framedgrpcservice java at com linecorp armeria server grpc framedgrpcservice lambda startcall framedgrpcservice java at com google common util concurrent sequentialexecutor run sequentialexecutor java at com google common util concurrent sequentialexecutor queueworker workonqueue sequentialexecutor java at com google common util concurrent sequentialexecutor queueworker run sequentialexecutor java at com linecorp armeria common requestcontext lambda makecontextaware requestcontext java at java util concurrent executors runnableadapter call executors java at java util concurrent futuretask run futuretask java
| 0
|
67,396
| 8,129,813,456
|
IssuesEvent
|
2018-08-17 16:13:07
|
ManageIQ/manageiq-v2v
|
https://api.github.com/repos/ManageIQ/manageiq-v2v
|
opened
|
Filters on Migration Not Started Details Page
|
needs-design
|
We are seeing some spacing issues with the toolbar in FireFox. Also, the question has been raised as to whether or not the value added by filtering/sorting functionality is worth having the additional UI element.
# Screens
|
1.0
|
Filters on Migration Not Started Details Page - We are seeing some spacing issues with the toolbar in FireFox. Also, the question has been raised as to whether or not the value added by filtering/sorting functionality is worth having the additional UI element.
# Screens
|
non_process
|
filters on migration not started details page we are seeing some spacing issues with the toolbar in firefox also the question has been raised as to whether or not the value added by filtering sorting functionality is worth having the additional ui element screens
| 0
|
259,999
| 19,652,636,919
|
IssuesEvent
|
2022-01-10 09:10:29
|
laravel-streams/streams
|
https://api.github.com/repos/laravel-streams/streams
|
closed
|
Etags and Caching API Documentation
|
Documentation
|
- [x] Etag documentation for API client
- [x] Cache documentation for API server
|
1.0
|
Etags and Caching API Documentation - - [x] Etag documentation for API client
- [x] Cache documentation for API server
|
non_process
|
etags and caching api documentation etag documentation for api client cache documentation for api server
| 0
|
74,538
| 20,201,050,223
|
IssuesEvent
|
2022-02-11 15:18:00
|
neuronsimulator/nrn
|
https://api.github.com/repos/neuronsimulator/nrn
|
closed
|
nrn_is_python_extension value likely less meaningful for Python 3.10+
|
python building
|
While the [docs for `Py_GetVersion`](https://docs.python.org/3/c-api/init.html#c.Py_GetVersion) say that the third character of the return is the minor version number, this is presumably not true in [Python 3.10](https://docs.python.org/3.10/whatsnew/3.10.html) (currently a preview release). This means that ``nrn_is_python_extension``, defined as:
```c++
nrn_is_python_extension = (pyver[0]-'0')*10 + (pyver[2] - '0');
```
would have the same value (31) for Python 3.1, and 3.10-3.19.
I don't think this is a problem per se, in that we currently only care if it's 0 or non-zero *except* in ``load_nrnpython`` where it affects which lib to load (but then it's a choice between 2.x and 3.x). That said, now that Python 3.10 semi-exists, if we are keeping track of the version, maybe we want to do it in some other way. Alternatively, now that we're dropping support for 2.x, maybe this should go back to being a boolean flag?
|
1.0
|
nrn_is_python_extension value likely less meaningful for Python 3.10+ - While the [docs for `Py_GetVersion`](https://docs.python.org/3/c-api/init.html#c.Py_GetVersion) say that the third character of the return is the minor version number, this is presumably not true in [Python 3.10](https://docs.python.org/3.10/whatsnew/3.10.html) (currently a preview release). This means that ``nrn_is_python_extension``, defined as:
```c++
nrn_is_python_extension = (pyver[0]-'0')*10 + (pyver[2] - '0');
```
would have the same value (31) for Python 3.1, and 3.10-3.19.
I don't think this is a problem per se, in that we currently only care if it's 0 or non-zero *except* in ``load_nrnpython`` where it affects which lib to load (but then it's a choice between 2.x and 3.x). That said, now that Python 3.10 semi-exists, if we are keeping track of the version, maybe we want to do it in some other way. Alternatively, now that we're dropping support for 2.x, maybe this should go back to being a boolean flag?
|
non_process
|
nrn is python extension value likely less meaningful for python while the say that the third character of the return is the minor version number this is presumably not true in currently a preview release this means that nrn is python extension defined as c nrn is python extension pyver pyver would have the same value for python and i don t think this is a problem per se in that we currently only care if it s or non zero except in load nrnpython where it affects which lib to load but then it s a choice between x and x that said now that python semi exists if we are keeping track of the version maybe we want to do it in some other way alternatively now that we re dropping support for x maybe this should go back to being a boolean flag
| 0
|
18,460
| 24,549,490,573
|
IssuesEvent
|
2022-10-12 11:27:17
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[PM] Participant details screen > UI issue
|
Bug P2 Participant manager Process: Fixed Process: Tested dev
|
Participant details screen > UI issue > Alignment of the columns in Enrollment history is not proper
AR:
ER:
|
2.0
|
[PM] Participant details screen > UI issue - Participant details screen > UI issue > Alignment of the columns in Enrollment history is not proper
AR:
ER:
|
process
|
participant details screen ui issue participant details screen ui issue alignment of the columns in enrollment history is not proper ar er
| 1
|
842
| 3,143,524,156
|
IssuesEvent
|
2015-09-14 07:41:03
|
boniface/hashwork
|
https://api.github.com/repos/boniface/hashwork
|
opened
|
Payroll - ui/deductions service facade
|
service facade
|
- complete service facade for all classes listed in domain/payroll/ui/deductions package
- service facade will be found in this package hashwork/app/facade
Note: LocationFacade exists in the facade package for your guidance.
|
1.0
|
Payroll - ui/deductions service facade - - complete service facade for all classes listed in domain/payroll/ui/deductions package
- service facade will be found in this package hashwork/app/facade
Note: LocationFacade exists in the facade package for your guidance.
|
non_process
|
payroll ui deductions service facade complete service facade for all classes listed in domain payroll ui deductions package service facade will be found in this package hashwork app facade note locationfacade exists in the facade package for your guidance
| 0
|
21,682
| 30,123,002,177
|
IssuesEvent
|
2023-06-30 16:46:06
|
UnitTestBot/UTBotJava
|
https://api.github.com/repos/UnitTestBot/UTBotJava
|
opened
|
Warm up the database in Spring integration tests
|
ctg-enhancement comp-instrumented-process comp-spring
|
**Description**
It is better to create some "fake" operations of adding data to the database and removing it before real test generation.
If some small values are used as id, fuzzer may just guess it, so generated test may not be reliable.
Even though we reset some Spring beans between the tests, database tables ids are not reset, so some warm up will highly likely help to avoid ids clashes.
|
1.0
|
Warm up the database in Spring integration tests - **Description**
It is better to create some "fake" operations of adding data to the database and removing it before real test generation.
If some small values are used as id, fuzzer may just guess it, so generated test may not be reliable.
Even though we reset some Spring beans between the tests, database tables ids are not reset, so some warm up will highly likely help to avoid ids clashes.
|
process
|
warm up the database in spring integration tests description it is better to create some fake operations of adding data to the database and removing it before real test generation if some small values are used as id fuzzer may just guess it so generated test may not be reliable even though we reset some spring beans between the tests database tables ids are not reset so some warm up will highly likely help to avoid ids clashes
| 1
|
2,306
| 5,119,277,014
|
IssuesEvent
|
2017-01-08 16:20:33
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
Error: spawnSync /bin/sh ENOENT
|
child_process
|
```js
let { execSync: exec } = require('child_process');
let os = require('os');
let tmp = os.tmpdir();
exec(`npm install --prefix ${tmp}`, {
cwd: './',
encoding: 'utf8',
stdio: 'inherit'
});
```
```
child_process.js:531
throw err;
^
Error: spawnSync /bin/sh ENOENT
at exports._errnoException (util.js:1026:11)
at spawnSync (child_process.js:466:20)
at execSync (child_process.js:522:13)
at Cache.installModules (/index.js:173:3)
at Object.<anonymous> (/install.js:11:7)
at Module._compile (module.js:573:32)
at Object.Module._extensions..js (module.js:582:10)
at Module.load (module.js:490:32)
at tryModuleLoad (module.js:449:12)
at Function.Module._load (module.js:441:3)
```
* **Version**: v7.0.0
* **Platform**: 3.10.8
* **Subsystem**: Darwin (MacOS Sierra 10.12.1 (16B2555))
Darwin local 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64
Please read my [another](https://github.com/npm/npm/issues/14633) issue before
|
1.0
|
Error: spawnSync /bin/sh ENOENT - ```js
let { execSync: exec } = require('child_process');
let os = require('os');
let tmp = os.tmpdir();
exec(`npm install --prefix ${tmp}`, {
cwd: './',
encoding: 'utf8',
stdio: 'inherit'
});
```
```
child_process.js:531
throw err;
^
Error: spawnSync /bin/sh ENOENT
at exports._errnoException (util.js:1026:11)
at spawnSync (child_process.js:466:20)
at execSync (child_process.js:522:13)
at Cache.installModules (/index.js:173:3)
at Object.<anonymous> (/install.js:11:7)
at Module._compile (module.js:573:32)
at Object.Module._extensions..js (module.js:582:10)
at Module.load (module.js:490:32)
at tryModuleLoad (module.js:449:12)
at Function.Module._load (module.js:441:3)
```
* **Version**: v7.0.0
* **Platform**: 3.10.8
* **Subsystem**: Darwin (MacOS Sierra 10.12.1 (16B2555))
Darwin local 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64
Please read my [another](https://github.com/npm/npm/issues/14633) issue before
|
process
|
error spawnsync bin sh enoent js let execsync exec require child process let os require os let tmp os tmpdir exec npm install prefix tmp cwd encoding stdio inherit child process js throw err error spawnsync bin sh enoent at exports errnoexception util js at spawnsync child process js at execsync child process js at cache installmodules index js at object install js at module compile module js at object module extensions js module js at module load module js at trymoduleload module js at function module load module js version platform subsystem darwin macos sierra darwin local darwin kernel version thu oct pdt root xnu release please read my issue before
| 1
|
84,580
| 16,518,718,657
|
IssuesEvent
|
2021-05-26 12:32:34
|
eth-cscs/reframe
|
https://api.github.com/repos/eth-cscs/reframe
|
closed
|
Remove deprecated attributes of `ContainerPlatform`
|
4.x code quality prio: normal
|
These are the following:
- `commands`
- `workdir`
|
1.0
|
Remove deprecated attributes of `ContainerPlatform` - These are the following:
- `commands`
- `workdir`
|
non_process
|
remove deprecated attributes of containerplatform these are the following commands workdir
| 0
|
20,137
| 26,683,558,257
|
IssuesEvent
|
2023-01-26 19:48:24
|
microsoft/vscode
|
https://api.github.com/repos/microsoft/vscode
|
reopened
|
Local terminal can't be opened: \bin\bash not found (though VS Code running on Windows)
|
bug important verification-found remote confirmed insiders-released terminal-process
|
<!-- Please search existing issues to avoid creating duplicates, and review our troubleshooting tips: https://code.visualstudio.com/docs/remote/troubleshooting -->
<!-- Please attach logs to help us diagnose your issue. Learn more here: https://code.visualstudio.com/docs/remote/troubleshooting#_reporting-issues -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
- VSCode Version: 1.66.1
- Local OS Version: Windows 10
- Remote OS Version: Linux
- Remote Extension/Connection Type: Docker/WSL2 running on host
- Logs: error message: ```The terminal process failed to launch: Path to shell executable "\bin\bash" does not exist.```
Steps to Reproduce:
1. VS Code command: ```> Terminal: Create New Integrated Terminal (Local)```
2. The error popup appears (see above "Logs")
<!-- Check to see if the problem is general, with a specific extension, or only happens when remote -->
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: Yes
<!-- If your issue only appears in Codespaces, please visit: https://github.com/github/feedback/discussions/categories/codespaces-feedback -->
Seems like microsoft/vscode-remote-release#730 is broken.
I checked with ```@modified terminal``` if there are any changes. Only inside the container the following settings are set:
```terminal.integrated.profiles.linux``` and ```terminal.integrated.defaultProfile.linux```.
Shouldn't it run cmd or powershell locally?
|
1.0
|
Local terminal can't be opened: \bin\bash not found (though VS Code running on Windows) - <!-- Please search existing issues to avoid creating duplicates, and review our troubleshooting tips: https://code.visualstudio.com/docs/remote/troubleshooting -->
<!-- Please attach logs to help us diagnose your issue. Learn more here: https://code.visualstudio.com/docs/remote/troubleshooting#_reporting-issues -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
- VSCode Version: 1.66.1
- Local OS Version: Windows 10
- Remote OS Version: Linux
- Remote Extension/Connection Type: Docker/WSL2 running on host
- Logs: error message: ```The terminal process failed to launch: Path to shell executable "\bin\bash" does not exist.```
Steps to Reproduce:
1. VS Code command: ```> Terminal: Create New Integrated Terminal (Local)```
2. The error popup appears (see above "Logs")
<!-- Check to see if the problem is general, with a specific extension, or only happens when remote -->
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: Yes
<!-- If your issue only appears in Codespaces, please visit: https://github.com/github/feedback/discussions/categories/codespaces-feedback -->
Seems like microsoft/vscode-remote-release#730 is broken.
I checked with ```@modified terminal``` if there are any changes. Only inside the container the following settings are set:
```terminal.integrated.profiles.linux``` and ```terminal.integrated.defaultProfile.linux```.
Shouldn't it run cmd or powershell locally?
|
process
|
local terminal can t be opened bin bash not found though vs code running on windows vscode version local os version windows remote os version linux remote extension connection type docker running on host logs error message the terminal process failed to launch path to shell executable bin bash does not exist steps to reproduce vs code command terminal create new integrated terminal local the error popup appears see above logs does this issue occur when you try this locally n a does this issue occur when you try this locally and all extensions are disabled yes seems like microsoft vscode remote release is broken i checked with modified terminal if there are any changes only inside the container the following settings are set terminal integrated profiles linux and terminal integrated defaultprofile linux shouldn t it run cmd or powershell locally
| 1
|
17,503
| 23,315,753,000
|
IssuesEvent
|
2022-08-08 12:22:47
|
prisma/prisma
|
https://api.github.com/repos/prisma/prisma
|
closed
|
Issue that occurred during `prisma db pull`
|
bug/1-unconfirmed kind/bug process/candidate tech/engines/introspection engine team/schema topic: prisma db pull topic: Your friendly prisma developers
|
Hi Prisma Team! Prisma Migrate just crashed.
## Command
`db pull`
## Versions
| Name | Version |
|-------------|--------------------|
| Platform | darwin |
| Node | v16.15.1 |
| Prisma CLI | 4.1.1 |
| Engine | 8d8414deb360336e4698a65aa45a1fbaf1ce13d8|
## Error
```
Error: [libs/datamodel/connectors/dml/src/model.rs:494:29] Hi there! We've been seeing this error in our error reporting backend, but cannot reproduce it in our own tests. The problem is that we have a primary key in the model `addressAttributesString` that uses the column `productId` which we for some reason don't have in our internal representation. If you see this, could you please file an issue to https://github.com/prisma/prisma so we can discuss about fixing this. -- Your friendly prisma developers.
```
|
1.0
|
Issue that occurred during `prisma db pull` - Hi Prisma Team! Prisma Migrate just crashed.
## Command
`db pull`
## Versions
| Name | Version |
|-------------|--------------------|
| Platform | darwin |
| Node | v16.15.1 |
| Prisma CLI | 4.1.1 |
| Engine | 8d8414deb360336e4698a65aa45a1fbaf1ce13d8|
## Error
```
Error: [libs/datamodel/connectors/dml/src/model.rs:494:29] Hi there! We've been seeing this error in our error reporting backend, but cannot reproduce it in our own tests. The problem is that we have a primary key in the model `addressAttributesString` that uses the column `productId` which we for some reason don't have in our internal representation. If you see this, could you please file an issue to https://github.com/prisma/prisma so we can discuss about fixing this. -- Your friendly prisma developers.
```
|
process
|
issue that occurred during prisma db pull hi prisma team prisma migrate just crashed command db pull versions name version platform darwin node prisma cli engine error error hi there we ve been seeing this error in our error reporting backend but cannot reproduce it in our own tests the problem is that we have a primary key in the model addressattributesstring that uses the column productid which we for some reason don t have in our internal representation if you see this could you please file an issue to so we can discuss about fixing this your friendly prisma developers
| 1
|
139,966
| 11,300,300,659
|
IssuesEvent
|
2020-01-17 13:19:09
|
opentracing-contrib/java-specialagent
|
https://api.github.com/repos/opentracing-contrib/java-specialagent
|
closed
|
Improve test module structure
|
1 request test
|
Currently, the module structure under `/test` is flat. This organization is convenient, because it does not require an additional layer of module indirection, thus reducing overall code complexity. One disadvantage, however, is that this design pushes the complexity of "grouping of tests" into `test/pom.xml` and into `.travis.yml`. When migrating to GitHub Actions (#312) or Circle CI (#344), this modular structure would require the complexity to be replicated in each respective CI system's configuration.
A better approach would be to adopt a modular structure that is hierarchical, thus automatically absorbing the "grouping of tests" complexity in the structure itself.
|
1.0
|
Improve test module structure - Currently, the module structure under `/test` is flat. This organization is convenient, because it does not require an additional layer of module indirection, thus reducing overall code complexity. One disadvantage, however, is that this design pushes the complexity of "grouping of tests" into `test/pom.xml` and into `.travis.yml`. When migrating to GitHub Actions (#312) or Circle CI (#344), this modular structure would require the complexity to be replicated in each respective CI system's configuration.
A better approach would be to adopt a modular structure that is hierarchical, thus automatically absorbing the "grouping of tests" complexity in the structure itself.
|
non_process
|
improve test module structure currently the module structure under test is flat this organization is convenient because it does not require an additional layer of module indirection thus reducing overall code complexity one disadvantage however is that this design pushes the complexity of grouping of tests into test pom xml and into travis yml when migrating to github actions or circle ci this modular structure would require the complexity to be replicated in each respective ci system s configuration a better approach would be to adopt a modular structure that is hierarchical thus automatically absorbing the grouping of tests complexity in the structure itself
| 0
|
165,879
| 6,287,559,816
|
IssuesEvent
|
2017-07-19 15:11:31
|
OperationCode/operationcode_frontend
|
https://api.github.com/repos/OperationCode/operationcode_frontend
|
closed
|
Incorrect confirm password validation text
|
in progress Priority: Medium Status: In Progress Type: Bug
|
# Bug Report
## What is the current behavior?
The second password field on the signup form (for confirmation) says "Must be 6 characters long and include a capitalized letter" when its validation fails
## What is the expected behavior?
When the two passwords don't match, the confirm password field should instead say something like "Passwords must match"
## What steps did you take to get this behavior?
Enter two different passwords into the signup form fields (which each meet the 6 characters & capital letter criteria)
## Additional Info
### Operating System
### Browser
### Screenshots
|
1.0
|
Incorrect confirm password validation text - # Bug Report
## What is the current behavior?
The second password field on the signup form (for confirmation) says "Must be 6 characters long and include a capitalized letter" when its validation fails
## What is the expected behavior?
When the two passwords don't match, the confirm password field should instead say something like "Passwords must match"
## What steps did you take to get this behavior?
Enter two different passwords into the signup form fields (which each meet the 6 characters & capital letter criteria)
## Additional Info
### Operating System
### Browser
### Screenshots
|
non_process
|
incorrect confirm password validation text bug report what is the current behavior the second password field on the signup form for confirmation says must be characters long and include a capitalized letter when its validation fails what is the expected behavior when the two passwords don t match the confirm password field should instead say something like passwords must match what steps did you take to get this behavior enter two different passwords into the signup form fields which each meet the characters capital letter criteria additional info operating system browser screenshots
| 0
|
14,785
| 18,062,041,986
|
IssuesEvent
|
2021-09-20 14:54:45
|
monetr/rest-api
|
https://api.github.com/repos/monetr/rest-api
|
opened
|
jobs: Panics are not handled or well reported within jobs.
|
bug Job Processing
|
Jobs are crashing but the only indication that they are failing is a log entry. Nothing is being sent to sentry because its a panic not just a regular error.
Need to make sure that these types of failures manifest in better ways and that there is a way to discover them easily.
|
1.0
|
jobs: Panics are not handled or well reported within jobs. - 
Jobs are crashing but the only indication that they are failing is a log entry. Nothing is being sent to sentry because its a panic not just a regular error.
Need to make sure that these types of failures manifest in better ways and that there is a way to discover them easily.
|
process
|
jobs panics are not handled or well reported within jobs jobs are crashing but the only indication that they are failing is a log entry nothing is being sent to sentry because its a panic not just a regular error need to make sure that these types of failures manifest in better ways and that there is a way to discover them easily
| 1
|
5,631
| 8,483,261,952
|
IssuesEvent
|
2018-10-25 21:00:41
|
material-components/material-components-ios
|
https://api.github.com/repos/material-components/material-components-ios
|
closed
|
Internal issue: b/117280582
|
Internal [TextFields] type:Process
|
This is an internal issue. If you are a Googler, please visit [b/117280582](http://b/117280582) for more details.
<!-- Auto-generated content below, do not modify -->
---
#### Internal data
- Associated internal bug: [b/117280582](http://b/117280582)
- Blocked by: https://github.com/material-components/material-components-ios/issues/5306
|
1.0
|
Internal issue: b/117280582 - This is an internal issue. If you are a Googler, please visit [b/117280582](http://b/117280582) for more details.
<!-- Auto-generated content below, do not modify -->
---
#### Internal data
- Associated internal bug: [b/117280582](http://b/117280582)
- Blocked by: https://github.com/material-components/material-components-ios/issues/5306
|
process
|
internal issue b this is an internal issue if you are a googler please visit for more details internal data associated internal bug blocked by
| 1
|
460,351
| 13,208,606,119
|
IssuesEvent
|
2020-08-15 05:58:05
|
Breadkenty/Smash_Combos
|
https://api.github.com/repos/Breadkenty/Smash_Combos
|
opened
|
Make the the static HTML dynamic with the database
|
Priority enhancement
|
After the backend and static HTML is set up, we can start plugging in data to make these changes dynamic.
- [ ] Drive the `Reports` page from data
- [ ] Drive the `User` page's combos from data
- [ ] Drive the `Reports` on the `User` page from data
- [ ] Drive the `Infractions` on the `User` page from data
- [ ] Users should only be able to report once. Disable the button, if the report already exists
- [ ] The report's useState object should be in this JSON format
{
userId: Id of the user being reported,
reporterId: Id of the user reporting,
comboId: Id of the combo that was reported (if reported on a comment, this will be null),
commentId: Id of the comment that was reported (if reported on a combo, this will be null),
body: "THIS COMBO WAS UNCALLED FOR!",
}
- [ ] The infraction useState object should be in this JSON format
#### a user getting banned
```
{
userId: Id of the user being infracted,
moderatorId: Id of the moderator infracting,
IsBan: true
banDuration: "2 days",
type: "inappropriate",
body: "Inappropriate post for PK Blazing Butthole",
}
```
`banDuration` (I'm thinking of setting this up in the controller based on the string value for `banDuration`.
`"2 Days"` = 172800s
`"1 Week"` = 604800s
`"2 weeks"` = 1209600s
`"1 month"` = 2419200s
`"Permanent"` = infinite
#### a user getting warned
```
{
userId: Id of the user being infracted,
moderatorId: Id of the moderator infracting,
IsBan: false
banDuration: null;
type: "spam",
body: "Spamming the same combos",
}
```
Looking to expand this list. thinking about removing other so mods will not be able to abuse the point system.
`spam` = `1` point
`inappropriate` = `1` point
`harassment` = `2` points
`other` = `custom?` points
|
1.0
|
Make the the static HTML dynamic with the database - After the backend and static HTML is set up, we can start plugging in data to make these changes dynamic.
- [ ] Drive the `Reports` page from data
- [ ] Drive the `User` page's combos from data
- [ ] Drive the `Reports` on the `User` page from data
- [ ] Drive the `Infractions` on the `User` page from data
- [ ] Users should only be able to report once. Disable the button, if the report already exists
- [ ] The report's useState object should be in this JSON format
{
userId: Id of the user being reported,
reporterId: Id of the user reporting,
comboId: Id of the combo that was reported (if reported on a comment, this will be null),
commentId: Id of the comment that was reported (if reported on a combo, this will be null),
body: "THIS COMBO WAS UNCALLED FOR!",
}
- [ ] The infraction useState object should be in this JSON format
#### a user getting banned
```
{
userId: Id of the user being infracted,
moderatorId: Id of the moderator infracting,
IsBan: true
banDuration: "2 days",
type: "inappropriate",
body: "Inappropriate post for PK Blazing Butthole",
}
```
`banDuration` (I'm thinking of setting this up in the controller based on the string value for `banDuration`.
`"2 Days"` = 172800s
`"1 Week"` = 604800s
`"2 weeks"` = 1209600s
`"1 month"` = 2419200s
`"Permanent"` = infinite
#### a user getting warned
```
{
userId: Id of the user being infracted,
moderatorId: Id of the moderator infracting,
IsBan: false
banDuration: null;
type: "spam",
body: "Spamming the same combos",
}
```
Looking to expand this list. thinking about removing other so mods will not be able to abuse the point system.
`spam` = `1` point
`inappropriate` = `1` point
`harassment` = `2` points
`other` = `custom?` points
|
non_process
|
make the the static html dynamic with the database after the backend and static html is set up we can start plugging in data to make these changes dynamic drive the reports page from data drive the user page s combos from data drive the reports on the user page from data drive the infractions on the user page from data users should only be able to report once disable the button if the report already exists the report s usestate object should be in this json format userid id of the user being reported reporterid id of the user reporting comboid id of the combo that was reported if reported on a comment this will be null commentid id of the comment that was reported if reported on a combo this will be null body this combo was uncalled for the infraction usestate object should be in this json format a user getting banned userid id of the user being infracted moderatorid id of the moderator infracting isban true banduration days type inappropriate body inappropriate post for pk blazing butthole banduration i m thinking of setting this up in the controller based on the string value for banduration days week weeks month permanent infinite a user getting warned userid id of the user being infracted moderatorid id of the moderator infracting isban false banduration null type spam body spamming the same combos looking to expand this list thinking about removing other so mods will not be able to abuse the point system spam point inappropriate point harassment points other custom points
| 0
|
11,047
| 13,866,729,762
|
IssuesEvent
|
2020-10-16 07:19:45
|
pingcap/tidb
|
https://api.github.com/repos/pingcap/tidb
|
closed
|
Add unit test for Copr Cache in TiDB side
|
component/coprocessor epic/copr-cache feature/accepted status/TODO type/enhancement
|
## Development Task
Currently, Copr Cache has no related unit test in TiDB side.
We may need to implement Copr Cache protocol in mocktikv or unistore then write the unit test for it.
|
1.0
|
Add unit test for Copr Cache in TiDB side - ## Development Task
Currently, Copr Cache has no related unit test in TiDB side.
We may need to implement Copr Cache protocol in mocktikv or unistore then write the unit test for it.
|
process
|
add unit test for copr cache in tidb side development task currently copr cache has no related unit test in tidb side we may need to implement copr cache protocol in mocktikv or unistore then write the unit test for it
| 1
|
10,034
| 13,044,161,495
|
IssuesEvent
|
2020-07-29 03:47:23
|
tikv/tikv
|
https://api.github.com/repos/tikv/tikv
|
closed
|
UCP: Migrate scalar function `AddDateDurationString` from TiDB
|
challenge-program-2 component/coprocessor difficulty/easy sig/coprocessor
|
## Description
Port the scalar function `AddDateDurationString` from TiDB to coprocessor.
## Score
* 50
## Mentor(s)
* @andylokandy
## Recommended Skills
* Rust programming
## Learning Materials
Already implemented expressions ported from TiDB
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)
|
2.0
|
UCP: Migrate scalar function `AddDateDurationString` from TiDB -
## Description
Port the scalar function `AddDateDurationString` from TiDB to coprocessor.
## Score
* 50
## Mentor(s)
* @andylokandy
## Recommended Skills
* Rust programming
## Learning Materials
Already implemented expressions ported from TiDB
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)
|
process
|
ucp migrate scalar function adddatedurationstring from tidb description port the scalar function adddatedurationstring from tidb to coprocessor score mentor s andylokandy recommended skills rust programming learning materials already implemented expressions ported from tidb
| 1
|
244,227
| 20,617,255,108
|
IssuesEvent
|
2022-03-07 14:21:53
|
distributed-system-analysis/pbench
|
https://api.github.com/repos/distributed-system-analysis/pbench
|
closed
|
Non-deterministic outcomes of Tool Meister tests under Jenkins
|
bug Agent Unit tests Tool Meister
|
Certain of the Tool Meister "unit tests" occasionally report errors ([example](http://jenkins.perf.lab.eng.bos.redhat.com/job/pbench-ci-multi/job/main/111/console)) like:
```
pbench-tool-meister-stop [...] failed to execute successfully.
```
|
1.0
|
Non-deterministic outcomes of Tool Meister tests under Jenkins - Certain of the Tool Meister "unit tests" occasionally report errors ([example](http://jenkins.perf.lab.eng.bos.redhat.com/job/pbench-ci-multi/job/main/111/console)) like:
```
pbench-tool-meister-stop [...] failed to execute successfully.
```
|
non_process
|
non deterministic outcomes of tool meister tests under jenkins certain of the tool meister unit tests occasionally report errors like pbench tool meister stop failed to execute successfully
| 0
|
7,580
| 10,694,825,192
|
IssuesEvent
|
2019-10-23 11:45:09
|
nodejs/citgm
|
https://api.github.com/repos/nodejs/citgm
|
closed
|
Execution of local bin scripts fails on Windows
|
Windows child_process weirdness good first issue
|
To reproduce:
```
citgm bufferutil
```
It cannot find `node-gyp-build`. Probably another PATH issue...
|
1.0
|
Execution of local bin scripts fails on Windows - To reproduce:
```
citgm bufferutil
```
It cannot find `node-gyp-build`. Probably another PATH issue...
|
process
|
execution of local bin scripts fails on windows to reproduce citgm bufferutil it cannot find node gyp build probably another path issue
| 1
|
53,504
| 6,332,816,396
|
IssuesEvent
|
2017-07-26 13:32:25
|
manchesergit/material-ui
|
https://api.github.com/repos/manchesergit/material-ui
|
closed
|
Test Step generates an ID
|
unit testing
|
Tests need to be added to prove that Step
- [x] produces a unique ID for itself if none is given
- [x] uses the ID given in the properties
|
1.0
|
Test Step generates an ID - Tests need to be added to prove that Step
- [x] produces a unique ID for itself if none is given
- [x] uses the ID given in the properties
|
non_process
|
test step generates an id tests need to be added to prove that step produces a unique id for itself if none is given uses the id given in the properties
| 0
|
308,213
| 9,436,308,307
|
IssuesEvent
|
2019-04-13 05:14:03
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
opened
|
web.skype.com - see bug description
|
browser-firefox priority-important
|
<!-- @browser: Firefox 66.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0 -->
<!-- @reported_with: web -->
**URL**: https://web.skype.com/
**Browser / Version**: Firefox 66.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Claims incompatibility with Firefox, despite working flawlessly when the UA String is changed to Chrome's.
**Steps to Reproduce**:
Navigate to the website on Firefox.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
web.skype.com - see bug description - <!-- @browser: Firefox 66.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0 -->
<!-- @reported_with: web -->
**URL**: https://web.skype.com/
**Browser / Version**: Firefox 66.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Claims incompatibility with Firefox, despite working flawlessly when the UA String is changed to Chrome's.
**Steps to Reproduce**:
Navigate to the website on Firefox.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_process
|
web skype com see bug description url browser version firefox operating system windows tested another browser yes problem type something else description claims incompatibility with firefox despite working flawlessly when the ua string is changed to chrome s steps to reproduce navigate to the website on firefox browser configuration none from with ❤️
| 0
|
97,432
| 28,290,224,951
|
IssuesEvent
|
2023-04-09 05:09:51
|
spack/spack
|
https://api.github.com/repos/spack/spack
|
opened
|
Installation issue: meson, py-attrs, ... (dependents of py-wheel)
|
build-error
|
### Steps to reproduce the issue
For example:
```console
$ spack spec -I py-attrs ^python~ctypes
Input spec
--------------------------------
- py-attrs
- ^python~ctypes
Concretized
--------------------------------
- py-attrs@22.2.0%gcc@11.3.0 build_system=python_pip arch=linux-ubuntu22.04-zen2
[+] ^py-pip@23.0%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^py-setuptools@67.6.0%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^py-wheel@0.37.1%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^python@3.10.10%gcc@11.3.0+bz2+crypt~ctypes+dbm~debug+libxml2+lzma~nis~optimizations+pic+pyexpat+pythoncmd+readline+shared+sqlite3+ssl~tkinter+uuid+zlib build_system=generic patches=0d98e93,7d40923,f2fd060 arch=linux-ubuntu22.04-zen2
[+] ^bzip2@1.0.8%gcc@11.3.0~debug~pic+shared build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^diffutils@3.9%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^expat@2.5.0%gcc@11.3.0+libbsd build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^libbsd@0.11.7%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^libmd@1.0.4%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^gdbm@1.23%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^gettext@0.21.1%gcc@11.3.0+bzip2+curses+git~libunistring+libxml2+tar+xz build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^libiconv@1.17%gcc@11.3.0 build_system=autotools libs=shared,static arch=linux-ubuntu22.04-zen2
[+] ^libxml2@2.10.3%gcc@11.3.0~python build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^tar@1.34%gcc@11.3.0 build_system=autotools zip=pigz arch=linux-ubuntu22.04-zen2
[+] ^pigz@2.7%gcc@11.3.0 build_system=makefile arch=linux-ubuntu22.04-zen2
[+] ^zstd@1.5.4%gcc@11.3.0+programs build_system=makefile compression=none libs=shared,static arch=linux-ubuntu22.04-zen2
[+] ^libxcrypt@4.4.33%gcc@11.3.0~obsolete_api build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^perl@5.36.0%gcc@11.3.0+cpanm+open+shared+threads build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^berkeley-db@18.1.40%gcc@11.3.0+cxx~docs+stl build_system=autotools patches=26090f4,b231fcc arch=linux-ubuntu22.04-zen2
[+] ^ncurses@6.4%gcc@11.3.0~symlinks+termlib abi=none build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^openssl@1.1.1t%gcc@11.3.0~docs~shared build_system=generic certs=mozilla arch=linux-ubuntu22.04-zen2
[+] ^ca-certificates-mozilla@2023-01-10%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^pkgconf@1.8.0%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^readline@8.2%gcc@11.3.0 build_system=autotools patches=bbf97f1 arch=linux-ubuntu22.04-zen2
[+] ^sqlite@3.40.1%gcc@11.3.0+column_metadata+dynamic_extensions+fts~functions+rtree build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^util-linux-uuid@2.38.1%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^xz@5.4.1%gcc@11.3.0~pic build_system=autotools libs=shared,static arch=linux-ubuntu22.04-zen2
[+] ^zlib@1.2.13%gcc@11.3.0+optimize+pic+shared build_system=makefile arch=linux-ubuntu22.04-zen2
```
### Error message
<details><summary>Error message</summary>
```
==> Installing py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap
==> No binary for py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap found: installing from source
==> Using cached archive: /root/spack/var/spack/cache/_source-cache/archive/c9/c9227bfc2f01993c03f68db37d1d15c9690188323c067c641f1a35ca58185f99.tar.gz
==> No patches needed for py-attrs
==> py-attrs: Executing phase: 'install'
==> Error: ProcessError: Command exited with status 1:
'/root/spack/opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/python-3.10.10-o2aqsvvrq4dypsdhslrmk3tg2xr5ilb6/bin/python3.10' '-m' 'pip' '-vvv' '--no-input' '--no-cache-dir' '--disable-pip-version-check' 'install' '--no-deps' '--ignore-installed' '--no-build-isolation' '--no-warn-script-location' '--no-index' '--prefix=/root/spack/opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap' '.'
1 error found in build log:
85 ╰─> See above for output.
86
87 note: This error originates from a subprocess, and is likely not a problem with pip.
88 full command: /root/spack/opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/python-3.10.10-o2aqsvvrq4dypsdhslrmk3tg2xr5ilb6/bin/python3.10 /root/spack/
opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/py-pip-23.0-575yxb23ooh3h5hpm3gsaxopgkimli77/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_
in_process/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpawirel9z
89 cwd: /tmp/root/spack-stage/spack-stage-py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap/spack-src
90 Preparing metadata (pyproject.toml): finished with status 'error'
>> 91 error: metadata-generation-failed
92
93 × Encountered error while generating package metadata.
94 ╰─> See above for output.
95
96 note: This is an issue with the package mentioned above, not pip.
97 hint: See above for details.
See build log for details:
/tmp/root/spack-stage/spack-stage-py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap/spack-build-out.txt
```
</details>
### Information on your system
* **Spack:** 0.20.0.dev0 (6de3786c36053f413595986e6a91b94e23b3e6b1)
* **Python:** 3.10.6
* **Platform:** linux-ubuntu22.04-zen2
* **Concretizer:** clingo
### Additional information
[spack-build-out.txt](https://github.com/spack/spack/files/11184827/spack-build-out.txt)
[spack-build-env.txt](https://github.com/spack/spack/files/11184828/spack-build-env.txt)
@adamjstewart @pradyunsg
### General information
- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate
|
1.0
|
Installation issue: meson, py-attrs, ... (dependents of py-wheel) - ### Steps to reproduce the issue
For example:
```console
$ spack spec -I py-attrs ^python~ctypes
Input spec
--------------------------------
- py-attrs
- ^python~ctypes
Concretized
--------------------------------
- py-attrs@22.2.0%gcc@11.3.0 build_system=python_pip arch=linux-ubuntu22.04-zen2
[+] ^py-pip@23.0%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^py-setuptools@67.6.0%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^py-wheel@0.37.1%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^python@3.10.10%gcc@11.3.0+bz2+crypt~ctypes+dbm~debug+libxml2+lzma~nis~optimizations+pic+pyexpat+pythoncmd+readline+shared+sqlite3+ssl~tkinter+uuid+zlib build_system=generic patches=0d98e93,7d40923,f2fd060 arch=linux-ubuntu22.04-zen2
[+] ^bzip2@1.0.8%gcc@11.3.0~debug~pic+shared build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^diffutils@3.9%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^expat@2.5.0%gcc@11.3.0+libbsd build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^libbsd@0.11.7%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^libmd@1.0.4%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^gdbm@1.23%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^gettext@0.21.1%gcc@11.3.0+bzip2+curses+git~libunistring+libxml2+tar+xz build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^libiconv@1.17%gcc@11.3.0 build_system=autotools libs=shared,static arch=linux-ubuntu22.04-zen2
[+] ^libxml2@2.10.3%gcc@11.3.0~python build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^tar@1.34%gcc@11.3.0 build_system=autotools zip=pigz arch=linux-ubuntu22.04-zen2
[+] ^pigz@2.7%gcc@11.3.0 build_system=makefile arch=linux-ubuntu22.04-zen2
[+] ^zstd@1.5.4%gcc@11.3.0+programs build_system=makefile compression=none libs=shared,static arch=linux-ubuntu22.04-zen2
[+] ^libxcrypt@4.4.33%gcc@11.3.0~obsolete_api build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^perl@5.36.0%gcc@11.3.0+cpanm+open+shared+threads build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^berkeley-db@18.1.40%gcc@11.3.0+cxx~docs+stl build_system=autotools patches=26090f4,b231fcc arch=linux-ubuntu22.04-zen2
[+] ^ncurses@6.4%gcc@11.3.0~symlinks+termlib abi=none build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^openssl@1.1.1t%gcc@11.3.0~docs~shared build_system=generic certs=mozilla arch=linux-ubuntu22.04-zen2
[+] ^ca-certificates-mozilla@2023-01-10%gcc@11.3.0 build_system=generic arch=linux-ubuntu22.04-zen2
[+] ^pkgconf@1.8.0%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^readline@8.2%gcc@11.3.0 build_system=autotools patches=bbf97f1 arch=linux-ubuntu22.04-zen2
[+] ^sqlite@3.40.1%gcc@11.3.0+column_metadata+dynamic_extensions+fts~functions+rtree build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^util-linux-uuid@2.38.1%gcc@11.3.0 build_system=autotools arch=linux-ubuntu22.04-zen2
[+] ^xz@5.4.1%gcc@11.3.0~pic build_system=autotools libs=shared,static arch=linux-ubuntu22.04-zen2
[+] ^zlib@1.2.13%gcc@11.3.0+optimize+pic+shared build_system=makefile arch=linux-ubuntu22.04-zen2
```
### Error message
<details><summary>Error message</summary>
```
==> Installing py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap
==> No binary for py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap found: installing from source
==> Using cached archive: /root/spack/var/spack/cache/_source-cache/archive/c9/c9227bfc2f01993c03f68db37d1d15c9690188323c067c641f1a35ca58185f99.tar.gz
==> No patches needed for py-attrs
==> py-attrs: Executing phase: 'install'
==> Error: ProcessError: Command exited with status 1:
'/root/spack/opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/python-3.10.10-o2aqsvvrq4dypsdhslrmk3tg2xr5ilb6/bin/python3.10' '-m' 'pip' '-vvv' '--no-input' '--no-cache-dir' '--disable-pip-version-check' 'install' '--no-deps' '--ignore-installed' '--no-build-isolation' '--no-warn-script-location' '--no-index' '--prefix=/root/spack/opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap' '.'
1 error found in build log:
85 ╰─> See above for output.
86
87 note: This error originates from a subprocess, and is likely not a problem with pip.
88 full command: /root/spack/opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/python-3.10.10-o2aqsvvrq4dypsdhslrmk3tg2xr5ilb6/bin/python3.10 /root/spack/
opt/spack/linux-ubuntu22.04-zen2/gcc-11.3.0/py-pip-23.0-575yxb23ooh3h5hpm3gsaxopgkimli77/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_
in_process/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpawirel9z
89 cwd: /tmp/root/spack-stage/spack-stage-py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap/spack-src
90 Preparing metadata (pyproject.toml): finished with status 'error'
>> 91 error: metadata-generation-failed
92
93 × Encountered error while generating package metadata.
94 ╰─> See above for output.
95
96 note: This is an issue with the package mentioned above, not pip.
97 hint: See above for details.
See build log for details:
/tmp/root/spack-stage/spack-stage-py-attrs-22.2.0-ykvlmh2bdqek2k62ho7txur732khelap/spack-build-out.txt
```
</details>
### Information on your system
* **Spack:** 0.20.0.dev0 (6de3786c36053f413595986e6a91b94e23b3e6b1)
* **Python:** 3.10.6
* **Platform:** linux-ubuntu22.04-zen2
* **Concretizer:** clingo
### Additional information
[spack-build-out.txt](https://github.com/spack/spack/files/11184827/spack-build-out.txt)
[spack-build-env.txt](https://github.com/spack/spack/files/11184828/spack-build-env.txt)
@adamjstewart @pradyunsg
### General information
- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate
|
non_process
|
installation issue meson py attrs dependents of py wheel steps to reproduce the issue for example console spack spec i py attrs python ctypes input spec py attrs python ctypes concretized py attrs gcc build system python pip arch linux py pip gcc build system generic arch linux py setuptools gcc build system generic arch linux py wheel gcc build system generic arch linux python gcc crypt ctypes dbm debug lzma nis optimizations pic pyexpat pythoncmd readline shared ssl tkinter uuid zlib build system generic patches arch linux gcc debug pic shared build system generic arch linux diffutils gcc build system autotools arch linux expat gcc libbsd build system autotools arch linux libbsd gcc build system autotools arch linux libmd gcc build system autotools arch linux gdbm gcc build system autotools arch linux gettext gcc curses git libunistring tar xz build system autotools arch linux libiconv gcc build system autotools libs shared static arch linux gcc python build system autotools arch linux tar gcc build system autotools zip pigz arch linux pigz gcc build system makefile arch linux zstd gcc programs build system makefile compression none libs shared static arch linux libxcrypt gcc obsolete api build system autotools arch linux perl gcc cpanm open shared threads build system generic arch linux berkeley db gcc cxx docs stl build system autotools patches arch linux ncurses gcc symlinks termlib abi none build system autotools arch linux openssl gcc docs shared build system generic certs mozilla arch linux ca certificates mozilla gcc build system generic arch linux pkgconf gcc build system autotools arch linux readline gcc build system autotools patches arch linux sqlite gcc column metadata dynamic extensions fts functions rtree build system autotools arch linux util linux uuid gcc build system autotools arch linux xz gcc pic build system autotools libs shared static arch linux zlib gcc optimize pic shared build system makefile arch linux error message error message installing py attrs no binary for py attrs found installing from source using cached archive root spack var spack cache source cache archive tar gz no patches needed for py attrs py attrs executing phase install error processerror command exited with status root spack opt spack linux gcc python bin m pip vvv no input no cache dir disable pip version check install no deps ignore installed no build isolation no warn script location no index prefix root spack opt spack linux gcc py attrs error found in build log ╰─ see above for output note this error originates from a subprocess and is likely not a problem with pip full command root spack opt spack linux gcc python bin root spack opt spack linux gcc py pip lib site packages pip vendor pyproject hooks in process in process py prepare metadata for build wheel tmp cwd tmp root spack stage spack stage py attrs spack src preparing metadata pyproject toml finished with status error error metadata generation failed × encountered error while generating package metadata ╰─ see above for output note this is an issue with the package mentioned above not pip hint see above for details see build log for details tmp root spack stage spack stage py attrs spack build out txt information on your system spack python platform linux concretizer clingo additional information adamjstewart pradyunsg general information i have run spack debug report and reported the version of spack python platform i have run spack maintainers and mentioned any maintainers i have uploaded the build log and environment files i have searched the issues of this repo and believe this is not a duplicate
| 0
|
14,925
| 18,359,529,539
|
IssuesEvent
|
2021-10-09 01:45:53
|
DevExpress/testcafe-hammerhead
|
https://api.github.com/repos/DevExpress/testcafe-hammerhead
|
closed
|
Strange behavior in IE11
|
TYPE: bug SYSTEM: URL processing AREA: server BROWSER: IE11 FREQUENCY: level 1 STATE: Stale
|
Site: https://getbootstrap.com/docs/4.2/components/buttons/
```
https:/getbootstrap.com/docs/4.2/dist/css/bootstrap.min.css
(node:19220) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
at new ClientRequest (_http_client.js:119:11)
at Object.request (http.js:42:10)
at Domain.<anonymous> (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:93:47)
at Domain.run (domain.js:342:14)
at exports.default (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\connection-reset-guard.js:6:27)
at DestinationRequest._send (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:85:44)
at new DestinationRequest (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:81:14)
at resolve (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\utils.js:267:83)
at new Promise (<anonymous>)
at sendRequest (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\utils.js:266:12)
(node:19220) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)
```
The error occurs if I open the site in the playground in IE11 with the opened Developer Tools. However, everything operates correctly when Developer Tools are not opened.
I don't know how the browser sends the second request, but it fails because the URL has only one slash after a protocol.
|
1.0
|
Strange behavior in IE11 - Site: https://getbootstrap.com/docs/4.2/components/buttons/
```
https:/getbootstrap.com/docs/4.2/dist/css/bootstrap.min.css
(node:19220) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
at new ClientRequest (_http_client.js:119:11)
at Object.request (http.js:42:10)
at Domain.<anonymous> (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:93:47)
at Domain.run (domain.js:342:14)
at exports.default (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\connection-reset-guard.js:6:27)
at DestinationRequest._send (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:85:44)
at new DestinationRequest (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:81:14)
at resolve (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\utils.js:267:83)
at new Promise (<anonymous>)
at sendRequest (C:\Users\lavrov.artem\Documents\Projects\testcafe-hammerhead\lib\request-pipeline\utils.js:266:12)
(node:19220) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)
```
The error occurs if I open the site in the playground in IE11 with the opened Developer Tools. However, everything operates correctly when Developer Tools are not opened.
I don't know how the browser sends the second request, but it fails because the URL has only one slash after a protocol.
|
process
|
strange behavior in site https getbootstrap com docs dist css bootstrap min css node unhandledpromiserejectionwarning typeerror protocol http not supported expected https at new clientrequest http client js at object request http js at domain c users lavrov artem documents projects testcafe hammerhead lib request pipeline destination request index js at domain run domain js at exports default c users lavrov artem documents projects testcafe hammerhead lib request pipeline connection reset guard js at destinationrequest send c users lavrov artem documents projects testcafe hammerhead lib request pipeline destination request index js at new destinationrequest c users lavrov artem documents projects testcafe hammerhead lib request pipeline destination request index js at resolve c users lavrov artem documents projects testcafe hammerhead lib request pipeline utils js at new promise at sendrequest c users lavrov artem documents projects testcafe hammerhead lib request pipeline utils js node unhandledpromiserejectionwarning unhandled promise rejection this error originated either by throwing inside of an async function without a catch block or by rejecting a promise which was not handled with catch rejection id the error occurs if i open the site in the playground in with the opened developer tools however everything operates correctly when developer tools are not opened i don t know how the browser sends the second request but it fails because the url has only one slash after a protocol
| 1
|
7,599
| 10,707,565,612
|
IssuesEvent
|
2019-10-24 17:45:20
|
googleapis/google-cloud-python
|
https://api.github.com/repos/googleapis/google-cloud-python
|
opened
|
Bigtable: systest module setup flakes creating clusters.
|
api: bigtable flaky testing type: process
|
From [this CI failure](https://source.cloud.google.com/results/invocations/28bd6c2f-e092-432c-b7f8-4e8b6bf8b0d7/targets/cloud-devrel%2Fclient-libraries%2Fgoogle-cloud-python%2Fpresubmit%2Fbigtable/log):
```python
__________ ERROR at setup of TestInstanceAdminAPI.test_cluster_exists __________
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fb0249bc488>
sleep_generator = <generator object exponential_sleep_generator at 0x7fb024880930>
deadline = 10, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target.
on_error (Callable): A function to call while processing a retryable
exception. Any error raised by this function will *not* be
caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
> return target()
../api_core/google/api_core/retry.py:182:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fb024845240>
def _done_or_raise(self):
"""Check if the future is done and raise if it's not."""
if not self.done():
> raise _OperationNotComplete()
E google.api_core.future.polling._OperationNotComplete
../api_core/google/api_core/future/polling.py:81: _OperationNotComplete
The above exception was the direct cause of the following exception:
self = <google.api_core.operation.Operation object at 0x7fb024845240>
timeout = 10
def _blocking_poll(self, timeout=None):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
> retry_(self._done_or_raise)()
../api_core/google/api_core/future/polling.py:101:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
args = (), kwargs = {}
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>)
sleep_generator = <generator object exponential_sleep_generator at 0x7fb024880930>
@general_helpers.wraps(func)
def retry_wrapped_func(*args, **kwargs):
"""A wrapper that calls target function with retry."""
target = functools.partial(func, *args, **kwargs)
sleep_generator = exponential_sleep_generator(
self._initial, self._maximum, multiplier=self._multiplier
)
return retry_target(
target,
self._predicate,
sleep_generator,
self._deadline,
> on_error=on_error,
)
../api_core/google/api_core/retry.py:277:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fb0249bc488>
sleep_generator = <generator object exponential_sleep_generator at 0x7fb024880930>
deadline = 10, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target.
on_error (Callable): A function to call while processing a retryable
exception. Any error raised by this function will *not* be
caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
return target()
# pylint: disable=broad-except
# This function explicitly must deal with broad exceptions.
except Exception as exc:
if not predicate(exc):
raise
last_exc = exc
if on_error is not None:
on_error(exc)
now = datetime_helpers.utcnow()
if deadline_datetime is not None and deadline_datetime < now:
six.raise_from(
exceptions.RetryError(
"Deadline of {:.1f}s exceeded while calling {}".format(
deadline, target
),
last_exc,
),
> last_exc,
)
../api_core/google/api_core/retry.py:202:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = None, from_value = _OperationNotComplete()
> ???
E google.api_core.exceptions.RetryError: Deadline of 10.0s exceeded while calling functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>), last exception:
<string>:3: RetryError
During handling of the above exception, another exception occurred:
def setUpModule():
from google.cloud.exceptions import GrpcRendezvous
from google.cloud.bigtable.enums import Instance
# See: https://github.com/googleapis/google-cloud-python/issues/5928
interfaces = table_admin_config.config["interfaces"]
iface_config = interfaces["google.bigtable.admin.v2.BigtableTableAdmin"]
methods = iface_config["methods"]
create_table = methods["CreateTable"]
create_table["timeout_millis"] = 90000
Config.IN_EMULATOR = os.getenv(BIGTABLE_EMULATOR) is not None
if Config.IN_EMULATOR:
credentials = EmulatorCreds()
Config.CLIENT = Client(admin=True, credentials=credentials)
else:
Config.CLIENT = Client(admin=True)
Config.INSTANCE = Config.CLIENT.instance(INSTANCE_ID, labels=LABELS)
Config.CLUSTER = Config.INSTANCE.cluster(
CLUSTER_ID, location_id=LOCATION_ID, serve_nodes=SERVE_NODES
)
Config.INSTANCE_DATA = Config.CLIENT.instance(
INSTANCE_ID_DATA, instance_type=Instance.Type.DEVELOPMENT, labels=LABELS
)
Config.CLUSTER_DATA = Config.INSTANCE_DATA.cluster(
CLUSTER_ID_DATA, location_id=LOCATION_ID
)
if not Config.IN_EMULATOR:
retry = RetryErrors(GrpcRendezvous, error_predicate=_retry_on_unavailable)
instances, failed_locations = retry(Config.CLIENT.list_instances)()
if len(failed_locations) != 0:
raise ValueError("List instances failed in module set up.")
EXISTING_INSTANCES[:] = instances
# After listing, create the test instances.
admin_op = Config.INSTANCE.create(clusters=[Config.CLUSTER])
admin_op.result(timeout=10)
data_op = Config.INSTANCE_DATA.create(clusters=[Config.CLUSTER_DATA])
> data_op.result(timeout=10)
tests/system.py:141:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../api_core/google/api_core/future/polling.py:122: in result
self._blocking_poll(timeout=timeout)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fb024845240>
timeout = 10
def _blocking_poll(self, timeout=None):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
retry_(self._done_or_raise)()
except exceptions.RetryError:
raise concurrent.futures.TimeoutError(
> "Operation did not complete within the designated " "timeout."
)
E concurrent.futures._base.TimeoutError: Operation did not complete within the designated timeout.
../api_core/google/api_core/future/polling.py:104: TimeoutError
```
Repeated multiple times.
|
1.0
|
Bigtable: systest module setup flakes creating clusters. - From [this CI failure](https://source.cloud.google.com/results/invocations/28bd6c2f-e092-432c-b7f8-4e8b6bf8b0d7/targets/cloud-devrel%2Fclient-libraries%2Fgoogle-cloud-python%2Fpresubmit%2Fbigtable/log):
```python
__________ ERROR at setup of TestInstanceAdminAPI.test_cluster_exists __________
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fb0249bc488>
sleep_generator = <generator object exponential_sleep_generator at 0x7fb024880930>
deadline = 10, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target.
on_error (Callable): A function to call while processing a retryable
exception. Any error raised by this function will *not* be
caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
> return target()
../api_core/google/api_core/retry.py:182:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fb024845240>
def _done_or_raise(self):
"""Check if the future is done and raise if it's not."""
if not self.done():
> raise _OperationNotComplete()
E google.api_core.future.polling._OperationNotComplete
../api_core/google/api_core/future/polling.py:81: _OperationNotComplete
The above exception was the direct cause of the following exception:
self = <google.api_core.operation.Operation object at 0x7fb024845240>
timeout = 10
def _blocking_poll(self, timeout=None):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
> retry_(self._done_or_raise)()
../api_core/google/api_core/future/polling.py:101:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
args = (), kwargs = {}
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>)
sleep_generator = <generator object exponential_sleep_generator at 0x7fb024880930>
@general_helpers.wraps(func)
def retry_wrapped_func(*args, **kwargs):
"""A wrapper that calls target function with retry."""
target = functools.partial(func, *args, **kwargs)
sleep_generator = exponential_sleep_generator(
self._initial, self._maximum, multiplier=self._multiplier
)
return retry_target(
target,
self._predicate,
sleep_generator,
self._deadline,
> on_error=on_error,
)
../api_core/google/api_core/retry.py:277:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fb0249bc488>
sleep_generator = <generator object exponential_sleep_generator at 0x7fb024880930>
deadline = 10, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target.
on_error (Callable): A function to call while processing a retryable
exception. Any error raised by this function will *not* be
caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
return target()
# pylint: disable=broad-except
# This function explicitly must deal with broad exceptions.
except Exception as exc:
if not predicate(exc):
raise
last_exc = exc
if on_error is not None:
on_error(exc)
now = datetime_helpers.utcnow()
if deadline_datetime is not None and deadline_datetime < now:
six.raise_from(
exceptions.RetryError(
"Deadline of {:.1f}s exceeded while calling {}".format(
deadline, target
),
last_exc,
),
> last_exc,
)
../api_core/google/api_core/retry.py:202:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = None, from_value = _OperationNotComplete()
> ???
E google.api_core.exceptions.RetryError: Deadline of 10.0s exceeded while calling functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fb024845240>>), last exception:
<string>:3: RetryError
During handling of the above exception, another exception occurred:
def setUpModule():
from google.cloud.exceptions import GrpcRendezvous
from google.cloud.bigtable.enums import Instance
# See: https://github.com/googleapis/google-cloud-python/issues/5928
interfaces = table_admin_config.config["interfaces"]
iface_config = interfaces["google.bigtable.admin.v2.BigtableTableAdmin"]
methods = iface_config["methods"]
create_table = methods["CreateTable"]
create_table["timeout_millis"] = 90000
Config.IN_EMULATOR = os.getenv(BIGTABLE_EMULATOR) is not None
if Config.IN_EMULATOR:
credentials = EmulatorCreds()
Config.CLIENT = Client(admin=True, credentials=credentials)
else:
Config.CLIENT = Client(admin=True)
Config.INSTANCE = Config.CLIENT.instance(INSTANCE_ID, labels=LABELS)
Config.CLUSTER = Config.INSTANCE.cluster(
CLUSTER_ID, location_id=LOCATION_ID, serve_nodes=SERVE_NODES
)
Config.INSTANCE_DATA = Config.CLIENT.instance(
INSTANCE_ID_DATA, instance_type=Instance.Type.DEVELOPMENT, labels=LABELS
)
Config.CLUSTER_DATA = Config.INSTANCE_DATA.cluster(
CLUSTER_ID_DATA, location_id=LOCATION_ID
)
if not Config.IN_EMULATOR:
retry = RetryErrors(GrpcRendezvous, error_predicate=_retry_on_unavailable)
instances, failed_locations = retry(Config.CLIENT.list_instances)()
if len(failed_locations) != 0:
raise ValueError("List instances failed in module set up.")
EXISTING_INSTANCES[:] = instances
# After listing, create the test instances.
admin_op = Config.INSTANCE.create(clusters=[Config.CLUSTER])
admin_op.result(timeout=10)
data_op = Config.INSTANCE_DATA.create(clusters=[Config.CLUSTER_DATA])
> data_op.result(timeout=10)
tests/system.py:141:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../api_core/google/api_core/future/polling.py:122: in result
self._blocking_poll(timeout=timeout)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fb024845240>
timeout = 10
def _blocking_poll(self, timeout=None):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
retry_(self._done_or_raise)()
except exceptions.RetryError:
raise concurrent.futures.TimeoutError(
> "Operation did not complete within the designated " "timeout."
)
E concurrent.futures._base.TimeoutError: Operation did not complete within the designated timeout.
../api_core/google/api_core/future/polling.py:104: TimeoutError
```
Repeated multiple times.
|
process
|
bigtable systest module setup flakes creating clusters from python error at setup of testinstanceadminapi test cluster exists target functools partial predicate if exception type predicate at sleep generator deadline on error none def retry target target predicate sleep generator deadline on error none call a function and retry if it fails this is the lowest level retry helper generally you ll use the higher level retry helper class retry args target callable the function to call and retry this must be a nullary function apply arguments with functools partial predicate callable a callable used to determine if an exception raised by the target should be considered retryable it should return true to retry or false otherwise sleep generator iterable an infinite iterator that determines how long to sleep between retries deadline float how long to keep retrying the target on error callable a function to call while processing a retryable exception any error raised by this function will not be caught returns any the return value of the target function raises google api core retryerror if the deadline is exceeded while retrying valueerror if the sleep generator stops yielding values exception if the target raises a method that isn t retryable if deadline is not none deadline datetime datetime helpers utcnow datetime timedelta seconds deadline else deadline datetime none last exc none for sleep in sleep generator try return target api core google api core retry py self def done or raise self check if the future is done and raise if it s not if not self done raise operationnotcomplete e google api core future polling operationnotcomplete api core google api core future polling py operationnotcomplete the above exception was the direct cause of the following exception self timeout def blocking poll self timeout none poll and wait for the future to be resolved args timeout int how long in seconds to wait for the operation to complete if none wait indefinitely if self result set return retry self retry with deadline timeout try retry self done or raise api core google api core future polling py args kwargs target functools partial sleep generator general helpers wraps func def retry wrapped func args kwargs a wrapper that calls target function with retry target functools partial func args kwargs sleep generator exponential sleep generator self initial self maximum multiplier self multiplier return retry target target self predicate sleep generator self deadline on error on error api core google api core retry py target functools partial predicate if exception type predicate at sleep generator deadline on error none def retry target target predicate sleep generator deadline on error none call a function and retry if it fails this is the lowest level retry helper generally you ll use the higher level retry helper class retry args target callable the function to call and retry this must be a nullary function apply arguments with functools partial predicate callable a callable used to determine if an exception raised by the target should be considered retryable it should return true to retry or false otherwise sleep generator iterable an infinite iterator that determines how long to sleep between retries deadline float how long to keep retrying the target on error callable a function to call while processing a retryable exception any error raised by this function will not be caught returns any the return value of the target function raises google api core retryerror if the deadline is exceeded while retrying valueerror if the sleep generator stops yielding values exception if the target raises a method that isn t retryable if deadline is not none deadline datetime datetime helpers utcnow datetime timedelta seconds deadline else deadline datetime none last exc none for sleep in sleep generator try return target pylint disable broad except this function explicitly must deal with broad exceptions except exception as exc if not predicate exc raise last exc exc if on error is not none on error exc now datetime helpers utcnow if deadline datetime is not none and deadline datetime now six raise from exceptions retryerror deadline of s exceeded while calling format deadline target last exc last exc api core google api core retry py value none from value operationnotcomplete e google api core exceptions retryerror deadline of exceeded while calling functools partial last exception retryerror during handling of the above exception another exception occurred def setupmodule from google cloud exceptions import grpcrendezvous from google cloud bigtable enums import instance see interfaces table admin config config iface config interfaces methods iface config create table methods create table config in emulator os getenv bigtable emulator is not none if config in emulator credentials emulatorcreds config client client admin true credentials credentials else config client client admin true config instance config client instance instance id labels labels config cluster config instance cluster cluster id location id location id serve nodes serve nodes config instance data config client instance instance id data instance type instance type development labels labels config cluster data config instance data cluster cluster id data location id location id if not config in emulator retry retryerrors grpcrendezvous error predicate retry on unavailable instances failed locations retry config client list instances if len failed locations raise valueerror list instances failed in module set up existing instances instances after listing create the test instances admin op config instance create clusters admin op result timeout data op config instance data create clusters data op result timeout tests system py api core google api core future polling py in result self blocking poll timeout timeout self timeout def blocking poll self timeout none poll and wait for the future to be resolved args timeout int how long in seconds to wait for the operation to complete if none wait indefinitely if self result set return retry self retry with deadline timeout try retry self done or raise except exceptions retryerror raise concurrent futures timeouterror operation did not complete within the designated timeout e concurrent futures base timeouterror operation did not complete within the designated timeout api core google api core future polling py timeouterror repeated multiple times
| 1
|
46,575
| 5,823,921,707
|
IssuesEvent
|
2017-05-07 07:36:24
|
FACN1/VolunteerApp
|
https://api.github.com/repos/FACN1/VolunteerApp
|
closed
|
Home page colors for words
|
enhancement user-testing
|
i think the words are too colorful, even as an arab they are kinda hard to read
|
1.0
|
Home page colors for words - i think the words are too colorful, even as an arab they are kinda hard to read
|
non_process
|
home page colors for words i think the words are too colorful even as an arab they are kinda hard to read
| 0
|
307,528
| 23,202,830,000
|
IssuesEvent
|
2022-08-02 00:06:02
|
fga-eps-mds/2022-1-OiaAMoeda
|
https://api.github.com/repos/fga-eps-mds/2022-1-OiaAMoeda
|
closed
|
Sprint 7 - Revisar o termo de abertura
|
documentation
|
# Descrição
O termo de abertura do projeto está faltando o preço do projeto.
# Tarefas
- [x] Colocar a estimativa de preço do projeto.
- [x] Revisar a escrita geral do projeto.
# Critérios de aceitação
- [ ] Documento revisado.
|
1.0
|
Sprint 7 - Revisar o termo de abertura - # Descrição
O termo de abertura do projeto está faltando o preço do projeto.
# Tarefas
- [x] Colocar a estimativa de preço do projeto.
- [x] Revisar a escrita geral do projeto.
# Critérios de aceitação
- [ ] Documento revisado.
|
non_process
|
sprint revisar o termo de abertura descrição o termo de abertura do projeto está faltando o preço do projeto tarefas colocar a estimativa de preço do projeto revisar a escrita geral do projeto critérios de aceitação documento revisado
| 0
|
5,380
| 8,205,137,876
|
IssuesEvent
|
2018-09-03 09:10:29
|
zeebe-io/zeebe
|
https://api.github.com/repos/zeebe-io/zeebe
|
closed
|
Concurrent reprocessing of Workflows and Deployments is broken
|
broker bug ready stream processor
|
## Scenario
* deploy workflow
* start workflow instance
* stop broker
* purge snapshots
* start broker
* reprocess is happening in parallel
* reprocess workflow instance events
* reprocess deployment events
## Problem
Since deployment are not yet deployed again (not added to the WorkflowRepository)
workflow reprocessing fails. Workflow reprocessing tries to fetch workflow, which returns `null`.
## Note
Workflow repo api returns nothing/null if workflow is not deployed/added.
Current code in BpmnStepProcessor does not expect that and continues without checking returned workflow.
It was not a problem before #1116 , since the `FetchRequestHandler` is installed after reprocessing of the DeploymentProcessor. The processing/reprocessing takes longer now since the deployments are pushed to the remaining partitions.
## Possible solution
We could integrate the deployment processor into the workflow instance processor.
This would mean that the deployment events are read before and added to the cache and then the workflow events are reprocessed successfully.
|
1.0
|
Concurrent reprocessing of Workflows and Deployments is broken - ## Scenario
* deploy workflow
* start workflow instance
* stop broker
* purge snapshots
* start broker
* reprocess is happening in parallel
* reprocess workflow instance events
* reprocess deployment events
## Problem
Since deployment are not yet deployed again (not added to the WorkflowRepository)
workflow reprocessing fails. Workflow reprocessing tries to fetch workflow, which returns `null`.
## Note
Workflow repo api returns nothing/null if workflow is not deployed/added.
Current code in BpmnStepProcessor does not expect that and continues without checking returned workflow.
It was not a problem before #1116 , since the `FetchRequestHandler` is installed after reprocessing of the DeploymentProcessor. The processing/reprocessing takes longer now since the deployments are pushed to the remaining partitions.
## Possible solution
We could integrate the deployment processor into the workflow instance processor.
This would mean that the deployment events are read before and added to the cache and then the workflow events are reprocessed successfully.
|
process
|
concurrent reprocessing of workflows and deployments is broken scenario deploy workflow start workflow instance stop broker purge snapshots start broker reprocess is happening in parallel reprocess workflow instance events reprocess deployment events problem since deployment are not yet deployed again not added to the workflowrepository workflow reprocessing fails workflow reprocessing tries to fetch workflow which returns null note workflow repo api returns nothing null if workflow is not deployed added current code in bpmnstepprocessor does not expect that and continues without checking returned workflow it was not a problem before since the fetchrequesthandler is installed after reprocessing of the deploymentprocessor the processing reprocessing takes longer now since the deployments are pushed to the remaining partitions possible solution we could integrate the deployment processor into the workflow instance processor this would mean that the deployment events are read before and added to the cache and then the workflow events are reprocessed successfully
| 1
|
108,778
| 4,350,462,580
|
IssuesEvent
|
2016-07-31 08:31:48
|
japanesemediamanager/jmmserver
|
https://api.github.com/repos/japanesemediamanager/jmmserver
|
opened
|
JMM Not Scanning Sub-Folders On Networked Drive
|
Bug - High Priority
|
As reported by Shadow Kamui on Discord, JMM will scan an import folder that's a networked drive, but will not scan any of the sub-folders within in it or sub-folders within sub-folders.
|
1.0
|
JMM Not Scanning Sub-Folders On Networked Drive - As reported by Shadow Kamui on Discord, JMM will scan an import folder that's a networked drive, but will not scan any of the sub-folders within in it or sub-folders within sub-folders.
|
non_process
|
jmm not scanning sub folders on networked drive as reported by shadow kamui on discord jmm will scan an import folder that s a networked drive but will not scan any of the sub folders within in it or sub folders within sub folders
| 0
|
8,914
| 12,017,380,439
|
IssuesEvent
|
2020-04-10 18:15:16
|
MicrosoftDocs/azure-devops-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-devops-docs
|
closed
|
Split like function
|
Pri1 devops-cicd-process/tech devops/prod doc-bug
|
Does a function exist that allows splitting a string base off of a specific delimiter?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
* Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
* Content: [Expressions - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops#feedback)
* Content Source: [docs/pipelines/process/expressions.md](https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/pipelines/process/expressions.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
1.0
|
Split like function - Does a function exist that allows splitting a string base off of a specific delimiter?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
* Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
* Content: [Expressions - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops#feedback)
* Content Source: [docs/pipelines/process/expressions.md](https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/pipelines/process/expressions.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
process
|
split like function does a function exist that allows splitting a string base off of a specific delimiter document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product devops technology devops cicd process github login juliakm microsoft alias jukullam
| 1
|
246,678
| 18,850,954,310
|
IssuesEvent
|
2021-11-11 20:47:32
|
matheuswhite/backpack
|
https://api.github.com/repos/matheuswhite/backpack
|
closed
|
Code documentation
|
documentation
|
- [x] Search badge for documentation
- [x] Add badge for documentation
- [x] Error codes
- [x] return tag in macros
## Header files
- [x] bp_array.h
- [x] bp_iter.h
- [x] bp_types.h
- [x] bp_heap.h
- [x] bp_ring.h
- [x] bp_stack.h
## Source files
- [x] bp_array.c
- [x] bp_heap.c
- [x] bp_ring.c
- [x] bp_stack.c
|
1.0
|
Code documentation - - [x] Search badge for documentation
- [x] Add badge for documentation
- [x] Error codes
- [x] return tag in macros
## Header files
- [x] bp_array.h
- [x] bp_iter.h
- [x] bp_types.h
- [x] bp_heap.h
- [x] bp_ring.h
- [x] bp_stack.h
## Source files
- [x] bp_array.c
- [x] bp_heap.c
- [x] bp_ring.c
- [x] bp_stack.c
|
non_process
|
code documentation search badge for documentation add badge for documentation error codes return tag in macros header files bp array h bp iter h bp types h bp heap h bp ring h bp stack h source files bp array c bp heap c bp ring c bp stack c
| 0
|
48,878
| 5,988,926,836
|
IssuesEvent
|
2017-06-02 06:58:15
|
mautic/mautic
|
https://api.github.com/repos/mautic/mautic
|
closed
|
NotificationBundle Integration
|
Bug Ready To Test
|
What type of report is this:
| Q | A
| ---| ---
| Bug report? | Yes
| Feature request? | No
| Enhancement? | No
## Description:
In `app/bundles/NotificationBundle/Helper/NotificationHelper.php`
Replace `$integration = $this->integrationHelper->getIntegrationObject('Twilio');`
Per `$integration = $this->integrationHelper->getIntegrationObject('OneSignal');`
## If a bug:
| Q | A
| --- | ---
| Mautic version | 2.8.0
| PHP version | 5.6.30
### Log errors:
PHP Notice: Undefined index: app_id in /app/bundles/NotificationBundle/Helper/NotificationHelper.php on line 116, referer: https://xxxxx
PHP Notice: Undefined index: safari_web_id in /app/bundles/NotificationBundle/Helper/NotificationHelper.php on line 117, referer: https://xxxxx
PHP Notice: Undefined index: subdomain_name in /app/bundles/NotificationBundle/Helper/NotificationHelper.php on line 119, referer: https://xxxxx
|
1.0
|
NotificationBundle Integration - What type of report is this:
| Q | A
| ---| ---
| Bug report? | Yes
| Feature request? | No
| Enhancement? | No
## Description:
In `app/bundles/NotificationBundle/Helper/NotificationHelper.php`
Replace `$integration = $this->integrationHelper->getIntegrationObject('Twilio');`
Per `$integration = $this->integrationHelper->getIntegrationObject('OneSignal');`
## If a bug:
| Q | A
| --- | ---
| Mautic version | 2.8.0
| PHP version | 5.6.30
### Log errors:
PHP Notice: Undefined index: app_id in /app/bundles/NotificationBundle/Helper/NotificationHelper.php on line 116, referer: https://xxxxx
PHP Notice: Undefined index: safari_web_id in /app/bundles/NotificationBundle/Helper/NotificationHelper.php on line 117, referer: https://xxxxx
PHP Notice: Undefined index: subdomain_name in /app/bundles/NotificationBundle/Helper/NotificationHelper.php on line 119, referer: https://xxxxx
|
non_process
|
notificationbundle integration what type of report is this q a bug report yes feature request no enhancement no description in app bundles notificationbundle helper notificationhelper php replace integration this integrationhelper getintegrationobject twilio per integration this integrationhelper getintegrationobject onesignal if a bug q a mautic version php version log errors php notice undefined index app id in app bundles notificationbundle helper notificationhelper php on line referer php notice undefined index safari web id in app bundles notificationbundle helper notificationhelper php on line referer php notice undefined index subdomain name in app bundles notificationbundle helper notificationhelper php on line referer
| 0
|
290,962
| 8,915,559,466
|
IssuesEvent
|
2019-01-19 07:20:02
|
Text-Mining/Persian-NER
|
https://api.github.com/repos/Text-Mining/Persian-NER
|
closed
|
مشخص کردن ترتیب و کلیدهای منقضی شده api با رنگ
|
Effort: Low Priority: Low Product: Web App Type: enhancement
|
لطفا کلیدهای API منقضی شده با رنگ دیگری مشخص شود.
همچنین ترتیب رکوردهای جدول لیست API مشخص نیست براساس کدام ستون هست!
|
1.0
|
مشخص کردن ترتیب و کلیدهای منقضی شده api با رنگ - لطفا کلیدهای API منقضی شده با رنگ دیگری مشخص شود.
همچنین ترتیب رکوردهای جدول لیست API مشخص نیست براساس کدام ستون هست!
|
non_process
|
مشخص کردن ترتیب و کلیدهای منقضی شده api با رنگ لطفا کلیدهای api منقضی شده با رنگ دیگری مشخص شود همچنین ترتیب رکوردهای جدول لیست api مشخص نیست براساس کدام ستون هست
| 0
|
3,683
| 6,714,721,803
|
IssuesEvent
|
2017-10-13 18:04:49
|
syndesisio/syndesis
|
https://api.github.com/repos/syndesisio/syndesis
|
opened
|
Better co-operation between Dev and QE
|
process/retro
|
Development should have more insights in QE. It is especially important that developer can run QE tests on their own easily or at least where to look at our development environment. QE tests need better visibility.
Developers should also help QE to automate test, ideally already when implementing features. This should happen in an agile and flexible way.
|
1.0
|
Better co-operation between Dev and QE - Development should have more insights in QE. It is especially important that developer can run QE tests on their own easily or at least where to look at our development environment. QE tests need better visibility.
Developers should also help QE to automate test, ideally already when implementing features. This should happen in an agile and flexible way.
|
process
|
better co operation between dev and qe development should have more insights in qe it is especially important that developer can run qe tests on their own easily or at least where to look at our development environment qe tests need better visibility developers should also help qe to automate test ideally already when implementing features this should happen in an agile and flexible way
| 1
|
35,537
| 7,763,775,334
|
IssuesEvent
|
2018-06-01 17:47:52
|
StrikeNP/trac_test
|
https://api.github.com/repos/StrikeNP/trac_test
|
closed
|
Certain folder arguments do not allow plotgen to function (Trac #10)
|
Migrated from Trac defect nielsenb@uwm.edu post_processing
|
It seems that if a folder named output is specified as an argument for a source folder, plotgen will not operate as expected. This is a minor issue as one can move the files being examined to another folder. However, the default output folder for CLUBB output is labeled 'output'. As a result this makes the use of plotgen less convenient.
This issue was tested two ways:
1) Both folders named 'output'
```text
plotgen -c projects/experimental/clubb/output projects/baseline/clubb/output TestThis/ 0 0 0
```
2) Only one folder named 'output'
```text
plotgen -c projects/experimental/clubb/output Old Testthat/ 0 0 0
```
This testing was done on Condella.
Migrated from http://carson.math.uwm.edu/trac/clubb/ticket/10
```json
{
"status": "closed",
"changetime": "2009-09-01T20:34:02",
"description": "It seems that if a folder named output is specified as an argument for a source folder, plotgen will not operate as expected. This is a minor issue as one can move the files being examined to another folder. However, the default output folder for CLUBB output is labeled 'output'. As a result this makes the use of plotgen less convenient.\n\nThis issue was tested two ways:\n1) Both folders named 'output'\n\n{{{\nplotgen -c projects/experimental/clubb/output projects/baseline/clubb/output TestThis/ 0 0 0\n}}}\n\n2) Only one folder named 'output'\n\n{{{\nplotgen -c projects/experimental/clubb/output Old Testthat/ 0 0 0 \n}}}\n\nThis testing was done on Condella.",
"reporter": "fasching@uwm.edu",
"cc": "senkbeil@uwm.edu",
"resolution": "Verified by V. Larson",
"_ts": "1251837242000000",
"component": "post_processing",
"summary": "Certain folder arguments do not allow plotgen to function",
"priority": "minor",
"keywords": "plotgen",
"time": "2009-05-06T18:24:44",
"milestone": "Plotgen 3.0",
"owner": "nielsenb@uwm.edu",
"type": "defect"
}
```
|
1.0
|
Certain folder arguments do not allow plotgen to function (Trac #10) - It seems that if a folder named output is specified as an argument for a source folder, plotgen will not operate as expected. This is a minor issue as one can move the files being examined to another folder. However, the default output folder for CLUBB output is labeled 'output'. As a result this makes the use of plotgen less convenient.
This issue was tested two ways:
1) Both folders named 'output'
```text
plotgen -c projects/experimental/clubb/output projects/baseline/clubb/output TestThis/ 0 0 0
```
2) Only one folder named 'output'
```text
plotgen -c projects/experimental/clubb/output Old Testthat/ 0 0 0
```
This testing was done on Condella.
Migrated from http://carson.math.uwm.edu/trac/clubb/ticket/10
```json
{
"status": "closed",
"changetime": "2009-09-01T20:34:02",
"description": "It seems that if a folder named output is specified as an argument for a source folder, plotgen will not operate as expected. This is a minor issue as one can move the files being examined to another folder. However, the default output folder for CLUBB output is labeled 'output'. As a result this makes the use of plotgen less convenient.\n\nThis issue was tested two ways:\n1) Both folders named 'output'\n\n{{{\nplotgen -c projects/experimental/clubb/output projects/baseline/clubb/output TestThis/ 0 0 0\n}}}\n\n2) Only one folder named 'output'\n\n{{{\nplotgen -c projects/experimental/clubb/output Old Testthat/ 0 0 0 \n}}}\n\nThis testing was done on Condella.",
"reporter": "fasching@uwm.edu",
"cc": "senkbeil@uwm.edu",
"resolution": "Verified by V. Larson",
"_ts": "1251837242000000",
"component": "post_processing",
"summary": "Certain folder arguments do not allow plotgen to function",
"priority": "minor",
"keywords": "plotgen",
"time": "2009-05-06T18:24:44",
"milestone": "Plotgen 3.0",
"owner": "nielsenb@uwm.edu",
"type": "defect"
}
```
|
non_process
|
certain folder arguments do not allow plotgen to function trac it seems that if a folder named output is specified as an argument for a source folder plotgen will not operate as expected this is a minor issue as one can move the files being examined to another folder however the default output folder for clubb output is labeled output as a result this makes the use of plotgen less convenient this issue was tested two ways both folders named output text plotgen c projects experimental clubb output projects baseline clubb output testthis only one folder named output text plotgen c projects experimental clubb output old testthat this testing was done on condella migrated from json status closed changetime description it seems that if a folder named output is specified as an argument for a source folder plotgen will not operate as expected this is a minor issue as one can move the files being examined to another folder however the default output folder for clubb output is labeled output as a result this makes the use of plotgen less convenient n nthis issue was tested two ways both folders named output n n nplotgen c projects experimental clubb output projects baseline clubb output testthis n n only one folder named output n n nplotgen c projects experimental clubb output old testthat n n nthis testing was done on condella reporter fasching uwm edu cc senkbeil uwm edu resolution verified by v larson ts component post processing summary certain folder arguments do not allow plotgen to function priority minor keywords plotgen time milestone plotgen owner nielsenb uwm edu type defect
| 0
|
9,404
| 12,403,992,711
|
IssuesEvent
|
2020-05-21 14:49:14
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
closed
|
Flaky internal test: e2e plugins fails when there is an async error at the root [chrome]
|
browser: chrome process: flaky test stage: needs review stage: work in progress type: chore
|
### Current behavior:
See this internal test fail sometimes. e2e plugins fails when there is an async error at the root [chrome] - fails when there is an async error at the root [chrome]
Looks like this was added a week ago in https://github.com/cypress-io/cypress/pull/7230 with a relevant [comment](https://github.com/cypress-io/cypress/pull/7230/files#r420345661) from @chrisbreiding
>This is a related test that was skipped before because it was flaky. I think I have it more reliable now.
**CircleCI Failure**: https://circleci.com/gh/cypress-io/cypress/323426
**Test Code**: https://github.com/cypress-io/cypress/blob/develop/packages/server/test/e2e/3_plugins_spec.js#L32:L32
```
Error: Different value of snapshot "e2e plugins / fails when there is an async error at the root"
----------
Difference
----------
-
-====================================================================================================
-
- (Run Starting)
-
- ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
- │ Cypress: 1.2.3 │
- │ Browser: FooBrowser 88 │
- │ Specs: 1 found (app_spec.js) │
- │ Searched: cypress/integration/app_spec.js │
- └────────────────────────────────────────────────────────────────────────────────────────────────┘
-
-
-────────────────────────────────────────────────────────────────────────────────────────────────────
-
- Running: app_spec.js (1 of 1)
-
The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (`/foo/bar/.projects/plugins-root-async-error/cypress/plugins/index.js`)
Error: Root async error from plugins file
- [stack trace lines]
-
- (Results)
-
- ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
- │ Tests: 0 │
- │ Passing: 0 │
- │ Failing: 1 │
- │ Pending: 0 │
- │ Skipped: 0 │
- │ Screenshots: 0 │
- │ Video: false │
- │ Duration: X seconds │
- │ Spec Ran: app_spec.js │
- └────────────────────────────────────────────────────────────────────────────────────────────────┘
-
-
-====================================================================================================
-
- (Run Finished)
-
-
- Spec Tests Passing Failing Pending Skipped
- ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
- │ ✖ app_spec.js XX:XX - - 1 - - │
- └────────────────────────────────────────────────────────────────────────────────────────────────┘
- ✖ 1 of 1 failed (100%) XX:XX - - 1 - -
-
+ [stack trace lines]
-------------------
Saved snapshot text
-------------------
====================================================================================================
(Run Starting)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress: 1.2.3 │
│ Browser: FooBrowser 88 │
│ Specs: 1 found (app_spec.js) │
│ Searched: cypress/integration/app_spec.js │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
Running: app_spec.js (1 of 1)
The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (`/foo/bar/.projects/plugins-root-async-error/cypress/plugins/index.js`)
Error: Root async error from plugins file
[stack trace lines]
(Results)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Tests: 0 │
│ Passing: 0 │
│ Failing: 1 │
│ Pending: 0 │
│ Skipped: 0 │
│ Screenshots: 0 │
│ Video: false │
│ Duration: X seconds │
│ Spec Ran: app_spec.js │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
====================================================================================================
(Run Finished)
Spec Tests Passing Failing Pending Skipped
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ ✖ app_spec.js XX:XX - - 1 - - │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
✖ 1 of 1 failed (100%) XX:XX - - 1 - -
------------
Current text
------------
The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (`/foo/bar/.projects/plugins-root-async-error/cypress/plugins/index.js`)
Error: Root async error from plugins file
[stack trace lines]
--------
Diff end
--------
at /root/cypress/node_modules/snap-shot-core/src/file-system.js:263:11
at InternalConstructor.orElse (/root/cypress/node_modules/folktale/result/result.js:187:14)
at raiseIfDifferent (/root/cypress/node_modules/snap-shot-core/src/file-system.js:254:10)
at setOrCheckValue (/root/cypress/node_modules/snap-shot-core/src/index.js:367:7)
at core (/root/cypress/node_modules/snap-shot-core/src/index.js:388:12)
at snapshot (/root/cypress/node_modules/snap-shot-it/src/index.js:293:18)
at exit (test/support/helpers/e2e.js:657:11)
at processImmediate (internal/timers.js:439:21)
From previous event:
at Object.exec (test/support/helpers/e2e.js:721:6)
at execFn (test/support/helpers/e2e.js:341:20)
at Object.onRun (test/support/helpers/e2e.js:305:14)
at Context.<anonymous> (test/support/helpers/e2e.js:344:22)
```
### Versions
4.5.0
|
1.0
|
Flaky internal test: e2e plugins fails when there is an async error at the root [chrome] - ### Current behavior:
See this internal test fail sometimes. e2e plugins fails when there is an async error at the root [chrome] - fails when there is an async error at the root [chrome]
Looks like this was added a week ago in https://github.com/cypress-io/cypress/pull/7230 with a relevant [comment](https://github.com/cypress-io/cypress/pull/7230/files#r420345661) from @chrisbreiding
>This is a related test that was skipped before because it was flaky. I think I have it more reliable now.
**CircleCI Failure**: https://circleci.com/gh/cypress-io/cypress/323426
**Test Code**: https://github.com/cypress-io/cypress/blob/develop/packages/server/test/e2e/3_plugins_spec.js#L32:L32
```
Error: Different value of snapshot "e2e plugins / fails when there is an async error at the root"
----------
Difference
----------
-
-====================================================================================================
-
- (Run Starting)
-
- ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
- │ Cypress: 1.2.3 │
- │ Browser: FooBrowser 88 │
- │ Specs: 1 found (app_spec.js) │
- │ Searched: cypress/integration/app_spec.js │
- └────────────────────────────────────────────────────────────────────────────────────────────────┘
-
-
-────────────────────────────────────────────────────────────────────────────────────────────────────
-
- Running: app_spec.js (1 of 1)
-
The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (`/foo/bar/.projects/plugins-root-async-error/cypress/plugins/index.js`)
Error: Root async error from plugins file
- [stack trace lines]
-
- (Results)
-
- ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
- │ Tests: 0 │
- │ Passing: 0 │
- │ Failing: 1 │
- │ Pending: 0 │
- │ Skipped: 0 │
- │ Screenshots: 0 │
- │ Video: false │
- │ Duration: X seconds │
- │ Spec Ran: app_spec.js │
- └────────────────────────────────────────────────────────────────────────────────────────────────┘
-
-
-====================================================================================================
-
- (Run Finished)
-
-
- Spec Tests Passing Failing Pending Skipped
- ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
- │ ✖ app_spec.js XX:XX - - 1 - - │
- └────────────────────────────────────────────────────────────────────────────────────────────────┘
- ✖ 1 of 1 failed (100%) XX:XX - - 1 - -
-
+ [stack trace lines]
-------------------
Saved snapshot text
-------------------
====================================================================================================
(Run Starting)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress: 1.2.3 │
│ Browser: FooBrowser 88 │
│ Specs: 1 found (app_spec.js) │
│ Searched: cypress/integration/app_spec.js │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
Running: app_spec.js (1 of 1)
The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (`/foo/bar/.projects/plugins-root-async-error/cypress/plugins/index.js`)
Error: Root async error from plugins file
[stack trace lines]
(Results)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Tests: 0 │
│ Passing: 0 │
│ Failing: 1 │
│ Pending: 0 │
│ Skipped: 0 │
│ Screenshots: 0 │
│ Video: false │
│ Duration: X seconds │
│ Spec Ran: app_spec.js │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
====================================================================================================
(Run Finished)
Spec Tests Passing Failing Pending Skipped
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ ✖ app_spec.js XX:XX - - 1 - - │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
✖ 1 of 1 failed (100%) XX:XX - - 1 - -
------------
Current text
------------
The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (`/foo/bar/.projects/plugins-root-async-error/cypress/plugins/index.js`)
Error: Root async error from plugins file
[stack trace lines]
--------
Diff end
--------
at /root/cypress/node_modules/snap-shot-core/src/file-system.js:263:11
at InternalConstructor.orElse (/root/cypress/node_modules/folktale/result/result.js:187:14)
at raiseIfDifferent (/root/cypress/node_modules/snap-shot-core/src/file-system.js:254:10)
at setOrCheckValue (/root/cypress/node_modules/snap-shot-core/src/index.js:367:7)
at core (/root/cypress/node_modules/snap-shot-core/src/index.js:388:12)
at snapshot (/root/cypress/node_modules/snap-shot-it/src/index.js:293:18)
at exit (test/support/helpers/e2e.js:657:11)
at processImmediate (internal/timers.js:439:21)
From previous event:
at Object.exec (test/support/helpers/e2e.js:721:6)
at execFn (test/support/helpers/e2e.js:341:20)
at Object.onRun (test/support/helpers/e2e.js:305:14)
at Context.<anonymous> (test/support/helpers/e2e.js:344:22)
```
### Versions
4.5.0
|
process
|
flaky internal test plugins fails when there is an async error at the root current behavior see this internal test fail sometimes plugins fails when there is an async error at the root fails when there is an async error at the root looks like this was added a week ago in with a relevant from chrisbreiding this is a related test that was skipped before because it was flaky i think i have it more reliable now circleci failure test code error different value of snapshot plugins fails when there is an async error at the root difference run starting ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ cypress │ │ browser foobrowser │ │ specs found app spec js │ │ searched cypress integration app spec js │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ──────────────────────────────────────────────────────────────────────────────────────────────────── running app spec js of the following error was thrown by a plugin we stopped running your tests because a plugin crashed please check your plugins file foo bar projects plugins root async error cypress plugins index js error root async error from plugins file results ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ tests │ │ passing │ │ failing │ │ pending │ │ skipped │ │ screenshots │ │ video false │ │ duration x seconds │ │ spec ran app spec js │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ run finished spec tests passing failing pending skipped ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ ✖ app spec js xx xx │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ✖ of failed xx xx saved snapshot text run starting ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ cypress │ │ browser foobrowser │ │ specs found app spec js │ │ searched cypress integration app spec js │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ──────────────────────────────────────────────────────────────────────────────────────────────────── running app spec js of the following error was thrown by a plugin we stopped running your tests because a plugin crashed please check your plugins file foo bar projects plugins root async error cypress plugins index js error root async error from plugins file results ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ tests │ │ passing │ │ failing │ │ pending │ │ skipped │ │ screenshots │ │ video false │ │ duration x seconds │ │ spec ran app spec js │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ run finished spec tests passing failing pending skipped ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ ✖ app spec js xx xx │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ✖ of failed xx xx current text the following error was thrown by a plugin we stopped running your tests because a plugin crashed please check your plugins file foo bar projects plugins root async error cypress plugins index js error root async error from plugins file diff end at root cypress node modules snap shot core src file system js at internalconstructor orelse root cypress node modules folktale result result js at raiseifdifferent root cypress node modules snap shot core src file system js at setorcheckvalue root cypress node modules snap shot core src index js at core root cypress node modules snap shot core src index js at snapshot root cypress node modules snap shot it src index js at exit test support helpers js at processimmediate internal timers js from previous event at object exec test support helpers js at execfn test support helpers js at object onrun test support helpers js at context test support helpers js versions
| 1
|
124,843
| 12,240,010,356
|
IssuesEvent
|
2020-05-04 23:01:41
|
daidodo/tsimportsorter
|
https://api.github.com/repos/daidodo/tsimportsorter
|
closed
|
Missing Option to turn of blank line after group
|
documentation enhancement
|
> Feature Request
I don't mind the grouping but I did not see any option to disable the empty
line after each group.
|
1.0
|
Missing Option to turn of blank line after group - > Feature Request
I don't mind the grouping but I did not see any option to disable the empty
line after each group.
|
non_process
|
missing option to turn of blank line after group feature request i don t mind the grouping but i did not see any option to disable the empty line after each group
| 0
|
185,478
| 14,356,042,526
|
IssuesEvent
|
2020-11-30 10:57:28
|
Cxbx-Reloaded/Cxbx-Reloaded
|
https://api.github.com/repos/Cxbx-Reloaded/Cxbx-Reloaded
|
closed
|
Pop-up "Applying 3925 fog disable hack"
|
HLE graphics informational test-case-popup
|
<!--
Questions can be asked on Discord: https://discord.gg/26Xjx23
If this is an issue specifically related to one game, please report it at https://github.com/Cxbx-Reloaded/game-compatibility
Any emulation/general issues like crashes when a controller is connected, or regressions across several titles can be reported here.
-->
LOG_TEST_CASE: Applying 3925 fog disable hack
In ApplyDeferredRenderState (D:\a\Cxbx-Reloaded\Cxbx-Reloaded\src\core\hle\D3D8\Direct3D9\RenderStates.cpp line 337)
Titles:
- Airforce Delta Storm
|
1.0
|
Pop-up "Applying 3925 fog disable hack" - <!--
Questions can be asked on Discord: https://discord.gg/26Xjx23
If this is an issue specifically related to one game, please report it at https://github.com/Cxbx-Reloaded/game-compatibility
Any emulation/general issues like crashes when a controller is connected, or regressions across several titles can be reported here.
-->
LOG_TEST_CASE: Applying 3925 fog disable hack
In ApplyDeferredRenderState (D:\a\Cxbx-Reloaded\Cxbx-Reloaded\src\core\hle\D3D8\Direct3D9\RenderStates.cpp line 337)
Titles:
- Airforce Delta Storm
|
non_process
|
pop up applying fog disable hack questions can be asked on discord if this is an issue specifically related to one game please report it at any emulation general issues like crashes when a controller is connected or regressions across several titles can be reported here log test case applying fog disable hack in applydeferredrenderstate d a cxbx reloaded cxbx reloaded src core hle renderstates cpp line titles airforce delta storm
| 0
|
21,983
| 30,479,695,421
|
IssuesEvent
|
2023-07-17 19:17:53
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
closed
|
Citus mainnet cluster
|
enhancement process
|
### Problem
We'd like to standup a production-like Citus cluster with mainnet staging data to get real performance numbers and production experience managing this new database.
### Solution
* Dump mainnet data from mainnet-staging db
* Create a GKE cluster alongside current mainnet clusters
* Create two node pools: one standard one and one specific to Citus
* Install ZFS
* Change chart to use PG15 and skip pg_cron since it's not pg15 compatible
* Install citus using the [HA](https://github.com/hashgraph/hedera-mirror-node/issues/5233) setup and the resources defined via https://github.com/hashgraph/hedera-mirror-node/issues/2685
* Restore mainnet data to Citus cluster
### Alternatives
_No response_
|
1.0
|
Citus mainnet cluster - ### Problem
We'd like to standup a production-like Citus cluster with mainnet staging data to get real performance numbers and production experience managing this new database.
### Solution
* Dump mainnet data from mainnet-staging db
* Create a GKE cluster alongside current mainnet clusters
* Create two node pools: one standard one and one specific to Citus
* Install ZFS
* Change chart to use PG15 and skip pg_cron since it's not pg15 compatible
* Install citus using the [HA](https://github.com/hashgraph/hedera-mirror-node/issues/5233) setup and the resources defined via https://github.com/hashgraph/hedera-mirror-node/issues/2685
* Restore mainnet data to Citus cluster
### Alternatives
_No response_
|
process
|
citus mainnet cluster problem we d like to standup a production like citus cluster with mainnet staging data to get real performance numbers and production experience managing this new database solution dump mainnet data from mainnet staging db create a gke cluster alongside current mainnet clusters create two node pools one standard one and one specific to citus install zfs change chart to use and skip pg cron since it s not compatible install citus using the setup and the resources defined via restore mainnet data to citus cluster alternatives no response
| 1
|
8,074
| 11,251,643,043
|
IssuesEvent
|
2020-01-11 01:40:52
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
boolean field filters don't work correctly for Oracle
|
.Backend Database/Oracle Priority:P2 Querying/Native Querying/Parameters & Variables Querying/Processor Type:Bug
|
This is the exact same issue as #11592 but for Oracle instead of SQL Server. e.g.
```clj
:class java.sql.SQLSyntaxErrorException
:error "ORA-00904: \"TRUE\": invalid identifier\n",
:stacktrace ["oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)" ...]
```
|
1.0
|
boolean field filters don't work correctly for Oracle - This is the exact same issue as #11592 but for Oracle instead of SQL Server. e.g.
```clj
:class java.sql.SQLSyntaxErrorException
:error "ORA-00904: \"TRUE\": invalid identifier\n",
:stacktrace ["oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)" ...]
```
|
process
|
boolean field filters don t work correctly for oracle this is the exact same issue as but for oracle instead of sql server e g clj class java sql sqlsyntaxerrorexception error ora true invalid identifier n stacktrace
| 1
|
64,611
| 14,670,969,835
|
IssuesEvent
|
2020-12-30 06:49:53
|
anyulled/react-skeleton
|
https://api.github.com/repos/anyulled/react-skeleton
|
closed
|
CVE-2018-19827 (High) detected in opennmsopennms-source-26.0.0-1 - autoclosed
|
security vulnerability
|
## CVE-2018-19827 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opennmsopennms-source-26.0.0-1</b></p></summary>
<p>
<p>A Java based fault and performance management system</p>
<p>Library home page: <a href=https://sourceforge.net/projects/opennms/>https://sourceforge.net/projects/opennms/</a></p>
<p>Found in HEAD commit: <a href="https://github.com/anyulled/react-skeleton/commit/31d18fc62d4b9fd8478e25646768563f16d86d87">31d18fc62d4b9fd8478e25646768563f16d86d87</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>react-skeleton/client/node_modules/node-sass/src/libsass/src/expand.cpp</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19827>CVE-2018-19827</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>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sass/libsass/pull/2784">https://github.com/sass/libsass/pull/2784</a></p>
<p>Release Date: 2019-08-29</p>
<p>Fix Resolution: LibSass - 3.6.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-2018-19827 (High) detected in opennmsopennms-source-26.0.0-1 - autoclosed - ## CVE-2018-19827 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opennmsopennms-source-26.0.0-1</b></p></summary>
<p>
<p>A Java based fault and performance management system</p>
<p>Library home page: <a href=https://sourceforge.net/projects/opennms/>https://sourceforge.net/projects/opennms/</a></p>
<p>Found in HEAD commit: <a href="https://github.com/anyulled/react-skeleton/commit/31d18fc62d4b9fd8478e25646768563f16d86d87">31d18fc62d4b9fd8478e25646768563f16d86d87</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>react-skeleton/client/node_modules/node-sass/src/libsass/src/expand.cpp</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19827>CVE-2018-19827</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>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sass/libsass/pull/2784">https://github.com/sass/libsass/pull/2784</a></p>
<p>Release Date: 2019-08-29</p>
<p>Fix Resolution: LibSass - 3.6.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_process
|
cve high detected in opennmsopennms source autoclosed cve high severity vulnerability vulnerable library opennmsopennms source a java based fault and performance management system library home page a href found in head commit a href found in base branch master vulnerable source files react skeleton client node modules node sass src libsass src expand cpp vulnerability details in libsass a use after free vulnerability exists in the sharedptr class in sharedptr cpp or sharedptr hpp that may cause a denial of service application crash or possibly have unspecified other impact publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libsass step up your open source security game with whitesource
| 0
|
215,857
| 24,196,535,821
|
IssuesEvent
|
2022-09-24 01:14:28
|
HoloRes/holomatsuri-counterplugin
|
https://api.github.com/repos/HoloRes/holomatsuri-counterplugin
|
opened
|
CVE-2022-38398 (Medium) detected in batik-all-1.13.jar, batik-bridge-1.13.jar
|
security vulnerability
|
## CVE-2022-38398 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>batik-all-1.13.jar</b>, <b>batik-bridge-1.13.jar</b></p></summary>
<p>
<details><summary><b>batik-all-1.13.jar</b></p></summary>
<p>Batik aggregate artifact</p>
<p>Path to dependency file: /dependency-reduced-pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/xmlgraphics/batik-all/1.13/batik-all-1.13.jar</p>
<p>
Dependency Hierarchy:
- poi-ooxml-5.0.0.jar (Root Library)
- :x: **batik-all-1.13.jar** (Vulnerable Library)
</details>
<details><summary><b>batik-bridge-1.13.jar</b></p></summary>
<p>Batik bridge</p>
<p>Library home page: <a href="http://xmlgraphics.apache.org/batik/">http://xmlgraphics.apache.org/batik/</a></p>
<p>Path to dependency file: /dependency-reduced-pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/xmlgraphics/batik-bridge/1.13/batik-bridge-1.13.jar</p>
<p>
Dependency Hierarchy:
- poi-ooxml-5.0.0.jar (Root Library)
- batik-all-1.13.jar
- :x: **batik-bridge-1.13.jar** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to load a url thru the jar protocol. This issue affects Apache XML Graphics Batik 1.14.
<p>Publish Date: 2022-09-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-38398>CVE-2022-38398</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-38398 (Medium) detected in batik-all-1.13.jar, batik-bridge-1.13.jar - ## CVE-2022-38398 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>batik-all-1.13.jar</b>, <b>batik-bridge-1.13.jar</b></p></summary>
<p>
<details><summary><b>batik-all-1.13.jar</b></p></summary>
<p>Batik aggregate artifact</p>
<p>Path to dependency file: /dependency-reduced-pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/xmlgraphics/batik-all/1.13/batik-all-1.13.jar</p>
<p>
Dependency Hierarchy:
- poi-ooxml-5.0.0.jar (Root Library)
- :x: **batik-all-1.13.jar** (Vulnerable Library)
</details>
<details><summary><b>batik-bridge-1.13.jar</b></p></summary>
<p>Batik bridge</p>
<p>Library home page: <a href="http://xmlgraphics.apache.org/batik/">http://xmlgraphics.apache.org/batik/</a></p>
<p>Path to dependency file: /dependency-reduced-pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/xmlgraphics/batik-bridge/1.13/batik-bridge-1.13.jar</p>
<p>
Dependency Hierarchy:
- poi-ooxml-5.0.0.jar (Root Library)
- batik-all-1.13.jar
- :x: **batik-bridge-1.13.jar** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to load a url thru the jar protocol. This issue affects Apache XML Graphics Batik 1.14.
<p>Publish Date: 2022-09-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-38398>CVE-2022-38398</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in batik all jar batik bridge jar cve medium severity vulnerability vulnerable libraries batik all jar batik bridge jar batik all jar batik aggregate artifact path to dependency file dependency reduced pom xml path to vulnerable library home wss scanner repository org apache xmlgraphics batik all batik all jar dependency hierarchy poi ooxml jar root library x batik all jar vulnerable library batik bridge jar batik bridge library home page a href path to dependency file dependency reduced pom xml path to vulnerable library home wss scanner repository org apache xmlgraphics batik bridge batik bridge jar dependency hierarchy poi ooxml jar root library batik all jar x batik bridge jar vulnerable library found in base branch master vulnerability details server side request forgery ssrf vulnerability in batik of apache xml graphics allows an attacker to load a url thru the jar protocol this issue affects apache xml graphics batik publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href step up your open source security game with mend
| 0
|
754,761
| 26,400,817,000
|
IssuesEvent
|
2023-01-13 00:56:01
|
nikolaystrikhar/gutenberg-forms
|
https://api.github.com/repos/nikolaystrikhar/gutenberg-forms
|
closed
|
Send data to success URL
|
enhancement low-priority
|
Hello guys!
I need to pass the collected data in form to the success URL.
It can be using query string(GET), POST into the success URL, cookies...
It's possible to do this today?
Thanks! :)
|
1.0
|
Send data to success URL - Hello guys!
I need to pass the collected data in form to the success URL.
It can be using query string(GET), POST into the success URL, cookies...
It's possible to do this today?
Thanks! :)
|
non_process
|
send data to success url hello guys i need to pass the collected data in form to the success url it can be using query string get post into the success url cookies it s possible to do this today thanks
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.