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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9,288
| 12,305,768,930
|
IssuesEvent
|
2020-05-11 23:25:17
|
kubeflow/testing
|
https://api.github.com/repos/kubeflow/testing
|
opened
|
Setup buildcop
|
area/engprod kind/process priority/p0
|
We need to setup an appropriate buildcop team and "rotation" in order to spread the load of managing the CI/CD infrastructure along.
Here are the big ticket items
1. Identify appropriate folks to be on the build copy rotation
* These should be folks with a long track record of contribution and involvement in Kubeflow
* There is non trivial setup to be done getting folks setup with access to kubeflow-ci
1. Document process for getting people added to the buildcop team.
|
1.0
|
Setup buildcop - We need to setup an appropriate buildcop team and "rotation" in order to spread the load of managing the CI/CD infrastructure along.
Here are the big ticket items
1. Identify appropriate folks to be on the build copy rotation
* These should be folks with a long track record of contribution and involvement in Kubeflow
* There is non trivial setup to be done getting folks setup with access to kubeflow-ci
1. Document process for getting people added to the buildcop team.
|
process
|
setup buildcop we need to setup an appropriate buildcop team and rotation in order to spread the load of managing the ci cd infrastructure along here are the big ticket items identify appropriate folks to be on the build copy rotation these should be folks with a long track record of contribution and involvement in kubeflow there is non trivial setup to be done getting folks setup with access to kubeflow ci document process for getting people added to the buildcop team
| 1
|
15,153
| 18,908,430,911
|
IssuesEvent
|
2021-11-16 11:35:14
|
streamnative/pulsar-flink
|
https://api.github.com/repos/streamnative/pulsar-flink
|
closed
|
[FEATURE] Support start consume from timestamp in flink sql job
|
type/feature platform/data-processing
|
**Is your feature request related to a problem? Please describe.**
pulsar-flink connector now can not support start consume topic from timestamp like flink-kafka connector.
**Describe the solution you'd like**
when consume from a pulsar topic in a flink sql job, set the consume mode as `timestamp`, and set the start consume timestamp value in DDL, like
```
create table test_in(
name string,
proctime as PROCTIME()
) with (
'connector' = 'pulsar',
'topic' = 'persistent://public/default/test_in_1',
'value.format' = 'csv',
'service-url' = '',
'admin-url' = '',
'properties.pulsar.reader.subscription-role-prefix' = 'test_consume_sub',
'scan.startup.mode' = 'timestamp',
'scan.startup.timestamp-millis' = '1636945080000'
);
```
when the sql job started, read the configed mode and value, and seek the reader to the timestamp, by use `reader.seek(...)` method.
**Describe alternatives you've considered**
**Additional context**
|
1.0
|
[FEATURE] Support start consume from timestamp in flink sql job - **Is your feature request related to a problem? Please describe.**
pulsar-flink connector now can not support start consume topic from timestamp like flink-kafka connector.
**Describe the solution you'd like**
when consume from a pulsar topic in a flink sql job, set the consume mode as `timestamp`, and set the start consume timestamp value in DDL, like
```
create table test_in(
name string,
proctime as PROCTIME()
) with (
'connector' = 'pulsar',
'topic' = 'persistent://public/default/test_in_1',
'value.format' = 'csv',
'service-url' = '',
'admin-url' = '',
'properties.pulsar.reader.subscription-role-prefix' = 'test_consume_sub',
'scan.startup.mode' = 'timestamp',
'scan.startup.timestamp-millis' = '1636945080000'
);
```
when the sql job started, read the configed mode and value, and seek the reader to the timestamp, by use `reader.seek(...)` method.
**Describe alternatives you've considered**
**Additional context**
|
process
|
support start consume from timestamp in flink sql job is your feature request related to a problem please describe pulsar flink connector now can not support start consume topic from timestamp like flink kafka connector describe the solution you d like when consume from a pulsar topic in a flink sql job set the consume mode as timestamp and set the start consume timestamp value in ddl like create table test in name string proctime as proctime with connector pulsar topic persistent public default test in value format csv service url admin url properties pulsar reader subscription role prefix test consume sub scan startup mode timestamp scan startup timestamp millis when the sql job started read the configed mode and value and seek the reader to the timestamp by use reader seek method describe alternatives you ve considered additional context
| 1
|
7,057
| 10,216,698,494
|
IssuesEvent
|
2019-08-15 11:28:36
|
eobermuhlner/big-math
|
https://api.github.com/repos/eobermuhlner/big-math
|
closed
|
Prepare release 2.2.0
|
development process
|
- [x] run performance benchmarks, create png, commit
- [x] add release number header to release note
- [x] rename release note
- [x] change version in `build.gradle`
- [x] upload artifacts to maven central
- [x] uncomment task `uploadArtifacts` in `build.gradle`
- [x] run `./gradlew clean`
- [x] run `./gradlew :ch.obermuhlner.math.big:uploadArchives`
- [x] comment task `uploadArtifacts` in `build.gradle`
- [x] go to https://oss.sonatype.org/
- [x] in tab 'Staging Repositories' locate own Repository (typically at the end of the list)
- [x] verify content of own Repository (version number!)
- [x] `Close` own Repository
- [x] `Refresh` until `Release` becomes enabled
- [x] `Release` own Repository
- [x] create github release from same artifacts
- [x] Create new draft release
- [x] Copy content of release note into draft release
- [x] Add artefacts from gradle build to draft release
- [x] big-math-*.jar
- [x] big-math-*-javadoc.jar
- [x] big-math-*-sources.jar
- [x] Publish release
- [x] update readme
- [x] add generated javadoc to `docs/javadoc`
- [x] update `docs/index.md`
- [x] update dependent projects
- [x] create empty release note for next release
|
1.0
|
Prepare release 2.2.0 - - [x] run performance benchmarks, create png, commit
- [x] add release number header to release note
- [x] rename release note
- [x] change version in `build.gradle`
- [x] upload artifacts to maven central
- [x] uncomment task `uploadArtifacts` in `build.gradle`
- [x] run `./gradlew clean`
- [x] run `./gradlew :ch.obermuhlner.math.big:uploadArchives`
- [x] comment task `uploadArtifacts` in `build.gradle`
- [x] go to https://oss.sonatype.org/
- [x] in tab 'Staging Repositories' locate own Repository (typically at the end of the list)
- [x] verify content of own Repository (version number!)
- [x] `Close` own Repository
- [x] `Refresh` until `Release` becomes enabled
- [x] `Release` own Repository
- [x] create github release from same artifacts
- [x] Create new draft release
- [x] Copy content of release note into draft release
- [x] Add artefacts from gradle build to draft release
- [x] big-math-*.jar
- [x] big-math-*-javadoc.jar
- [x] big-math-*-sources.jar
- [x] Publish release
- [x] update readme
- [x] add generated javadoc to `docs/javadoc`
- [x] update `docs/index.md`
- [x] update dependent projects
- [x] create empty release note for next release
|
process
|
prepare release run performance benchmarks create png commit add release number header to release note rename release note change version in build gradle upload artifacts to maven central uncomment task uploadartifacts in build gradle run gradlew clean run gradlew ch obermuhlner math big uploadarchives comment task uploadartifacts in build gradle go to in tab staging repositories locate own repository typically at the end of the list verify content of own repository version number close own repository refresh until release becomes enabled release own repository create github release from same artifacts create new draft release copy content of release note into draft release add artefacts from gradle build to draft release big math jar big math javadoc jar big math sources jar publish release update readme add generated javadoc to docs javadoc update docs index md update dependent projects create empty release note for next release
| 1
|
16,275
| 20,883,882,127
|
IssuesEvent
|
2022-03-23 01:23:31
|
openvinotoolkit/openvino
|
https://api.github.com/repos/openvinotoolkit/openvino
|
closed
|
Custom preprocess command
|
category: preprocessing feature
|
Greetings!
I am interested in implementing custom preprocess command.
I had had a look at the geometric_transformations.py and implemented a custom command with `Resize` in mind.
I also added that command inside the __init__.py in preprocessor folder but it doesn't get called for when added inside the `.yml` file's `preprocess` entry.
Any thoughts on how to implement this?
Best regards,
Nikola
|
1.0
|
Custom preprocess command - Greetings!
I am interested in implementing custom preprocess command.
I had had a look at the geometric_transformations.py and implemented a custom command with `Resize` in mind.
I also added that command inside the __init__.py in preprocessor folder but it doesn't get called for when added inside the `.yml` file's `preprocess` entry.
Any thoughts on how to implement this?
Best regards,
Nikola
|
process
|
custom preprocess command greetings i am interested in implementing custom preprocess command i had had a look at the geometric transformations py and implemented a custom command with resize in mind i also added that command inside the init py in preprocessor folder but it doesn t get called for when added inside the yml file s preprocess entry any thoughts on how to implement this best regards nikola
| 1
|
923
| 12,149,003,377
|
IssuesEvent
|
2020-04-24 15:27:12
|
AzureAD/microsoft-authentication-library-for-dotnet
|
https://api.github.com/repos/AzureAD/microsoft-authentication-library-for-dotnet
|
closed
|
[Bug] AcquireTokenForClient throws a null reference exception when using a cert in .cer format / without private key
|
Fixed Supportability bug good first issue
|
**Which Version of MSAL are you using ?**
4.10
**Platform**
netcore (did not test net45, probably the same)
**What authentication flow has the issue?**
Client Creds
**Repro**
```csharp
var certWithNoPrivateKey = new X509Certificate2("path/to/cert.cer");
var cca = // create CCA with certificate
await cca.AcquireTokenForClient(scopes).ExecuteAsync();
```
**Expected behavior**
A nice exception telling me to use a certificate that can be used for signing.
**Actual behavior**
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=Microsoft.Identity.Client
StackTrace:
at Microsoft.Identity.Client.Platforms.netcore.NetCoreCryptographyManager.SignWithCertificate(String message, X509Certificate2 certificate) in C:\g\msal\src\client\Microsoft.Identity.Client\Platforms\netcore\NetCoreCryptographyManager.cs:line 70
**Possible Solution**
Before signing, check if certificate has private key. If there isn't a private key, throw a nice exception.
|
True
|
[Bug] AcquireTokenForClient throws a null reference exception when using a cert in .cer format / without private key - **Which Version of MSAL are you using ?**
4.10
**Platform**
netcore (did not test net45, probably the same)
**What authentication flow has the issue?**
Client Creds
**Repro**
```csharp
var certWithNoPrivateKey = new X509Certificate2("path/to/cert.cer");
var cca = // create CCA with certificate
await cca.AcquireTokenForClient(scopes).ExecuteAsync();
```
**Expected behavior**
A nice exception telling me to use a certificate that can be used for signing.
**Actual behavior**
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=Microsoft.Identity.Client
StackTrace:
at Microsoft.Identity.Client.Platforms.netcore.NetCoreCryptographyManager.SignWithCertificate(String message, X509Certificate2 certificate) in C:\g\msal\src\client\Microsoft.Identity.Client\Platforms\netcore\NetCoreCryptographyManager.cs:line 70
**Possible Solution**
Before signing, check if certificate has private key. If there isn't a private key, throw a nice exception.
|
non_process
|
acquiretokenforclient throws a null reference exception when using a cert in cer format without private key which version of msal are you using platform netcore did not test probably the same what authentication flow has the issue client creds repro csharp var certwithnoprivatekey new path to cert cer var cca create cca with certificate await cca acquiretokenforclient scopes executeasync expected behavior a nice exception telling me to use a certificate that can be used for signing actual behavior system nullreferenceexception hresult message object reference not set to an instance of an object source microsoft identity client stacktrace at microsoft identity client platforms netcore netcorecryptographymanager signwithcertificate string message certificate in c g msal src client microsoft identity client platforms netcore netcorecryptographymanager cs line possible solution before signing check if certificate has private key if there isn t a private key throw a nice exception
| 0
|
30,068
| 6,009,582,426
|
IssuesEvent
|
2017-06-06 10:55:20
|
scipy/scipy
|
https://api.github.com/repos/scipy/scipy
|
closed
|
Mistake in the documentation of `ndimage.distance_transform_bf`.
|
defect Documentation easy-fix scipy.ndimage
|
This was reported on stackoverflow: http://stackoverflow.com/questions/43737790/ndimage-distance-transform-bf-transforms-the-wrong-elements
The docstring for `distance_transform_bf` says
This function calculates the distance transform of the `input`, by
replacing each background element (zero values), with its
shortest distance to the foreground (any element non-zero).
In fact, it replaces foreground elements with the distance to the nearest background element. That is the behavior that is checked in the unit tests.
Here's another example:
```
In [113]: a = np.zeros((6, 6))
In [114]: a[1:-1,1:-1] = 9
In [115]: a
Out[115]:
array([[ 0., 0., 0., 0., 0., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 0., 0., 0., 0., 0.]])
In [116]: distance_transform_bf(a)
Out[116]:
array([[ 0., 0., 0., 0., 0., 0.],
[ 0., 1., 1., 1., 1., 0.],
[ 0., 1., 2., 2., 1., 0.],
[ 0., 1., 2., 2., 1., 0.],
[ 0., 1., 1., 1., 1., 0.],
[ 0., 0., 0., 0., 0., 0.]])
```
Clearly it is the nonzero values that are being replaced with the shortest distance to a zero value.
|
1.0
|
Mistake in the documentation of `ndimage.distance_transform_bf`. - This was reported on stackoverflow: http://stackoverflow.com/questions/43737790/ndimage-distance-transform-bf-transforms-the-wrong-elements
The docstring for `distance_transform_bf` says
This function calculates the distance transform of the `input`, by
replacing each background element (zero values), with its
shortest distance to the foreground (any element non-zero).
In fact, it replaces foreground elements with the distance to the nearest background element. That is the behavior that is checked in the unit tests.
Here's another example:
```
In [113]: a = np.zeros((6, 6))
In [114]: a[1:-1,1:-1] = 9
In [115]: a
Out[115]:
array([[ 0., 0., 0., 0., 0., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 9., 9., 9., 9., 0.],
[ 0., 0., 0., 0., 0., 0.]])
In [116]: distance_transform_bf(a)
Out[116]:
array([[ 0., 0., 0., 0., 0., 0.],
[ 0., 1., 1., 1., 1., 0.],
[ 0., 1., 2., 2., 1., 0.],
[ 0., 1., 2., 2., 1., 0.],
[ 0., 1., 1., 1., 1., 0.],
[ 0., 0., 0., 0., 0., 0.]])
```
Clearly it is the nonzero values that are being replaced with the shortest distance to a zero value.
|
non_process
|
mistake in the documentation of ndimage distance transform bf this was reported on stackoverflow the docstring for distance transform bf says this function calculates the distance transform of the input by replacing each background element zero values with its shortest distance to the foreground any element non zero in fact it replaces foreground elements with the distance to the nearest background element that is the behavior that is checked in the unit tests here s another example in a np zeros in a in a out array in distance transform bf a out array clearly it is the nonzero values that are being replaced with the shortest distance to a zero value
| 0
|
2,971
| 5,962,795,344
|
IssuesEvent
|
2017-05-30 00:55:14
|
Data4Democracy/quorum
|
https://api.github.com/repos/Data4Democracy/quorum
|
opened
|
[Processor – AWS ] Add functionally to store data on AWS
|
processor
|
Add functionality so that the output from a consumer can be efficiently stored on an S3 bucket.
|
1.0
|
[Processor – AWS ] Add functionally to store data on AWS - Add functionality so that the output from a consumer can be efficiently stored on an S3 bucket.
|
process
|
add functionally to store data on aws add functionality so that the output from a consumer can be efficiently stored on an bucket
| 1
|
350,612
| 31,930,842,947
|
IssuesEvent
|
2023-09-19 07:18:35
|
Convergence-Project/step-backend
|
https://api.github.com/repos/Convergence-Project/step-backend
|
closed
|
[2주차] (문제집) 문제집 리그 삭제 구현
|
🎯test ✨feature
|
✏️Description
-
문제집 리그 삭제 구현
✅TODO
-
- [x] 삭제 테스트 코드 작성
- [x] 컨트롤러 및 프론트 연동
🐾ETC
-
|
1.0
|
[2주차] (문제집) 문제집 리그 삭제 구현 - ✏️Description
-
문제집 리그 삭제 구현
✅TODO
-
- [x] 삭제 테스트 코드 작성
- [x] 컨트롤러 및 프론트 연동
🐾ETC
-
|
non_process
|
문제집 문제집 리그 삭제 구현 ✏️description 문제집 리그 삭제 구현 ✅todo 삭제 테스트 코드 작성 컨트롤러 및 프론트 연동 🐾etc
| 0
|
16,071
| 20,240,128,659
|
IssuesEvent
|
2022-02-14 08:27:40
|
metallb/metallb
|
https://api.github.com/repos/metallb/metallb
|
closed
|
CNCF: CII best practices badge
|
process
|
From CNCF onboarding https://github.com/cncf/toc/issues/720 :
> CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en
|
1.0
|
CNCF: CII best practices badge - From CNCF onboarding https://github.com/cncf/toc/issues/720 :
> CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en
|
process
|
cncf cii best practices badge from cncf onboarding cii start on a cii best practices badge
| 1
|
189,394
| 15,187,332,381
|
IssuesEvent
|
2021-02-15 13:39:35
|
open-contracting/standard
|
https://api.github.com/repos/open-contracting/standard
|
opened
|
General guidance on version upgrades
|
Focus - Documentation
|
With the release of OCDS 1.2, many data publishers will wonder how to upgrade, the available options, the potential side effects etc.
The revision and upgrade process is well documented in [Governance](https://standard.open-contracting.org/latest/en/governance/?highlight=upgrade#versioning-and-upgrade-process) from a standardization point of view, but not from a data publication point of view.
|
1.0
|
General guidance on version upgrades - With the release of OCDS 1.2, many data publishers will wonder how to upgrade, the available options, the potential side effects etc.
The revision and upgrade process is well documented in [Governance](https://standard.open-contracting.org/latest/en/governance/?highlight=upgrade#versioning-and-upgrade-process) from a standardization point of view, but not from a data publication point of view.
|
non_process
|
general guidance on version upgrades with the release of ocds many data publishers will wonder how to upgrade the available options the potential side effects etc the revision and upgrade process is well documented in from a standardization point of view but not from a data publication point of view
| 0
|
4,694
| 7,529,065,651
|
IssuesEvent
|
2018-04-14 00:18:03
|
ncbo/bioportal-project
|
https://api.github.com/repos/ncbo/bioportal-project
|
closed
|
MIRO: bad pull location, corrupt submission objects
|
ontology processing problem
|
The pull URL for MIRO is no longer valid, which has resulted in 9 submissions that show status of "uploaded, error rdf". These invalid submissions should be deleted, and the [pull URL](http://purl.obolibrary.org/obo/miro.obo) removed. This is an OBO library ontology, and they are aware of the broken PURL to access the ontology sources (see https://github.com/OBOFoundry/OBOFoundry.github.io/issues/257).
|
1.0
|
MIRO: bad pull location, corrupt submission objects - The pull URL for MIRO is no longer valid, which has resulted in 9 submissions that show status of "uploaded, error rdf". These invalid submissions should be deleted, and the [pull URL](http://purl.obolibrary.org/obo/miro.obo) removed. This is an OBO library ontology, and they are aware of the broken PURL to access the ontology sources (see https://github.com/OBOFoundry/OBOFoundry.github.io/issues/257).
|
process
|
miro bad pull location corrupt submission objects the pull url for miro is no longer valid which has resulted in submissions that show status of uploaded error rdf these invalid submissions should be deleted and the removed this is an obo library ontology and they are aware of the broken purl to access the ontology sources see
| 1
|
21,151
| 28,127,350,069
|
IssuesEvent
|
2023-03-31 18:59:21
|
hsmusic/hsmusic-data
|
https://api.github.com/repos/hsmusic/hsmusic-data
|
closed
|
Art tag investigation for Skaia in king's staffs/god tier clocks
|
scope: other/additional type: data fix type: involved process what: art tags
|
Multiple times in the comic these are zoomed into to reveal they're actually also literally Skaia, I think mainly just as a rule of cool thing but whatever. These are inconsistently not tagged as Skaia, and there are probably a fair amount of instances hiding around the wiki.
|
1.0
|
Art tag investigation for Skaia in king's staffs/god tier clocks - Multiple times in the comic these are zoomed into to reveal they're actually also literally Skaia, I think mainly just as a rule of cool thing but whatever. These are inconsistently not tagged as Skaia, and there are probably a fair amount of instances hiding around the wiki.
|
process
|
art tag investigation for skaia in king s staffs god tier clocks multiple times in the comic these are zoomed into to reveal they re actually also literally skaia i think mainly just as a rule of cool thing but whatever these are inconsistently not tagged as skaia and there are probably a fair amount of instances hiding around the wiki
| 1
|
2,240
| 5,088,640,696
|
IssuesEvent
|
2016-12-31 23:49:25
|
sw4j-org/tool-jpa-processor
|
https://api.github.com/repos/sw4j-org/tool-jpa-processor
|
opened
|
Handle @ManyToMany Annotation
|
annotation processor task
|
Handle the `@ManyToMany` annotation for a property or field.
See [JSR 338: Java Persistence API, Version 2.1](http://download.oracle.com/otn-pub/jcp/persistence-2_1-fr-eval-spec/JavaPersistence.pdf)
- 11.1.29 ManyToMany Annotation
|
1.0
|
Handle @ManyToMany Annotation - Handle the `@ManyToMany` annotation for a property or field.
See [JSR 338: Java Persistence API, Version 2.1](http://download.oracle.com/otn-pub/jcp/persistence-2_1-fr-eval-spec/JavaPersistence.pdf)
- 11.1.29 ManyToMany Annotation
|
process
|
handle manytomany annotation handle the manytomany annotation for a property or field see manytomany annotation
| 1
|
7,001
| 10,145,608,485
|
IssuesEvent
|
2019-08-05 05:16:21
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Typo under 'Permissions required to create an Automation account' section
|
Pri2 automation/svc cxp doc-enhancement process-automation/subsvc triaged
|
The second bullet should read "...under Azure Active Directory > MANAGE > User settings, if App registrations...". Currently reads incorrectly as "...under Azure Active Directory > MANAGE > App registrations, if App registrations...". Please fix, thanks.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 9b4440e0-1ff5-0fd3-6983-d5f6ed86e818
* Version Independent ID: 8d6aecae-1a58-83aa-45f7-306fb6c92d38
* Content: [Create a standalone Azure Automation account](https://docs.microsoft.com/en-us/azure/automation/automation-create-standalone-account)
* Content Source: [articles/automation/automation-create-standalone-account.md](https://github.com/Microsoft/azure-docs/blob/master/articles/automation/automation-create-standalone-account.md)
* Service: **automation**
* Sub-service: **process-automation**
* GitHub Login: @bobbytreed
* Microsoft Alias: **robreed**
|
1.0
|
Typo under 'Permissions required to create an Automation account' section - The second bullet should read "...under Azure Active Directory > MANAGE > User settings, if App registrations...". Currently reads incorrectly as "...under Azure Active Directory > MANAGE > App registrations, if App registrations...". Please fix, thanks.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 9b4440e0-1ff5-0fd3-6983-d5f6ed86e818
* Version Independent ID: 8d6aecae-1a58-83aa-45f7-306fb6c92d38
* Content: [Create a standalone Azure Automation account](https://docs.microsoft.com/en-us/azure/automation/automation-create-standalone-account)
* Content Source: [articles/automation/automation-create-standalone-account.md](https://github.com/Microsoft/azure-docs/blob/master/articles/automation/automation-create-standalone-account.md)
* Service: **automation**
* Sub-service: **process-automation**
* GitHub Login: @bobbytreed
* Microsoft Alias: **robreed**
|
process
|
typo under permissions required to create an automation account section the second bullet should read under azure active directory gt manage gt user settings if app registrations currently reads incorrectly as under azure active directory gt manage gt app registrations if app registrations please fix thanks document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service automation sub service process automation github login bobbytreed microsoft alias robreed
| 1
|
92,292
| 18,817,330,793
|
IssuesEvent
|
2021-11-10 01:47:45
|
sourcegraph/sourcegraph
|
https://api.github.com/repos/sourcegraph/sourcegraph
|
closed
|
insights: [FE] Implement gql API for dashboard creation/edit UI
|
team/code-insights insights-settings-migration
|
### Context
Things to implement on these pages:
1. `getInsightsSubjects` - this method provides a list of possible dashboard visibility things. (at the moment all dashboards are stored in setting cascade and therefore at the moment we use setting subject there)
2. `createDashboard` mutation
3. `updateDashboard` mutation
**Note** that if you have to extend something in the API that should be supported in setting-based API too.
|
1.0
|
insights: [FE] Implement gql API for dashboard creation/edit UI -
### Context
Things to implement on these pages:
1. `getInsightsSubjects` - this method provides a list of possible dashboard visibility things. (at the moment all dashboards are stored in setting cascade and therefore at the moment we use setting subject there)
2. `createDashboard` mutation
3. `updateDashboard` mutation
**Note** that if you have to extend something in the API that should be supported in setting-based API too.
|
non_process
|
insights implement gql api for dashboard creation edit ui context things to implement on these pages getinsightssubjects this method provides a list of possible dashboard visibility things at the moment all dashboards are stored in setting cascade and therefore at the moment we use setting subject there createdashboard mutation updatedashboard mutation note that if you have to extend something in the api that should be supported in setting based api too
| 0
|
151,895
| 23,889,404,613
|
IssuesEvent
|
2022-09-08 10:14:08
|
stores-cedcommerce/HSL-Home-page-design
|
https://api.github.com/repos/stores-cedcommerce/HSL-Home-page-design
|
closed
|
For the instagram feed, for the mobile view and tab view the insta icon will not be visible.
|
Tab Mobile Design / UI / UX Not required homepage
|
**Actual result:**
For the instagram feed, for the mobile view and tab view the insta icon will not be visible.

**Expected result:**
We can use the insta gram icon on the instagram feed.( suggestion)
|
1.0
|
For the instagram feed, for the mobile view and tab view the insta icon will not be visible. - **Actual result:**
For the instagram feed, for the mobile view and tab view the insta icon will not be visible.

**Expected result:**
We can use the insta gram icon on the instagram feed.( suggestion)
|
non_process
|
for the instagram feed for the mobile view and tab view the insta icon will not be visible actual result for the instagram feed for the mobile view and tab view the insta icon will not be visible expected result we can use the insta gram icon on the instagram feed suggestion
| 0
|
10,486
| 13,253,269,491
|
IssuesEvent
|
2020-08-20 07:16:59
|
xingty/xingty.github.io
|
https://api.github.com/repos/xingty/xingty.github.io
|
opened
|
谈谈Spring中的InstantiationAwareBeanPostProcessor - Bigbyto's blog
|
Gitalk spring-instantiation-aware-bean-post-processor
|
https://wiyi.org/spring-instantiation-aware-bean-post-processor.html
熟悉Spring的朋友应该都知道InstantiationAwareBeanPostProcessor这个接口。从它的继承结构可以看出它是一个BeanPostProcessor,不过它是一个非常特殊的BeanPostProcessor,因为它的贯穿了bean创建的每一个周期。Bean创建流程上面展示了Instan...
|
1.0
|
谈谈Spring中的InstantiationAwareBeanPostProcessor - Bigbyto's blog - https://wiyi.org/spring-instantiation-aware-bean-post-processor.html
熟悉Spring的朋友应该都知道InstantiationAwareBeanPostProcessor这个接口。从它的继承结构可以看出它是一个BeanPostProcessor,不过它是一个非常特殊的BeanPostProcessor,因为它的贯穿了bean创建的每一个周期。Bean创建流程上面展示了Instan...
|
process
|
谈谈spring中的instantiationawarebeanpostprocessor bigbyto s blog 熟悉spring的朋友应该都知道instantiationawarebeanpostprocessor这个接口。从它的继承结构可以看出它是一个beanpostprocessor,不过它是一个非常特殊的beanpostprocessor,因为它的贯穿了bean创建的每一个周期。bean创建流程上面展示了instan
| 1
|
647,307
| 21,098,311,162
|
IssuesEvent
|
2022-04-04 12:28:34
|
AY2122S2-CS2103T-T09-3/tp
|
https://api.github.com/repos/AY2122S2-CS2103T-T09-3/tp
|
closed
|
[PE-D] Minor bug regarding adding of rating
|
type.Task priority.High severity.VeryLow
|
I noticed that you could put as the rating "+1", "+3" etc; and it would still count. Is this an intended feature?
<!--session: 1648792905347-3859179d-ce8b-44f6-9a12-effe95a47d11-->
<!--Version: Web v3.4.2-->
-------------
Labels: `severity.VeryLow` `type.FunctionalityBug`
original: NicsunXnus/ped#7
|
1.0
|
[PE-D] Minor bug regarding adding of rating - I noticed that you could put as the rating "+1", "+3" etc; and it would still count. Is this an intended feature?
<!--session: 1648792905347-3859179d-ce8b-44f6-9a12-effe95a47d11-->
<!--Version: Web v3.4.2-->
-------------
Labels: `severity.VeryLow` `type.FunctionalityBug`
original: NicsunXnus/ped#7
|
non_process
|
minor bug regarding adding of rating i noticed that you could put as the rating etc and it would still count is this an intended feature labels severity verylow type functionalitybug original nicsunxnus ped
| 0
|
528,464
| 15,367,553,194
|
IssuesEvent
|
2021-03-02 03:33:03
|
apcountryman/picolibrary
|
https://api.github.com/repos/apcountryman/picolibrary
|
closed
|
Document special member functions expected by concepts
|
priority-normal status-awaiting_approval type-enhancement
|
Document (and default) the special member functions that each concept expects.
|
1.0
|
Document special member functions expected by concepts - Document (and default) the special member functions that each concept expects.
|
non_process
|
document special member functions expected by concepts document and default the special member functions that each concept expects
| 0
|
81,822
| 15,806,052,919
|
IssuesEvent
|
2021-04-04 02:47:02
|
metio/yosql
|
https://api.github.com/repos/metio/yosql
|
closed
|
support methods that return only a single result
|
CodeGen :: API Priority :: High Type :: Enhancement
|
`findOne` in case only one result is expected and everything else is an error.
`findFirst` in case only the first of many should be returned
|
1.0
|
support methods that return only a single result - `findOne` in case only one result is expected and everything else is an error.
`findFirst` in case only the first of many should be returned
|
non_process
|
support methods that return only a single result findone in case only one result is expected and everything else is an error findfirst in case only the first of many should be returned
| 0
|
130,965
| 18,214,360,562
|
IssuesEvent
|
2021-09-30 01:02:17
|
doc-ai/tensorflow
|
https://api.github.com/repos/doc-ai/tensorflow
|
opened
|
CVE-2021-37678 (High) detected in tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl
|
security vulnerability
|
## CVE-2021-37678 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>Path to vulnerable library: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37678>CVE-2021-37678</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: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"tensorflow","packageVersion":"2.0.0b1","packageFilePaths":["/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt"],"isTransitiveDependency":false,"dependencyTree":"tensorflow:2.0.0b1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-37678","vulnerabilityDetails":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37678","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Local","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-37678 (High) detected in tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl - ## CVE-2021-37678 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>Path to vulnerable library: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37678>CVE-2021-37678</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: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"tensorflow","packageVersion":"2.0.0b1","packageFilePaths":["/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt"],"isTransitiveDependency":false,"dependencyTree":"tensorflow:2.0.0b1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-37678","vulnerabilityDetails":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37678","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Local","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_process
|
cve high detected in tensorflow whl cve high severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file tensorflow tensorflow lite micro examples magic wand train requirements txt path to vulnerable library tensorflow tensorflow lite micro examples magic wand train requirements txt dependency hierarchy x tensorflow whl vulnerable library vulnerability details tensorflow is an end to end open source platform for machine learning in affected versions tensorflow and keras can be tricked to perform arbitrary code execution when deserializing a keras model from yaml format the uses yaml unsafe load which can perform arbitrary code execution on the input given that yaml format support requires a significant amount of work we have removed it for now we have patched the issue in github commit the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow and tensorflow as these are also affected and still in supported range publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree tensorflow isminimumfixversionavailable true minimumfixversion tensorflow tensorflow cpu tensorflow gpu basebranches vulnerabilityidentifier cve vulnerabilitydetails tensorflow is an end to end open source platform for machine learning in affected versions tensorflow and keras can be tricked to perform arbitrary code execution when deserializing a keras model from yaml format the uses yaml unsafe load which can perform arbitrary code execution on the input given that yaml format support requires a significant amount of work we have removed it for now we have patched the issue in github commit the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow and tensorflow as these are also affected and still in supported range vulnerabilityurl
| 0
|
6,256
| 9,215,618,090
|
IssuesEvent
|
2019-03-11 04:11:17
|
dotnet/corefx
|
https://api.github.com/repos/dotnet/corefx
|
closed
|
Test failure: System.Diagnostics.Tests.ProcessTests/ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith: \"vi\")
|
area-System.Diagnostics.Process bug os-linux
|
Opened on behalf of @Sunny-pu
The test `System.Diagnostics.Tests.ProcessTests/ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith: \"vi\")` has failed.
System.InvalidOperationException : Process has exited, so the requested information is not available.
Stack Trace:
at System.Diagnostics.Process.EnsureState(State state) in /root/corefx-1980122/src/System.Diagnostics.Process/src/System/Diagnostics/Process.cs:line 954
at System.Diagnostics.Process.get_ProcessName() in /root/corefx-1980122/src/System.Diagnostics.Process/src/System/Diagnostics/Process.cs:line 507
at System.Diagnostics.Tests.ProcessTests.ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(String programToOpenWith) in /root/corefx-1980122/src/System.Diagnostics.Process/tests/ProcessTests.Unix.cs:line 194
Build : 3.0 - 20180827.01 (Core Tests)
Failing configurations:
- Alpine.36.Amd64-x64
- Release
Details: https://mc.dot.net/#/product/netcore/30/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fcli~2F/build/20180827.01/workItem/System.Diagnostics.Process.Tests/analysis/xunit/System.Diagnostics.Tests.ProcessTests~2FProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith:%20%5C%22vi%5C%22)
|
1.0
|
Test failure: System.Diagnostics.Tests.ProcessTests/ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith: \"vi\") - Opened on behalf of @Sunny-pu
The test `System.Diagnostics.Tests.ProcessTests/ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith: \"vi\")` has failed.
System.InvalidOperationException : Process has exited, so the requested information is not available.
Stack Trace:
at System.Diagnostics.Process.EnsureState(State state) in /root/corefx-1980122/src/System.Diagnostics.Process/src/System/Diagnostics/Process.cs:line 954
at System.Diagnostics.Process.get_ProcessName() in /root/corefx-1980122/src/System.Diagnostics.Process/src/System/Diagnostics/Process.cs:line 507
at System.Diagnostics.Tests.ProcessTests.ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(String programToOpenWith) in /root/corefx-1980122/src/System.Diagnostics.Process/tests/ProcessTests.Unix.cs:line 194
Build : 3.0 - 20180827.01 (Core Tests)
Failing configurations:
- Alpine.36.Amd64-x64
- Release
Details: https://mc.dot.net/#/product/netcore/30/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fcli~2F/build/20180827.01/workItem/System.Diagnostics.Process.Tests/analysis/xunit/System.Diagnostics.Tests.ProcessTests~2FProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith:%20%5C%22vi%5C%22)
|
process
|
test failure system diagnostics tests processtests processstart openfileonlinux usesspecifiedprogramusingargumentlist programtoopenwith vi opened on behalf of sunny pu the test system diagnostics tests processtests processstart openfileonlinux usesspecifiedprogramusingargumentlist programtoopenwith vi has failed system invalidoperationexception process has exited so the requested information is not available stack trace at system diagnostics process ensurestate state state in root corefx src system diagnostics process src system diagnostics process cs line at system diagnostics process get processname in root corefx src system diagnostics process src system diagnostics process cs line at system diagnostics tests processtests processstart openfileonlinux usesspecifiedprogramusingargumentlist string programtoopenwith in root corefx src system diagnostics process tests processtests unix cs line build core tests failing configurations alpine release details
| 1
|
6,949
| 7,801,612,433
|
IssuesEvent
|
2018-06-09 23:48:43
|
fga-gpp-mds/2018.1_Gerencia_mais
|
https://api.github.com/repos/fga-gpp-mds/2018.1_Gerencia_mais
|
closed
|
[TS57]Implementar microserviço para enviar email
|
[EPS] [Important] [MICROSERVICE] [Technical Stories]
|
eu como desenvolvedor
desejo que seja implementado microserviço para enviar email
para que possa ser enviado quadros semanais para médicos.
|
1.0
|
[TS57]Implementar microserviço para enviar email - eu como desenvolvedor
desejo que seja implementado microserviço para enviar email
para que possa ser enviado quadros semanais para médicos.
|
non_process
|
implementar microserviço para enviar email eu como desenvolvedor desejo que seja implementado microserviço para enviar email para que possa ser enviado quadros semanais para médicos
| 0
|
820,831
| 30,791,660,593
|
IssuesEvent
|
2023-07-31 16:36:40
|
dag-hammarskjold-library/dlx-rest
|
https://api.github.com/repos/dag-hammarskjold-library/dlx-rest
|
opened
|
New save action for field 089
|
priority: high type: configuration function: automatic
|
We need a new save action that automatically adds 089__a:veto to field that has 089__b:B06. The subfield $a should be added to the same field.
So when a user enters this:

This is what should be added upon save:

|
1.0
|
New save action for field 089 - We need a new save action that automatically adds 089__a:veto to field that has 089__b:B06. The subfield $a should be added to the same field.
So when a user enters this:

This is what should be added upon save:

|
non_process
|
new save action for field we need a new save action that automatically adds a veto to field that has b the subfield a should be added to the same field so when a user enters this this is what should be added upon save
| 0
|
222,441
| 7,432,197,086
|
IssuesEvent
|
2018-03-25 22:10:10
|
RoboJackets/apiary
|
https://api.github.com/repos/RoboJackets/apiary
|
closed
|
Manual attendance entry for teams
|
area / frontend priority / medium type / feature
|
Administrators (not necessarily the `admin` role per se, but perhaps `officer-i`) should be able to manually enter a GTID, date, and team.
|
1.0
|
Manual attendance entry for teams - Administrators (not necessarily the `admin` role per se, but perhaps `officer-i`) should be able to manually enter a GTID, date, and team.
|
non_process
|
manual attendance entry for teams administrators not necessarily the admin role per se but perhaps officer i should be able to manually enter a gtid date and team
| 0
|
266,766
| 8,374,883,464
|
IssuesEvent
|
2018-10-05 14:52:19
|
nco/nco
|
https://api.github.com/repos/nco/nco
|
opened
|
ncap2 array notation unexpected behavior
|
bug high priority
|
Please investigate this and fix this if possible or explain why it is not.
Correct/Expected:
```
zender@aerosol:~$ ncap2 -O -s 'three_dmn_rec_var(:,:,2:)=0*three_dmn_rec_var(:,:,2:);print(three_dmn_rec_var)' ~/nco/data/in.nc ~/foo.nc
three_dmn_rec_var[0]=1
three_dmn_rec_var[1]=2
three_dmn_rec_var[2]=0
three_dmn_rec_var[3]=0
three_dmn_rec_var[4]=5
three_dmn_rec_var[5]=6
three_dmn_rec_var[6]=0
three_dmn_rec_var[7]=0
```
Incorrect/Unexpected:
```
zender@aerosol:~$ ncap2 -O -s 'three_dmn_rec_var(:,:,2:)*=0;print(three_dmn_rec_var)' ~/nco/data/in.nc ~/foo.nc
three_dmn_rec_var[0]=9.96921e+36
three_dmn_rec_var[1]=9.96921e+36
three_dmn_rec_var[2]=0
three_dmn_rec_var[3]=0
three_dmn_rec_var[4]=9.96921e+36
three_dmn_rec_var[5]=9.96921e+36
three_dmn_rec_var[6]=0
three_dmn_rec_var[7]=0
```
|
1.0
|
ncap2 array notation unexpected behavior - Please investigate this and fix this if possible or explain why it is not.
Correct/Expected:
```
zender@aerosol:~$ ncap2 -O -s 'three_dmn_rec_var(:,:,2:)=0*three_dmn_rec_var(:,:,2:);print(three_dmn_rec_var)' ~/nco/data/in.nc ~/foo.nc
three_dmn_rec_var[0]=1
three_dmn_rec_var[1]=2
three_dmn_rec_var[2]=0
three_dmn_rec_var[3]=0
three_dmn_rec_var[4]=5
three_dmn_rec_var[5]=6
three_dmn_rec_var[6]=0
three_dmn_rec_var[7]=0
```
Incorrect/Unexpected:
```
zender@aerosol:~$ ncap2 -O -s 'three_dmn_rec_var(:,:,2:)*=0;print(three_dmn_rec_var)' ~/nco/data/in.nc ~/foo.nc
three_dmn_rec_var[0]=9.96921e+36
three_dmn_rec_var[1]=9.96921e+36
three_dmn_rec_var[2]=0
three_dmn_rec_var[3]=0
three_dmn_rec_var[4]=9.96921e+36
three_dmn_rec_var[5]=9.96921e+36
three_dmn_rec_var[6]=0
three_dmn_rec_var[7]=0
```
|
non_process
|
array notation unexpected behavior please investigate this and fix this if possible or explain why it is not correct expected zender aerosol o s three dmn rec var three dmn rec var print three dmn rec var nco data in nc foo nc three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var incorrect unexpected zender aerosol o s three dmn rec var print three dmn rec var nco data in nc foo nc three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var three dmn rec var
| 0
|
126,918
| 17,141,870,790
|
IssuesEvent
|
2021-07-13 10:30:25
|
betagouv/mon-entreprise
|
https://api.github.com/repos/betagouv/mon-entreprise
|
closed
|
Ré-organisation du pied de page
|
good first issue 🎨 design
|
Avec les liens que l'on a ajouté au fur et à mesure, le pied de page est devenu un peu désorganisé :

Par ailleurs, j'ai l'impression que le pied de page actuel est trop large sur mobile et qu'il crée une barre de défilement horizontale sur la page.
|
1.0
|
Ré-organisation du pied de page - Avec les liens que l'on a ajouté au fur et à mesure, le pied de page est devenu un peu désorganisé :

Par ailleurs, j'ai l'impression que le pied de page actuel est trop large sur mobile et qu'il crée une barre de défilement horizontale sur la page.
|
non_process
|
ré organisation du pied de page avec les liens que l on a ajouté au fur et à mesure le pied de page est devenu un peu désorganisé par ailleurs j ai l impression que le pied de page actuel est trop large sur mobile et qu il crée une barre de défilement horizontale sur la page
| 0
|
449,995
| 31,879,825,890
|
IssuesEvent
|
2023-09-16 08:28:00
|
keploy/keploy
|
https://api.github.com/repos/keploy/keploy
|
closed
|
[bug]: same page linked to the next button of pagination navbar
|
bug Documentation Good First Issue Hacktoberfest docs hacktoberfest2023
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior

The next button is showing `introduction` in the introduction page.
### Steps to reproduce
1. Go to https://docs.keploy.io/docs/keploy-explained/introduction/
2. Scroll to the navigation navbar in the bottom.
### Environment
None
### Version
Cloud
### Repository
docs
|
1.0
|
[bug]: same page linked to the next button of pagination navbar - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior

The next button is showing `introduction` in the introduction page.
### Steps to reproduce
1. Go to https://docs.keploy.io/docs/keploy-explained/introduction/
2. Scroll to the navigation navbar in the bottom.
### Environment
None
### Version
Cloud
### Repository
docs
|
non_process
|
same page linked to the next button of pagination navbar is there an existing issue for this i have searched the existing issues current behavior the next button is showing introduction in the introduction page steps to reproduce go to scroll to the navigation navbar in the bottom environment none version cloud repository docs
| 0
|
172,489
| 21,047,082,896
|
IssuesEvent
|
2022-03-31 17:01:38
|
jgeraigery/teamcity-ibm-cloud
|
https://api.github.com/repos/jgeraigery/teamcity-ibm-cloud
|
opened
|
WS-2022-0107 (High) detected in spring-beans-4.3.12.RELEASE.jar
|
security vulnerability
|
## WS-2022-0107 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-4.3.12.RELEASE.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /ibm-cloud-server/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/4.3.12.RELEASE/547dd432d47d0f01d9ccbedc4b705f9f7c1240a/spring-beans-4.3.12.RELEASE.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/4.3.12.RELEASE/547dd432d47d0f01d9ccbedc4b705f9f7c1240a/spring-beans-4.3.12.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- cloud-shared-2017.2.jar (Root Library)
- common-api-2017.2.jar
- :x: **spring-beans-4.3.12.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״.
The current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution).
Please note that the ease of exploitation may diverge by the code implementation.
Currently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux.
Spring Framework 5.3.18 and 5.2.20 have already been released.
WhiteSource’s research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.
This is a temporary WhiteSource ID until an official CVE ID will be released.
<p>Publish Date: 2022-03-30
<p>URL: <a href=https://www.cyberkendra.com/2022/03/springshell-rce-0-day-vulnerability.html>WS-2022-0107</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://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-03-30</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.20.RELEASE,5.3.18</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-beans","packageVersion":"4.3.12.RELEASE","packageFilePaths":["/ibm-cloud-server/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"org.jetbrains.teamcity:cloud-shared:2017.2;org.jetbrains.teamcity:common-api:2017.2;org.springframework:spring-beans:4.3.12.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-beans:5.2.20.RELEASE,5.3.18","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2022-0107","vulnerabilityDetails":"Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״.\n\nThe current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution).\nPlease note that the ease of exploitation may diverge by the code implementation.\n\nCurrently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux.\nSpring Framework 5.3.18 and 5.2.20 have already been released.\n\nWhiteSource’s research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.\nThis is a temporary WhiteSource ID until an official CVE ID will be released.","vulnerabilityUrl":"https://www.cyberkendra.com/2022/03/springshell-rce-0-day-vulnerability.html","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
WS-2022-0107 (High) detected in spring-beans-4.3.12.RELEASE.jar - ## WS-2022-0107 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-4.3.12.RELEASE.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /ibm-cloud-server/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/4.3.12.RELEASE/547dd432d47d0f01d9ccbedc4b705f9f7c1240a/spring-beans-4.3.12.RELEASE.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/4.3.12.RELEASE/547dd432d47d0f01d9ccbedc4b705f9f7c1240a/spring-beans-4.3.12.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- cloud-shared-2017.2.jar (Root Library)
- common-api-2017.2.jar
- :x: **spring-beans-4.3.12.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״.
The current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution).
Please note that the ease of exploitation may diverge by the code implementation.
Currently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux.
Spring Framework 5.3.18 and 5.2.20 have already been released.
WhiteSource’s research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.
This is a temporary WhiteSource ID until an official CVE ID will be released.
<p>Publish Date: 2022-03-30
<p>URL: <a href=https://www.cyberkendra.com/2022/03/springshell-rce-0-day-vulnerability.html>WS-2022-0107</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://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-03-30</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.20.RELEASE,5.3.18</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-beans","packageVersion":"4.3.12.RELEASE","packageFilePaths":["/ibm-cloud-server/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"org.jetbrains.teamcity:cloud-shared:2017.2;org.jetbrains.teamcity:common-api:2017.2;org.springframework:spring-beans:4.3.12.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-beans:5.2.20.RELEASE,5.3.18","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2022-0107","vulnerabilityDetails":"Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״.\n\nThe current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution).\nPlease note that the ease of exploitation may diverge by the code implementation.\n\nCurrently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux.\nSpring Framework 5.3.18 and 5.2.20 have already been released.\n\nWhiteSource’s research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.\nThis is a temporary WhiteSource ID until an official CVE ID will be released.","vulnerabilityUrl":"https://www.cyberkendra.com/2022/03/springshell-rce-0-day-vulnerability.html","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_process
|
ws high detected in spring beans release jar ws high severity vulnerability vulnerable library spring beans release jar spring beans library home page a href path to dependency file ibm cloud server build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring beans release spring beans release jar home wss scanner gradle caches modules files org springframework spring beans release spring beans release jar dependency hierarchy cloud shared jar root library common api jar x spring beans release jar vulnerable library found in base branch master vulnerability details spring framework before and x before are vulnerable due to a vulnerability in spring beans which allows attackers under certain circumstances to achieve remote code execution this vulnerability is also known as ״ ״ or ״springshell״ the current poc related to the attack is done by creating a specially crafted request which manipulates classloader to successfully achieve rce remote code execution please note that the ease of exploitation may diverge by the code implementation currently the exploit requires jdk or higher apache tomcat as the servlet container the application packaged as war and dependency on spring webmvc or spring webflux spring framework and have already been released whitesource’s research team is carefully observing developments and researching the case we will keep updating this page and our whitesource resources with updates this is a temporary whitesource id until an official cve id will be released 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 org springframework spring beans release isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org jetbrains teamcity cloud shared org jetbrains teamcity common api org springframework spring beans release isminimumfixversionavailable true minimumfixversion org springframework spring beans release isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails spring framework before and x before are vulnerable due to a vulnerability in spring beans which allows attackers under certain circumstances to achieve remote code execution this vulnerability is also known as ״ ״ or ״springshell״ n nthe current poc related to the attack is done by creating a specially crafted request which manipulates classloader to successfully achieve rce remote code execution nplease note that the ease of exploitation may diverge by the code implementation n ncurrently the exploit requires jdk or higher apache tomcat as the servlet container the application packaged as war and dependency on spring webmvc or spring webflux nspring framework and have already been released n nwhitesource’s research team is carefully observing developments and researching the case we will keep updating this page and our whitesource resources with updates nthis is a temporary whitesource id until an official cve id will be released vulnerabilityurl
| 0
|
19,925
| 3,787,147,514
|
IssuesEvent
|
2016-03-21 09:15:28
|
red/red
|
https://api.github.com/repos/red/red
|
closed
|
Console crashes when `word!` used with `url!` as an argument to `write`
|
Red status.built status.tested type.review
|
```
red>> write http://www.abc.com 'crashed
```
gives (in debug mode) -
```
*** Runtime Error 1: access violation
*** in file: /C/Users/ABC/Desktop/red/environment/console/unicode.reds
*** at line: 625
***
*** stack: red/unicode/to-utf16-len 02733BA0h 0018F568h
*** stack: red/unicode/to-utf16 02733BA0h
*** stack: red/simple-io/request-http 2 02733B90h 00000000h 02733BA0h false false false
*** stack: red/url/write 02733B90h 02733BA0h false false false false 02733B80h 02733B80h 02733B80h 02733B80h *** stack: red/actions/write 02733B90h 02733BA0h false false false false 02733B80h 02733B80h 02733B80h 02733B80h
*** stack: red/actions/write* -1 -1 -1 -1 -1 -1 -1 -1
*** stack: red/interpreter/eval-arguments 027CB310h 027EC798h 027EC798h 00000000h 00000000h
*** stack: red/interpreter/eval-code 027CB310h 027EC778h 027EC798h false 00000000h 00000000h 027CB310h
*** stack: red/interpreter/eval-expression 027EC778h 027EC798h false false
*** stack: red/interpreter/eval 02733B80h true
*** stack: red/natives/do* false -1
*** stack: red/interpreter/eval-arguments 027CB4D0h 027BEEB0h 027BEEB0h 00000000h 00000000h
*** stack: red/interpreter/eval-code 027CB4D0h 027BEEA0h 027BEEB0h true 00000000h 00000000h 027CB4D0h
*** stack: red/interpreter/eval-expression 027BEEA0h 027BEEB0h false true
*** stack: red/interpreter/eval-arguments 027CAA70h 027BEE90h 027BEEB0h 027BEE70h 027BEEC4h
*** stack: red/interpreter/eval-code 027CAA70h 027BEE80h 027BEEB0h true 027BEE70h 027BEEC4h 027CAA70h
*** stack: red/interpreter/eval-path 027BEE70h 027BEE80h 027BEEB0h false false false false
*** stack: red/interpreter/eval-expression 027BEE80h 027BEEB0h false false
*** stack: red/interpreter/eval 02733B50h true
*** stack: red/natives/catch* true 1
*** stack: ctx253~try-do 0067CE0Ch
*** stack: red/_function/call 027A914Ch 0067CE0Ch
*** stack: red/interpreter/eval-code 027A914Ch 027BF574h 027BF5C4h true 00000000h 00000000h 027A914Ch
*** stack: red/interpreter/eval-expression 027BF564h 027BF5C4h false true
*** stack: red/interpreter/eval-arguments 027CAA70h 027BF554h 027BF5C4h 027BF534h 027BF5D8h
*** stack: red/interpreter/eval-code 027CAA70h 027BF544h 027BF5C4h true 027BF534h 027BF5D8h 027CAA70h
*** stack: red/interpreter/eval-path 027BF534h 027BF544h 027BF5C4h false false false false
*** stack: red/interpreter/eval-expression 027BF544h 027BF5C4h false false
*** stack: red/interpreter/eval 02733AD0h true
*** stack: red/natives/unless* false
*** stack: red/interpreter/eval-arguments 027CB370h 027BF410h 027BF430h 00000000h 00000000h
*** stack: red/interpreter/eval-code 027CB370h 027BF3E0h 027BF430h false 00000000h 00000000h 027CB370h
*** stack: red/interpreter/eval-expression 027BF3E0h 027BF430h false false
*** stack: red/interpreter/eval 02733AB0h true
*** stack: red/natives/do* true -1
*** stack: ctx253~eval-command 0067CE0Ch
*** stack: ctx253~run 0067CE0Ch
*** stack: ctx253~launch 0067CE0Ch
```
|
1.0
|
Console crashes when `word!` used with `url!` as an argument to `write` - ```
red>> write http://www.abc.com 'crashed
```
gives (in debug mode) -
```
*** Runtime Error 1: access violation
*** in file: /C/Users/ABC/Desktop/red/environment/console/unicode.reds
*** at line: 625
***
*** stack: red/unicode/to-utf16-len 02733BA0h 0018F568h
*** stack: red/unicode/to-utf16 02733BA0h
*** stack: red/simple-io/request-http 2 02733B90h 00000000h 02733BA0h false false false
*** stack: red/url/write 02733B90h 02733BA0h false false false false 02733B80h 02733B80h 02733B80h 02733B80h *** stack: red/actions/write 02733B90h 02733BA0h false false false false 02733B80h 02733B80h 02733B80h 02733B80h
*** stack: red/actions/write* -1 -1 -1 -1 -1 -1 -1 -1
*** stack: red/interpreter/eval-arguments 027CB310h 027EC798h 027EC798h 00000000h 00000000h
*** stack: red/interpreter/eval-code 027CB310h 027EC778h 027EC798h false 00000000h 00000000h 027CB310h
*** stack: red/interpreter/eval-expression 027EC778h 027EC798h false false
*** stack: red/interpreter/eval 02733B80h true
*** stack: red/natives/do* false -1
*** stack: red/interpreter/eval-arguments 027CB4D0h 027BEEB0h 027BEEB0h 00000000h 00000000h
*** stack: red/interpreter/eval-code 027CB4D0h 027BEEA0h 027BEEB0h true 00000000h 00000000h 027CB4D0h
*** stack: red/interpreter/eval-expression 027BEEA0h 027BEEB0h false true
*** stack: red/interpreter/eval-arguments 027CAA70h 027BEE90h 027BEEB0h 027BEE70h 027BEEC4h
*** stack: red/interpreter/eval-code 027CAA70h 027BEE80h 027BEEB0h true 027BEE70h 027BEEC4h 027CAA70h
*** stack: red/interpreter/eval-path 027BEE70h 027BEE80h 027BEEB0h false false false false
*** stack: red/interpreter/eval-expression 027BEE80h 027BEEB0h false false
*** stack: red/interpreter/eval 02733B50h true
*** stack: red/natives/catch* true 1
*** stack: ctx253~try-do 0067CE0Ch
*** stack: red/_function/call 027A914Ch 0067CE0Ch
*** stack: red/interpreter/eval-code 027A914Ch 027BF574h 027BF5C4h true 00000000h 00000000h 027A914Ch
*** stack: red/interpreter/eval-expression 027BF564h 027BF5C4h false true
*** stack: red/interpreter/eval-arguments 027CAA70h 027BF554h 027BF5C4h 027BF534h 027BF5D8h
*** stack: red/interpreter/eval-code 027CAA70h 027BF544h 027BF5C4h true 027BF534h 027BF5D8h 027CAA70h
*** stack: red/interpreter/eval-path 027BF534h 027BF544h 027BF5C4h false false false false
*** stack: red/interpreter/eval-expression 027BF544h 027BF5C4h false false
*** stack: red/interpreter/eval 02733AD0h true
*** stack: red/natives/unless* false
*** stack: red/interpreter/eval-arguments 027CB370h 027BF410h 027BF430h 00000000h 00000000h
*** stack: red/interpreter/eval-code 027CB370h 027BF3E0h 027BF430h false 00000000h 00000000h 027CB370h
*** stack: red/interpreter/eval-expression 027BF3E0h 027BF430h false false
*** stack: red/interpreter/eval 02733AB0h true
*** stack: red/natives/do* true -1
*** stack: ctx253~eval-command 0067CE0Ch
*** stack: ctx253~run 0067CE0Ch
*** stack: ctx253~launch 0067CE0Ch
```
|
non_process
|
console crashes when word used with url as an argument to write red write crashed gives in debug mode runtime error access violation in file c users abc desktop red environment console unicode reds at line stack red unicode to len stack red unicode to stack red simple io request http false false false stack red url write false false false false stack red actions write false false false false stack red actions write stack red interpreter eval arguments stack red interpreter eval code false stack red interpreter eval expression false false stack red interpreter eval true stack red natives do false stack red interpreter eval arguments stack red interpreter eval code true stack red interpreter eval expression false true stack red interpreter eval arguments stack red interpreter eval code true stack red interpreter eval path false false false false stack red interpreter eval expression false false stack red interpreter eval true stack red natives catch true stack try do stack red function call stack red interpreter eval code true stack red interpreter eval expression false true stack red interpreter eval arguments stack red interpreter eval code true stack red interpreter eval path false false false false stack red interpreter eval expression false false stack red interpreter eval true stack red natives unless false stack red interpreter eval arguments stack red interpreter eval code false stack red interpreter eval expression false false stack red interpreter eval true stack red natives do true stack eval command stack run stack launch
| 0
|
212,862
| 16,485,684,159
|
IssuesEvent
|
2021-05-24 17:35:33
|
Realm667/WolfenDoom
|
https://api.github.com/repos/Realm667/WolfenDoom
|
closed
|
C1M0: Gas countdown timer obstructs Übermutant health bar.
|
mapping playtesting resources
|
When facing down the Übermutant boss in Operation Eisenmann, the gas countdown timer obstructs its health bar.

|
1.0
|
C1M0: Gas countdown timer obstructs Übermutant health bar. - When facing down the Übermutant boss in Operation Eisenmann, the gas countdown timer obstructs its health bar.

|
non_process
|
gas countdown timer obstructs übermutant health bar when facing down the übermutant boss in operation eisenmann the gas countdown timer obstructs its health bar
| 0
|
2,298
| 5,116,304,421
|
IssuesEvent
|
2017-01-07 02:00:17
|
P0cL4bs/WiFi-Pumpkin
|
https://api.github.com/repos/P0cL4bs/WiFi-Pumpkin
|
closed
|
Copy HTTP-Requests
|
enhancement in process solved
|
Thanks for updating WIFI-Pumpkin!
A quick question: Is it possible to copy/save HTTP Requests from the Monitor window?
Right-click and other ways dont do anything. Thanks!
|
1.0
|
Copy HTTP-Requests - Thanks for updating WIFI-Pumpkin!
A quick question: Is it possible to copy/save HTTP Requests from the Monitor window?
Right-click and other ways dont do anything. Thanks!
|
process
|
copy http requests thanks for updating wifi pumpkin a quick question is it possible to copy save http requests from the monitor window right click and other ways dont do anything thanks
| 1
|
414,593
| 27,994,249,745
|
IssuesEvent
|
2023-03-27 07:17:43
|
VanSubstance/To-the-North
|
https://api.github.com/repos/VanSubstance/To-the-North
|
closed
|
Varietion of Modal Contents
|
documentation enhancement Module Structure
|
기본 모달 시스템 구상 완료
모달의 종류에 따라, 내부 컨텐츠가 모듈 형태로 추가되어야 함
1. ...
종류는 진행하면서 추가 요망
|
1.0
|
Varietion of Modal Contents - 기본 모달 시스템 구상 완료
모달의 종류에 따라, 내부 컨텐츠가 모듈 형태로 추가되어야 함
1. ...
종류는 진행하면서 추가 요망
|
non_process
|
varietion of modal contents 기본 모달 시스템 구상 완료 모달의 종류에 따라 내부 컨텐츠가 모듈 형태로 추가되어야 함 종류는 진행하면서 추가 요망
| 0
|
7,536
| 10,617,133,526
|
IssuesEvent
|
2019-10-12 16:52:32
|
cetic/tsorage
|
https://api.github.com/repos/cetic/tsorage
|
closed
|
Consider Avro as an alternative representation format of published messages
|
enhancement ingestion processing
|
The current representation format for published messages is JSON.
While convenient for the human reader, Avro is supposed to be more performant, because of its binary representation.
- [ ] Implement an Avro encoder / decoder as an alternative to the JSON one.
- [ ] Determine to which extend this representation is better than JSON.
|
1.0
|
Consider Avro as an alternative representation format of published messages - The current representation format for published messages is JSON.
While convenient for the human reader, Avro is supposed to be more performant, because of its binary representation.
- [ ] Implement an Avro encoder / decoder as an alternative to the JSON one.
- [ ] Determine to which extend this representation is better than JSON.
|
process
|
consider avro as an alternative representation format of published messages the current representation format for published messages is json while convenient for the human reader avro is supposed to be more performant because of its binary representation implement an avro encoder decoder as an alternative to the json one determine to which extend this representation is better than json
| 1
|
9,016
| 12,125,133,531
|
IssuesEvent
|
2020-04-22 15:07:07
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Allow to set the order of inputs in processing models
|
Feature Request Processing
|
Author Name: **Olivier Dalang** (@olivierdalang)
Original Redmine Issue: [19965](https://issues.qgis.org/issues/19965)
Redmine category:processing/modeller
---
Hi,
It's not possible to control the order in which inputs appear in processing models execution dialog.
It seems (not confirmed) that the order used is the alphabetical order of the input internal name, which cannot be modified from the GUI once set and is often different than the display name.
This makes it easy to have models where less important fields appear before more important fields (e.g. an attribute dropdown appearing before the layer it refers to), making the dialogs a bit confusing.
Suggested fixes :
- by default, use the inputs position (X then Y value) to determine the order rather than alphabetical order of the input
- add an "order" field to the inputs, and sort according to that field (those with no order appearing at the end)
Maybe we could also consider adding an "advanced" checkbox, for the input to be displayed as an advanced parameter.
Thanks !
|
1.0
|
Allow to set the order of inputs in processing models - Author Name: **Olivier Dalang** (@olivierdalang)
Original Redmine Issue: [19965](https://issues.qgis.org/issues/19965)
Redmine category:processing/modeller
---
Hi,
It's not possible to control the order in which inputs appear in processing models execution dialog.
It seems (not confirmed) that the order used is the alphabetical order of the input internal name, which cannot be modified from the GUI once set and is often different than the display name.
This makes it easy to have models where less important fields appear before more important fields (e.g. an attribute dropdown appearing before the layer it refers to), making the dialogs a bit confusing.
Suggested fixes :
- by default, use the inputs position (X then Y value) to determine the order rather than alphabetical order of the input
- add an "order" field to the inputs, and sort according to that field (those with no order appearing at the end)
Maybe we could also consider adding an "advanced" checkbox, for the input to be displayed as an advanced parameter.
Thanks !
|
process
|
allow to set the order of inputs in processing models author name olivier dalang olivierdalang original redmine issue redmine category processing modeller hi it s not possible to control the order in which inputs appear in processing models execution dialog it seems not confirmed that the order used is the alphabetical order of the input internal name which cannot be modified from the gui once set and is often different than the display name this makes it easy to have models where less important fields appear before more important fields e g an attribute dropdown appearing before the layer it refers to making the dialogs a bit confusing suggested fixes by default use the inputs position x then y value to determine the order rather than alphabetical order of the input add an order field to the inputs and sort according to that field those with no order appearing at the end maybe we could also consider adding an advanced checkbox for the input to be displayed as an advanced parameter thanks
| 1
|
4,971
| 7,807,193,263
|
IssuesEvent
|
2018-06-11 16:04:53
|
tripott/todo-cli-summer18
|
https://api.github.com/repos/tripott/todo-cli-summer18
|
closed
|
Add todo item
|
enhancement good first issue in process
|
As a developer, I desire the ability to add items to my list of to-dos so that I can keep track of all the tasks that I need to get done. After adding the item, list the todos.
Here's an example:
```
todo add create documentation for GET /cats
```
|
1.0
|
Add todo item - As a developer, I desire the ability to add items to my list of to-dos so that I can keep track of all the tasks that I need to get done. After adding the item, list the todos.
Here's an example:
```
todo add create documentation for GET /cats
```
|
process
|
add todo item as a developer i desire the ability to add items to my list of to dos so that i can keep track of all the tasks that i need to get done after adding the item list the todos here s an example todo add create documentation for get cats
| 1
|
37,133
| 12,473,775,384
|
IssuesEvent
|
2020-05-29 08:27:41
|
Kalskiman/gentelella
|
https://api.github.com/repos/Kalskiman/gentelella
|
opened
|
CVE-2018-11694 (High) detected in multiple libraries
|
security vulnerability
|
## CVE-2018-11694 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.11.0.tgz</b>, <b>node-sass-3.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.11.0.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.11.0.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.11.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/gentelella/vendors/bootstrap/package.json</p>
<p>Path to vulnerable library: /gentelella/vendors/bootstrap/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.11.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-3.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/gentelella/vendors/select2/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/gentelella/vendors/bootstrap-daterangepicker/node_modules/node-sass/package.json,/gentelella/vendors/bootstrap-daterangepicker/node_modules/node-sass/package.json,/tmp/ws-scm/gentelella/vendors/bootstrap-daterangepicker/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-3.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Kalskiman/gentelella/commit/0736072b46adcf2ceef588bb8660b4851929bc43">0736072b46adcf2ceef588bb8660b4851929bc43</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.4. A NULL pointer dereference was found in the function Sass::Functions::selector_append which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11694>CVE-2018-11694</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11694">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11694</a></p>
<p>Release Date: 2018-06-04</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-11694 (High) detected in multiple libraries - ## CVE-2018-11694 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.11.0.tgz</b>, <b>node-sass-3.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.11.0.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.11.0.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.11.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/gentelella/vendors/bootstrap/package.json</p>
<p>Path to vulnerable library: /gentelella/vendors/bootstrap/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.11.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-3.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/gentelella/vendors/select2/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/gentelella/vendors/bootstrap-daterangepicker/node_modules/node-sass/package.json,/gentelella/vendors/bootstrap-daterangepicker/node_modules/node-sass/package.json,/tmp/ws-scm/gentelella/vendors/bootstrap-daterangepicker/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-3.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Kalskiman/gentelella/commit/0736072b46adcf2ceef588bb8660b4851929bc43">0736072b46adcf2ceef588bb8660b4851929bc43</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.4. A NULL pointer dereference was found in the function Sass::Functions::selector_append which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11694>CVE-2018-11694</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11694">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11694</a></p>
<p>Release Date: 2018-06-04</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 multiple libraries cve high severity vulnerability vulnerable libraries node sass tgz node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm gentelella vendors bootstrap package json path to vulnerable library gentelella vendors bootstrap node modules node sass package json dependency hierarchy x node sass tgz vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm gentelella vendors package json path to vulnerable library tmp ws scm gentelella vendors bootstrap daterangepicker node modules node sass package json gentelella vendors bootstrap daterangepicker node modules node sass package json tmp ws scm gentelella vendors bootstrap daterangepicker node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href vulnerability details an issue was discovered in libsass through a null pointer dereference was found in the function sass functions selector append which could be leveraged by an attacker to 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
|
252,120
| 8,032,181,373
|
IssuesEvent
|
2018-07-28 12:17:12
|
JGDSN/jcroft
|
https://api.github.com/repos/JGDSN/jcroft
|
closed
|
Power Permission System
|
Priority: Medium enhancement in progress type: coding
|
Add a power permission system, so active members cannot edit roots and so on.
|
1.0
|
Power Permission System - Add a power permission system, so active members cannot edit roots and so on.
|
non_process
|
power permission system add a power permission system so active members cannot edit roots and so on
| 0
|
2,970
| 5,962,792,267
|
IssuesEvent
|
2017-05-30 00:53:50
|
Data4Democracy/quorum
|
https://api.github.com/repos/Data4Democracy/quorum
|
opened
|
[Processor – Azure ] Add functionality to store data on Azure
|
processor
|
Add functionality so that the output from a consumer can be efficiently stored on an Azure data lake.
|
1.0
|
[Processor – Azure ] Add functionality to store data on Azure - Add functionality so that the output from a consumer can be efficiently stored on an Azure data lake.
|
process
|
add functionality to store data on azure add functionality so that the output from a consumer can be efficiently stored on an azure data lake
| 1
|
14,643
| 17,773,045,617
|
IssuesEvent
|
2021-08-30 15:42:24
|
digitalmethodsinitiative/4cat
|
https://api.github.com/repos/digitalmethodsinitiative/4cat
|
closed
|
Tokeniser removes non-latin characters
|
bug processors
|
The tokenisation processor removes non-letter characters from input strings to avoid including punctuation etc in the tokens. But its method is too naive, removing basically any character outside of `[a-zA-Z0-9]`. This mangles any text containing non-latin characters (Cyrillic, Armenian, you name it). So this needs to be fixed to remove punctuation but not actual letter characters.
|
1.0
|
Tokeniser removes non-latin characters - The tokenisation processor removes non-letter characters from input strings to avoid including punctuation etc in the tokens. But its method is too naive, removing basically any character outside of `[a-zA-Z0-9]`. This mangles any text containing non-latin characters (Cyrillic, Armenian, you name it). So this needs to be fixed to remove punctuation but not actual letter characters.
|
process
|
tokeniser removes non latin characters the tokenisation processor removes non letter characters from input strings to avoid including punctuation etc in the tokens but its method is too naive removing basically any character outside of this mangles any text containing non latin characters cyrillic armenian you name it so this needs to be fixed to remove punctuation but not actual letter characters
| 1
|
99,439
| 20,964,416,670
|
IssuesEvent
|
2022-03-28 04:18:42
|
Regalis11/Barotrauma
|
https://api.github.com/repos/Regalis11/Barotrauma
|
closed
|
Stabilozine does not heal poisoning if skill check is failed
|
Bug Need more info Code
|
- [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
Stabilozine does not heal afflictions of type "poison" if the skill check is failed on use due to a typo in the XML.
**Version**
Windows v0.16.7.0
**Additional information**

|
1.0
|
Stabilozine does not heal poisoning if skill check is failed - - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
Stabilozine does not heal afflictions of type "poison" if the skill check is failed on use due to a typo in the XML.
**Version**
Windows v0.16.7.0
**Additional information**

|
non_process
|
stabilozine does not heal poisoning if skill check is failed i have searched the issue tracker to check if the issue has already been reported description stabilozine does not heal afflictions of type poison if the skill check is failed on use due to a typo in the xml version windows additional information
| 0
|
142,910
| 5,479,812,420
|
IssuesEvent
|
2017-03-13 04:18:46
|
g8os/blockstor
|
https://api.github.com/repos/g8os/blockstor
|
closed
|
Panic
|
priority_critical
|
```
panic: runtime error: slice bounds out of range
goroutine 11 [running]:
panic(0x4372920, 0xc420012120)
/usr/local/Cellar/go/1.7.3/libexec/src/runtime/panic.go:500 +0x1a1
main.(*ArdbBackend).ReadAt(0xc42006e9c0, 0x4f65128, 0xc4201d2b80, 0xc4210b6000, 0x1000, 0x10000, 0x504200, 0x0, 0x0, 0x0)
/Users/rob/workspace/go/src/github.com/g8os/blockstor/nbdserver/nbd.go:138 +0x4c7
github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd.(*Connection).receive(0xc4201220e0, 0x4f65128, 0xc4201d2b80)
/Users/rob/workspace/go/src/github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd/connection.go:317 +0xfda
created by github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd.(*Connection).Serve
/Users/rob/workspace/go/src/github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd/connection.go:538 +0x536
```
Steps to reproduce:
```
root@ubuntu:/mnt# nbd-client -b 4096 -name default 192.168.64.1 6666 /dev/nbd0
Negotiation: ..size = 19073MB
bs=4096, sz=19999997952 bytes
root@ubuntu:/mnt# qemu-img convert -p -n Ubuntu.1604.uefi.x64.qcow2 -O raw /dev/nbd0
(100.00/100%)
root@ubuntu:/mnt# nbd-client -d /dev/nbd0
disconnect, sock, done
```
Then start a qemu vm from the generated image:
```
qemu-system-x86_64 -machine pc-1.3,usb=off -boot order=c -m 2048 -smp 2 -net nic -net user -drive file=nbd+tcp://localhost:6666/default,index=0,format=raw
```
|
1.0
|
Panic - ```
panic: runtime error: slice bounds out of range
goroutine 11 [running]:
panic(0x4372920, 0xc420012120)
/usr/local/Cellar/go/1.7.3/libexec/src/runtime/panic.go:500 +0x1a1
main.(*ArdbBackend).ReadAt(0xc42006e9c0, 0x4f65128, 0xc4201d2b80, 0xc4210b6000, 0x1000, 0x10000, 0x504200, 0x0, 0x0, 0x0)
/Users/rob/workspace/go/src/github.com/g8os/blockstor/nbdserver/nbd.go:138 +0x4c7
github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd.(*Connection).receive(0xc4201220e0, 0x4f65128, 0xc4201d2b80)
/Users/rob/workspace/go/src/github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd/connection.go:317 +0xfda
created by github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd.(*Connection).Serve
/Users/rob/workspace/go/src/github.com/g8os/blockstor/nbdserver/vendor/github.com/g8os/gonbdserver/nbd/connection.go:538 +0x536
```
Steps to reproduce:
```
root@ubuntu:/mnt# nbd-client -b 4096 -name default 192.168.64.1 6666 /dev/nbd0
Negotiation: ..size = 19073MB
bs=4096, sz=19999997952 bytes
root@ubuntu:/mnt# qemu-img convert -p -n Ubuntu.1604.uefi.x64.qcow2 -O raw /dev/nbd0
(100.00/100%)
root@ubuntu:/mnt# nbd-client -d /dev/nbd0
disconnect, sock, done
```
Then start a qemu vm from the generated image:
```
qemu-system-x86_64 -machine pc-1.3,usb=off -boot order=c -m 2048 -smp 2 -net nic -net user -drive file=nbd+tcp://localhost:6666/default,index=0,format=raw
```
|
non_process
|
panic panic runtime error slice bounds out of range goroutine panic usr local cellar go libexec src runtime panic go main ardbbackend readat users rob workspace go src github com blockstor nbdserver nbd go github com blockstor nbdserver vendor github com gonbdserver nbd connection receive users rob workspace go src github com blockstor nbdserver vendor github com gonbdserver nbd connection go created by github com blockstor nbdserver vendor github com gonbdserver nbd connection serve users rob workspace go src github com blockstor nbdserver vendor github com gonbdserver nbd connection go steps to reproduce root ubuntu mnt nbd client b name default dev negotiation size bs sz bytes root ubuntu mnt qemu img convert p n ubuntu uefi o raw dev root ubuntu mnt nbd client d dev disconnect sock done then start a qemu vm from the generated image qemu system machine pc usb off boot order c m smp net nic net user drive file nbd tcp localhost default index format raw
| 0
|
71,867
| 23,836,437,051
|
IssuesEvent
|
2022-09-06 06:29:11
|
martinrotter/rssguard
|
https://api.github.com/repos/martinrotter/rssguard
|
closed
|
[BUG]: List of feed entries is not read when using a screen reader
|
Type-Defect
|
### Brief description of the issue
I am blind and I'd like to use RSS Guard with the orca screen reading software on Linux.
All though not perfect regarding accessebility, RSS Guard is useable for me and thats great! There are not so many accessible RSS reader options for a blind computer user... Thanks for the great work!
The biggest issue I have with the current RSS Guard release is that the entries of a chosen RSS feed are not read by my screen reading software. The screen reading software is called orca, its outputting the content of a screen with its elements via a synthetic voice or, if a braille device is attached to the computer, also in braille.
I can see the feed entries on my braille device but there is no speech output.
I think its related to the grafical element that is used to generate the entry list, it seems to be another element then the tree or list that is used e.g. for the feeds.
Is there a chance to get the entry list for feed entries also more accessible somehow? That would be really great. I can open also reports for the other accessibility issues, but they are not so central... Because I am no programmer I can't give hints how to improve accessibility unfortunately, but I know there are accessibility guidelines or at least hints how to deal with it.
Thanks a lot for your support and ofcourse I'd be happy to help at least with testing...
### How to reproduce the bug?
Install orca on a Linux system and use RSS Guard with it. I understand that this very challenging for a sighted person...
### What was the expected result?
The list of feed entries should be spoken by the screen reading software.
### What actually happened?
The ontent of the entry list is not spoken.
### Debug log
I can post a debug log, but I think this will not help in my case...
### Operating system and version
* OS:
4.2.3, manualy installed* RSS Guard version:
Testing
|
1.0
|
[BUG]: List of feed entries is not read when using a screen reader - ### Brief description of the issue
I am blind and I'd like to use RSS Guard with the orca screen reading software on Linux.
All though not perfect regarding accessebility, RSS Guard is useable for me and thats great! There are not so many accessible RSS reader options for a blind computer user... Thanks for the great work!
The biggest issue I have with the current RSS Guard release is that the entries of a chosen RSS feed are not read by my screen reading software. The screen reading software is called orca, its outputting the content of a screen with its elements via a synthetic voice or, if a braille device is attached to the computer, also in braille.
I can see the feed entries on my braille device but there is no speech output.
I think its related to the grafical element that is used to generate the entry list, it seems to be another element then the tree or list that is used e.g. for the feeds.
Is there a chance to get the entry list for feed entries also more accessible somehow? That would be really great. I can open also reports for the other accessibility issues, but they are not so central... Because I am no programmer I can't give hints how to improve accessibility unfortunately, but I know there are accessibility guidelines or at least hints how to deal with it.
Thanks a lot for your support and ofcourse I'd be happy to help at least with testing...
### How to reproduce the bug?
Install orca on a Linux system and use RSS Guard with it. I understand that this very challenging for a sighted person...
### What was the expected result?
The list of feed entries should be spoken by the screen reading software.
### What actually happened?
The ontent of the entry list is not spoken.
### Debug log
I can post a debug log, but I think this will not help in my case...
### Operating system and version
* OS:
4.2.3, manualy installed* RSS Guard version:
Testing
|
non_process
|
list of feed entries is not read when using a screen reader brief description of the issue i am blind and i d like to use rss guard with the orca screen reading software on linux all though not perfect regarding accessebility rss guard is useable for me and thats great there are not so many accessible rss reader options for a blind computer user thanks for the great work the biggest issue i have with the current rss guard release is that the entries of a chosen rss feed are not read by my screen reading software the screen reading software is called orca its outputting the content of a screen with its elements via a synthetic voice or if a braille device is attached to the computer also in braille i can see the feed entries on my braille device but there is no speech output i think its related to the grafical element that is used to generate the entry list it seems to be another element then the tree or list that is used e g for the feeds is there a chance to get the entry list for feed entries also more accessible somehow that would be really great i can open also reports for the other accessibility issues but they are not so central because i am no programmer i can t give hints how to improve accessibility unfortunately but i know there are accessibility guidelines or at least hints how to deal with it thanks a lot for your support and ofcourse i d be happy to help at least with testing how to reproduce the bug install orca on a linux system and use rss guard with it i understand that this very challenging for a sighted person what was the expected result the list of feed entries should be spoken by the screen reading software what actually happened the ontent of the entry list is not spoken debug log i can post a debug log but i think this will not help in my case operating system and version os manualy installed rss guard version testing
| 0
|
5,846
| 8,672,964,078
|
IssuesEvent
|
2018-11-30 00:07:23
|
HumanCellAtlas/dcp-community
|
https://api.github.com/repos/HumanCellAtlas/dcp-community
|
closed
|
Charter Template: Document reuse potential in Description section
|
charter-process
|
**Notes from PM F2F (9/25/18):**
Add a note to the *Description* to document whether a project is HCA specific or has reuse in other communities - *Data Store FISMA scenario* for example.
|
1.0
|
Charter Template: Document reuse potential in Description section -
**Notes from PM F2F (9/25/18):**
Add a note to the *Description* to document whether a project is HCA specific or has reuse in other communities - *Data Store FISMA scenario* for example.
|
process
|
charter template document reuse potential in description section notes from pm add a note to the description to document whether a project is hca specific or has reuse in other communities data store fisma scenario for example
| 1
|
3,292
| 6,385,105,640
|
IssuesEvent
|
2017-08-03 07:39:08
|
zotero/zotero
|
https://api.github.com/repos/zotero/zotero
|
opened
|
Don't bundle word processor plugins as Zotero addons
|
Word Processor Integration
|
[This piece of code](https://github.com/zotero/zotero/blob/81d5618346475a723c1e8f489a0c1de8f596a243/resource/word-processor-plugin-installer.js#L68-L73) is causing numerous users problems with Word plugins not installing. Since the plugins are bundled with Zotero there's no point to keep them as addons proper and we should just load them with the main codebase in zotero-service.js or similar.
|
1.0
|
Don't bundle word processor plugins as Zotero addons - [This piece of code](https://github.com/zotero/zotero/blob/81d5618346475a723c1e8f489a0c1de8f596a243/resource/word-processor-plugin-installer.js#L68-L73) is causing numerous users problems with Word plugins not installing. Since the plugins are bundled with Zotero there's no point to keep them as addons proper and we should just load them with the main codebase in zotero-service.js or similar.
|
process
|
don t bundle word processor plugins as zotero addons is causing numerous users problems with word plugins not installing since the plugins are bundled with zotero there s no point to keep them as addons proper and we should just load them with the main codebase in zotero service js or similar
| 1
|
19,036
| 25,042,408,344
|
IssuesEvent
|
2022-11-04 22:41:08
|
USGS-WiM/StreamStats
|
https://api.github.com/repos/USGS-WiM/StreamStats
|
opened
|
BP: Add "Compute Basin Characteristics" checklist
|
Batch Processor
|
Part of #1455
- [ ] Create a checkbox that says "Compute Basin Characteristics". When the checkbox is checked, the checklist (described below) should appear. When the checkbox is unchecked, the checklist should disappear.
- [ ] If any Flow Statistics are checked, the "Compute Basin Characteristics" checkbox should be forcibly selected.
- [ ] Create a checklist that says "Select Basin Characteristics:"
- [ ] When a Region/State is selected, make a service call to https://streamstats.usgs.gov/streamstatsservices/parameters.json?rcode=AZ (example is for Arizona) to get a full list of the Basin Characteristics (aka "parameters")
- [ ] Display both the "code" and "description" of each Basin Characteristic in the checklist; this may be best formatted as a table
- [ ] When a Flow Statistic is checked, refer back to the service response used to retrieve Flow Statistics (https://streamstats.usgs.gov/nssservices/Regions/AZ,NA/Scenarios). Look at the specific Flow Statistic that was checked and look at the "parameters" listed. Forcibly check these Basin Characteristics in the checklist, since these Basin Characteristics must be computed in order to compute the desired Flow Statistics.
|
1.0
|
BP: Add "Compute Basin Characteristics" checklist - Part of #1455
- [ ] Create a checkbox that says "Compute Basin Characteristics". When the checkbox is checked, the checklist (described below) should appear. When the checkbox is unchecked, the checklist should disappear.
- [ ] If any Flow Statistics are checked, the "Compute Basin Characteristics" checkbox should be forcibly selected.
- [ ] Create a checklist that says "Select Basin Characteristics:"
- [ ] When a Region/State is selected, make a service call to https://streamstats.usgs.gov/streamstatsservices/parameters.json?rcode=AZ (example is for Arizona) to get a full list of the Basin Characteristics (aka "parameters")
- [ ] Display both the "code" and "description" of each Basin Characteristic in the checklist; this may be best formatted as a table
- [ ] When a Flow Statistic is checked, refer back to the service response used to retrieve Flow Statistics (https://streamstats.usgs.gov/nssservices/Regions/AZ,NA/Scenarios). Look at the specific Flow Statistic that was checked and look at the "parameters" listed. Forcibly check these Basin Characteristics in the checklist, since these Basin Characteristics must be computed in order to compute the desired Flow Statistics.
|
process
|
bp add compute basin characteristics checklist part of create a checkbox that says compute basin characteristics when the checkbox is checked the checklist described below should appear when the checkbox is unchecked the checklist should disappear if any flow statistics are checked the compute basin characteristics checkbox should be forcibly selected create a checklist that says select basin characteristics when a region state is selected make a service call to example is for arizona to get a full list of the basin characteristics aka parameters display both the code and description of each basin characteristic in the checklist this may be best formatted as a table when a flow statistic is checked refer back to the service response used to retrieve flow statistics look at the specific flow statistic that was checked and look at the parameters listed forcibly check these basin characteristics in the checklist since these basin characteristics must be computed in order to compute the desired flow statistics
| 1
|
586,909
| 17,599,664,954
|
IssuesEvent
|
2021-08-17 10:11:36
|
jmoenig/Snap
|
https://api.github.com/repos/jmoenig/Snap
|
closed
|
Building a way of extending Snap!
|
enhancement low priority
|
I'd like to think about a way that we could try to make Snap! a bit more extendible for custom use without having to actually fork or modify the core Snap! code base.
I was thinking something of these two options:
A URL parameter that loads in an extensions file. So, maybe: `#extension:URL` or something?
Or:
A way of storing JS in a project / sprite file and having Snap execute that JS and load in any customizations.
The initial idea of this was prompted by edX development (and Hour of Code) where we'd like to remove some UI elements for easing students into Snap!.
Basically, what I think this file would contain, at least initially, is a bunch of functions which simply override the builtin Snap ones. That'd be the first step.
Eventually, I think it'd be nice to refactor some of the GUI code to make adding or removing UI elements or blocks as simple as modifying a JS object. (So instead of large conditionals or case statements we could use a JS object `blocksInCategory` or something with a better name.)
I'm mostly throwing this idea out there, it's not urgent, but I think it could make some development easier. It'd also enable us to make additions to Snap that don't deserve to be in the official version (like advanced XHRs and Oauth support.)
|
1.0
|
Building a way of extending Snap! - I'd like to think about a way that we could try to make Snap! a bit more extendible for custom use without having to actually fork or modify the core Snap! code base.
I was thinking something of these two options:
A URL parameter that loads in an extensions file. So, maybe: `#extension:URL` or something?
Or:
A way of storing JS in a project / sprite file and having Snap execute that JS and load in any customizations.
The initial idea of this was prompted by edX development (and Hour of Code) where we'd like to remove some UI elements for easing students into Snap!.
Basically, what I think this file would contain, at least initially, is a bunch of functions which simply override the builtin Snap ones. That'd be the first step.
Eventually, I think it'd be nice to refactor some of the GUI code to make adding or removing UI elements or blocks as simple as modifying a JS object. (So instead of large conditionals or case statements we could use a JS object `blocksInCategory` or something with a better name.)
I'm mostly throwing this idea out there, it's not urgent, but I think it could make some development easier. It'd also enable us to make additions to Snap that don't deserve to be in the official version (like advanced XHRs and Oauth support.)
|
non_process
|
building a way of extending snap i d like to think about a way that we could try to make snap a bit more extendible for custom use without having to actually fork or modify the core snap code base i was thinking something of these two options a url parameter that loads in an extensions file so maybe extension url or something or a way of storing js in a project sprite file and having snap execute that js and load in any customizations the initial idea of this was prompted by edx development and hour of code where we d like to remove some ui elements for easing students into snap basically what i think this file would contain at least initially is a bunch of functions which simply override the builtin snap ones that d be the first step eventually i think it d be nice to refactor some of the gui code to make adding or removing ui elements or blocks as simple as modifying a js object so instead of large conditionals or case statements we could use a js object blocksincategory or something with a better name i m mostly throwing this idea out there it s not urgent but i think it could make some development easier it d also enable us to make additions to snap that don t deserve to be in the official version like advanced xhrs and oauth support
| 0
|
78,362
| 14,988,496,413
|
IssuesEvent
|
2021-01-29 01:23:43
|
codereport/jsource
|
https://api.github.com/repos/codereport/jsource
|
closed
|
Remove PREFETCH(2) macros
|
code removal good first issue
|
Remove the following:
```c
#define PREFETCH(x) __builtin_prefetch(x)
#define PREFETCH2(x) __builtin_prefetch((x),0,2) // prefetch into L2 cache but not L1
```
|
1.0
|
Remove PREFETCH(2) macros - Remove the following:
```c
#define PREFETCH(x) __builtin_prefetch(x)
#define PREFETCH2(x) __builtin_prefetch((x),0,2) // prefetch into L2 cache but not L1
```
|
non_process
|
remove prefetch macros remove the following c define prefetch x builtin prefetch x define x builtin prefetch x prefetch into cache but not
| 0
|
2,091
| 4,927,593,627
|
IssuesEvent
|
2016-11-26 20:50:46
|
dita-ot/dita-ot
|
https://api.github.com/repos/dita-ot/dita-ot
|
closed
|
Override @scope and @format with keyref
|
bug P2 preprocess/keyref
|
Keyref processing doesn't correctly override default `@scope` and `@format` from key definition. If you have
```xml
<keydef href="http://www.example.com" scope="external" format="html"/>
```
```xml
<link href="topic.dita" scope="local" format="dita"/>
```
This is incorrectly processed to
```xml
<link href="http://www.example.com" scope="local" format="dita"/>
```
|
1.0
|
Override @scope and @format with keyref - Keyref processing doesn't correctly override default `@scope` and `@format` from key definition. If you have
```xml
<keydef href="http://www.example.com" scope="external" format="html"/>
```
```xml
<link href="topic.dita" scope="local" format="dita"/>
```
This is incorrectly processed to
```xml
<link href="http://www.example.com" scope="local" format="dita"/>
```
|
process
|
override scope and format with keyref keyref processing doesn t correctly override default scope and format from key definition if you have xml xml this is incorrectly processed to xml
| 1
|
4,837
| 7,734,238,941
|
IssuesEvent
|
2018-05-26 21:49:45
|
kerubistan/kerub
|
https://api.github.com/repos/kerubistan/kerub
|
closed
|
delete vms, vns, storage
|
component:data processing enhancement
|
The UI does not have any functionality related to deleting virtual resources.
Also, on the server side:
- before deleting VM, the VM must be down
- before deleting a vstorage, the vstorage must be detached from vms, after deleting the storage must be freed
- before deleting a Virtual Network, all VM's must be detached
|
1.0
|
delete vms, vns, storage - The UI does not have any functionality related to deleting virtual resources.
Also, on the server side:
- before deleting VM, the VM must be down
- before deleting a vstorage, the vstorage must be detached from vms, after deleting the storage must be freed
- before deleting a Virtual Network, all VM's must be detached
|
process
|
delete vms vns storage the ui does not have any functionality related to deleting virtual resources also on the server side before deleting vm the vm must be down before deleting a vstorage the vstorage must be detached from vms after deleting the storage must be freed before deleting a virtual network all vm s must be detached
| 1
|
73,056
| 15,252,458,498
|
IssuesEvent
|
2021-02-20 03:00:36
|
AlexRogalskiy/screenshots
|
https://api.github.com/repos/AlexRogalskiy/screenshots
|
opened
|
CVE-2015-9251 (Medium) detected in jquery-1.8.1.min.js
|
security vulnerability
|
## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: screenshots/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: screenshots/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/screenshots/commit/571fdc24c8184179670367d3935ff8f28587d999">571fdc24c8184179670367d3935ff8f28587d999</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</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://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.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-2015-9251 (Medium) detected in jquery-1.8.1.min.js - ## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: screenshots/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: screenshots/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/screenshots/commit/571fdc24c8184179670367d3935ff8f28587d999">571fdc24c8184179670367d3935ff8f28587d999</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</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://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.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 medium detected in jquery min js cve medium severity vulnerability vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file screenshots node modules redeyed examples browser index html path to vulnerable library screenshots node modules redeyed examples browser index html dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch master vulnerability details jquery before is vulnerable to cross site scripting xss attacks when a cross domain ajax request is performed without the datatype option causing text javascript responses to be executed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource
| 0
|
2,882
| 5,844,452,318
|
IssuesEvent
|
2017-05-10 11:58:03
|
cyipt/cyipt
|
https://api.github.com/repos/cyipt/cyipt
|
closed
|
Calculate combined path and road widths and add to OSM
|
data preprocessing
|
Similar to issue #28 but for roads and roads and roadsides
|
1.0
|
Calculate combined path and road widths and add to OSM - Similar to issue #28 but for roads and roads and roadsides
|
process
|
calculate combined path and road widths and add to osm similar to issue but for roads and roads and roadsides
| 1
|
9,029
| 12,128,691,955
|
IssuesEvent
|
2020-04-22 20:58:40
|
parcel-bundler/parcel
|
https://api.github.com/repos/parcel-bundler/parcel
|
closed
|
Parcel convert index.html classnames to css modules, but not html classes.
|
:bug: Bug CSS Preprocessing
|
🐛 bug report
Using a html file as the end point, parcel will throw any css <styles>'s to postcss. If you're using CSS modules, it will convert classes and such to module names. But it won't convert the relevant class names.
## 🎛 Configuration (.babelrc, package.json, cli command)
### .postcssrc
```
{
"modules": true
}
```
## 🤔 Expected Behavior
Either ignore styles in html. Or convert relevant class="names".
## 😯 Current Behavior
It coverts the class names within the style, but not the html class names. So the html element is "this" when the style name is now "_this_123abc".
## 💁 Possible Solution
Either don't do that. Or add a configuration so it don't do that.
## 🔦 Context
Trying to make a spinner appear while it loads the JS, etc. Simple stuff.
## 💻 Code Sample
### index.html
```
<html>
<head>
<style>
.loading { }
// becomes:
// __loading_1gsd
</style>
</head>
<body>
<div class="loading"></div>
</body>
</html>
```
## 🌍 Your Environment
All the latest.
|
1.0
|
Parcel convert index.html classnames to css modules, but not html classes. - 🐛 bug report
Using a html file as the end point, parcel will throw any css <styles>'s to postcss. If you're using CSS modules, it will convert classes and such to module names. But it won't convert the relevant class names.
## 🎛 Configuration (.babelrc, package.json, cli command)
### .postcssrc
```
{
"modules": true
}
```
## 🤔 Expected Behavior
Either ignore styles in html. Or convert relevant class="names".
## 😯 Current Behavior
It coverts the class names within the style, but not the html class names. So the html element is "this" when the style name is now "_this_123abc".
## 💁 Possible Solution
Either don't do that. Or add a configuration so it don't do that.
## 🔦 Context
Trying to make a spinner appear while it loads the JS, etc. Simple stuff.
## 💻 Code Sample
### index.html
```
<html>
<head>
<style>
.loading { }
// becomes:
// __loading_1gsd
</style>
</head>
<body>
<div class="loading"></div>
</body>
</html>
```
## 🌍 Your Environment
All the latest.
|
process
|
parcel convert index html classnames to css modules but not html classes 🐛 bug report using a html file as the end point parcel will throw any css s to postcss if you re using css modules it will convert classes and such to module names but it won t convert the relevant class names 🎛 configuration babelrc package json cli command postcssrc modules true 🤔 expected behavior either ignore styles in html or convert relevant class names 😯 current behavior it coverts the class names within the style but not the html class names so the html element is this when the style name is now this 💁 possible solution either don t do that or add a configuration so it don t do that 🔦 context trying to make a spinner appear while it loads the js etc simple stuff 💻 code sample index html loading becomes loading 🌍 your environment all the latest
| 1
|
420,575
| 28,290,418,244
|
IssuesEvent
|
2023-04-09 05:47:36
|
arambazamba/ng-adv
|
https://api.github.com/repos/arambazamba/ng-adv
|
closed
|
testing - add bdt tutorial
|
documentation feature
|
e2e defines the overall journey … unit test define the stepping stones to completing that journey
I. Write E2E test
2. Watch it fail
3. Write unit test(s)
4. Watch them fail
5. Implement functionality for unit tests
6. Watch unit tests pass
7. See if E2E test passes now
8. If it still doesn't pass, add more unit tests
|
1.0
|
testing - add bdt tutorial - e2e defines the overall journey … unit test define the stepping stones to completing that journey
I. Write E2E test
2. Watch it fail
3. Write unit test(s)
4. Watch them fail
5. Implement functionality for unit tests
6. Watch unit tests pass
7. See if E2E test passes now
8. If it still doesn't pass, add more unit tests
|
non_process
|
testing add bdt tutorial defines the overall journey … unit test define the stepping stones to completing that journey i write test watch it fail write unit test s watch them fail implement functionality for unit tests watch unit tests pass see if test passes now if it still doesn t pass add more unit tests
| 0
|
136,089
| 11,034,662,061
|
IssuesEvent
|
2019-12-07 07:31:20
|
a2000-erp-team/WEBERP
|
https://api.github.com/repos/a2000-erp-team/WEBERP
|
closed
|
SALES-Order Processing-Goods Returned Credit Note (CC). CC transaction does not appear in GST some GST reports.
|
WEB ERP Testing By Katrina
|






|
1.0
|
SALES-Order Processing-Goods Returned Credit Note (CC). CC transaction does not appear in GST some GST reports. - 





|
non_process
|
sales order processing goods returned credit note cc cc transaction does not appear in gst some gst reports
| 0
|
17,209
| 22,793,966,566
|
IssuesEvent
|
2022-07-10 12:34:28
|
B2o5T/graphql-eslint
|
https://api.github.com/repos/B2o5T/graphql-eslint
|
closed
|
no-unreachable-types: Support document-only fragments
|
process/candidate kind/bug
|
**Is your feature request related to a problem? Please describe.**
It's common to have document-only `directive`s in schemas. Such schema items are, by definition, "unreachable".
Example:
```
directive @onLoggedIn on FIELD | FRAGMENT_SPREAD | INLINE_FRAGMENT
```
The [no-unreachable-types](https://github.com/B2o5T/graphql-eslint/blob/master/docs/rules/no-unreachable-types.md) rule, however, does not understand this, and detects them as issues.
Of course, it's possible to disable the lint rule for such items; however, that would be redundant to the item definition.
**Describe the solution you'd like**
**Describe alternatives you've considered**
I guess there are different ways to handle this:
1) Make `no-unreachable-types` smarter, without new options for users to do so.
2) Add options to `no-unreachable-types` to allow control over item types, so a user can disable this check specifically on `directive`s.
3) Add options to `no-unreachable-types` to allow user to disable the check depending on the allowed location of directives.
From these, I think (2) is the easiest to implement and a useful generic control for the rule. The other two are more complicated. Solution (1) could be ideal, while solution (3) could be hard-to-configure.
|
1.0
|
no-unreachable-types: Support document-only fragments - **Is your feature request related to a problem? Please describe.**
It's common to have document-only `directive`s in schemas. Such schema items are, by definition, "unreachable".
Example:
```
directive @onLoggedIn on FIELD | FRAGMENT_SPREAD | INLINE_FRAGMENT
```
The [no-unreachable-types](https://github.com/B2o5T/graphql-eslint/blob/master/docs/rules/no-unreachable-types.md) rule, however, does not understand this, and detects them as issues.
Of course, it's possible to disable the lint rule for such items; however, that would be redundant to the item definition.
**Describe the solution you'd like**
**Describe alternatives you've considered**
I guess there are different ways to handle this:
1) Make `no-unreachable-types` smarter, without new options for users to do so.
2) Add options to `no-unreachable-types` to allow control over item types, so a user can disable this check specifically on `directive`s.
3) Add options to `no-unreachable-types` to allow user to disable the check depending on the allowed location of directives.
From these, I think (2) is the easiest to implement and a useful generic control for the rule. The other two are more complicated. Solution (1) could be ideal, while solution (3) could be hard-to-configure.
|
process
|
no unreachable types support document only fragments is your feature request related to a problem please describe it s common to have document only directive s in schemas such schema items are by definition unreachable example directive onloggedin on field fragment spread inline fragment the rule however does not understand this and detects them as issues of course it s possible to disable the lint rule for such items however that would be redundant to the item definition describe the solution you d like describe alternatives you ve considered i guess there are different ways to handle this make no unreachable types smarter without new options for users to do so add options to no unreachable types to allow control over item types so a user can disable this check specifically on directive s add options to no unreachable types to allow user to disable the check depending on the allowed location of directives from these i think is the easiest to implement and a useful generic control for the rule the other two are more complicated solution could be ideal while solution could be hard to configure
| 1
|
19,019
| 25,021,787,395
|
IssuesEvent
|
2022-11-04 01:57:35
|
quark-engine/quark-engine
|
https://api.github.com/repos/quark-engine/quark-engine
|
closed
|
Typo Found on Quark web report
|
issue-processing-state-04
|
Hi guys
I found a typo on the Quark web report
Select ```labels``` not ```lables``` .
<img width="605" alt="Screen Shot 2022-10-26 at 11 15 49 AM" src="https://user-images.githubusercontent.com/593954/197926369-378fbfcc-f4b1-4fb5-b907-55eba7085c7d.png">
|
1.0
|
Typo Found on Quark web report - Hi guys
I found a typo on the Quark web report
Select ```labels``` not ```lables``` .
<img width="605" alt="Screen Shot 2022-10-26 at 11 15 49 AM" src="https://user-images.githubusercontent.com/593954/197926369-378fbfcc-f4b1-4fb5-b907-55eba7085c7d.png">
|
process
|
typo found on quark web report hi guys i found a typo on the quark web report select labels not lables img width alt screen shot at am src
| 1
|
15,751
| 19,911,673,896
|
IssuesEvent
|
2022-01-25 17:47:11
|
input-output-hk/high-assurance-legacy
|
https://api.github.com/repos/input-output-hk/high-assurance-legacy
|
closed
|
Modularize the definition of the basic transition system
|
language: isabelle topic: process calculus type: improvement
|
Our goal is to split the definition of the basic transition system into the following three parts:
1. atomic rules
2. rules for scoped transitions
3. recursion (“tying the knot”)
This split will be helpful for later developments, as it will allow us to refer to different parts of the transition system definition individually.
|
1.0
|
Modularize the definition of the basic transition system - Our goal is to split the definition of the basic transition system into the following three parts:
1. atomic rules
2. rules for scoped transitions
3. recursion (“tying the knot”)
This split will be helpful for later developments, as it will allow us to refer to different parts of the transition system definition individually.
|
process
|
modularize the definition of the basic transition system our goal is to split the definition of the basic transition system into the following three parts atomic rules rules for scoped transitions recursion “tying the knot” this split will be helpful for later developments as it will allow us to refer to different parts of the transition system definition individually
| 1
|
105,925
| 16,663,520,231
|
IssuesEvent
|
2021-06-06 19:12:00
|
utopikkad/vue-modal
|
https://api.github.com/repos/utopikkad/vue-modal
|
opened
|
CVE-2021-33502 (High) detected in normalize-url-1.9.1.tgz, normalize-url-3.3.0.tgz
|
security vulnerability
|
## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>normalize-url-1.9.1.tgz</b>, <b>normalize-url-3.3.0.tgz</b></p></summary>
<p>
<details><summary><b>normalize-url-1.9.1.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz</a></p>
<p>Path to dependency file: vue-modal/package.json</p>
<p>Path to vulnerable library: vue-modal/node_modules/mini-css-extract-plugin/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-4.2.3.tgz (Root Library)
- mini-css-extract-plugin-0.9.0.tgz
- :x: **normalize-url-1.9.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>normalize-url-3.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz</a></p>
<p>Path to dependency file: vue-modal/package.json</p>
<p>Path to vulnerable library: vue-modal/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-4.2.3.tgz (Root Library)
- optimize-cssnano-plugin-1.0.6.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-normalize-url-4.0.1.tgz
- :x: **normalize-url-3.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/utopikkad/vue-modal/commit/de44095ce300a1ee5abfa46831106f749d78078f">de44095ce300a1ee5abfa46831106f749d78078f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.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-2021-33502 (High) detected in normalize-url-1.9.1.tgz, normalize-url-3.3.0.tgz - ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>normalize-url-1.9.1.tgz</b>, <b>normalize-url-3.3.0.tgz</b></p></summary>
<p>
<details><summary><b>normalize-url-1.9.1.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz</a></p>
<p>Path to dependency file: vue-modal/package.json</p>
<p>Path to vulnerable library: vue-modal/node_modules/mini-css-extract-plugin/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-4.2.3.tgz (Root Library)
- mini-css-extract-plugin-0.9.0.tgz
- :x: **normalize-url-1.9.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>normalize-url-3.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz</a></p>
<p>Path to dependency file: vue-modal/package.json</p>
<p>Path to vulnerable library: vue-modal/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-4.2.3.tgz (Root Library)
- optimize-cssnano-plugin-1.0.6.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-normalize-url-4.0.1.tgz
- :x: **normalize-url-3.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/utopikkad/vue-modal/commit/de44095ce300a1ee5abfa46831106f749d78078f">de44095ce300a1ee5abfa46831106f749d78078f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.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 high detected in normalize url tgz normalize url tgz cve high severity vulnerability vulnerable libraries normalize url tgz normalize url tgz normalize url tgz normalize a url library home page a href path to dependency file vue modal package json path to vulnerable library vue modal node modules mini css extract plugin node modules normalize url package json dependency hierarchy cli service tgz root library mini css extract plugin tgz x normalize url tgz vulnerable library normalize url tgz normalize a url library home page a href path to dependency file vue modal package json path to vulnerable library vue modal node modules normalize url package json dependency hierarchy cli service tgz root library optimize cssnano plugin tgz cssnano preset default tgz postcss normalize url tgz x normalize url tgz vulnerable library found in head commit a href vulnerability details the normalize url package before x before and x before for node js has a redos regular expression denial of service issue because it has exponential performance for data urls publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution normalize url step up your open source security game with whitesource
| 0
|
12,643
| 15,018,397,380
|
IssuesEvent
|
2021-02-01 12:10:05
|
MotusDev/Motus-TO-DO
|
https://api.github.com/repos/MotusDev/Motus-TO-DO
|
closed
|
Salvaging data from receivers without GPS fixes
|
Followup Required - Resolved? Receiver Reprocessing required.
|
Project 236 has a receiver [deployment ](https://motus.org/data/receiverDeployment?id=5802)that was active for about a month, only for them to discover that no GPS fix had been obtained throughout that period.
So the time started from 2000-01-01 and just started incrementing from there, and consequently there were no detections for that period.
Is there any way of correcting the dates and reprocessing the data? This would at least require them to know exactly when they started the deployment, which they may or may not know. Has something similar been done in similar cases? Or are there any other suggestions?
We actually have another [receiver ](https://motus.org/data/receiver/timeline?year=1970&id=3724)here which ran for a week or so without a GPS fix. That was a test, so doesn't contain crucial data, but it occurred to me that this much happen from time to time.
|
1.0
|
Salvaging data from receivers without GPS fixes - Project 236 has a receiver [deployment ](https://motus.org/data/receiverDeployment?id=5802)that was active for about a month, only for them to discover that no GPS fix had been obtained throughout that period.
So the time started from 2000-01-01 and just started incrementing from there, and consequently there were no detections for that period.
Is there any way of correcting the dates and reprocessing the data? This would at least require them to know exactly when they started the deployment, which they may or may not know. Has something similar been done in similar cases? Or are there any other suggestions?
We actually have another [receiver ](https://motus.org/data/receiver/timeline?year=1970&id=3724)here which ran for a week or so without a GPS fix. That was a test, so doesn't contain crucial data, but it occurred to me that this much happen from time to time.
|
process
|
salvaging data from receivers without gps fixes project has a receiver was active for about a month only for them to discover that no gps fix had been obtained throughout that period so the time started from and just started incrementing from there and consequently there were no detections for that period is there any way of correcting the dates and reprocessing the data this would at least require them to know exactly when they started the deployment which they may or may not know has something similar been done in similar cases or are there any other suggestions we actually have another which ran for a week or so without a gps fix that was a test so doesn t contain crucial data but it occurred to me that this much happen from time to time
| 1
|
4,174
| 7,109,853,434
|
IssuesEvent
|
2018-01-17 08:31:06
|
openvstorage/alba
|
https://api.github.com/repos/openvstorage/alba
|
closed
|
lots of Alba_client_preset_cache.propagate_preset logging
|
process_cantreproduce type_enhancement
|
This log line isn't very informative and was seen quite a lot (more than expected?) on the OVH env. To be investigated.
|
1.0
|
lots of Alba_client_preset_cache.propagate_preset logging - This log line isn't very informative and was seen quite a lot (more than expected?) on the OVH env. To be investigated.
|
process
|
lots of alba client preset cache propagate preset logging this log line isn t very informative and was seen quite a lot more than expected on the ovh env to be investigated
| 1
|
1,608
| 4,226,464,497
|
IssuesEvent
|
2016-07-02 13:38:29
|
iTXTech/Genisys
|
https://api.github.com/repos/iTXTech/Genisys
|
opened
|
@dktapps' Win10 edition bug checklist
|
enhancement help wanted processing
|
My issue tracker for Windows 10 Edition bugfixes
- [x] Crafting
- [x] Using "Q" to drop one item at a time
- [x] Dropping items directly from the inventory
- [ ] **Hotbar (-_-)** (common issue across all platforms)
- [ ] Rapid crafting causing inventory spaz
- [ ] Spreading items between slots causes inventory spaz
- [ ] Sometimes crafting adds the item straight to the inventory, allowing duplication
##### If you can help fix these, your help is appreciated! Please submit PRs to the **`windows-10-beta`** branch, **not** the `master` branch!
|
1.0
|
@dktapps' Win10 edition bug checklist - My issue tracker for Windows 10 Edition bugfixes
- [x] Crafting
- [x] Using "Q" to drop one item at a time
- [x] Dropping items directly from the inventory
- [ ] **Hotbar (-_-)** (common issue across all platforms)
- [ ] Rapid crafting causing inventory spaz
- [ ] Spreading items between slots causes inventory spaz
- [ ] Sometimes crafting adds the item straight to the inventory, allowing duplication
##### If you can help fix these, your help is appreciated! Please submit PRs to the **`windows-10-beta`** branch, **not** the `master` branch!
|
process
|
dktapps edition bug checklist my issue tracker for windows edition bugfixes crafting using q to drop one item at a time dropping items directly from the inventory hotbar common issue across all platforms rapid crafting causing inventory spaz spreading items between slots causes inventory spaz sometimes crafting adds the item straight to the inventory allowing duplication if you can help fix these your help is appreciated please submit prs to the windows beta branch not the master branch
| 1
|
13,517
| 16,055,676,647
|
IssuesEvent
|
2021-04-23 04:24:02
|
dita-ot/dita-ot
|
https://api.github.com/repos/dita-ot/dita-ot
|
reopened
|
Remove DOTX032E error from xref to equation-block
|
enhancement preprocess priority/low stale
|
In DITA-OT 2.2.1 an xref to equation-block always causes [DOTX032E] error in topicpull processing.
```
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:7:172: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_ec2_w3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:8:151: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_jvq_w3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:9:145: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_x41_x3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:10:159: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_xcm_y3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
```
However the plug-in (PDF, HTML) should generate auto equation number from <eqyation-number/> for xref text. Or <eqyation-number> contains non-whitespace text or child elements the contents should be outputted as the xref text. This is the responsibility of the plug-in.
So DITA-OT should not generate [DOTX032E] error for it.
You can download the test data from following URL: https://www.dropbox.com/s/oc6xoowjv3km1u3/20151211-equation.zip?dl=0
|
1.0
|
Remove DOTX032E error from xref to equation-block - In DITA-OT 2.2.1 an xref to equation-block always causes [DOTX032E] error in topicpull processing.
```
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:7:172: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_ec2_w3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:8:151: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_jvq_w3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:9:145: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_x41_x3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
[topicpull] file:/D:/SVN/pdf5/testdata/20151211-equation/topic/equation_test2.dita:10:159: [DOTX032E][ERROR]: Unable to retrieve link text from target: 'equation_test1.dita#topic_fdf_fmm_h5/equation-block_xcm_y3q_35'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.
```
However the plug-in (PDF, HTML) should generate auto equation number from <eqyation-number/> for xref text. Or <eqyation-number> contains non-whitespace text or child elements the contents should be outputted as the xref text. This is the responsibility of the plug-in.
So DITA-OT should not generate [DOTX032E] error for it.
You can download the test data from following URL: https://www.dropbox.com/s/oc6xoowjv3km1u3/20151211-equation.zip?dl=0
|
process
|
remove error from xref to equation block in dita ot an xref to equation block always causes error in topicpull processing file d svn testdata equation topic equation dita unable to retrieve link text from target equation dita topic fdf fmm equation block if the target is not accessible at build time or does not have a title provide the link text inside the reference file d svn testdata equation topic equation dita unable to retrieve link text from target equation dita topic fdf fmm equation block jvq if the target is not accessible at build time or does not have a title provide the link text inside the reference file d svn testdata equation topic equation dita unable to retrieve link text from target equation dita topic fdf fmm equation block if the target is not accessible at build time or does not have a title provide the link text inside the reference file d svn testdata equation topic equation dita unable to retrieve link text from target equation dita topic fdf fmm equation block xcm if the target is not accessible at build time or does not have a title provide the link text inside the reference however the plug in pdf html should generate auto equation number from lt eqyation number gt for xref text or lt eqyation number gt contains non whitespace text or child elements the contents should be outputted as the xref text this is the responsibility of the plug in so dita ot should not generate error for it you can download the test data from following url
| 1
|
683,689
| 23,391,214,394
|
IssuesEvent
|
2022-08-11 18:02:05
|
NCAR/tuv-x
|
https://api.github.com/repos/NCAR/tuv-x
|
closed
|
Accept variable conditions as arguments to `photolysis_core_t%run()`
|
priority:2 points: 2
|
Modify `photolysis_core_t%run()` to accept all conditions (sza, species concentrations, environmental conditions, etc.) that would be expected to vary during a 3-D simulation as arguments. Allow these to be specified in a configuration file for the stand-alone photo-decomp tool and processed by the driver in `photolysis.F90`.
|
1.0
|
Accept variable conditions as arguments to `photolysis_core_t%run()` - Modify `photolysis_core_t%run()` to accept all conditions (sza, species concentrations, environmental conditions, etc.) that would be expected to vary during a 3-D simulation as arguments. Allow these to be specified in a configuration file for the stand-alone photo-decomp tool and processed by the driver in `photolysis.F90`.
|
non_process
|
accept variable conditions as arguments to photolysis core t run modify photolysis core t run to accept all conditions sza species concentrations environmental conditions etc that would be expected to vary during a d simulation as arguments allow these to be specified in a configuration file for the stand alone photo decomp tool and processed by the driver in photolysis
| 0
|
716,285
| 24,627,107,716
|
IssuesEvent
|
2022-10-16 17:03:44
|
KinsonDigital/CICD
|
https://api.github.com/repos/KinsonDigital/CICD
|
opened
|
🔬Codecov publishing
|
medium priority 🔬research
|
### Complete The Item Below
- [X] I have updated the title without removing the 🔬 emoji.
### What To Research
There are projects throughout the organization that push code coverage results to [codecov](https://about.codecov.io/).
The project does not have this capability. Research if this can be done somehow using the _**Codecov**_ public API and this is if the product has a public API.
### Research Results
_No response_
### Acceptance Criteria
**This issue is finished when:**
- [ ] Research complete and issues created _(if needed)_.
- [ ] If any issues were created, they have been added to the _**Related Work**_ section below.
### ToDo Items
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct.
|
1.0
|
🔬Codecov publishing - ### Complete The Item Below
- [X] I have updated the title without removing the 🔬 emoji.
### What To Research
There are projects throughout the organization that push code coverage results to [codecov](https://about.codecov.io/).
The project does not have this capability. Research if this can be done somehow using the _**Codecov**_ public API and this is if the product has a public API.
### Research Results
_No response_
### Acceptance Criteria
**This issue is finished when:**
- [ ] Research complete and issues created _(if needed)_.
- [ ] If any issues were created, they have been added to the _**Related Work**_ section below.
### ToDo Items
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct.
|
non_process
|
🔬codecov publishing complete the item below i have updated the title without removing the 🔬 emoji what to research there are projects throughout the organization that push code coverage results to the project does not have this capability research if this can be done somehow using the codecov public api and this is if the product has a public api research results no response acceptance criteria this issue is finished when research complete and issues created if needed if any issues were created they have been added to the related work section below todo items priority label added to this issue refer to the priority type labels section below issue linked to the correct project issue dependencies no response related work no response additional information priority type labels priority type label low priority low priority medium priority medium priority high priority high priority code of conduct i agree to follow this project s code of conduct
| 0
|
49,078
| 25,977,254,493
|
IssuesEvent
|
2022-12-19 15:47:30
|
JuliaDynamics/Entropies.jl
|
https://api.github.com/repos/JuliaDynamics/Entropies.jl
|
opened
|
Determining the bin visitations for `TransferOperator` can be faster
|
performance
|
When determining bin visitations for the estimation of the rectangular transfer operator, the bins are sorted after order of first appearance according to the input `pts`.
If first sorting the input data, the search for visitations is quite a bit faster. However, then we loose temporal ordering, which is essential for the transfer operator approximation to be valid, so we must sort back with respect to the original time indices.
My hypothesis is that the added benefit of the inital sort vastly outweights the added cost of re-indexing after visitations have been determined. Try that.
|
True
|
Determining the bin visitations for `TransferOperator` can be faster - When determining bin visitations for the estimation of the rectangular transfer operator, the bins are sorted after order of first appearance according to the input `pts`.
If first sorting the input data, the search for visitations is quite a bit faster. However, then we loose temporal ordering, which is essential for the transfer operator approximation to be valid, so we must sort back with respect to the original time indices.
My hypothesis is that the added benefit of the inital sort vastly outweights the added cost of re-indexing after visitations have been determined. Try that.
|
non_process
|
determining the bin visitations for transferoperator can be faster when determining bin visitations for the estimation of the rectangular transfer operator the bins are sorted after order of first appearance according to the input pts if first sorting the input data the search for visitations is quite a bit faster however then we loose temporal ordering which is essential for the transfer operator approximation to be valid so we must sort back with respect to the original time indices my hypothesis is that the added benefit of the inital sort vastly outweights the added cost of re indexing after visitations have been determined try that
| 0
|
8,783
| 11,902,280,787
|
IssuesEvent
|
2020-03-30 13:45:09
|
threefoldtech/jumpscaleX_core
|
https://api.github.com/repos/threefoldtech/jumpscaleX_core
|
reopened
|
jsx install on ubuntu breaks: container does not have jsx script in /tmp
|
process_wontfix type_bug
|
In the install process there is:
```
+ ssh -oStrictHostKeyChecking=no -t root@localhost -A -p 9000 bash -e /tmp/script_3bot.sh
```
Which executes in the container.
```
3BOTDEVEL:3bot:tmp: ls -asl
total 16
4 drwxrwxrwx 1 root root 4096 Mar 30 09:28 .
4 drwxr-xr-x 1 root root 4096 Mar 30 09:27 ..
4 -rw-r--r-- 1 root root 585 Mar 29 05:32 script_3botdev.sh
4 -rw-r--r-- 1 root root 78 Mar 30 09:28 script_3bot.sh
3BOTDEVEL:3bot:tmp: more script_3bot.sh
set -e
cd /tmp
python3 jsx configure --sshkey id_rsa -s
python3 jsx install
3BOTDEVEL:3bot:tmp:
```
In the container there is no jsx python script in /tmp
|
1.0
|
jsx install on ubuntu breaks: container does not have jsx script in /tmp - In the install process there is:
```
+ ssh -oStrictHostKeyChecking=no -t root@localhost -A -p 9000 bash -e /tmp/script_3bot.sh
```
Which executes in the container.
```
3BOTDEVEL:3bot:tmp: ls -asl
total 16
4 drwxrwxrwx 1 root root 4096 Mar 30 09:28 .
4 drwxr-xr-x 1 root root 4096 Mar 30 09:27 ..
4 -rw-r--r-- 1 root root 585 Mar 29 05:32 script_3botdev.sh
4 -rw-r--r-- 1 root root 78 Mar 30 09:28 script_3bot.sh
3BOTDEVEL:3bot:tmp: more script_3bot.sh
set -e
cd /tmp
python3 jsx configure --sshkey id_rsa -s
python3 jsx install
3BOTDEVEL:3bot:tmp:
```
In the container there is no jsx python script in /tmp
|
process
|
jsx install on ubuntu breaks container does not have jsx script in tmp in the install process there is ssh ostricthostkeychecking no t root localhost a p bash e tmp script sh which executes in the container tmp ls asl total drwxrwxrwx root root mar drwxr xr x root root mar rw r r root root mar script sh rw r r root root mar script sh tmp more script sh set e cd tmp jsx configure sshkey id rsa s jsx install tmp in the container there is no jsx python script in tmp
| 1
|
331,171
| 24,295,053,054
|
IssuesEvent
|
2022-09-29 09:23:37
|
Intility/templates
|
https://api.github.com/repos/Intility/templates
|
closed
|
Deploy with ArgoCD
|
documentation blocked dotnet cra
|
Add guide for both dotnet and cra on how to deploy with ArgoCD. Blocked as ArgoCD is not ready for use yet.
- [ ] dotnet doc
- [ ] cra doc
|
1.0
|
Deploy with ArgoCD - Add guide for both dotnet and cra on how to deploy with ArgoCD. Blocked as ArgoCD is not ready for use yet.
- [ ] dotnet doc
- [ ] cra doc
|
non_process
|
deploy with argocd add guide for both dotnet and cra on how to deploy with argocd blocked as argocd is not ready for use yet dotnet doc cra doc
| 0
|
167,215
| 14,105,870,720
|
IssuesEvent
|
2020-11-06 14:08:25
|
openhab/openhab-addons
|
https://api.github.com/repos/openhab/openhab-addons
|
closed
|
"How to develop in the Eclipse IDE" does not work.
|
documentation
|
The description how to debug/develop a binding does not work on my Windows-10 machine.
I installed the Eclipse-IDE in "advanced-mode" using the "openHAB Add-ons" Project.
With that Installation the descriptions works pretty well - but I have 2 problems:
1) It's not possible to drag-drop my example/test "Serial-button"-binding like described to the "Run-requirements". An error box pops up:

2) If I start my browser with "http://localhost:8080" - the Access is forbidden….
It seems, that "localhost:8080/paperui/index.html" must be used….. This should be described in the docu…

|
1.0
|
"How to develop in the Eclipse IDE" does not work. - The description how to debug/develop a binding does not work on my Windows-10 machine.
I installed the Eclipse-IDE in "advanced-mode" using the "openHAB Add-ons" Project.
With that Installation the descriptions works pretty well - but I have 2 problems:
1) It's not possible to drag-drop my example/test "Serial-button"-binding like described to the "Run-requirements". An error box pops up:

2) If I start my browser with "http://localhost:8080" - the Access is forbidden….
It seems, that "localhost:8080/paperui/index.html" must be used….. This should be described in the docu…

|
non_process
|
how to develop in the eclipse ide does not work the description how to debug develop a binding does not work on my windows machine i installed the eclipse ide in advanced mode using the openhab add ons project with that installation the descriptions works pretty well but i have problems it s not possible to drag drop my example test serial button binding like described to the run requirements an error box pops up if i start my browser with the access is forbidden… it seems that localhost paperui index html must be used… this should be described in the docu…
| 0
|
923
| 3,385,736,157
|
IssuesEvent
|
2015-11-27 13:24:16
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
"Error: write EBADF" when sending a TLSSocket to the parent process
|
child_process tls
|
When sending a tls.TLSSocket to the parent process, the parent crashes with the following message: "Error: write EBADF".
Steps to reproduce:
$ cat bug_parent.js
var cp = require('child_process');
var child = cp.fork('./bug_child.js');
console.log('master: child forked');
child.on('message', function(msg, handle) {
console.log('parent: incoming handle %s %j', msg, handle);
});
$ cat bug_child.js
var fs = require('fs');
var tls = require('tls');
var opts = {
key: fs.readFileSync('private.pem'),
cert: fs.readFileSync('server.crt')
};
var tlsServer = tls.createServer(opts, function(conn) {
console.log('child: incoming connection, send to parent...');
process.send('socket', conn);
});
tlsServer.listen(8001, '127.0.0.1');
console.log('child: server started');
$ cat bug_client.js
var fs = require('fs');
var tls = require('tls');
var opts = {
host: 'localhost',
port: 8001,
ca: fs.readFileSync('server.crt'),
};
var conn = tls.connect(opts, function() {
console.log('connected');
});
Start the server in a terminal.
$ node bug_parent.js
master: child forked
child: server started
Now start the client in another terminal.
$ node bug_client.js
events.js:141
throw er; // Unhandled 'error' event
^
Error: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1089:19)
at TLSSocket.g (events.js:260:16)
at emitNone (events.js:72:20)
at TLSSocket.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:905:12)
at doNTCallback2 (node.js:452:9)
at process._tickCallback (node.js:366:17)
Server terminal prints:
child: incoming connection, send to parent...
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EBADF
at exports._errnoException (util.js:856:11)
at process.target._send (internal/child_process.js:606:18)
at process.target.send (internal/child_process.js:507:19)
at Server.<anonymous> (/Users/tim/code/persdb/bug_child.js:11:11)
at emitOne (events.js:77:13)
at Server.emit (events.js:169:7)
at TLSSocket.<anonymous> (_tls_wrap.js:813:14)
at emitNone (events.js:67:13)
at TLSSocket.emit (events.js:166:7)
at TLSSocket._finishInit (_tls_wrap.js:596:8)
Tested with Node 5.1.0, the problem exists in Node 4.2.2 as well, albeit with a different message: "listener must be a function". It all works when requiring `net` instead of `tls`.
|
1.0
|
"Error: write EBADF" when sending a TLSSocket to the parent process - When sending a tls.TLSSocket to the parent process, the parent crashes with the following message: "Error: write EBADF".
Steps to reproduce:
$ cat bug_parent.js
var cp = require('child_process');
var child = cp.fork('./bug_child.js');
console.log('master: child forked');
child.on('message', function(msg, handle) {
console.log('parent: incoming handle %s %j', msg, handle);
});
$ cat bug_child.js
var fs = require('fs');
var tls = require('tls');
var opts = {
key: fs.readFileSync('private.pem'),
cert: fs.readFileSync('server.crt')
};
var tlsServer = tls.createServer(opts, function(conn) {
console.log('child: incoming connection, send to parent...');
process.send('socket', conn);
});
tlsServer.listen(8001, '127.0.0.1');
console.log('child: server started');
$ cat bug_client.js
var fs = require('fs');
var tls = require('tls');
var opts = {
host: 'localhost',
port: 8001,
ca: fs.readFileSync('server.crt'),
};
var conn = tls.connect(opts, function() {
console.log('connected');
});
Start the server in a terminal.
$ node bug_parent.js
master: child forked
child: server started
Now start the client in another terminal.
$ node bug_client.js
events.js:141
throw er; // Unhandled 'error' event
^
Error: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1089:19)
at TLSSocket.g (events.js:260:16)
at emitNone (events.js:72:20)
at TLSSocket.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:905:12)
at doNTCallback2 (node.js:452:9)
at process._tickCallback (node.js:366:17)
Server terminal prints:
child: incoming connection, send to parent...
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EBADF
at exports._errnoException (util.js:856:11)
at process.target._send (internal/child_process.js:606:18)
at process.target.send (internal/child_process.js:507:19)
at Server.<anonymous> (/Users/tim/code/persdb/bug_child.js:11:11)
at emitOne (events.js:77:13)
at Server.emit (events.js:169:7)
at TLSSocket.<anonymous> (_tls_wrap.js:813:14)
at emitNone (events.js:67:13)
at TLSSocket.emit (events.js:166:7)
at TLSSocket._finishInit (_tls_wrap.js:596:8)
Tested with Node 5.1.0, the problem exists in Node 4.2.2 as well, albeit with a different message: "listener must be a function". It all works when requiring `net` instead of `tls`.
|
process
|
error write ebadf when sending a tlssocket to the parent process when sending a tls tlssocket to the parent process the parent crashes with the following message error write ebadf steps to reproduce cat bug parent js var cp require child process var child cp fork bug child js console log master child forked child on message function msg handle console log parent incoming handle s j msg handle cat bug child js var fs require fs var tls require tls var opts key fs readfilesync private pem cert fs readfilesync server crt var tlsserver tls createserver opts function conn console log child incoming connection send to parent process send socket conn tlsserver listen console log child server started cat bug client js var fs require fs var tls require tls var opts host localhost port ca fs readfilesync server crt var conn tls connect opts function console log connected start the server in a terminal node bug parent js master child forked child server started now start the client in another terminal node bug client js events js throw er unhandled error event error socket hang up at tlssocket onhangup tls wrap js at tlssocket g events js at emitnone events js at tlssocket emit events js at endreadablent stream readable js at node js at process tickcallback node js server terminal prints child incoming connection send to parent events js throw er unhandled error event error write ebadf at exports errnoexception util js at process target send internal child process js at process target send internal child process js at server users tim code persdb bug child js at emitone events js at server emit events js at tlssocket tls wrap js at emitnone events js at tlssocket emit events js at tlssocket finishinit tls wrap js tested with node the problem exists in node as well albeit with a different message listener must be a function it all works when requiring net instead of tls
| 1
|
195,359
| 15,527,388,261
|
IssuesEvent
|
2021-03-13 05:45:12
|
CliMA/Oceananigans.jl
|
https://api.github.com/repos/CliMA/Oceananigans.jl
|
opened
|
Stratified Couette flow validation section in Docs: images not showing up
|
documentation 📜
|
<img width="750" alt="Screen Shot 2021-03-13 at 4 44 11 pm" src="https://user-images.githubusercontent.com/7112768/111020624-6e090380-841b-11eb-8658-1130d560d86b.png">
|
1.0
|
Stratified Couette flow validation section in Docs: images not showing up - <img width="750" alt="Screen Shot 2021-03-13 at 4 44 11 pm" src="https://user-images.githubusercontent.com/7112768/111020624-6e090380-841b-11eb-8658-1130d560d86b.png">
|
non_process
|
stratified couette flow validation section in docs images not showing up img width alt screen shot at pm src
| 0
|
181,568
| 6,662,126,231
|
IssuesEvent
|
2017-10-02 11:49:49
|
spring-projects/spring-boot
|
https://api.github.com/repos/spring-projects/spring-boot
|
closed
|
`spring.profiles.active` from JNDI and context-param are added to active profiles instead of overriding them
|
priority: normal type: bug
|
When running a Spring Boot application as a WAR in a servlet container (Tested in Tomcat and WebSphere Liberty), `spring.profiles.active` property set using JNDI or context-param are added to active profiles instead of overriding them.
For example, here's a web.xml that sets both JNDI and context-param:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1">
<display-name>demo</display-name>
<context-param>
<param-name>spring.profiles.active</param-name>
<param-value>from-context-param</param-value>
</context-param>
<!-- sets JNDI -->
<env-entry>
<env-entry-name>spring.profiles.active</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>from-jndi</env-entry-value>
</env-entry>
</web-app>
```
With the above, the following profiles become active: `from-context-param,from-jndi`
To reproduce, add the above to `src/main/webapp/WEB-INF/web.xml` in a Spring Boot application packaged as WAR then run it in a servlet container.
Also, I did more tests by setting `spring.profiles.active` from different sources and observing the active profiles. The results were quite inconsistent:
(`X` means I set `spring.profiles.active` in the property source. `1`/`2` means the profile was active and the number is its order in the active profiles)
|context-param|JNDI|system property|environment property|application.properties|
|-|-|-|-|-|
|X1|X2|X|X|X|
|X1|X2|X||X|
|X1|X2||X|X|
|X1|X2|||X|
|X1||X2|X|X|
|X1||X2||X|
|X1|||X2|X|
|X1||||X|
||X2|X1|X|X|
||X2|X1||X|
||X2||X1|X|
||X2|||X1|
|||X1|X|X|
|||X1||X|
||||X1|X|
|||||X1|
|
1.0
|
`spring.profiles.active` from JNDI and context-param are added to active profiles instead of overriding them - When running a Spring Boot application as a WAR in a servlet container (Tested in Tomcat and WebSphere Liberty), `spring.profiles.active` property set using JNDI or context-param are added to active profiles instead of overriding them.
For example, here's a web.xml that sets both JNDI and context-param:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1">
<display-name>demo</display-name>
<context-param>
<param-name>spring.profiles.active</param-name>
<param-value>from-context-param</param-value>
</context-param>
<!-- sets JNDI -->
<env-entry>
<env-entry-name>spring.profiles.active</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>from-jndi</env-entry-value>
</env-entry>
</web-app>
```
With the above, the following profiles become active: `from-context-param,from-jndi`
To reproduce, add the above to `src/main/webapp/WEB-INF/web.xml` in a Spring Boot application packaged as WAR then run it in a servlet container.
Also, I did more tests by setting `spring.profiles.active` from different sources and observing the active profiles. The results were quite inconsistent:
(`X` means I set `spring.profiles.active` in the property source. `1`/`2` means the profile was active and the number is its order in the active profiles)
|context-param|JNDI|system property|environment property|application.properties|
|-|-|-|-|-|
|X1|X2|X|X|X|
|X1|X2|X||X|
|X1|X2||X|X|
|X1|X2|||X|
|X1||X2|X|X|
|X1||X2||X|
|X1|||X2|X|
|X1||||X|
||X2|X1|X|X|
||X2|X1||X|
||X2||X1|X|
||X2|||X1|
|||X1|X|X|
|||X1||X|
||||X1|X|
|||||X1|
|
non_process
|
spring profiles active from jndi and context param are added to active profiles instead of overriding them when running a spring boot application as a war in a servlet container tested in tomcat and websphere liberty spring profiles active property set using jndi or context param are added to active profiles instead of overriding them for example here s a web xml that sets both jndi and context param xml web app xmlns xmlns xsi xsi schemalocation version demo spring profiles active from context param spring profiles active java lang string from jndi with the above the following profiles become active from context param from jndi to reproduce add the above to src main webapp web inf web xml in a spring boot application packaged as war then run it in a servlet container also i did more tests by setting spring profiles active from different sources and observing the active profiles the results were quite inconsistent x means i set spring profiles active in the property source means the profile was active and the number is its order in the active profiles context param jndi system property environment property application properties x x x x x x x x x x x x x x x x x x x x x
| 0
|
13,634
| 16,254,013,533
|
IssuesEvent
|
2021-05-08 00:44:43
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
add link to Hybrid Runbook Worker.
|
Pri2 automation/svc cxp doc-enhancement process-automation/subsvc triaged
|
In the sentence
“For long-running Azure Automation tasks, it's recommended to use a Hybrid Runbook Worker.” It will be good to add link to https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: bf4da869-3f32-d2bb-d804-62679c1c3cbd
* Version Independent ID: 49ec3073-a31e-a0ab-882d-17d3a7a420b0
* Content: [Runbook execution in Azure Automation](https://docs.microsoft.com/en-us/azure/automation/automation-runbook-execution#fair-share)
* Content Source: [articles/automation/automation-runbook-execution.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/automation/automation-runbook-execution.md)
* Service: **automation**
* Sub-service: **process-automation**
* GitHub Login: @MGoedtel
* Microsoft Alias: **magoedte**
|
1.0
|
add link to Hybrid Runbook Worker. - In the sentence
“For long-running Azure Automation tasks, it's recommended to use a Hybrid Runbook Worker.” It will be good to add link to https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: bf4da869-3f32-d2bb-d804-62679c1c3cbd
* Version Independent ID: 49ec3073-a31e-a0ab-882d-17d3a7a420b0
* Content: [Runbook execution in Azure Automation](https://docs.microsoft.com/en-us/azure/automation/automation-runbook-execution#fair-share)
* Content Source: [articles/automation/automation-runbook-execution.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/automation/automation-runbook-execution.md)
* Service: **automation**
* Sub-service: **process-automation**
* GitHub Login: @MGoedtel
* Microsoft Alias: **magoedte**
|
process
|
add link to hybrid runbook worker in the sentence “for long running azure automation tasks it s recommended to use a hybrid runbook worker ” it will be good to add link to document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service automation sub service process automation github login mgoedtel microsoft alias magoedte
| 1
|
9,285
| 12,304,336,811
|
IssuesEvent
|
2020-05-11 20:18:42
|
nextgenhealthcare/connect
|
https://api.github.com/repos/nextgenhealthcare/connect
|
closed
|
Process HL7 ACK now rejecting valid Enhanced mode codes e.g. CA, CE, CR
|
ack process
|
With 'Process HL7 ACK' set in the TCP sender, Mirth Connect is now rejecting messages such as
MSH|^~\&|eGate|GSST|ADT|iSOFT Engine|20131210090610||ACK|c4c0f802-ad67-432d-be8f-c307efdfc8dd|D|2.3|
MSA|CA|907175784|||||
which were previously accepted by version 2.x
Mirth queues the message on error 'Invalid HL7 v2.x acknowledgement received'
Imported Issue. Original Details:
Jira Issue Key: MIRTH-3092
Reporter: seaston
Created: 2013-12-10T01:08:33.000-0800
|
1.0
|
Process HL7 ACK now rejecting valid Enhanced mode codes e.g. CA, CE, CR - With 'Process HL7 ACK' set in the TCP sender, Mirth Connect is now rejecting messages such as
MSH|^~\&|eGate|GSST|ADT|iSOFT Engine|20131210090610||ACK|c4c0f802-ad67-432d-be8f-c307efdfc8dd|D|2.3|
MSA|CA|907175784|||||
which were previously accepted by version 2.x
Mirth queues the message on error 'Invalid HL7 v2.x acknowledgement received'
Imported Issue. Original Details:
Jira Issue Key: MIRTH-3092
Reporter: seaston
Created: 2013-12-10T01:08:33.000-0800
|
process
|
process ack now rejecting valid enhanced mode codes e g ca ce cr with process ack set in the tcp sender mirth connect is now rejecting messages such as msh egate gsst adt isoft engine ack d msa ca which were previously accepted by version x mirth queues the message on error invalid x acknowledgement received imported issue original details jira issue key mirth reporter seaston created
| 1
|
60,469
| 17,023,433,709
|
IssuesEvent
|
2021-07-03 02:00:42
|
tomhughes/trac-tickets
|
https://api.github.com/repos/tomhughes/trac-tickets
|
closed
|
Track areas need to be rendered
|
Component: mapnik Priority: minor Resolution: fixed Type: defect
|
**[Submitted to the original trac issue database at 10.29am, Thursday, 2nd July 2009]**
I have done some mapping for the Royal Norfolk Show, visible at:
http://www.openstreetmap.org/?lat=52.64898&lon=1.17735&zoom=16&layers=B000FTF
This mainly consists of highway=track, tracktype=grade1; which renders fine.
However, closed areas of the same surface tagged with area=yes are not rendered in Mapnik currently - though they appear in Osmarender.
|
1.0
|
Track areas need to be rendered - **[Submitted to the original trac issue database at 10.29am, Thursday, 2nd July 2009]**
I have done some mapping for the Royal Norfolk Show, visible at:
http://www.openstreetmap.org/?lat=52.64898&lon=1.17735&zoom=16&layers=B000FTF
This mainly consists of highway=track, tracktype=grade1; which renders fine.
However, closed areas of the same surface tagged with area=yes are not rendered in Mapnik currently - though they appear in Osmarender.
|
non_process
|
track areas need to be rendered i have done some mapping for the royal norfolk show visible at this mainly consists of highway track tracktype which renders fine however closed areas of the same surface tagged with area yes are not rendered in mapnik currently though they appear in osmarender
| 0
|
290,244
| 32,045,666,885
|
IssuesEvent
|
2023-09-23 01:34:21
|
Chiencc/asuswrt-gt-ac5300
|
https://api.github.com/repos/Chiencc/asuswrt-gt-ac5300
|
reopened
|
clientsoftwarelibgcrypt-1.5.1: 11 vulnerabilities (highest severity is: 7.8)
|
Mend: dependency security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p></summary>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
</p>
</p></p>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (clientsoftwarelibgcrypt version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-3345](https://www.mend.io/vulnerability-database/CVE-2021-3345) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.8 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.9.1 | ❌ |
| [CVE-2021-33560](https://www.mend.io/vulnerability-database/CVE-2021-33560) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.9.3 | ❌ |
| [CVE-2018-6829](https://www.mend.io/vulnerability-database/CVE-2018-6829) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt - 1.9.3 | ❌ |
| [CVE-2017-0379](https://www.mend.io/vulnerability-database/CVE-2017-0379) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | detected in multiple dependencies | Direct | 1.8.1 | ❌ |
| [CVE-2017-7526](https://www.mend.io/vulnerability-database/CVE-2017-7526) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.8 | detected in multiple dependencies | Direct | 1.7.8 | ❌ |
| [CVE-2019-13627](https://www.mend.io/vulnerability-database/CVE-2019-13627) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.3 | detected in multiple dependencies | Direct | 1.8.5 | ❌ |
| [CVE-2015-0837](https://www.mend.io/vulnerability-database/CVE-2015-0837) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.9 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.6.3 | ❌ |
| [CVE-2016-6313](https://www.mend.io/vulnerability-database/CVE-2016-6313) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.5.6,1.6.6,1.7.3, GnuPG-1.4.21 | ❌ |
| [CVE-2014-3591](https://www.mend.io/vulnerability-database/CVE-2014-3591) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.2 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.6.3 | ❌ |
| [CVE-2014-5270](https://www.mend.io/vulnerability-database/CVE-2014-5270) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.0 | clientsoftwarelibgcrypt-1.5.1 | Direct | 1.5.4 | ❌ |
| [CVE-2015-7511](https://www.mend.io/vulnerability-database/CVE-2015-7511) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 2.0 | clientsoftwarelibgcrypt-1.5.1 | Direct | 1.6.5 | ❌ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-3345</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/hash-common.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/hash-common.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/hash-common.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
_gcry_md_block_write in cipher/hash-common.c in Libgcrypt version 1.9.0 has a heap-based buffer overflow when the digest final function sets a large count value. It is recommended to upgrade to 1.9.1 or later.
<p>Publish Date: 2021-01-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3345>CVE-2021-3345</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3345">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3345</a></p>
<p>Release Date: 2021-01-29</p>
<p>Fix Resolution: libgcrypt-1.9.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-33560</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.
<p>Publish Date: 2021-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33560>CVE-2021-33560</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33560">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33560</a></p>
<p>Release Date: 2021-06-08</p>
<p>Fix Resolution: libgcrypt-1.9.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2018-6829</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
<p>Publish Date: 2018-02-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-6829>CVE-2018-6829</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-6829">https://nvd.nist.gov/vuln/detail/CVE-2018-6829</a></p>
<p>Release Date: 2018-02-07</p>
<p>Fix Resolution: libgcrypt - 1.9.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2017-0379</summary>
### Vulnerable Libraries - <b>clientsoftwarelibgcrypt-1.5.1</b>, <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret key, related to cipher/ecc.c and mpi/ec.c.
<p>Publish Date: 2017-08-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-0379>CVE-2017-0379</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-0379">https://nvd.nist.gov/vuln/detail/CVE-2017-0379</a></p>
<p>Release Date: 2017-08-29</p>
<p>Fix Resolution: 1.8.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2017-7526</summary>
### Vulnerable Libraries - <b>clientsoftwarelibgcrypt-1.5.1</b>, <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
</p>
<p></p>
### Vulnerability Details
<p>
libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attacker can run arbitrary software on the hardware where the private RSA key is used.
<p>Publish Date: 2018-07-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-7526>CVE-2017-7526</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7526">https://nvd.nist.gov/vuln/detail/CVE-2017-7526</a></p>
<p>Release Date: 2018-07-26</p>
<p>Fix Resolution: 1.7.8</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2019-13627</summary>
### Vulnerable Libraries - <b>clientsoftwarelibgcrypt-1.5.1</b>, <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
</p>
<p></p>
### Vulnerability Details
<p>
It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.
<p>Publish Date: 2019-09-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-13627>CVE-2019-13627</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://gitlab.alpinelinux.org/alpine/aports/issues/10823">https://gitlab.alpinelinux.org/alpine/aports/issues/10823</a></p>
<p>Release Date: 2019-09-25</p>
<p>Fix Resolution: 1.8.5</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2015-0837</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mpi_powm function in Libgcrypt before 1.6.3 and GnuPG before 1.4.19 allows attackers to obtain sensitive information by leveraging timing differences when accessing a pre-computed table during modular exponentiation, related to a "Last-Level Cache Side-Channel Attack."
<p>Publish Date: 2019-11-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-0837>CVE-2015-0837</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0837">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0837</a></p>
<p>Release Date: 2019-11-29</p>
<p>Fix Resolution: libgcrypt-1.6.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2016-6313</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/random/random-csprng.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/random/random-csprng.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/random/random-csprng.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits.
<p>Publish Date: 2016-12-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-6313>CVE-2016-6313</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-6313">https://nvd.nist.gov/vuln/detail/CVE-2016-6313</a></p>
<p>Release Date: 2016-12-13</p>
<p>Fix Resolution: libgcrypt-1.5.6,1.6.6,1.7.3, GnuPG-1.4.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2014-3591</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.6.3 and GnuPG before 1.4.19 does not implement ciphertext blinding for Elgamal decryption, which allows physically proximate attackers to obtain the server's private key by determining factors using crafted ciphertext and the fluctuations in the electromagnetic field during multiplication.
<p>Publish Date: 2019-11-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-3591>CVE-2014-3591</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.2</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3591">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3591</a></p>
<p>Release Date: 2015-03-03</p>
<p>Fix Resolution: libgcrypt-1.6.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2014-5270</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.5.4, as used in GnuPG and other products, does not properly perform ciphertext normalization and ciphertext randomization, which makes it easier for physically proximate attackers to conduct key-extraction attacks by leveraging the ability to collect voltage data from exposed metal, a different vector than CVE-2013-4576.
<p>Publish Date: 2014-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-5270>CVE-2014-5270</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-5270">https://nvd.nist.gov/vuln/detail/CVE-2014-5270</a></p>
<p>Release Date: 2014-10-10</p>
<p>Fix Resolution: 1.5.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2015-7511</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (1)
<p></p>
<p>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.6.5 does not properly perform elliptic-point curve multiplication during decryption, which makes it easier for physically proximate attackers to extract ECDH keys by measuring electromagnetic emanations.
<p>Publish Date: 2016-04-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-7511>CVE-2015-7511</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>2.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: High
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-7511">https://nvd.nist.gov/vuln/detail/CVE-2015-7511</a></p>
<p>Release Date: 2016-04-19</p>
<p>Fix Resolution: 1.6.5</p>
</p>
<p></p>
</details>
|
True
|
clientsoftwarelibgcrypt-1.5.1: 11 vulnerabilities (highest severity is: 7.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p></summary>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
</p>
</p></p>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (clientsoftwarelibgcrypt version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-3345](https://www.mend.io/vulnerability-database/CVE-2021-3345) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.8 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.9.1 | ❌ |
| [CVE-2021-33560](https://www.mend.io/vulnerability-database/CVE-2021-33560) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.9.3 | ❌ |
| [CVE-2018-6829](https://www.mend.io/vulnerability-database/CVE-2018-6829) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt - 1.9.3 | ❌ |
| [CVE-2017-0379](https://www.mend.io/vulnerability-database/CVE-2017-0379) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | detected in multiple dependencies | Direct | 1.8.1 | ❌ |
| [CVE-2017-7526](https://www.mend.io/vulnerability-database/CVE-2017-7526) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.8 | detected in multiple dependencies | Direct | 1.7.8 | ❌ |
| [CVE-2019-13627](https://www.mend.io/vulnerability-database/CVE-2019-13627) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.3 | detected in multiple dependencies | Direct | 1.8.5 | ❌ |
| [CVE-2015-0837](https://www.mend.io/vulnerability-database/CVE-2015-0837) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.9 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.6.3 | ❌ |
| [CVE-2016-6313](https://www.mend.io/vulnerability-database/CVE-2016-6313) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.5.6,1.6.6,1.7.3, GnuPG-1.4.21 | ❌ |
| [CVE-2014-3591](https://www.mend.io/vulnerability-database/CVE-2014-3591) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.2 | clientsoftwarelibgcrypt-1.5.1 | Direct | libgcrypt-1.6.3 | ❌ |
| [CVE-2014-5270](https://www.mend.io/vulnerability-database/CVE-2014-5270) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.0 | clientsoftwarelibgcrypt-1.5.1 | Direct | 1.5.4 | ❌ |
| [CVE-2015-7511](https://www.mend.io/vulnerability-database/CVE-2015-7511) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 2.0 | clientsoftwarelibgcrypt-1.5.1 | Direct | 1.6.5 | ❌ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-3345</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/hash-common.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/hash-common.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/hash-common.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
_gcry_md_block_write in cipher/hash-common.c in Libgcrypt version 1.9.0 has a heap-based buffer overflow when the digest final function sets a large count value. It is recommended to upgrade to 1.9.1 or later.
<p>Publish Date: 2021-01-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3345>CVE-2021-3345</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3345">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3345</a></p>
<p>Release Date: 2021-01-29</p>
<p>Fix Resolution: libgcrypt-1.9.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-33560</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.
<p>Publish Date: 2021-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33560>CVE-2021-33560</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33560">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33560</a></p>
<p>Release Date: 2021-06-08</p>
<p>Fix Resolution: libgcrypt-1.9.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2018-6829</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
<p>Publish Date: 2018-02-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-6829>CVE-2018-6829</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-6829">https://nvd.nist.gov/vuln/detail/CVE-2018-6829</a></p>
<p>Release Date: 2018-02-07</p>
<p>Fix Resolution: libgcrypt - 1.9.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2017-0379</summary>
### Vulnerable Libraries - <b>clientsoftwarelibgcrypt-1.5.1</b>, <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret key, related to cipher/ecc.c and mpi/ec.c.
<p>Publish Date: 2017-08-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-0379>CVE-2017-0379</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-0379">https://nvd.nist.gov/vuln/detail/CVE-2017-0379</a></p>
<p>Release Date: 2017-08-29</p>
<p>Fix Resolution: 1.8.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2017-7526</summary>
### Vulnerable Libraries - <b>clientsoftwarelibgcrypt-1.5.1</b>, <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
</p>
<p></p>
### Vulnerability Details
<p>
libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attacker can run arbitrary software on the hardware where the private RSA key is used.
<p>Publish Date: 2018-07-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-7526>CVE-2017-7526</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7526">https://nvd.nist.gov/vuln/detail/CVE-2017-7526</a></p>
<p>Release Date: 2018-07-26</p>
<p>Fix Resolution: 1.7.8</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2019-13627</summary>
### Vulnerable Libraries - <b>clientsoftwarelibgcrypt-1.5.1</b>, <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
</p>
<p></p>
### Vulnerability Details
<p>
It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.
<p>Publish Date: 2019-09-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-13627>CVE-2019-13627</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://gitlab.alpinelinux.org/alpine/aports/issues/10823">https://gitlab.alpinelinux.org/alpine/aports/issues/10823</a></p>
<p>Release Date: 2019-09-25</p>
<p>Fix Resolution: 1.8.5</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2015-0837</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mpi_powm function in Libgcrypt before 1.6.3 and GnuPG before 1.4.19 allows attackers to obtain sensitive information by leveraging timing differences when accessing a pre-computed table during modular exponentiation, related to a "Last-Level Cache Side-Channel Attack."
<p>Publish Date: 2019-11-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-0837>CVE-2015-0837</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0837">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0837</a></p>
<p>Release Date: 2019-11-29</p>
<p>Fix Resolution: libgcrypt-1.6.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2016-6313</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/random/random-csprng.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/random/random-csprng.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/random/random-csprng.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits.
<p>Publish Date: 2016-12-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-6313>CVE-2016-6313</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-6313">https://nvd.nist.gov/vuln/detail/CVE-2016-6313</a></p>
<p>Release Date: 2016-12-13</p>
<p>Fix Resolution: libgcrypt-1.5.6,1.6.6,1.7.3, GnuPG-1.4.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2014-3591</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/cipher/elgamal.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.6.3 and GnuPG before 1.4.19 does not implement ciphertext blinding for Elgamal decryption, which allows physically proximate attackers to obtain the server's private key by determining factors using crafted ciphertext and the fluctuations in the electromagnetic field during multiplication.
<p>Publish Date: 2019-11-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-3591>CVE-2014-3591</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.2</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3591">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3591</a></p>
<p>Release Date: 2015-03-03</p>
<p>Fix Resolution: libgcrypt-1.6.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2014-5270</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (3)
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/libgcrypt-1.5.1/mpi/mpi-pow.c</b>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.5.4, as used in GnuPG and other products, does not properly perform ciphertext normalization and ciphertext randomization, which makes it easier for physically proximate attackers to conduct key-extraction attacks by leveraging the ability to collect voltage data from exposed metal, a different vector than CVE-2013-4576.
<p>Publish Date: 2014-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-5270>CVE-2014-5270</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-5270">https://nvd.nist.gov/vuln/detail/CVE-2014-5270</a></p>
<p>Release Date: 2014-10-10</p>
<p>Fix Resolution: 1.5.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2015-7511</summary>
### Vulnerable Library - <b>clientsoftwarelibgcrypt-1.5.1</b></p>
<p>
<p>Client Software for Imprint Management</p>
<p>Library home page: <a href=https://github.com/WaveLLC/clientsoftware.git>https://github.com/WaveLLC/clientsoftware.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
<p>Found in base branch: <b>master</b></p></p>
</p></p>
### Vulnerable Source Files (1)
<p></p>
<p>
</p>
<p></p>
</p>
<p></p>
### Vulnerability Details
<p>
Libgcrypt before 1.6.5 does not properly perform elliptic-point curve multiplication during decryption, which makes it easier for physically proximate attackers to extract ECDH keys by measuring electromagnetic emanations.
<p>Publish Date: 2016-04-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-7511>CVE-2015-7511</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>2.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: High
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-7511">https://nvd.nist.gov/vuln/detail/CVE-2015-7511</a></p>
<p>Release Date: 2016-04-19</p>
<p>Fix Resolution: 1.6.5</p>
</p>
<p></p>
</details>
|
non_process
|
clientsoftwarelibgcrypt vulnerabilities highest severity is vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href vulnerable source files release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c vulnerabilities cve severity cvss dependency type fixed in clientsoftwarelibgcrypt version remediation possible high clientsoftwarelibgcrypt direct libgcrypt high clientsoftwarelibgcrypt direct libgcrypt high clientsoftwarelibgcrypt direct libgcrypt high detected in multiple dependencies direct medium detected in multiple dependencies direct medium detected in multiple dependencies direct medium clientsoftwarelibgcrypt direct libgcrypt medium clientsoftwarelibgcrypt direct libgcrypt gnupg medium clientsoftwarelibgcrypt direct libgcrypt medium clientsoftwarelibgcrypt direct low clientsoftwarelibgcrypt direct in some cases remediation pr cannot be created automatically for a vulnerability despite the availability of remediation details cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt cipher hash common c release src router libgcrypt cipher hash common c release src router libgcrypt cipher hash common c vulnerability details gcry md block write in cipher hash common c in libgcrypt version has a heap based buffer overflow when the digest final function sets a large count value it is recommended to upgrade to or later 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 libgcrypt cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c vulnerability details libgcrypt before and x before mishandles elgamal encryption because it lacks exponent blinding to address a side channel attack against mpi powm and the window size is not chosen appropriately this for example affects use of elgamal in openpgp publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libgcrypt cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c vulnerability details cipher elgamal c in libgcrypt through when used to encrypt messages directly improperly encodes plaintexts which allows attackers to obtain sensitive information by reading ciphertext data i e it does not have semantic security in face of a ciphertext only attack the decisional diffie hellman ddh assumption does not hold for libgcrypt s elgamal implementation publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libgcrypt cve vulnerable libraries clientsoftwarelibgcrypt clientsoftwarelibgcrypt vulnerability details libgcrypt before does not properly consider side channel attacks which makes it easier for attackers to discover a secret key related to cipher ecc c and mpi ec c publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable libraries clientsoftwarelibgcrypt clientsoftwarelibgcrypt vulnerability details libgcrypt before version is vulnerable to a cache side channel attack resulting into a complete break of rsa while using the left to right method for computing the sliding window expansion the same attack is believed to work on rsa with moderately more computation this side channel requires that attacker can run arbitrary software on the hardware where the private rsa key is used publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable libraries clientsoftwarelibgcrypt clientsoftwarelibgcrypt vulnerability details it was discovered that there was a ecdsa timing attack in the cryptographic library version affected and versions fixed and publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt mpi mpi pow c release src router libgcrypt mpi mpi pow c release src router libgcrypt mpi mpi pow c vulnerability details the mpi powm function in libgcrypt before and gnupg before allows attackers to obtain sensitive information by leveraging timing differences when accessing a pre computed table during modular exponentiation related to a last level cache side channel attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libgcrypt cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt random random csprng c release src router libgcrypt random random csprng c release src router libgcrypt random random csprng c vulnerability details the mixing functions in the random number generator in libgcrypt before x before and x before and gnupg before make it easier for attackers to obtain the values of bits by leveraging knowledge of the previous bits 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 suggested fix type upgrade version origin a href release date fix resolution libgcrypt gnupg cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c release src router libgcrypt cipher elgamal c vulnerability details libgcrypt before and gnupg before does not implement ciphertext blinding for elgamal decryption which allows physically proximate attackers to obtain the server s private key by determining factors using crafted ciphertext and the fluctuations in the electromagnetic field during multiplication publish date url a href cvss score details base score metrics exploitability metrics attack vector physical attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libgcrypt cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files release src router libgcrypt mpi mpi pow c release src router libgcrypt mpi mpi pow c release src router libgcrypt mpi mpi pow c vulnerability details libgcrypt before as used in gnupg and other products does not properly perform ciphertext normalization and ciphertext randomization which makes it easier for physically proximate attackers to conduct key extraction attacks by leveraging the ability to collect voltage data from exposed metal a different vector than cve publish date url a href cvss score details base score metrics exploitability metrics attack vector local 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 suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library clientsoftwarelibgcrypt client software for imprint management library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details libgcrypt before does not properly perform elliptic point curve multiplication during decryption which makes it easier for physically proximate attackers to extract ecdh keys by measuring electromagnetic emanations publish date url a href cvss score details base score metrics exploitability metrics attack vector physical attack complexity high 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 suggested fix type upgrade version origin a href release date fix resolution
| 0
|
8,655
| 11,795,368,936
|
IssuesEvent
|
2020-03-18 08:49:33
|
tikv/tikv
|
https://api.github.com/repos/tikv/tikv
|
closed
|
unexpected behavior for bytes column in where clause
|
component/coprocessor type/bug
|
## Bug Report
Run one SQL (from copr-test) but different results.
```sql
SELECT EXP( `col_set` ) AS field1, `col_timestamp_key` % '2013-03-22' AS field2, DEGREES( '15:00:34.037137' ) AS field3 FROM `table1_int_autoinc` WHERE `col_binary_8_key` AND '2006-04-04 16:25:30.047980'
```
Right after tidb starts, this SQL query will generate an IndexScan op (as `col_binary_8_key` is an index). Because `col_set` is too big, this SQL query will return an error.
But after several minutes, the execution plan will change. TiDB will generate Selection op to fully scan this table. While the filter `col_binary_8_key` is a `Bytes`, TiKV will convert it to int (with str2int rule) and compare it will 0.
```rust
impl AsMySQLBool for Bytes {
#[inline]
fn as_mysql_bool(&self, context: &mut EvalContext) -> Result<bool> {
Ok(!self.is_empty() && self.to_int(context, FieldTypeTp::LongLong)? != 0)
}
}
```
Actually this column is string "lyashfuw" so converting it to int will get a zero, and no row is returned. As a result, this query doesn't get an error.
### What version of TiKV are you using?
```
Release Version: 4.1.0-alpha
Git Commit Hash: 18b87012ac3450e8037baaa61ea26a73c40ef33e
Git Commit Branch: master
UTC Build Time: 2020-03-18 07:46:43
Rust Version: rustc 1.42.0-nightly (0de96d37f 2019-12-19)
Enable Features: jemalloc portable sse protobuf-codec
Profile: debug
```
### Steps to reproduce
See copr-test
### What did you expect?
Return no rows.
### What did happened?
Sometimes return an error but after several times no row is returned.
|
1.0
|
unexpected behavior for bytes column in where clause - ## Bug Report
Run one SQL (from copr-test) but different results.
```sql
SELECT EXP( `col_set` ) AS field1, `col_timestamp_key` % '2013-03-22' AS field2, DEGREES( '15:00:34.037137' ) AS field3 FROM `table1_int_autoinc` WHERE `col_binary_8_key` AND '2006-04-04 16:25:30.047980'
```
Right after tidb starts, this SQL query will generate an IndexScan op (as `col_binary_8_key` is an index). Because `col_set` is too big, this SQL query will return an error.
But after several minutes, the execution plan will change. TiDB will generate Selection op to fully scan this table. While the filter `col_binary_8_key` is a `Bytes`, TiKV will convert it to int (with str2int rule) and compare it will 0.
```rust
impl AsMySQLBool for Bytes {
#[inline]
fn as_mysql_bool(&self, context: &mut EvalContext) -> Result<bool> {
Ok(!self.is_empty() && self.to_int(context, FieldTypeTp::LongLong)? != 0)
}
}
```
Actually this column is string "lyashfuw" so converting it to int will get a zero, and no row is returned. As a result, this query doesn't get an error.
### What version of TiKV are you using?
```
Release Version: 4.1.0-alpha
Git Commit Hash: 18b87012ac3450e8037baaa61ea26a73c40ef33e
Git Commit Branch: master
UTC Build Time: 2020-03-18 07:46:43
Rust Version: rustc 1.42.0-nightly (0de96d37f 2019-12-19)
Enable Features: jemalloc portable sse protobuf-codec
Profile: debug
```
### Steps to reproduce
See copr-test
### What did you expect?
Return no rows.
### What did happened?
Sometimes return an error but after several times no row is returned.
|
process
|
unexpected behavior for bytes column in where clause bug report run one sql from copr test but different results sql select exp col set as col timestamp key as degrees as from int autoinc where col binary key and right after tidb starts this sql query will generate an indexscan op as col binary key is an index because col set is too big this sql query will return an error but after several minutes the execution plan will change tidb will generate selection op to fully scan this table while the filter col binary key is a bytes tikv will convert it to int with rule and compare it will rust impl asmysqlbool for bytes fn as mysql bool self context mut evalcontext result ok self is empty self to int context fieldtypetp longlong actually this column is string lyashfuw so converting it to int will get a zero and no row is returned as a result this query doesn t get an error what version of tikv are you using release version alpha git commit hash git commit branch master utc build time rust version rustc nightly enable features jemalloc portable sse protobuf codec profile debug steps to reproduce see copr test what did you expect return no rows what did happened sometimes return an error but after several times no row is returned
| 1
|
11,947
| 14,711,355,047
|
IssuesEvent
|
2021-01-05 07:17:01
|
modi-w/AutoVersionsDB
|
https://api.github.com/repos/modi-w/AutoVersionsDB
|
opened
|
Successful save indication on EditProjectView
|
area-UI process-discussion type-enhancement
|
**The Problem**
In the EditProjectView, when the user clicked on "Save" and the form saves successfully but the form contains errors, there is no indication for the user about the successful save execution.
**Solution**
Should be discussed on the solution.
|
1.0
|
Successful save indication on EditProjectView - **The Problem**
In the EditProjectView, when the user clicked on "Save" and the form saves successfully but the form contains errors, there is no indication for the user about the successful save execution.
**Solution**
Should be discussed on the solution.
|
process
|
successful save indication on editprojectview the problem in the editprojectview when the user clicked on save and the form saves successfully but the form contains errors there is no indication for the user about the successful save execution solution should be discussed on the solution
| 1
|
19,254
| 25,451,891,715
|
IssuesEvent
|
2022-11-24 11:06:11
|
deepset-ai/haystack
|
https://api.github.com/repos/deepset-ai/haystack
|
closed
|
PDFToTextConverter: [WinError 2] The system can't find the specified file
|
type:bug topic:preprocessing
|
Hi guys, I think what you are doing is very interesting. I am currently struggling with data Preprocessing(Tutorial 8).
When I open my own pdf file in function PDFToTextConverter, I get the following error:
[WinError 2] The system can't find the specified file
Unfortunately, I have not yet found a specific solution for it. Can you guide me?
|
1.0
|
PDFToTextConverter: [WinError 2] The system can't find the specified file - Hi guys, I think what you are doing is very interesting. I am currently struggling with data Preprocessing(Tutorial 8).
When I open my own pdf file in function PDFToTextConverter, I get the following error:
[WinError 2] The system can't find the specified file
Unfortunately, I have not yet found a specific solution for it. Can you guide me?
|
process
|
pdftotextconverter the system can t find the specified file hi guys i think what you are doing is very interesting i am currently struggling with data preprocessing tutorial when i open my own pdf file in function pdftotextconverter i get the following error the system can t find the specified file unfortunately i have not yet found a specific solution for it can you guide me
| 1
|
84,663
| 24,375,926,123
|
IssuesEvent
|
2022-10-04 00:52:02
|
symforce-org/symforce
|
https://api.github.com/repos/symforce-org/symforce
|
opened
|
Cython not found in Python binary directory
|
bug build
|
**Describe the bug**
If building in a Python environment whose `bin` directory is not on the `PATH` (e.g. doing a local pip install but not in a conda environment), symenginepy will not find Cython. `symenginepy` uses CMake `find_program` at `FindCython.cmake:8`, and fails with the error on line 48.
We should probably fix this by either telling symenginepy where to find cython, adding the directory containing the cython binary to PATH for the symenginepy build, or modifying the symenginepy build to always invoke cython as `python -m cython`.
Sample error message:
```
-- Python include path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8
-- Python version: 3.8
-- Python install path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/site-packages
-- Found Python: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8
CMake Error at cmake/FindCython.cmake:48 (MESSAGE):
Could not find Cython. Please install Cython.
Call Stack (most recent call first):
CMakeLists.txt:17 (find_package)
```
**Environment (please complete the following information):**
- OS and version: macOS (at least)
- Python version: all?
- SymForce Version: v0.6
|
1.0
|
Cython not found in Python binary directory - **Describe the bug**
If building in a Python environment whose `bin` directory is not on the `PATH` (e.g. doing a local pip install but not in a conda environment), symenginepy will not find Cython. `symenginepy` uses CMake `find_program` at `FindCython.cmake:8`, and fails with the error on line 48.
We should probably fix this by either telling symenginepy where to find cython, adding the directory containing the cython binary to PATH for the symenginepy build, or modifying the symenginepy build to always invoke cython as `python -m cython`.
Sample error message:
```
-- Python include path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8
-- Python version: 3.8
-- Python install path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/site-packages
-- Found Python: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8
CMake Error at cmake/FindCython.cmake:48 (MESSAGE):
Could not find Cython. Please install Cython.
Call Stack (most recent call first):
CMakeLists.txt:17 (find_package)
```
**Environment (please complete the following information):**
- OS and version: macOS (at least)
- Python version: all?
- SymForce Version: v0.6
|
non_process
|
cython not found in python binary directory describe the bug if building in a python environment whose bin directory is not on the path e g doing a local pip install but not in a conda environment symenginepy will not find cython symenginepy uses cmake find program at findcython cmake and fails with the error on line we should probably fix this by either telling symenginepy where to find cython adding the directory containing the cython binary to path for the symenginepy build or modifying the symenginepy build to always invoke cython as python m cython sample error message python include path library developer commandlinetools library frameworks framework versions include python version python install path library developer commandlinetools library frameworks framework versions lib site packages found python library developer commandlinetools library frameworks framework versions include cmake error at cmake findcython cmake message could not find cython please install cython call stack most recent call first cmakelists txt find package environment please complete the following information os and version macos at least python version all symforce version
| 0
|
47,825
| 19,728,298,711
|
IssuesEvent
|
2022-01-13 22:27:22
|
hashicorp/terraform-provider-aws
|
https://api.github.com/repos/hashicorp/terraform-provider-aws
|
closed
|
Can't change role path
|
service/iam
|
_This issue was originally opened by @hryamzik as hashicorp/terraform#23545. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._
<hr>
<!--
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
If your issue relates to a specific Terraform provider, please open it in the provider's own repository. The index of providers is at https://github.com/terraform-providers .
-->
### Terraform Version
<!---
Run `terraform -v` to show the version, and paste the result between the ``` marks below.
If you are not running the latest version of Terraform, please try upgrading because your issue may have already been fixed.
-->
```
Terraform v0.11.14
+ provider.aws v2.40.0
```
### Steps to Reproduce
1. Setup role and policy:
```hcl
resource "aws_iam_role" "test" {
...
}
resource "aws_iam_policy" "test" {
...
}
resource "aws_iam_role_policy_attachment" "media" {
role = "${aws_iam_role.test.name}"
policy_arn = "${aws_iam_policy.test.arn}"
}
```
2. init, apply
3. Add `path` option to a role
```hcl
resource "aws_iam_role" "test" {
path = "/test/"
...
}
```
4. init, apply
### Expected Behavior
<!--
What should have happened?
-->
Perform the update
### Actual Behavior
<!--
What actually happened?
-->
```
* aws_iam_role.test: Error deleting IAM role: DeleteConflict: Cannot delete entity, must detach all policies first.
```
|
1.0
|
Can't change role path - _This issue was originally opened by @hryamzik as hashicorp/terraform#23545. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._
<hr>
<!--
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
If your issue relates to a specific Terraform provider, please open it in the provider's own repository. The index of providers is at https://github.com/terraform-providers .
-->
### Terraform Version
<!---
Run `terraform -v` to show the version, and paste the result between the ``` marks below.
If you are not running the latest version of Terraform, please try upgrading because your issue may have already been fixed.
-->
```
Terraform v0.11.14
+ provider.aws v2.40.0
```
### Steps to Reproduce
1. Setup role and policy:
```hcl
resource "aws_iam_role" "test" {
...
}
resource "aws_iam_policy" "test" {
...
}
resource "aws_iam_role_policy_attachment" "media" {
role = "${aws_iam_role.test.name}"
policy_arn = "${aws_iam_policy.test.arn}"
}
```
2. init, apply
3. Add `path` option to a role
```hcl
resource "aws_iam_role" "test" {
path = "/test/"
...
}
```
4. init, apply
### Expected Behavior
<!--
What should have happened?
-->
Perform the update
### Actual Behavior
<!--
What actually happened?
-->
```
* aws_iam_role.test: Error deleting IAM role: DeleteConflict: Cannot delete entity, must detach all policies first.
```
|
non_process
|
can t change role path this issue was originally opened by hryamzik as hashicorp terraform it was migrated here as a result of the the original body of the issue is below hi there thank you for opening an issue please note that we try to keep the terraform issue tracker reserved for bug reports and feature requests for general usage questions please see if your issue relates to a specific terraform provider please open it in the provider s own repository the index of providers is at terraform version run terraform v to show the version and paste the result between the marks below if you are not running the latest version of terraform please try upgrading because your issue may have already been fixed terraform provider aws steps to reproduce setup role and policy hcl resource aws iam role test resource aws iam policy test resource aws iam role policy attachment media role aws iam role test name policy arn aws iam policy test arn init apply add path option to a role hcl resource aws iam role test path test init apply expected behavior what should have happened perform the update actual behavior what actually happened aws iam role test error deleting iam role deleteconflict cannot delete entity must detach all policies first
| 0
|
5,215
| 5,554,577,043
|
IssuesEvent
|
2017-03-24 00:39:33
|
bbijelic/certificate-authority
|
https://api.github.com/repos/bbijelic/certificate-authority
|
opened
|
ServiceAuthenticator should compare password hashes
|
enhancement security
|
ServiceAuthenticator should compare password hashes.
Introduce password salt.
Sha2 hashing should be used.
|
True
|
ServiceAuthenticator should compare password hashes - ServiceAuthenticator should compare password hashes.
Introduce password salt.
Sha2 hashing should be used.
|
non_process
|
serviceauthenticator should compare password hashes serviceauthenticator should compare password hashes introduce password salt hashing should be used
| 0
|
1,907
| 4,733,946,728
|
IssuesEvent
|
2016-10-19 12:54:41
|
scieloorg/search-journals
|
https://api.github.com/repos/scieloorg/search-journals
|
closed
|
Capacidade de busca pelo DOI
|
Processamento Tarefa
|
Atualmente o sistema de pesquisa da SciELO não permite utilizar o DOI para retornar um artigo considerando que o DOI é um código para encontrar artigos podemos utiliza-lo com mais um recurso na pesquisa.
|
1.0
|
Capacidade de busca pelo DOI - Atualmente o sistema de pesquisa da SciELO não permite utilizar o DOI para retornar um artigo considerando que o DOI é um código para encontrar artigos podemos utiliza-lo com mais um recurso na pesquisa.
|
process
|
capacidade de busca pelo doi atualmente o sistema de pesquisa da scielo não permite utilizar o doi para retornar um artigo considerando que o doi é um código para encontrar artigos podemos utiliza lo com mais um recurso na pesquisa
| 1
|
207,963
| 15,863,590,260
|
IssuesEvent
|
2021-04-08 12:57:34
|
nens/lizard-management-client
|
https://api.github.com/repos/nens/lizard-management-client
|
closed
|
Can't fill in "Before" in relative start and end
|
Sprint disruption Test result bug
|
When I select "Before" in the dropdown field it fills in "After". Second attempt gives same result. Third time in a row it succeeds and the filed is filled with "Before". Quite weird behavior.
|
1.0
|
Can't fill in "Before" in relative start and end - When I select "Before" in the dropdown field it fills in "After". Second attempt gives same result. Third time in a row it succeeds and the filed is filled with "Before". Quite weird behavior.
|
non_process
|
can t fill in before in relative start and end when i select before in the dropdown field it fills in after second attempt gives same result third time in a row it succeeds and the filed is filled with before quite weird behavior
| 0
|
115,564
| 11,882,133,571
|
IssuesEvent
|
2020-03-27 13:55:24
|
Cambridge-Digital-Library/Crowdsourcing
|
https://api.github.com/repos/Cambridge-Digital-Library/Crowdsourcing
|
closed
|
Create Guide: Create Account & Join
|
documentation
|
Create Guide page for creating a GitHub account, joining the project and uploading your transcription file.
|
1.0
|
Create Guide: Create Account & Join - Create Guide page for creating a GitHub account, joining the project and uploading your transcription file.
|
non_process
|
create guide create account join create guide page for creating a github account joining the project and uploading your transcription file
| 0
|
17,429
| 23,248,563,669
|
IssuesEvent
|
2022-08-03 23:31:54
|
microsoft/vscode
|
https://api.github.com/repos/microsoft/vscode
|
closed
|
No colors in task terminal
|
bug info-needed tasks confirmation-pending terminal-process
|
Issue Type: <b>Bug</b>
Simple c code.
Run build task with clang or cl.
In task terminal no colored output, but in ordinary terminal all fine.

VS Code version: Code 1.69.1 (b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a, 2022-07-12T08:21:24.514Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
<details><summary>Extensions (3)</summary>
Extension|Author (truncated)|Version
---|---|---
cmake-tools|ms-|1.11.26
cpptools|ms-|1.10.8
cmake|twx|0.0.17
(1 theme extensions excluded)
</details>
<!-- generated by issue reporter -->
|
1.0
|
No colors in task terminal - Issue Type: <b>Bug</b>
Simple c code.
Run build task with clang or cl.
In task terminal no colored output, but in ordinary terminal all fine.

VS Code version: Code 1.69.1 (b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a, 2022-07-12T08:21:24.514Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
<details><summary>Extensions (3)</summary>
Extension|Author (truncated)|Version
---|---|---
cmake-tools|ms-|1.11.26
cpptools|ms-|1.10.8
cmake|twx|0.0.17
(1 theme extensions excluded)
</details>
<!-- generated by issue reporter -->
|
process
|
no colors in task terminal issue type bug simple c code run build task with clang or cl in task terminal no colored output but in ordinary terminal all fine vs code version code os version windows nt restricted mode no extensions extension author truncated version cmake tools ms cpptools ms cmake twx theme extensions excluded
| 1
|
328,134
| 9,986,610,377
|
IssuesEvent
|
2019-07-10 19:33:36
|
marriott-library/newspaper_works
|
https://api.github.com/repos/marriott-library/newspaper_works
|
closed
|
breadcrumb links don't work with persistent URLs
|
Priority: High bug front-end views persistent URLs v.1.0
|
When trying to view pages using the ChronAm-style persistent URLs, the page throws an error:
```
NoMethodError in NewspaperWorks::Newspapers#page
Showing /home/vagrant/newspaper_works/app/views/newspaper_works/base/_newspaper_hierarchy.html.erb where line #11 raised:
undefined method `next_page_link' for #<#<Class:0x00000000088dce50>:0x00007f1f7c8f1ba8>
```
This is because the breadcrumb methods in `NewspaperWorks::BreadcrumbHelper` and `NewspaperPagesHelper` are not accessible by default to `NewspaperWorks::NewspapersController` which is responsible for handling the persistent URL requests.
This should be fairly easy to fix:
1. Create a `app/helpers/newspaper_works/newspapers_helper.rb` file:
```
module NewspaperWorks
module NewspapersHelper
include NewspaperWorks::BreadcrumbHelper
end
end
```
2. Move the `#previous_page_link` and `#next_page_link` methods from `NewspaperPagesHelper` into `NewspaperWorks::BreadcrumbHelper`. (This is fine, since these methods are well within the scope of `BreadcrumbHelper`.)
3. Adjust specs accordingly.
|
1.0
|
breadcrumb links don't work with persistent URLs - When trying to view pages using the ChronAm-style persistent URLs, the page throws an error:
```
NoMethodError in NewspaperWorks::Newspapers#page
Showing /home/vagrant/newspaper_works/app/views/newspaper_works/base/_newspaper_hierarchy.html.erb where line #11 raised:
undefined method `next_page_link' for #<#<Class:0x00000000088dce50>:0x00007f1f7c8f1ba8>
```
This is because the breadcrumb methods in `NewspaperWorks::BreadcrumbHelper` and `NewspaperPagesHelper` are not accessible by default to `NewspaperWorks::NewspapersController` which is responsible for handling the persistent URL requests.
This should be fairly easy to fix:
1. Create a `app/helpers/newspaper_works/newspapers_helper.rb` file:
```
module NewspaperWorks
module NewspapersHelper
include NewspaperWorks::BreadcrumbHelper
end
end
```
2. Move the `#previous_page_link` and `#next_page_link` methods from `NewspaperPagesHelper` into `NewspaperWorks::BreadcrumbHelper`. (This is fine, since these methods are well within the scope of `BreadcrumbHelper`.)
3. Adjust specs accordingly.
|
non_process
|
breadcrumb links don t work with persistent urls when trying to view pages using the chronam style persistent urls the page throws an error nomethoderror in newspaperworks newspapers page showing home vagrant newspaper works app views newspaper works base newspaper hierarchy html erb where line raised undefined method next page link for this is because the breadcrumb methods in newspaperworks breadcrumbhelper and newspaperpageshelper are not accessible by default to newspaperworks newspaperscontroller which is responsible for handling the persistent url requests this should be fairly easy to fix create a app helpers newspaper works newspapers helper rb file module newspaperworks module newspapershelper include newspaperworks breadcrumbhelper end end move the previous page link and next page link methods from newspaperpageshelper into newspaperworks breadcrumbhelper this is fine since these methods are well within the scope of breadcrumbhelper adjust specs accordingly
| 0
|
22,798
| 11,787,160,517
|
IssuesEvent
|
2020-03-17 13:35:41
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
What are the available values for WEBSITE_LOCAL_CACHE_OPTION to set
|
Pri3 app-service/svc cxp product-question triaged
|
"properties": {
"WEBSITE_LOCAL_CACHE_OPTION": "Always",
"WEBSITE_LOCAL_CACHE_SIZEINMB": "300"
}
I want to set the value for WEBSITE_LOCAL_CACHE_OPTION via parameter which will differ from environment to environment. For example, I don't want to use local cache for test environments, then what should be the value?
Edited: Added GitHub footer
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 93f1a8ab-c577-b9e8-b46e-28e0a90a0eae
* Version Independent ID: b716dcf9-1faf-fe60-b7be-f2bec92adbb5
* Content: [Local cache - Azure App Service](https://docs.microsoft.com/en-us/azure/app-service/overview-local-cache)
* Content Source: [articles/app-service/overview-local-cache.md](https://github.com/Microsoft/azure-docs/blob/master/articles/app-service/overview-local-cache.md)
* Service: **app-service**
* GitHub Login: @cephalin
* Microsoft Alias: **cephalin**
|
1.0
|
What are the available values for WEBSITE_LOCAL_CACHE_OPTION to set - "properties": {
"WEBSITE_LOCAL_CACHE_OPTION": "Always",
"WEBSITE_LOCAL_CACHE_SIZEINMB": "300"
}
I want to set the value for WEBSITE_LOCAL_CACHE_OPTION via parameter which will differ from environment to environment. For example, I don't want to use local cache for test environments, then what should be the value?
Edited: Added GitHub footer
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 93f1a8ab-c577-b9e8-b46e-28e0a90a0eae
* Version Independent ID: b716dcf9-1faf-fe60-b7be-f2bec92adbb5
* Content: [Local cache - Azure App Service](https://docs.microsoft.com/en-us/azure/app-service/overview-local-cache)
* Content Source: [articles/app-service/overview-local-cache.md](https://github.com/Microsoft/azure-docs/blob/master/articles/app-service/overview-local-cache.md)
* Service: **app-service**
* GitHub Login: @cephalin
* Microsoft Alias: **cephalin**
|
non_process
|
what are the available values for website local cache option to set properties website local cache option always website local cache sizeinmb i want to set the value for website local cache option via parameter which will differ from environment to environment for example i don t want to use local cache for test environments then what should be the value edited added github footer document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service app service github login cephalin microsoft alias cephalin
| 0
|
325
| 2,772,031,212
|
IssuesEvent
|
2015-05-02 08:05:48
|
arduino/Arduino
|
https://api.github.com/repos/arduino/Arduino
|
closed
|
wrong placement of arduino.h
|
Component: Preprocessor
|
My code begins with something like that
```
#if defined(__AVR_ATtiny85__)
const int Pin0 = 0;
#else
const int Pin0 = 4;
#endif
byte something;
```
Compiling it for any none __AVR_ATtiny85__ leads to an error due to wrong arduino.h placement into the if-else part.
Adding a dummy declaration at the start (in front of #if) omits the error... but a real fix would be better.
|
1.0
|
wrong placement of arduino.h - My code begins with something like that
```
#if defined(__AVR_ATtiny85__)
const int Pin0 = 0;
#else
const int Pin0 = 4;
#endif
byte something;
```
Compiling it for any none __AVR_ATtiny85__ leads to an error due to wrong arduino.h placement into the if-else part.
Adding a dummy declaration at the start (in front of #if) omits the error... but a real fix would be better.
|
process
|
wrong placement of arduino h my code begins with something like that if defined avr const int else const int endif byte something compiling it for any none avr leads to an error due to wrong arduino h placement into the if else part adding a dummy declaration at the start in front of if omits the error but a real fix would be better
| 1
|
288,555
| 21,711,045,836
|
IssuesEvent
|
2022-05-10 13:54:34
|
pyxem/orix
|
https://api.github.com/repos/pyxem/orix
|
opened
|
User guide notebook detailing use of Matplotlib to produce plots
|
documentation
|
@emichr asked how to include for example a `CrystalMap` plot with scalebar and all and an inverse pole figure in two separate axes but in the same figure. This isn't shown in the documentation, but is quite easily possible using the Matplotlib registered custom "projections" written in orix:
```python
import matplotlib.pyplot as plt
from orix import plot
from orix.crystal_map import CrystalMap
from orix.quaternion import Orientation, symmetry
from orix.vector import Vector3d
plt.rcParams.update({"font.size": 15, "figure.figsize": (10, 5)})
xmap = CrystalMap.empty((20, 30), step_sizes=(1, 1))
xmap.scan_unit = "nm"
g = Orientation.random(50)
g.symmetry = symmetry.Oh
v = Vector3d.zvector()
fig = plt.figure()
ax0 = fig.add_subplot(121, projection="plot_map")
ax0.plot_map(xmap, xmap.x)
ax0.remove_padding()
ax1 = fig.add_subplot(
122,
projection="ipf",
symmetry=g.symmetry,
direction=v,
hemisphere="upper"
)
ax1.set_title(str(v.data.squeeze()), fontweight="bold")
ax1.scatter(g)
fig.savefig("/home/hakon/kode/orix_test/crystal_map_ipf_plot_same_figure.png", bbox_inches="tight", pad_inches=0, dpi=150)
```

I suggest to add a new user guide topic "Plotting" where "Using orix with Matplotlib" can be explained in more detail, going beyond the convenience methods like `CrystalMap.plot()`, `Vector3d.plot()`, and `Orientation.plot()`, which are covered in other user guides.
|
1.0
|
User guide notebook detailing use of Matplotlib to produce plots - @emichr asked how to include for example a `CrystalMap` plot with scalebar and all and an inverse pole figure in two separate axes but in the same figure. This isn't shown in the documentation, but is quite easily possible using the Matplotlib registered custom "projections" written in orix:
```python
import matplotlib.pyplot as plt
from orix import plot
from orix.crystal_map import CrystalMap
from orix.quaternion import Orientation, symmetry
from orix.vector import Vector3d
plt.rcParams.update({"font.size": 15, "figure.figsize": (10, 5)})
xmap = CrystalMap.empty((20, 30), step_sizes=(1, 1))
xmap.scan_unit = "nm"
g = Orientation.random(50)
g.symmetry = symmetry.Oh
v = Vector3d.zvector()
fig = plt.figure()
ax0 = fig.add_subplot(121, projection="plot_map")
ax0.plot_map(xmap, xmap.x)
ax0.remove_padding()
ax1 = fig.add_subplot(
122,
projection="ipf",
symmetry=g.symmetry,
direction=v,
hemisphere="upper"
)
ax1.set_title(str(v.data.squeeze()), fontweight="bold")
ax1.scatter(g)
fig.savefig("/home/hakon/kode/orix_test/crystal_map_ipf_plot_same_figure.png", bbox_inches="tight", pad_inches=0, dpi=150)
```

I suggest to add a new user guide topic "Plotting" where "Using orix with Matplotlib" can be explained in more detail, going beyond the convenience methods like `CrystalMap.plot()`, `Vector3d.plot()`, and `Orientation.plot()`, which are covered in other user guides.
|
non_process
|
user guide notebook detailing use of matplotlib to produce plots emichr asked how to include for example a crystalmap plot with scalebar and all and an inverse pole figure in two separate axes but in the same figure this isn t shown in the documentation but is quite easily possible using the matplotlib registered custom projections written in orix python import matplotlib pyplot as plt from orix import plot from orix crystal map import crystalmap from orix quaternion import orientation symmetry from orix vector import plt rcparams update font size figure figsize xmap crystalmap empty step sizes xmap scan unit nm g orientation random g symmetry symmetry oh v zvector fig plt figure fig add subplot projection plot map plot map xmap xmap x remove padding fig add subplot projection ipf symmetry g symmetry direction v hemisphere upper set title str v data squeeze fontweight bold scatter g fig savefig home hakon kode orix test crystal map ipf plot same figure png bbox inches tight pad inches dpi i suggest to add a new user guide topic plotting where using orix with matplotlib can be explained in more detail going beyond the convenience methods like crystalmap plot plot and orientation plot which are covered in other user guides
| 0
|
28,265
| 4,086,920,956
|
IssuesEvent
|
2016-06-01 08:04:36
|
RestComm/Restcomm-Connect
|
https://api.github.com/repos/RestComm/Restcomm-Connect
|
opened
|
RVD application log UI does not work
|
1. Bug Visual App Designer
|
RVD application log UI does not display messages and the following exception is shown in server.log:
```
10:30:10,639 SEVERE [com.sun.jersey.spi.container.ContainerResponse] (http-/10.42.0.1:8080-20) The RuntimeException could not be mapped to a response, re-throwing to the HTTP container: java.lang.NullPointerException
at org.mobicents.servlet.restcomm.rvd.http.resources.SecuredRestService.secure(SecuredRestService.java:36) [classes:]
at org.mobicents.servlet.restcomm.rvd.http.resources.RvdController.appLog(RvdController.java:421) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_95]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_95]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_95]
```
|
1.0
|
RVD application log UI does not work - RVD application log UI does not display messages and the following exception is shown in server.log:
```
10:30:10,639 SEVERE [com.sun.jersey.spi.container.ContainerResponse] (http-/10.42.0.1:8080-20) The RuntimeException could not be mapped to a response, re-throwing to the HTTP container: java.lang.NullPointerException
at org.mobicents.servlet.restcomm.rvd.http.resources.SecuredRestService.secure(SecuredRestService.java:36) [classes:]
at org.mobicents.servlet.restcomm.rvd.http.resources.RvdController.appLog(RvdController.java:421) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_95]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_95]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_95]
```
|
non_process
|
rvd application log ui does not work rvd application log ui does not display messages and the following exception is shown in server log severe http the runtimeexception could not be mapped to a response re throwing to the http container java lang nullpointerexception at org mobicents servlet restcomm rvd http resources securedrestservice secure securedrestservice java at org mobicents servlet restcomm rvd http resources rvdcontroller applog rvdcontroller java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java
| 0
|
5,328
| 2,771,114,153
|
IssuesEvent
|
2015-05-01 19:14:08
|
isenseDev/rSENSE
|
https://api.github.com/repos/isenseDev/rSENSE
|
closed
|
Best fit line tooltip disappears after hovering over a data point
|
Bug In Testing Vis
|
**General description:**
Jim noticed this a while back. Essentially the tooltips are bound when a regression is created, but unbound whenever a regular data point/line is hovered over.
**live/dev/localhost:** Live
**iSENSE Version:** v5.5
**Logged in (Y or N):** Y
**Admin (Y or N):** N
**OS:** Ubuntu
**Browser/Version:** FFox/31
**Steps to Reproduce:**
1. Go to a scatter vis
2. Make a best fit line
3. Hover over a data point
4. Hover over the best fit line - the tooltip is missing
**Associated Image(s):** None
|
1.0
|
Best fit line tooltip disappears after hovering over a data point - **General description:**
Jim noticed this a while back. Essentially the tooltips are bound when a regression is created, but unbound whenever a regular data point/line is hovered over.
**live/dev/localhost:** Live
**iSENSE Version:** v5.5
**Logged in (Y or N):** Y
**Admin (Y or N):** N
**OS:** Ubuntu
**Browser/Version:** FFox/31
**Steps to Reproduce:**
1. Go to a scatter vis
2. Make a best fit line
3. Hover over a data point
4. Hover over the best fit line - the tooltip is missing
**Associated Image(s):** None
|
non_process
|
best fit line tooltip disappears after hovering over a data point general description jim noticed this a while back essentially the tooltips are bound when a regression is created but unbound whenever a regular data point line is hovered over live dev localhost live isense version logged in y or n y admin y or n n os ubuntu browser version ffox steps to reproduce go to a scatter vis make a best fit line hover over a data point hover over the best fit line the tooltip is missing associated image s none
| 0
|
21,744
| 30,258,392,207
|
IssuesEvent
|
2023-07-07 06:00:37
|
darktable-org/darktable
|
https://api.github.com/repos/darktable-org/darktable
|
closed
|
Graduated density module does opposite in 4.4.0, 4.4.1
|
understood: incomplete scope: image processing
|
### Describe the bug
Graduated density module, in 4.4.0 and 4.4.1, does the opposite of what it used to do. Photos that used it now show a lightening on the opposite side, instead of a darkening on the side it used to be.
### Steps to reproduce
Go to a photo that used the graduated density module before 4.4.0, you can visibly see the incorrect behaviour.
### Expected behavior
graduated density module should behave same way as pre 4.4.0
### Logfile | Screenshot | Screencast
_No response_
### Commit
_No response_
### Where did you install darktable from?
self compiled
### darktable version
4.4.1
### What OS are you using?
Linux
### What is the version of your OS?
Gentoo
### Describe your system?
_No response_
### Are you using OpenCL GPU in darktable?
I dont know
### If yes, what is the GPU card and driver?
_No response_
### Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
_No response_
|
1.0
|
Graduated density module does opposite in 4.4.0, 4.4.1 - ### Describe the bug
Graduated density module, in 4.4.0 and 4.4.1, does the opposite of what it used to do. Photos that used it now show a lightening on the opposite side, instead of a darkening on the side it used to be.
### Steps to reproduce
Go to a photo that used the graduated density module before 4.4.0, you can visibly see the incorrect behaviour.
### Expected behavior
graduated density module should behave same way as pre 4.4.0
### Logfile | Screenshot | Screencast
_No response_
### Commit
_No response_
### Where did you install darktable from?
self compiled
### darktable version
4.4.1
### What OS are you using?
Linux
### What is the version of your OS?
Gentoo
### Describe your system?
_No response_
### Are you using OpenCL GPU in darktable?
I dont know
### If yes, what is the GPU card and driver?
_No response_
### Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
_No response_
|
process
|
graduated density module does opposite in describe the bug graduated density module in and does the opposite of what it used to do photos that used it now show a lightening on the opposite side instead of a darkening on the side it used to be steps to reproduce go to a photo that used the graduated density module before you can visibly see the incorrect behaviour expected behavior graduated density module should behave same way as pre logfile screenshot screencast no response commit no response where did you install darktable from self compiled darktable version what os are you using linux what is the version of your os gentoo describe your system no response are you using opencl gpu in darktable i dont know if yes what is the gpu card and driver no response please provide additional context if applicable you can attach files too but might need to rename to txt or zip no response
| 1
|
9,768
| 12,750,135,335
|
IssuesEvent
|
2020-06-27 02:23:38
|
brucemiller/LaTeXML
|
https://api.github.com/repos/brucemiller/LaTeXML
|
closed
|
text subscript error
|
postprocessing regression
|
Hi. The following gives an error on the latest development version, but does not give an error on the release version or earlier versions. (But the release version gives other errors for me). It is called test.tex
`\documentclass{book}`
`\newcommand{\tx}[1]{\mbox{\emph{#1}}} % text in math`
`\begin{document}
$\tx{position}_2$
\end{document}`
`latexml --destination=artint.xml test.tex`
`latexmlpost --format=html5 artint`
Note that it does not give an error without html5
The error is
(MathML::Presentation processing...
Fatal:perl:die Perl died
Not an ARRAY reference at /Users/poole/LaTeXML/blib/script/../lib/LaTeXML/Post/MathML/Presentation.pm line 73.
In Post::MathML::Presentation[@0x7f8d4ae... ->associateNodeHook
1 fatal error
|
1.0
|
text subscript error - Hi. The following gives an error on the latest development version, but does not give an error on the release version or earlier versions. (But the release version gives other errors for me). It is called test.tex
`\documentclass{book}`
`\newcommand{\tx}[1]{\mbox{\emph{#1}}} % text in math`
`\begin{document}
$\tx{position}_2$
\end{document}`
`latexml --destination=artint.xml test.tex`
`latexmlpost --format=html5 artint`
Note that it does not give an error without html5
The error is
(MathML::Presentation processing...
Fatal:perl:die Perl died
Not an ARRAY reference at /Users/poole/LaTeXML/blib/script/../lib/LaTeXML/Post/MathML/Presentation.pm line 73.
In Post::MathML::Presentation[@0x7f8d4ae... ->associateNodeHook
1 fatal error
|
process
|
text subscript error hi the following gives an error on the latest development version but does not give an error on the release version or earlier versions but the release version gives other errors for me it is called test tex documentclass book newcommand tx mbox emph text in math begin document tx position end document latexml destination artint xml test tex latexmlpost format artint note that it does not give an error without the error is mathml presentation processing fatal perl die perl died not an array reference at users poole latexml blib script lib latexml post mathml presentation pm line in post mathml presentation associatenodehook fatal error
| 1
|
8,625
| 11,779,346,855
|
IssuesEvent
|
2020-03-16 17:51:09
|
googleapis/google-cloud-common
|
https://api.github.com/repos/googleapis/google-cloud-common
|
closed
|
Repos with CircleCI 1.0 configs
|
testing type: process
|
Nagmail from Circle prompted me to go look:
```bash
$ GITHUB_ORGANIZATION=GoogleCloudPlatform \
GITHUB_USER=tseaver GITHUB_ACCESS_TOKEN=<redacted> \
find-circle-yml
https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/php-docker/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/continuous-deployment-circle/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/slack-samples/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/js-data-cloud-datastore/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/android-docs-samples/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/stackdriver-trace-php-extension/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/stackdriver-debugger-php-extension/blob/master/circle.yml
```
and:
```bash
$ GITHUB_ORGANIZATION=googleapis \
GITHUB_USER=tseaver GITHUB_ACCESS_TOKEN=<redacted> \
find-circle-yml
https://github.com/googleapis/google-cloud-node-private/blob/master/circle.yml
```
|
1.0
|
Repos with CircleCI 1.0 configs - Nagmail from Circle prompted me to go look:
```bash
$ GITHUB_ORGANIZATION=GoogleCloudPlatform \
GITHUB_USER=tseaver GITHUB_ACCESS_TOKEN=<redacted> \
find-circle-yml
https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/php-docker/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/continuous-deployment-circle/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/slack-samples/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/js-data-cloud-datastore/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/android-docs-samples/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/stackdriver-trace-php-extension/blob/master/circle.yml
https://github.com/GoogleCloudPlatform/stackdriver-debugger-php-extension/blob/master/circle.yml
```
and:
```bash
$ GITHUB_ORGANIZATION=googleapis \
GITHUB_USER=tseaver GITHUB_ACCESS_TOKEN=<redacted> \
find-circle-yml
https://github.com/googleapis/google-cloud-node-private/blob/master/circle.yml
```
|
process
|
repos with circleci configs nagmail from circle prompted me to go look bash github organization googlecloudplatform github user tseaver github access token find circle yml and bash github organization googleapis github user tseaver github access token find circle yml
| 1
|
87,161
| 15,756,017,983
|
IssuesEvent
|
2021-03-31 02:47:04
|
ignatandrei/Presentations
|
https://api.github.com/repos/ignatandrei/Presentations
|
opened
|
CVE-2021-23358 (High) detected in underscore-1.10.2.tgz
|
security vulnerability
|
## CVE-2021-23358 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>underscore-1.10.2.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.10.2.tgz">https://registry.npmjs.org/underscore/-/underscore-1.10.2.tgz</a></p>
<p>Path to dependency file: Presentations/compile/package.json</p>
<p>Path to vulnerable library: Presentations/compile/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- folder-toc-0.3.1.tgz (Root Library)
- :x: **underscore-1.10.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Execution via the template function, particularly when a variable property is passed as an argument as it is not sanitized.
<p>Publish Date: 2021-03-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23358>CVE-2021-23358</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-2021-23358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358</a></p>
<p>Release Date: 2021-03-29</p>
<p>Fix Resolution: underscore - 1.12.1,1.13.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-2021-23358 (High) detected in underscore-1.10.2.tgz - ## CVE-2021-23358 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>underscore-1.10.2.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.10.2.tgz">https://registry.npmjs.org/underscore/-/underscore-1.10.2.tgz</a></p>
<p>Path to dependency file: Presentations/compile/package.json</p>
<p>Path to vulnerable library: Presentations/compile/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- folder-toc-0.3.1.tgz (Root Library)
- :x: **underscore-1.10.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Execution via the template function, particularly when a variable property is passed as an argument as it is not sanitized.
<p>Publish Date: 2021-03-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23358>CVE-2021-23358</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-2021-23358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358</a></p>
<p>Release Date: 2021-03-29</p>
<p>Fix Resolution: underscore - 1.12.1,1.13.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 underscore tgz cve high severity vulnerability vulnerable library underscore tgz javascript s functional programming helper library library home page a href path to dependency file presentations compile package json path to vulnerable library presentations compile node modules underscore package json dependency hierarchy folder toc tgz root library x underscore tgz vulnerable library found in base branch master vulnerability details the package underscore from and before from and before are vulnerable to arbitrary code execution via the template function particularly when a variable property is passed as an argument as it is not sanitized 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 underscore step up your open source security game with whitesource
| 0
|
2,967
| 5,960,702,981
|
IssuesEvent
|
2017-05-29 14:49:43
|
orbardugo/Hahot-Hameshulash
|
https://api.github.com/repos/orbardugo/Hahot-Hameshulash
|
closed
|
Create graph by C#
|
Development difficulty 3 help wanted in process priorty 3 requirement
|
**User Story:**
As the client of the app i would like to make a query, and see as a graph not only as list.
for example - see precentage of "בית חרדי" at jerusalem by female, from all females from Jerusalem.
**Test senarios:**
1.create the query and click on graph.
**Expected results:**
1. A "Cake Graph" or "Bar Graph" will appear on screen.
|
1.0
|
Create graph by C# - **User Story:**
As the client of the app i would like to make a query, and see as a graph not only as list.
for example - see precentage of "בית חרדי" at jerusalem by female, from all females from Jerusalem.
**Test senarios:**
1.create the query and click on graph.
**Expected results:**
1. A "Cake Graph" or "Bar Graph" will appear on screen.
|
process
|
create graph by c user story as the client of the app i would like to make a query and see as a graph not only as list for example see precentage of בית חרדי at jerusalem by female from all females from jerusalem test senarios create the query and click on graph expected results a cake graph or bar graph will appear on screen
| 1
|
272,504
| 20,748,248,682
|
IssuesEvent
|
2022-03-15 03:01:39
|
pola-rs/polars
|
https://api.github.com/repos/pola-rs/polars
|
closed
|
docs(node): pl.Series missing from docs
|
documentation node-js
|
#### Describe your bug.
pl.Series missing from docs. the code is all there, likely a misconfiguration causing it to not be generated.
#### What is the expected behavior?
pl.Series is in the docs.
|
1.0
|
docs(node): pl.Series missing from docs - #### Describe your bug.
pl.Series missing from docs. the code is all there, likely a misconfiguration causing it to not be generated.
#### What is the expected behavior?
pl.Series is in the docs.
|
non_process
|
docs node pl series missing from docs describe your bug pl series missing from docs the code is all there likely a misconfiguration causing it to not be generated what is the expected behavior pl series is in the docs
| 0
|
21,389
| 29,202,231,621
|
IssuesEvent
|
2023-05-21 00:37:36
|
devssa/onde-codar-em-salvador
|
https://api.github.com/repos/devssa/onde-codar-em-salvador
|
closed
|
[Hibrido / Bairro dos Funcionários, Minas Gerais, Brazil] PHP Developer (Júnior) na Coodesh
|
SALVADOR PHP MYSQL JAVASCRIPT FULL-STACK JUNIOR SQL STARTUP NODE.JS DOCKER POO REQUISITOS PROCESSOS GITHUB UMA QUALIDADE APIs SERVERLESS BI MANUTENÇÃO ALOCADO Stale
|
## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/desenvolvedor-php-junior-115803604?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>QUERO MEUS DIREITOS</strong> está em busca de <strong><ins>PHP Developer (Júnior)</ins></strong> para compor seu time!</p>
<p><br>Somos uma startup de impacto social. Democratizamos o acesso à justiça no Brasil. Estamos crescendo e fazendo coisas fantásticas. Precisamos de você para nos ajudar nessa missão. </p>
<p></p>
<p><strong>Responsabilidades</strong> (não se preocupe, você não estará sozinho =D):</p>
<ul>
<li>Desenvolvimento e manutenção de sistemas web;</li>
<li>Webscraping e RPA (hiperautomação de processos);</li>
<li>Produção e consumo de APIs;</li>
<li>Desenvolvimento de Dashboards.</li>
</ul>
<p></p>
<p><strong>Horário de trabalho (Presencial/Híbrido):</strong></p>
<ul>
<li>De segunda à sexta-feira;</li>
<li>Horário flexível;</li>
<li>Turno de 8 horas.</li>
</ul>
<p>Local do Trabalho: Belo Horizonte/Bairro Funcionários.</p>
## QUERO MEUS DIREITOS:
<p>A QUERO MEUS DIREITOS é uma Lawtech que está democratizando o acesso à justiça com qualidade, em todo o país, através de tecnologia de ponta. Já ajudamos milhares de pessoas a alcançar seus direitos.</p>
</p>
## Habilidades:
- PHP
- Javascript
- MySQL
## Local:
Bairro dos Funcionários, Minas Gerais, Brazil
## Requisitos:
- Conhecimentos em PHP;
- Ter alguma experiência com JavaScript;
- Ter bons fundamentos em algoritmos, estrutura de dados e POO;
- Proficiente em SQL (MySQL).
## Diferenciais:
- Node.js;
- BI;
- Docker;
- Serverless.
## Benefícios:
- Horários Flexíveis;
- Vale Alimentação/Refeição;
- Vale Transporte.
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [PHP Developer (Júnior) na QUERO MEUS DIREITOS](https://coodesh.com/vagas/desenvolvedor-php-junior-115803604?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Alocado
#### Regime
CLT
#### Categoria
Full-Stack
|
1.0
|
[Hibrido / Bairro dos Funcionários, Minas Gerais, Brazil] PHP Developer (Júnior) na Coodesh - ## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/desenvolvedor-php-junior-115803604?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>QUERO MEUS DIREITOS</strong> está em busca de <strong><ins>PHP Developer (Júnior)</ins></strong> para compor seu time!</p>
<p><br>Somos uma startup de impacto social. Democratizamos o acesso à justiça no Brasil. Estamos crescendo e fazendo coisas fantásticas. Precisamos de você para nos ajudar nessa missão. </p>
<p></p>
<p><strong>Responsabilidades</strong> (não se preocupe, você não estará sozinho =D):</p>
<ul>
<li>Desenvolvimento e manutenção de sistemas web;</li>
<li>Webscraping e RPA (hiperautomação de processos);</li>
<li>Produção e consumo de APIs;</li>
<li>Desenvolvimento de Dashboards.</li>
</ul>
<p></p>
<p><strong>Horário de trabalho (Presencial/Híbrido):</strong></p>
<ul>
<li>De segunda à sexta-feira;</li>
<li>Horário flexível;</li>
<li>Turno de 8 horas.</li>
</ul>
<p>Local do Trabalho: Belo Horizonte/Bairro Funcionários.</p>
## QUERO MEUS DIREITOS:
<p>A QUERO MEUS DIREITOS é uma Lawtech que está democratizando o acesso à justiça com qualidade, em todo o país, através de tecnologia de ponta. Já ajudamos milhares de pessoas a alcançar seus direitos.</p>
</p>
## Habilidades:
- PHP
- Javascript
- MySQL
## Local:
Bairro dos Funcionários, Minas Gerais, Brazil
## Requisitos:
- Conhecimentos em PHP;
- Ter alguma experiência com JavaScript;
- Ter bons fundamentos em algoritmos, estrutura de dados e POO;
- Proficiente em SQL (MySQL).
## Diferenciais:
- Node.js;
- BI;
- Docker;
- Serverless.
## Benefícios:
- Horários Flexíveis;
- Vale Alimentação/Refeição;
- Vale Transporte.
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [PHP Developer (Júnior) na QUERO MEUS DIREITOS](https://coodesh.com/vagas/desenvolvedor-php-junior-115803604?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Alocado
#### Regime
CLT
#### Categoria
Full-Stack
|
process
|
php developer júnior na coodesh descrição da vaga esta é uma vaga de um parceiro da plataforma coodesh ao candidatar se você terá acesso as informações completas sobre a empresa e benefícios fique atento ao redirecionamento que vai te levar para uma url com o pop up personalizado de candidatura 👋 a quero meus direitos está em busca de php developer júnior para compor seu time somos uma startup de impacto social democratizamos o acesso à justiça no brasil estamos crescendo e fazendo coisas fantásticas precisamos de você para nos ajudar nessa missão nbsp responsabilidades não se preocupe você não estará sozinho d desenvolvimento e manutenção de sistemas web webscraping e rpa hiperautomação de processos produção e consumo de apis desenvolvimento de dashboards horário de trabalho presencial híbrido de segunda à sexta feira horário flexível turno de horas local do trabalho belo horizonte bairro funcionários quero meus direitos a quero meus direitos é uma lawtech que está democratizando o acesso à justiça com qualidade em todo o país através de tecnologia de ponta já ajudamos milhares de pessoas a alcançar seus direitos habilidades php javascript mysql local bairro dos funcionários minas gerais brazil requisitos conhecimentos em php ter alguma experiência com javascript ter bons fundamentos em algoritmos estrutura de dados e poo proficiente em sql mysql diferenciais node js bi docker serverless benefícios horários flexíveis vale alimentação refeição vale transporte como se candidatar candidatar se exclusivamente através da plataforma coodesh no link a seguir após candidatar se via plataforma coodesh e validar o seu login você poderá acompanhar e receber todas as interações do processo por lá utilize a opção pedir feedback entre uma etapa e outra na vaga que se candidatou isso fará com que a pessoa recruiter responsável pelo processo na empresa receba a notificação labels alocação alocado regime clt categoria full stack
| 1
|
153,325
| 13,503,176,341
|
IssuesEvent
|
2020-09-13 12:18:45
|
ardnew/STUSB4500
|
https://api.github.com/repos/ardnew/STUSB4500
|
closed
|
Compiling and running the demo code in Arduino IDE 1.8.12 under Windows and MacOs
|
bug documentation
|
Hi there,
Awesome work what you did here and I would love to give it a spin but I seem to run into trouble :-) .
I am trying to compile the code for an Arduino UNO under Arduino IDE 1.8.12 on a windows 10 pc but also on MacOs Catalina with same errors .
If I try to compile the code I get first :
'class HardwareSerial' has no member named 'printf'; did you mean 'print'?
If I change all "Serial.printf" to Serial.print I get this :
C:\Users\......\arduino\hardware\avr\1.8.3\cores\arduino/Print.h:72:12: note: conversion of argument 2 would be ill-formed:
C:\Users\......\arduino\hardware\avr\1.8.3\cores\arduino\hardware\avr\1.8.3\cores\arduino/Print.h:73:12: note: candidate: size_t Print::print(long unsigned int, int) <near match>
size_t print(unsigned long, int = DEC);
^~~~~
C:\Users\......\arduino\hardware\avr\1.8.3\cores\arduino\hardware\avr\1.8.3\cores\arduino/Print.h:73:12: note: conversion of argument 2 would be ill-formed:
exit status 1
no matching function for call to 'HardwareSerial::print(const char [17], size_t&, uint16_t&, uint16_t&)'
If I try to split and print one by one the PDO number, PDO voltage and PDO current I get the same error as above .
Can you please point me in the right direction?
I have a plethora of atmel boards in my hands and I can use ATSAMD based boards also but I am unsure how to go about to get the example to compile :-D .
Thank you ,
Misujr
|
1.0
|
Compiling and running the demo code in Arduino IDE 1.8.12 under Windows and MacOs - Hi there,
Awesome work what you did here and I would love to give it a spin but I seem to run into trouble :-) .
I am trying to compile the code for an Arduino UNO under Arduino IDE 1.8.12 on a windows 10 pc but also on MacOs Catalina with same errors .
If I try to compile the code I get first :
'class HardwareSerial' has no member named 'printf'; did you mean 'print'?
If I change all "Serial.printf" to Serial.print I get this :
C:\Users\......\arduino\hardware\avr\1.8.3\cores\arduino/Print.h:72:12: note: conversion of argument 2 would be ill-formed:
C:\Users\......\arduino\hardware\avr\1.8.3\cores\arduino\hardware\avr\1.8.3\cores\arduino/Print.h:73:12: note: candidate: size_t Print::print(long unsigned int, int) <near match>
size_t print(unsigned long, int = DEC);
^~~~~
C:\Users\......\arduino\hardware\avr\1.8.3\cores\arduino\hardware\avr\1.8.3\cores\arduino/Print.h:73:12: note: conversion of argument 2 would be ill-formed:
exit status 1
no matching function for call to 'HardwareSerial::print(const char [17], size_t&, uint16_t&, uint16_t&)'
If I try to split and print one by one the PDO number, PDO voltage and PDO current I get the same error as above .
Can you please point me in the right direction?
I have a plethora of atmel boards in my hands and I can use ATSAMD based boards also but I am unsure how to go about to get the example to compile :-D .
Thank you ,
Misujr
|
non_process
|
compiling and running the demo code in arduino ide under windows and macos hi there awesome work what you did here and i would love to give it a spin but i seem to run into trouble i am trying to compile the code for an arduino uno under arduino ide on a windows pc but also on macos catalina with same errors if i try to compile the code i get first class hardwareserial has no member named printf did you mean print if i change all serial printf to serial print i get this c users arduino hardware avr cores arduino print h note conversion of argument would be ill formed c users arduino hardware avr cores arduino hardware avr cores arduino print h note candidate size t print print long unsigned int int size t print unsigned long int dec c users arduino hardware avr cores arduino hardware avr cores arduino print h note conversion of argument would be ill formed exit status no matching function for call to hardwareserial print const char size t t t if i try to split and print one by one the pdo number pdo voltage and pdo current i get the same error as above can you please point me in the right direction i have a plethora of atmel boards in my hands and i can use atsamd based boards also but i am unsure how to go about to get the example to compile d thank you misujr
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.