Technical Debt and it Types Datasets
Collection
24 items
•
Updated
•
1
Unnamed: 0
int64 0
829k
| id
float64 2.5B
32B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
73
| repo_url
stringlengths 36
102
| action
stringclasses 3
values | title
stringlengths 5
229
| labels
stringlengths 4
262
| body
stringlengths 17
187k
| index
stringclasses 6
values | text_combine
stringlengths 97
187k
| label
stringclasses 2
values | text
stringlengths 96
174k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
640
| 11,473,682,428
|
IssuesEvent
|
2020-02-10 00:40:09
|
kymr/daily-study
|
https://api.github.com/repos/kymr/daily-study
|
opened
|
방향에 대한 고민
|
culture people
|
+ 업무 변화 필요
1. 희망회로를 돌리기 위한 전략
2. 컨텍스트를 주고 스스로 계획하고 행동하도록
3. 건설적인 피드백
+ 방향
- 주어진 일 외에 무엇을 발의하고 할 수 있는가
+ 전략
+ 동인
+ 채용
|
1.0
|
방향에 대한 고민 - + 업무 변화 필요
1. 희망회로를 돌리기 위한 전략
2. 컨텍스트를 주고 스스로 계획하고 행동하도록
3. 건설적인 피드백
+ 방향
- 주어진 일 외에 무엇을 발의하고 할 수 있는가
+ 전략
+ 동인
+ 채용
|
people
|
방향에 대한 고민 업무 변화 필요 희망회로를 돌리기 위한 전략 컨텍스트를 주고 스스로 계획하고 행동하도록 건설적인 피드백 방향 주어진 일 외에 무엇을 발의하고 할 수 있는가 전략 동인 채용
| 1
|
593
| 10,470,875,836
|
IssuesEvent
|
2019-09-23 06:00:05
|
OfficeDev/office-ui-fabric-react
|
https://api.github.com/repos/OfficeDev/office-ui-fabric-react
|
closed
|
reopen: People Picker dropdown list is not being announced in Android
|
Area: Accessibility Component: PeoplePicker Needs: Author Feedback Needs: Triage :mag: Status: No Recent Activity
|
This is repro in Android app and Win32 apps.
#### Codepen demonstrating the issue
https://developer.microsoft.com/en-us/fabric#/controls/web/peoplepicker
#### Actual behavior:
When users navigate with a physical keyboard up and down, voiceover is silent.
#### Expected behavior:
When users navigate with a physical keyboard up and down on the dropdown available list, voiceover should announce the name of the person.
### Documentation describing expected behavior
|
1.0
|
reopen: People Picker dropdown list is not being announced in Android - This is repro in Android app and Win32 apps.
#### Codepen demonstrating the issue
https://developer.microsoft.com/en-us/fabric#/controls/web/peoplepicker
#### Actual behavior:
When users navigate with a physical keyboard up and down, voiceover is silent.
#### Expected behavior:
When users navigate with a physical keyboard up and down on the dropdown available list, voiceover should announce the name of the person.
### Documentation describing expected behavior
|
people
|
reopen people picker dropdown list is not being announced in android this is repro in android app and apps codepen demonstrating the issue actual behavior when users navigate with a physical keyboard up and down voiceover is silent expected behavior when users navigate with a physical keyboard up and down on the dropdown available list voiceover should announce the name of the person documentation describing expected behavior
| 1
|
465
| 8,353,428,445
|
IssuesEvent
|
2018-10-02 09:59:52
|
allenleein/brains
|
https://api.github.com/repos/allenleein/brains
|
closed
|
An Entire Community Got Together to Rape a Child: India Recoils at Girls Assault
|
People
|
<b>‘An Entire Community Got Together to Rape a Child’: India Recoils at Girl’s Assault</b><br>
NEW DELHI — For months, the police say, a group of men took turns raping an 11-year-old girl. In the gated community in Chennai, India, where the girl lived with her parents, the men gave her soft drinks laced with drugs, the police said.<br>
<br>
via Pocket https://ift.tt/2msf76Q<br>
<br>
July 21, 2018 at 01:12PM
|
1.0
|
An Entire Community Got Together to Rape a Child: India Recoils at Girls Assault - <b>‘An Entire Community Got Together to Rape a Child’: India Recoils at Girl’s Assault</b><br>
NEW DELHI — For months, the police say, a group of men took turns raping an 11-year-old girl. In the gated community in Chennai, India, where the girl lived with her parents, the men gave her soft drinks laced with drugs, the police said.<br>
<br>
via Pocket https://ift.tt/2msf76Q<br>
<br>
July 21, 2018 at 01:12PM
|
people
|
an entire community got together to rape a child india recoils at girls assault lsquo an entire community got together to rape a child rsquo india recoils at girl rsquo s assault new delhi mdash for months the police say a group of men took turns raping an year old girl in the gated community in chennai india where the girl lived with her parents the men gave her soft drinks laced with drugs the police said via pocket july at
| 1
|
186,751
| 15,083,158,078
|
IssuesEvent
|
2021-02-05 15:28:56
|
gianlucadetommaso/volatile
|
https://api.github.com/repos/gianlucadetommaso/volatile
|
closed
|
Do you have plan to provide a interact jupyter notebook to dive into the model construction ?
|
documentation
|
The tensorflow official website provide a example about multilevel modeling
https://www.tensorflow.org/probability/examples/Multilevel_Modeling_Primer
it interpret its components by visualize them separately.
I think you should also provide a correspondence about your model.
Let it to validate your model construction and change to adapt their own applications.
Even, if you have a guide about the feature selection and aggregate method
in your model with visualize is more bravo.
|
1.0
|
Do you have plan to provide a interact jupyter notebook to dive into the model construction ? - The tensorflow official website provide a example about multilevel modeling
https://www.tensorflow.org/probability/examples/Multilevel_Modeling_Primer
it interpret its components by visualize them separately.
I think you should also provide a correspondence about your model.
Let it to validate your model construction and change to adapt their own applications.
Even, if you have a guide about the feature selection and aggregate method
in your model with visualize is more bravo.
|
non_people
|
do you have plan to provide a interact jupyter notebook to dive into the model construction the tensorflow official website provide a example about multilevel modeling it interpret its components by visualize them separately i think you should also provide a correspondence about your model let it to validate your model construction and change to adapt their own applications even if you have a guide about the feature selection and aggregate method in your model with visualize is more bravo
| 0
|
133,446
| 29,179,316,711
|
IssuesEvent
|
2023-05-19 10:30:08
|
HarounAlarabi/Coursework-Planner
|
https://api.github.com/repos/HarounAlarabi/Coursework-Planner
|
opened
|
[TECH ED] Codewars
|
🏕 Priority Mandatory 📅 Week 4 📅 JS3 🎯 Topic Code Review 🎯 Topic Problem-Solving 🎯 Topic Programming Fundamentals 🎯 Topic Requirements 🎯 Topic Time Management
|
From Module-JS3 created by [Dedekind561](https://github.com/Dedekind561): CodeYourFuture/Module-JS3#19
### Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
### Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on [the CodeYourFuture account](https://www.codewars.com/users/CodeYourFuture/authored_collections).
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
### Maximum time in hours (Tech has max 16 per week total)
1
### How to get help
- Join the #cyf-codewars Slack channel
- Read the [CYF Codewars docs](https://docs.codeyourfuture.io/leaders/running-the-course/codewars)
- Read [Codewars advice from CYFers](https://docs.codeyourfuture.io/leaders/running-the-course/codewars/codewars-advice-from-cyfers)
- Read [Codewars advice from mentors](https://docs.codeyourfuture.io/leaders/running-the-course/codewars/codewars-advice-from-mentors)
Remember, after 20 minutes, take a break.
### How to submit
Your codewars progress is tracked automatically and is available on the public API. You don't need to submit it.
### How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
### Anything else?
_No response_
|
1.0
|
[TECH ED] Codewars - From Module-JS3 created by [Dedekind561](https://github.com/Dedekind561): CodeYourFuture/Module-JS3#19
### Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
### Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on [the CodeYourFuture account](https://www.codewars.com/users/CodeYourFuture/authored_collections).
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
### Maximum time in hours (Tech has max 16 per week total)
1
### How to get help
- Join the #cyf-codewars Slack channel
- Read the [CYF Codewars docs](https://docs.codeyourfuture.io/leaders/running-the-course/codewars)
- Read [Codewars advice from CYFers](https://docs.codeyourfuture.io/leaders/running-the-course/codewars/codewars-advice-from-cyfers)
- Read [Codewars advice from mentors](https://docs.codeyourfuture.io/leaders/running-the-course/codewars/codewars-advice-from-mentors)
Remember, after 20 minutes, take a break.
### How to submit
Your codewars progress is tracked automatically and is available on the public API. You don't need to submit it.
### How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
### Anything else?
_No response_
|
non_people
|
codewars from module created by codeyourfuture module link to the coursework why are we doing this every week you need to complete at least three kata spend at least minutes three times a week on your kata workout find the collection for this week on take some time to check your levels before you are accepted on to a final project on the developer track you need to complete the final projects collection and reach a level kyu in codewars are you on track to reach this standard have you run a study group to work on kata have you reached out on the cyf codewars channel what is your plan to meet this goal maximum time in hours tech has max per week total how to get help join the cyf codewars slack channel read the read read remember after minutes take a break how to submit your codewars progress is tracked automatically and is available on the public api you don t need to submit it how to review once you have completed your kata look at the other solutions in the solutions view consider how many different approaches there are anything else no response
| 0
|
575
| 10,130,756,480
|
IssuesEvent
|
2019-08-01 17:46:17
|
openopps/openopps-platform
|
https://api.github.com/repos/openopps/openopps-platform
|
closed
|
As an administrator, I want the People search to be weighted to better allow searching on multiple fields.
|
Enhancement People
|
People search searches on name, title, agency, and location. Upgrade to work better for multiple search fields. Determine appropriate weighting if multiple search options are entered (and search vs or?)
Entered per 3/6/18 bug bash
|
1.0
|
As an administrator, I want the People search to be weighted to better allow searching on multiple fields. - People search searches on name, title, agency, and location. Upgrade to work better for multiple search fields. Determine appropriate weighting if multiple search options are entered (and search vs or?)
Entered per 3/6/18 bug bash
|
people
|
as an administrator i want the people search to be weighted to better allow searching on multiple fields people search searches on name title agency and location upgrade to work better for multiple search fields determine appropriate weighting if multiple search options are entered and search vs or entered per bug bash
| 1
|
140,225
| 5,398,870,304
|
IssuesEvent
|
2017-02-27 17:59:34
|
18F/web-design-standards
|
https://api.github.com/repos/18F/web-design-standards
|
closed
|
Move to WDS site -> Federalist
|
[Priority] Major [Skill] DevOps [Type] Maintenance
|
## Description
In order to prepare for the Cloud.gov contract expiring and realize cost savings and dogfood with another 18f project, we're going to move to Federalist for hosting.
## Steps to reproduce the issue
- [ ] Copy and paste website (I don't know what is actually needed to be done but J&S do)
- [ ] Wipe hands on pants, receive bacon
|
1.0
|
Move to WDS site -> Federalist - ## Description
In order to prepare for the Cloud.gov contract expiring and realize cost savings and dogfood with another 18f project, we're going to move to Federalist for hosting.
## Steps to reproduce the issue
- [ ] Copy and paste website (I don't know what is actually needed to be done but J&S do)
- [ ] Wipe hands on pants, receive bacon
|
non_people
|
move to wds site federalist description in order to prepare for the cloud gov contract expiring and realize cost savings and dogfood with another project we re going to move to federalist for hosting steps to reproduce the issue copy and paste website i don t know what is actually needed to be done but j s do wipe hands on pants receive bacon
| 0
|
954
| 21,039,733,225
|
IssuesEvent
|
2022-03-31 11:10:36
|
AtB-AS/mittatb-app
|
https://api.github.com/repos/AtB-AS/mittatb-app
|
closed
|
Tilbakemeldingskomponent: Lage tabeller/grafer
|
PI: Innhøsting feedback :people_holding_hands: Teaminitiativ
|
# Mål
Kunne tydeliggjøre høstingen fra tilbakemeldingskomponenten til å finne svar på spørsmål som vi lurer på.
# Avhengighet fra Plattform:
Eksport av hele collection kjører nå hver natt til BigQuery: https://github.com/AtB-AS/team-platform/issues/104
# ToDo
- [ ] Vi må avklarerhvordan samspillet med å få opp grafer/spørringer skal være.
- [ ] Kundevendts behov:
- [ ] Markedsinnsikts behov:
|
1.0
|
Tilbakemeldingskomponent: Lage tabeller/grafer - # Mål
Kunne tydeliggjøre høstingen fra tilbakemeldingskomponenten til å finne svar på spørsmål som vi lurer på.
# Avhengighet fra Plattform:
Eksport av hele collection kjører nå hver natt til BigQuery: https://github.com/AtB-AS/team-platform/issues/104
# ToDo
- [ ] Vi må avklarerhvordan samspillet med å få opp grafer/spørringer skal være.
- [ ] Kundevendts behov:
- [ ] Markedsinnsikts behov:
|
people
|
tilbakemeldingskomponent lage tabeller grafer mål kunne tydeliggjøre høstingen fra tilbakemeldingskomponenten til å finne svar på spørsmål som vi lurer på avhengighet fra plattform eksport av hele collection kjører nå hver natt til bigquery todo vi må avklarerhvordan samspillet med å få opp grafer spørringer skal være kundevendts behov markedsinnsikts behov
| 1
|
766
| 14,085,940,472
|
IssuesEvent
|
2020-11-05 02:20:53
|
hackforla/civic-opportunity
|
https://api.github.com/repos/hackforla/civic-opportunity
|
closed
|
Post Marketing Director Position on Volunteer Match/Linkedin
|
people: 1 role: product management
|
### Overview
This description will be used for posting on LinkedIn.
### Action Items
- [x] Ray
- [x] determine which is most current
- [x] Bonnie
- [x] Get access to volunteer match
- [x] Snigdha
- [x] Document this process (below in the issue).
- [x] post on volunteer match
- [x] review with Bonnie
- [x] figure out how to make it post on linkedin
- [x] edit the Marketing Role Description doc, Volunteer Match section to be formatted for Volunteer Match specifically, including any constraints.
- [x] Update the Marketing Role Descriptions doc with the updated information from Volunteer Match
### Resources/Instructions
[Writeup in issue #3](https://github.com/hackforla/civic-opportunity/issues/3#issuecomment-663922272)
[Marketing Role descriptions](https://docs.google.com/document/d/1SQvBa8ctXJO78_ryiY5ejIBE3V7PDfA5n9A66j-3Ars/edit#heading=h.w3j8f3rqex71)
[instructions for adding job posting to linkedin from volunteer match](https://vmhelp.zendesk.com/hc/en-us/articles/215343787-Connecting-your-opportunities-to-LinkedIn)
[Volunteer Match Job Post constraints](https://docs.google.com/document/d/16EKuUwxIk1v5gVCPs-R21I5h7yCZKfAdoTCTIZnAtGQ/edit?usp=sharing)
|
1.0
|
Post Marketing Director Position on Volunteer Match/Linkedin - ### Overview
This description will be used for posting on LinkedIn.
### Action Items
- [x] Ray
- [x] determine which is most current
- [x] Bonnie
- [x] Get access to volunteer match
- [x] Snigdha
- [x] Document this process (below in the issue).
- [x] post on volunteer match
- [x] review with Bonnie
- [x] figure out how to make it post on linkedin
- [x] edit the Marketing Role Description doc, Volunteer Match section to be formatted for Volunteer Match specifically, including any constraints.
- [x] Update the Marketing Role Descriptions doc with the updated information from Volunteer Match
### Resources/Instructions
[Writeup in issue #3](https://github.com/hackforla/civic-opportunity/issues/3#issuecomment-663922272)
[Marketing Role descriptions](https://docs.google.com/document/d/1SQvBa8ctXJO78_ryiY5ejIBE3V7PDfA5n9A66j-3Ars/edit#heading=h.w3j8f3rqex71)
[instructions for adding job posting to linkedin from volunteer match](https://vmhelp.zendesk.com/hc/en-us/articles/215343787-Connecting-your-opportunities-to-LinkedIn)
[Volunteer Match Job Post constraints](https://docs.google.com/document/d/16EKuUwxIk1v5gVCPs-R21I5h7yCZKfAdoTCTIZnAtGQ/edit?usp=sharing)
|
people
|
post marketing director position on volunteer match linkedin overview this description will be used for posting on linkedin action items ray determine which is most current bonnie get access to volunteer match snigdha document this process below in the issue post on volunteer match review with bonnie figure out how to make it post on linkedin edit the marketing role description doc volunteer match section to be formatted for volunteer match specifically including any constraints update the marketing role descriptions doc with the updated information from volunteer match resources instructions
| 1
|
1,188
| 30,851,772,440
|
IssuesEvent
|
2023-08-02 17:17:47
|
jpleasants/plesk3
|
https://api.github.com/repos/jpleasants/plesk3
|
opened
|
🛑 Peoples Medical Care is down
|
status peoples-medical-care
|
In [`e33af9d`](https://github.com/jpleasants/plesk3/commit/e33af9d1b5c6ec3f55d1a42ad218708d20f671c1
), Peoples Medical Care (https://peoplesmedicalcare.org) was **down**:
- HTTP code: 0
- Response time: 0 ms
|
1.0
|
🛑 Peoples Medical Care is down - In [`e33af9d`](https://github.com/jpleasants/plesk3/commit/e33af9d1b5c6ec3f55d1a42ad218708d20f671c1
), Peoples Medical Care (https://peoplesmedicalcare.org) was **down**:
- HTTP code: 0
- Response time: 0 ms
|
people
|
🛑 peoples medical care is down in peoples medical care was down http code response time ms
| 1
|
391
| 2,496,218,966
|
IssuesEvent
|
2015-01-06 17:54:07
|
nlbdev/nordic-epub3-dtbook-migrator
|
https://api.github.com/repos/nlbdev/nordic-epub3-dtbook-migrator
|
opened
|
Check that "mailto:" links are handled correctly when converting to DTBook
|
0 - Low priority enhancement epub3-to-dtbook
|
`external="true"` should be added to links when converting mailto addresses.
By default we don't even keep the links after conversion, so this is a pretty low-priority issue. But it's worth getting into the code so that a possible future "generic DTBook" fork can support this properly.
|
1.0
|
Check that "mailto:" links are handled correctly when converting to DTBook - `external="true"` should be added to links when converting mailto addresses.
By default we don't even keep the links after conversion, so this is a pretty low-priority issue. But it's worth getting into the code so that a possible future "generic DTBook" fork can support this properly.
|
non_people
|
check that mailto links are handled correctly when converting to dtbook external true should be added to links when converting mailto addresses by default we don t even keep the links after conversion so this is a pretty low priority issue but it s worth getting into the code so that a possible future generic dtbook fork can support this properly
| 0
|
30,926
| 25,176,112,691
|
IssuesEvent
|
2022-11-11 09:24:25
|
airyhq/airy
|
https://api.github.com/repos/airyhq/airy
|
closed
|
Update the CLI to have the Google provider
|
infrastructure cli
|
The Airy CLI needs to deploy a new Airy instance on Google using:
```
airy create --provider gcp
```
|
1.0
|
Update the CLI to have the Google provider - The Airy CLI needs to deploy a new Airy instance on Google using:
```
airy create --provider gcp
```
|
non_people
|
update the cli to have the google provider the airy cli needs to deploy a new airy instance on google using airy create provider gcp
| 0
|
25,421
| 11,171,418,689
|
IssuesEvent
|
2019-12-28 19:35:09
|
eldorplus/conception-website
|
https://api.github.com/repos/eldorplus/conception-website
|
opened
|
WS-2019-0183 (Medium) detected in lodash.defaultsdeep-4.3.2.tgz
|
security vulnerability
|
## WS-2019-0183 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash.defaultsdeep-4.3.2.tgz</b></p></summary>
<p>The lodash method `_.defaultsDeep` exported as a module.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash.defaultsdeep/-/lodash.defaultsdeep-4.3.2.tgz">https://registry.npmjs.org/lodash.defaultsdeep/-/lodash.defaultsdeep-4.3.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/conception-website/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/conception-website/node_modules/lodash.defaultsdeep/package.json</p>
<p>
Dependency Hierarchy:
- nightwatch-0.9.21.tgz (Root Library)
- :x: **lodash.defaultsdeep-4.3.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/eldorplus/conception-website/commit/d01989566d2a70e542b08bc943c5de9d223ce39d">d01989566d2a70e542b08bc943c5de9d223ce39d</a></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>
lodash.defaultsdeep before 4.6.1 is vulnerable to prototype pollution. The function mergeWith() may allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2019-08-14
<p>URL: <a href=https://github.com/lodash/lodash/compare/4.6.0...4.6.1>WS-2019-0183</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1068">https://www.npmjs.com/advisories/1068</a></p>
<p>Release Date: 2019-08-14</p>
<p>Fix Resolution: 4.6.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
|
WS-2019-0183 (Medium) detected in lodash.defaultsdeep-4.3.2.tgz - ## WS-2019-0183 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash.defaultsdeep-4.3.2.tgz</b></p></summary>
<p>The lodash method `_.defaultsDeep` exported as a module.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash.defaultsdeep/-/lodash.defaultsdeep-4.3.2.tgz">https://registry.npmjs.org/lodash.defaultsdeep/-/lodash.defaultsdeep-4.3.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/conception-website/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/conception-website/node_modules/lodash.defaultsdeep/package.json</p>
<p>
Dependency Hierarchy:
- nightwatch-0.9.21.tgz (Root Library)
- :x: **lodash.defaultsdeep-4.3.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/eldorplus/conception-website/commit/d01989566d2a70e542b08bc943c5de9d223ce39d">d01989566d2a70e542b08bc943c5de9d223ce39d</a></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>
lodash.defaultsdeep before 4.6.1 is vulnerable to prototype pollution. The function mergeWith() may allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2019-08-14
<p>URL: <a href=https://github.com/lodash/lodash/compare/4.6.0...4.6.1>WS-2019-0183</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1068">https://www.npmjs.com/advisories/1068</a></p>
<p>Release Date: 2019-08-14</p>
<p>Fix Resolution: 4.6.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_people
|
ws medium detected in lodash defaultsdeep tgz ws medium severity vulnerability vulnerable library lodash defaultsdeep tgz the lodash method defaultsdeep exported as a module library home page a href path to dependency file tmp ws scm conception website package json path to vulnerable library tmp ws scm conception website node modules lodash defaultsdeep package json dependency hierarchy nightwatch tgz root library x lodash defaultsdeep tgz vulnerable library found in head commit a href vulnerability details lodash defaultsdeep before is vulnerable to prototype pollution the function mergewith may allow a malicious user to modify the prototype of object via constructor prototype causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
645,773
| 21,014,922,196
|
IssuesEvent
|
2022-03-30 10:05:35
|
GoogleCloudPlatform/python-docs-samples
|
https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples
|
reopened
|
appengine.flexible.storage.main_test: test_upload failed
|
priority: p1 type: bug api: appengine samples flakybot: issue flakybot: flaky
|
Note: #6724 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 3b6d797140afa6ca900a1e38a554795bfe800368
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/7e7321f5-302f-441b-b01b-0047fd05b625), [Sponge](http://sponge2/7e7321f5-302f-441b-b01b-0047fd05b625)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/appengine/flexible/storage/main_test.py", line 46, in blob_name
blob.delete()
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/blob.py", line 790, in delete
retry=retry,
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/bucket.py", line 1632, in delete_blob
_target_object=None,
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/client.py", line 677, in _delete_resource
_target_object=_target_object,
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/_http.py", line 80, in api_request
return call()
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/_http/__init__.py", line 480, in api_request
raise exceptions.from_http_response(response)
google.api_core.exceptions.NotFound: 404 DELETE https://storage.googleapis.com/storage/v1/b/python-docs-samples-tests-public/o/gae-flex-storage-76ec3976-87b9-4e57-8929-1f2155e3262f?prettyPrint=false: No such object: python-docs-samples-tests-public/gae-flex-storage-76ec3976-87b9-4e57-8929-1f2155e3262f</pre></details>
|
1.0
|
appengine.flexible.storage.main_test: test_upload failed - Note: #6724 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 3b6d797140afa6ca900a1e38a554795bfe800368
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/7e7321f5-302f-441b-b01b-0047fd05b625), [Sponge](http://sponge2/7e7321f5-302f-441b-b01b-0047fd05b625)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/appengine/flexible/storage/main_test.py", line 46, in blob_name
blob.delete()
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/blob.py", line 790, in delete
retry=retry,
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/bucket.py", line 1632, in delete_blob
_target_object=None,
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/client.py", line 677, in _delete_resource
_target_object=_target_object,
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/_http.py", line 80, in api_request
return call()
File "/workspace/appengine/flexible/storage/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/_http/__init__.py", line 480, in api_request
raise exceptions.from_http_response(response)
google.api_core.exceptions.NotFound: 404 DELETE https://storage.googleapis.com/storage/v1/b/python-docs-samples-tests-public/o/gae-flex-storage-76ec3976-87b9-4e57-8929-1f2155e3262f?prettyPrint=false: No such object: python-docs-samples-tests-public/gae-flex-storage-76ec3976-87b9-4e57-8929-1f2155e3262f</pre></details>
|
non_people
|
appengine flexible storage main test test upload failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output traceback most recent call last file workspace appengine flexible storage main test py line in blob name blob delete file workspace appengine flexible storage nox py lib site packages google cloud storage blob py line in delete retry retry file workspace appengine flexible storage nox py lib site packages google cloud storage bucket py line in delete blob target object none file workspace appengine flexible storage nox py lib site packages google cloud storage client py line in delete resource target object target object file workspace appengine flexible storage nox py lib site packages google cloud storage http py line in api request return call file workspace appengine flexible storage nox py lib site packages google cloud http init py line in api request raise exceptions from http response response google api core exceptions notfound delete no such object python docs samples tests public gae flex storage
| 0
|
823,806
| 31,034,482,268
|
IssuesEvent
|
2023-08-10 14:26:05
|
code4romania/bursa-binelui
|
https://api.github.com/repos/code4romania/bursa-binelui
|
closed
|
[Admin ONG] Edit domains deletes all domains from Organization profile
|
high-priority :fire:
|
If I click on Edit for the Domains field and I select a different domain and click Save then all domains disappear.
If I repeat the action after they dissappeared and select new domains, nothing happens, nothing is displayed.
|
1.0
|
[Admin ONG] Edit domains deletes all domains from Organization profile - If I click on Edit for the Domains field and I select a different domain and click Save then all domains disappear.
If I repeat the action after they dissappeared and select new domains, nothing happens, nothing is displayed.
|
non_people
|
edit domains deletes all domains from organization profile if i click on edit for the domains field and i select a different domain and click save then all domains disappear if i repeat the action after they dissappeared and select new domains nothing happens nothing is displayed
| 0
|
22,833
| 15,554,117,217
|
IssuesEvent
|
2021-03-16 03:03:33
|
astropy/photutils
|
https://api.github.com/repos/astropy/photutils
|
closed
|
MNT: Rename default branch from master to main
|
infrastructure
|
Please rename your default branch from `master` to `main` as part of astropy/astropy-project#151 , preferably by 2021-03-22. Also a friendly reminder to check documentation, workflows, etc., and update them accordingly. Please don't forget to communicate this change to your users and stakeholders. To summarize:
- [x] Rename branch from `master` to `main`, preferably by 2021-03-22.
- [x] Update documentation, workflows, etc., accordingly. -- See #1178
- [ ] Communicate this change to your users and stakeholders.
Once this is taken care of, you may close this issue.
*This is an automated issue. If this is opened in error, please let @pllim know!*
|
1.0
|
MNT: Rename default branch from master to main - Please rename your default branch from `master` to `main` as part of astropy/astropy-project#151 , preferably by 2021-03-22. Also a friendly reminder to check documentation, workflows, etc., and update them accordingly. Please don't forget to communicate this change to your users and stakeholders. To summarize:
- [x] Rename branch from `master` to `main`, preferably by 2021-03-22.
- [x] Update documentation, workflows, etc., accordingly. -- See #1178
- [ ] Communicate this change to your users and stakeholders.
Once this is taken care of, you may close this issue.
*This is an automated issue. If this is opened in error, please let @pllim know!*
|
non_people
|
mnt rename default branch from master to main please rename your default branch from master to main as part of astropy astropy project preferably by also a friendly reminder to check documentation workflows etc and update them accordingly please don t forget to communicate this change to your users and stakeholders to summarize rename branch from master to main preferably by update documentation workflows etc accordingly see communicate this change to your users and stakeholders once this is taken care of you may close this issue this is an automated issue if this is opened in error please let pllim know
| 0
|
762,239
| 26,712,367,689
|
IssuesEvent
|
2023-01-28 03:19:11
|
JackDotJS/minecraft-asset-extractor
|
https://api.github.com/repos/JackDotJS/minecraft-asset-extractor
|
closed
|
Ability to extract assets from the Minecraft jars
|
📁 category: new features ⚙️ complexity: 4 ⚠ priority: 4 🔁 status: in-progress legacy
|
Adds an option to extract the default resource pack assets from the Minecraft jar file. Will likely require major changes to the UI as well as the extractor, possibly even just a separate menu and internal method for extracting files.
|
1.0
|
Ability to extract assets from the Minecraft jars - Adds an option to extract the default resource pack assets from the Minecraft jar file. Will likely require major changes to the UI as well as the extractor, possibly even just a separate menu and internal method for extracting files.
|
non_people
|
ability to extract assets from the minecraft jars adds an option to extract the default resource pack assets from the minecraft jar file will likely require major changes to the ui as well as the extractor possibly even just a separate menu and internal method for extracting files
| 0
|
152
| 3,696,992,895
|
IssuesEvent
|
2016-02-27 10:39:43
|
friendlycode/strategic_plan
|
https://api.github.com/repos/friendlycode/strategic_plan
|
opened
|
Community Partners
|
Partnerships People & Partnerships
|
Develop a list of organizations or potential partners from CfA’s focus areas (Health, Safety and Justice, Economic Development, Communications and Engagement) with whom a mutually beneficially relationship can be developed
|
1.0
|
Community Partners - Develop a list of organizations or potential partners from CfA’s focus areas (Health, Safety and Justice, Economic Development, Communications and Engagement) with whom a mutually beneficially relationship can be developed
|
people
|
community partners develop a list of organizations or potential partners from cfa’s focus areas health safety and justice economic development communications and engagement with whom a mutually beneficially relationship can be developed
| 1
|
806
| 15,027,206,373
|
IssuesEvent
|
2021-02-02 00:15:59
|
Automattic/wp-calypso
|
https://api.github.com/repos/Automattic/wp-calypso
|
closed
|
Update top level wp-admin appearance link to redirect to Calypso
|
Me OSS Citizen People Management [Closed] Won't Fix [Type] Task
|
Update the wp-admin Appearance links to redirect to Calypso.
<ul>
<li>
Appearance links to Themes
<ul>
<li>
Themes <p><code>Old: https://example.wordpress.com/wp-admin/themes.php</code></p>
<p><code>New: https://wordpress.com/themes/example.wordpress.com</code></p>
</li>
<li>
Customize
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?return=%2Fwp-admin%2F</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com</code></p>
</li>
<li>
Widgets
<p><code>Old: https://example.wordpress.com/wp-admin/widgets.php</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[panel]=widgets</code></p>
</li>
<li>
Menus
<p><code>Old: https://example.wordpress.com/wp-admin/nav-menus.php</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[panel]=nav_menus</code></p>
</li>
<li>
Header
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?return=%2Fwp-admin%2F&autofocus%5Bcontrol%5D=header_image</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[control]=header_image</code></p>
</li>
<li>
Background
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?autofocus%5Bsection%5D=colors_manager_tool</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[section]=colors_manager_tool</code></p>
</li>
<li>
AMP
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?autofocus[panel]=amp_panel&return=https%3A%2F%2Fexample.wordpress.com%2Fwp-admin%2F&customize_amp=1</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?customize_amp=1&autofocus[section]=amp_design</code></p>
</li></ul></li></ul>
There is an additional menu option in wp-admin for "Mobile". It links to: https://example.wordpress.com/wp-admin/themes.php?page=mobile-options I haven't found a suitable redirect location in Calypso yet.
|
1.0
|
Update top level wp-admin appearance link to redirect to Calypso - Update the wp-admin Appearance links to redirect to Calypso.
<ul>
<li>
Appearance links to Themes
<ul>
<li>
Themes <p><code>Old: https://example.wordpress.com/wp-admin/themes.php</code></p>
<p><code>New: https://wordpress.com/themes/example.wordpress.com</code></p>
</li>
<li>
Customize
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?return=%2Fwp-admin%2F</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com</code></p>
</li>
<li>
Widgets
<p><code>Old: https://example.wordpress.com/wp-admin/widgets.php</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[panel]=widgets</code></p>
</li>
<li>
Menus
<p><code>Old: https://example.wordpress.com/wp-admin/nav-menus.php</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[panel]=nav_menus</code></p>
</li>
<li>
Header
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?return=%2Fwp-admin%2F&autofocus%5Bcontrol%5D=header_image</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[control]=header_image</code></p>
</li>
<li>
Background
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?autofocus%5Bsection%5D=colors_manager_tool</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?autofocus[section]=colors_manager_tool</code></p>
</li>
<li>
AMP
<p><code>Old: https://example.wordpress.com/wp-admin/customize.php?autofocus[panel]=amp_panel&return=https%3A%2F%2Fexample.wordpress.com%2Fwp-admin%2F&customize_amp=1</code></p>
<p><code>New: https://wordpress.com/customize/example.wordpress.com?customize_amp=1&autofocus[section]=amp_design</code></p>
</li></ul></li></ul>
There is an additional menu option in wp-admin for "Mobile". It links to: https://example.wordpress.com/wp-admin/themes.php?page=mobile-options I haven't found a suitable redirect location in Calypso yet.
|
people
|
update top level wp admin appearance link to redirect to calypso update the wp admin appearance links to redirect to calypso appearance links to themes themes old new customize old new widgets old new widgets menus old new nav menus header old new header image background old new colors manager tool amp old amp panel return https wordpress com admin customize amp new amp design there is an additional menu option in wp admin for mobile it links to i haven t found a suitable redirect location in calypso yet
| 1
|
191,045
| 6,825,164,200
|
IssuesEvent
|
2017-11-08 09:33:05
|
ballerinalang/composer
|
https://api.github.com/repos/ballerinalang/composer
|
closed
|
Finally keyword is not shown as a keyword in try-catch
|
Priority/High Severity/Major Type/Bug
|
Pack 0.93 13/09
Finally keyword is not shown as a keyword as it is not colored
|
1.0
|
Finally keyword is not shown as a keyword in try-catch - Pack 0.93 13/09
Finally keyword is not shown as a keyword as it is not colored
|
non_people
|
finally keyword is not shown as a keyword in try catch pack finally keyword is not shown as a keyword as it is not colored
| 0
|
505
| 8,710,877,757
|
IssuesEvent
|
2018-12-06 17:33:29
|
planningcenter/developers
|
https://api.github.com/repos/planningcenter/developers
|
closed
|
Getting phone number of people on a list
|
People
|
Hi, when I pull a list of people, I can get their info, but not their phone number in the single call.
Would I have to make 1 call per person to get each person's phone number? Or there there a way to include each person phone number that I have missed?
|
1.0
|
Getting phone number of people on a list - Hi, when I pull a list of people, I can get their info, but not their phone number in the single call.
Would I have to make 1 call per person to get each person's phone number? Or there there a way to include each person phone number that I have missed?
|
people
|
getting phone number of people on a list hi when i pull a list of people i can get their info but not their phone number in the single call would i have to make call per person to get each person s phone number or there there a way to include each person phone number that i have missed
| 1
|
493
| 8,454,437,628
|
IssuesEvent
|
2018-10-21 03:04:49
|
wordpress-mobile/WordPress-Android
|
https://api.github.com/repos/wordpress-mobile/WordPress-Android
|
closed
|
People: Viewer on a private site can't be invited as a member of the site
|
Calypsofication People Management [Pri] Medium [Status] Stale [Type] Bug
|
### Expected behavior
If a user is a Viewer on a private site, it should be possible to invite them to become a member (Contributor, Author, Editor, or Administrator) on the same site.
This is possible in Calypso web. If a user is a Viewer on a private site, and you try to invite them as a Viewer again, Calypso shows an error:
But if you select a different role for that Viewer, the invite works:
### Actual behavior
If a user is a Viewer on a private site, you are blocked from inviting them to become a member (Contributor, Author, Editor, or Administrator) on the same site.
### Steps to reproduce the behavior
1. Select a private site and add a user as a Viewer on that site
2. In the app, go to the site dashboard > People and tap the plus icon to invite a new member
3. Enter the username or email of the Viewer on the site
4. Tap in another field or tap Send
Result: An error appears in red: "There's already a member with the username 'USERNAME'"
##### Tested on Nexus 9, Android 6.0.1, WPAndroid alpha-16
|
1.0
|
People: Viewer on a private site can't be invited as a member of the site - ### Expected behavior
If a user is a Viewer on a private site, it should be possible to invite them to become a member (Contributor, Author, Editor, or Administrator) on the same site.
This is possible in Calypso web. If a user is a Viewer on a private site, and you try to invite them as a Viewer again, Calypso shows an error:
But if you select a different role for that Viewer, the invite works:
### Actual behavior
If a user is a Viewer on a private site, you are blocked from inviting them to become a member (Contributor, Author, Editor, or Administrator) on the same site.
### Steps to reproduce the behavior
1. Select a private site and add a user as a Viewer on that site
2. In the app, go to the site dashboard > People and tap the plus icon to invite a new member
3. Enter the username or email of the Viewer on the site
4. Tap in another field or tap Send
Result: An error appears in red: "There's already a member with the username 'USERNAME'"
##### Tested on Nexus 9, Android 6.0.1, WPAndroid alpha-16
|
people
|
people viewer on a private site can t be invited as a member of the site expected behavior if a user is a viewer on a private site it should be possible to invite them to become a member contributor author editor or administrator on the same site this is possible in calypso web if a user is a viewer on a private site and you try to invite them as a viewer again calypso shows an error but if you select a different role for that viewer the invite works actual behavior if a user is a viewer on a private site you are blocked from inviting them to become a member contributor author editor or administrator on the same site steps to reproduce the behavior select a private site and add a user as a viewer on that site in the app go to the site dashboard people and tap the plus icon to invite a new member enter the username or email of the viewer on the site tap in another field or tap send result an error appears in red there s already a member with the username username tested on nexus android wpandroid alpha
| 1
|
247,848
| 26,744,213,406
|
IssuesEvent
|
2023-01-30 14:59:01
|
hackariens/react
|
https://api.github.com/repos/hackariens/react
|
closed
|
jest-dom-5.14.1.tgz: 3 vulnerabilities (highest severity is: 7.5) - autoclosed
|
security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jest-dom-5.14.1.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/lodash/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (jest-dom version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-38900](https://www.mend.io/vulnerability-database/CVE-2022-38900) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | decode-uri-component-0.2.0.tgz | Transitive | 5.15.0 | ❌ |
| [CVE-2021-23337](https://www.mend.io/vulnerability-database/CVE-2021-23337) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.2 | lodash-4.17.20.tgz | Transitive | 5.15.0 | ❌ |
| [CVE-2020-28500](https://www.mend.io/vulnerability-database/CVE-2020-28500) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | lodash-4.17.20.tgz | Transitive | 5.15.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-38900</summary>
### Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.14.1.tgz (Root Library)
- css-3.0.0.tgz
- source-map-resolve-0.6.0.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-w573-4hg7-7wgq">https://github.com/advisories/GHSA-w573-4hg7-7wgq</a></p>
<p>Release Date: 2022-11-28</p>
<p>Fix Resolution (decode-uri-component): 0.2.1</p>
<p>Direct dependency fix Resolution (@testing-library/jest-dom): 5.15.0</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary>
### Vulnerable Library - <b>lodash-4.17.20.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.14.1.tgz (Root Library)
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.2</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution (lodash): 4.17.21</p>
<p>Direct dependency fix Resolution (@testing-library/jest-dom): 5.15.0</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary>
### Vulnerable Library - <b>lodash-4.17.20.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.14.1.tgz (Root Library)
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Mend Note: After conducting further research, Mend has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-28500>CVE-2020-28500</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: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution (lodash): 4.17.21</p>
<p>Direct dependency fix Resolution (@testing-library/jest-dom): 5.15.0</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
|
True
|
jest-dom-5.14.1.tgz: 3 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jest-dom-5.14.1.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/lodash/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (jest-dom version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-38900](https://www.mend.io/vulnerability-database/CVE-2022-38900) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | decode-uri-component-0.2.0.tgz | Transitive | 5.15.0 | ❌ |
| [CVE-2021-23337](https://www.mend.io/vulnerability-database/CVE-2021-23337) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.2 | lodash-4.17.20.tgz | Transitive | 5.15.0 | ❌ |
| [CVE-2020-28500](https://www.mend.io/vulnerability-database/CVE-2020-28500) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | lodash-4.17.20.tgz | Transitive | 5.15.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-38900</summary>
### Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.14.1.tgz (Root Library)
- css-3.0.0.tgz
- source-map-resolve-0.6.0.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-w573-4hg7-7wgq">https://github.com/advisories/GHSA-w573-4hg7-7wgq</a></p>
<p>Release Date: 2022-11-28</p>
<p>Fix Resolution (decode-uri-component): 0.2.1</p>
<p>Direct dependency fix Resolution (@testing-library/jest-dom): 5.15.0</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary>
### Vulnerable Library - <b>lodash-4.17.20.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.14.1.tgz (Root Library)
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.2</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution (lodash): 4.17.21</p>
<p>Direct dependency fix Resolution (@testing-library/jest-dom): 5.15.0</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary>
### Vulnerable Library - <b>lodash-4.17.20.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: /apps/package.json</p>
<p>Path to vulnerable library: /apps/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- jest-dom-5.14.1.tgz (Root Library)
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hackariens/react/commit/936546e118f7869172c534d1b6de23486e1deae3">936546e118f7869172c534d1b6de23486e1deae3</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Mend Note: After conducting further research, Mend has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-28500>CVE-2020-28500</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: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution (lodash): 4.17.21</p>
<p>Direct dependency fix Resolution (@testing-library/jest-dom): 5.15.0</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
|
non_people
|
jest dom tgz vulnerabilities highest severity is autoclosed vulnerable library jest dom tgz path to dependency file apps package json path to vulnerable library apps node modules lodash package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in jest dom version remediation available high decode uri component tgz transitive high lodash tgz transitive medium lodash tgz transitive details cve vulnerable library decode uri component tgz a better decodeuricomponent library home page a href path to dependency file apps package json path to vulnerable library apps node modules decode uri component package json dependency hierarchy jest dom tgz root library css tgz source map resolve tgz x decode uri component tgz vulnerable library found in head commit a href found in base branch develop vulnerability details decode uri component is vulnerable to improper input validation resulting in dos 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 decode uri component direct dependency fix resolution testing library jest dom step up your open source security game with mend cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file apps package json path to vulnerable library apps node modules lodash package json dependency hierarchy jest dom tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch develop vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution lodash direct dependency fix resolution testing library jest dom step up your open source security game with mend cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file apps package json path to vulnerable library apps node modules lodash package json dependency hierarchy jest dom tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch develop vulnerability details lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions mend note after conducting further research mend has determined that cve only affects environments with versions to of lodash 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 low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution testing library jest dom step up your open source security game with mend
| 0
|
884
| 17,481,298,747
|
IssuesEvent
|
2021-08-09 03:08:26
|
Automattic/wp-calypso
|
https://api.github.com/repos/Automattic/wp-calypso
|
closed
|
Ability to block other WordPress.com users from following
|
Reader People Management [Type] Feature Request User Report
|
(Edited from original) In this particular situation, the user is concerned that a certain WordPress.com user is consistently liking their blog posts as new blog posts are published. It is possible that they are doing so from the WordPress.com Reader. The user wants an option to have the ability to block other WordPress.com users from following, and to remove likes on Reader when the like settings in Calypso are turned off.
User report: 4081261-zen
Originally posted to pKdGS-27k-p2.
|
1.0
|
Ability to block other WordPress.com users from following - (Edited from original) In this particular situation, the user is concerned that a certain WordPress.com user is consistently liking their blog posts as new blog posts are published. It is possible that they are doing so from the WordPress.com Reader. The user wants an option to have the ability to block other WordPress.com users from following, and to remove likes on Reader when the like settings in Calypso are turned off.
User report: 4081261-zen
Originally posted to pKdGS-27k-p2.
|
people
|
ability to block other wordpress com users from following edited from original in this particular situation the user is concerned that a certain wordpress com user is consistently liking their blog posts as new blog posts are published it is possible that they are doing so from the wordpress com reader the user wants an option to have the ability to block other wordpress com users from following and to remove likes on reader when the like settings in calypso are turned off user report zen originally posted to pkdgs
| 1
|
50,790
| 3,006,619,599
|
IssuesEvent
|
2015-07-27 11:42:47
|
Itseez/opencv
|
https://api.github.com/repos/Itseez/opencv
|
opened
|
Crash when trying to load utf-8 xml file with a BOM
|
affected: master auto-transferred bug category: none priority: normal
|
Transferred from http://code.opencv.org/issues/4486
```
|| Lior Da on 2015-07-13 21:18
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: None
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: x64 / Windows
```
Crash when trying to load utf-8 xml file with a BOM
-----------
```
When calling the next line:
cv::FileStorage root("_root.xml", cv::FileStorage::READ);
the program crashes.
If I change _root.xml to be encoded without BOM, it does not crash.
```
History
-------
|
1.0
|
Crash when trying to load utf-8 xml file with a BOM - Transferred from http://code.opencv.org/issues/4486
```
|| Lior Da on 2015-07-13 21:18
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: None
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: x64 / Windows
```
Crash when trying to load utf-8 xml file with a BOM
-----------
```
When calling the next line:
cv::FileStorage root("_root.xml", cv::FileStorage::READ);
the program crashes.
If I change _root.xml to be encoded without BOM, it does not crash.
```
History
-------
|
non_people
|
crash when trying to load utf xml file with a bom transferred from lior da on priority normal affected branch master dev category none tracker bug difficulty pr platform windows crash when trying to load utf xml file with a bom when calling the next line cv filestorage root root xml cv filestorage read the program crashes if i change root xml to be encoded without bom it does not crash history
| 0
|
293,012
| 22,042,062,819
|
IssuesEvent
|
2022-05-29 14:02:26
|
lardemua/atom
|
https://api.github.com/repos/lardemua/atom
|
closed
|
LiDAR resolution
|
documentation
|
FYI @miguelriemoliveira
I made measurements for all the LiDARs and all of them were around 10cm
(length in the bottom left corner)
|
1.0
|
LiDAR resolution - FYI @miguelriemoliveira
I made measurements for all the LiDARs and all of them were around 10cm
(length in the bottom left corner)
|
non_people
|
lidar resolution fyi miguelriemoliveira i made measurements for all the lidars and all of them were around length in the bottom left corner
| 0
|
721
| 13,218,751,307
|
IssuesEvent
|
2020-08-17 09:16:52
|
Swiss-Polar-Institute/project-application
|
https://api.github.com/repos/Swiss-Polar-Institute/project-application
|
closed
|
Add grantee / applicant address
|
before next call opens people proposal
|
The address of a grantee or applicant is used for communication, such as sending the decision letter or grant agreement. Currently this is not part of the application form and therefore can be very tricky to find.
The applicant's address (that should be used for correspondance) could be included in the application form so it can be used to send the initial decision letter.
Adding it as part of the person position for the applicant would mean that it is possible for it to appear with the proposal and project, but could also change (as it is not with the physical person) as the person moves to different institutions.
Having the address as a text box is an option. Structuring the full address is tricky to account for variation in all possible countries. Validation for all parts of an address is tricky as well because of variation between countries. It might be useful to have separate fields for the postcode, city and country.
A country list could come from the ISO list of [countries](https://www.iso.org/iso-3166-country-codes.html) (to avoid duplications).
|
1.0
|
Add grantee / applicant address - The address of a grantee or applicant is used for communication, such as sending the decision letter or grant agreement. Currently this is not part of the application form and therefore can be very tricky to find.
The applicant's address (that should be used for correspondance) could be included in the application form so it can be used to send the initial decision letter.
Adding it as part of the person position for the applicant would mean that it is possible for it to appear with the proposal and project, but could also change (as it is not with the physical person) as the person moves to different institutions.
Having the address as a text box is an option. Structuring the full address is tricky to account for variation in all possible countries. Validation for all parts of an address is tricky as well because of variation between countries. It might be useful to have separate fields for the postcode, city and country.
A country list could come from the ISO list of [countries](https://www.iso.org/iso-3166-country-codes.html) (to avoid duplications).
|
people
|
add grantee applicant address the address of a grantee or applicant is used for communication such as sending the decision letter or grant agreement currently this is not part of the application form and therefore can be very tricky to find the applicant s address that should be used for correspondance could be included in the application form so it can be used to send the initial decision letter adding it as part of the person position for the applicant would mean that it is possible for it to appear with the proposal and project but could also change as it is not with the physical person as the person moves to different institutions having the address as a text box is an option structuring the full address is tricky to account for variation in all possible countries validation for all parts of an address is tricky as well because of variation between countries it might be useful to have separate fields for the postcode city and country a country list could come from the iso list of to avoid duplications
| 1
|
426,135
| 12,367,930,641
|
IssuesEvent
|
2020-05-18 13:05:06
|
jenkins-x/jx
|
https://api.github.com/repos/jenkins-x/jx
|
closed
|
Unable to update resources for webhook change during `jx upgrade ingress`
|
area/ingress kind/needs-validation lifecycle/rotten priority/awaiting-more-evidence
|
### Summary
`jx upgrade ingress` removes ingress configurations and doesn't recreate them.
### Steps to reproduce the behavior
```
jx upgrade ingress
Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
```
Choose: Yes
### Expected behavior
Upgrade successful
### Actual behavior
```
? Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
? Expose type Ingress
? Domain: ****
? If your network is publicly available would you like to enable cluster wide TLS? Yes
If testing LetsEncrypt you should use staging as you may be rate limited using production.
? Use LetsEncrypt staging or production? production
? Email address to register with LetsEncrypt: ****@****
? URLTemplate (press <Enter> to keep the current value): "{{.Service}}.{{.Domain}}"
? Using config values {****@***** ***** letsencrypt-prod false Ingress "{{.Service}}.{{.Domain}}" true}, ok? Yes
Looking for "cert-manager" deployment in namespace "cert-manager"...
Deleting ingress geeoz/deck
Deleting ingress geeoz/hook
Deleting ingress geeoz/tide
...
Ingress rules recreated
error: unable to update resources for webhook change: retrieving the webhook endpoint: getting ingress for service "hook" in namespace geeoz: ingresses.extensions "hook" not found
```
### Jx version
The output of `jx version` is:
```
NAME VERSION
jx 2.0.886
jenkins x platform 2.0.1480
Kubernetes cluster v1.15.3
kubectl v1.16.2
helm client Client: v2.14.3+g0e7f3b6
git 2.23.0
Operating System Mac OS X 10.15.1 build 19B77a
```
### Jenkins type
<!--
Select which installation type are you using.
-->
- [x] Serverless Jenkins X Pipelines (Tekton + Prow)
- [ ] Classic Jenkins
### Kubernetes cluster
<!--
What kind of Kubernetes cluster are you using & how did you create it?
-->
Self-created with kubespray
### Operating system / Environment
<!--
In which environment are you running the jx CLI?
-->
Running the CLI on my MacBook Pro (OS X)
|
1.0
|
Unable to update resources for webhook change during `jx upgrade ingress` - ### Summary
`jx upgrade ingress` removes ingress configurations and doesn't recreate them.
### Steps to reproduce the behavior
```
jx upgrade ingress
Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
```
Choose: Yes
### Expected behavior
Upgrade successful
### Actual behavior
```
? Existing ingress rules found in current namespace. Confirm to delete and recreate them Yes
? Expose type Ingress
? Domain: ****
? If your network is publicly available would you like to enable cluster wide TLS? Yes
If testing LetsEncrypt you should use staging as you may be rate limited using production.
? Use LetsEncrypt staging or production? production
? Email address to register with LetsEncrypt: ****@****
? URLTemplate (press <Enter> to keep the current value): "{{.Service}}.{{.Domain}}"
? Using config values {****@***** ***** letsencrypt-prod false Ingress "{{.Service}}.{{.Domain}}" true}, ok? Yes
Looking for "cert-manager" deployment in namespace "cert-manager"...
Deleting ingress geeoz/deck
Deleting ingress geeoz/hook
Deleting ingress geeoz/tide
...
Ingress rules recreated
error: unable to update resources for webhook change: retrieving the webhook endpoint: getting ingress for service "hook" in namespace geeoz: ingresses.extensions "hook" not found
```
### Jx version
The output of `jx version` is:
```
NAME VERSION
jx 2.0.886
jenkins x platform 2.0.1480
Kubernetes cluster v1.15.3
kubectl v1.16.2
helm client Client: v2.14.3+g0e7f3b6
git 2.23.0
Operating System Mac OS X 10.15.1 build 19B77a
```
### Jenkins type
<!--
Select which installation type are you using.
-->
- [x] Serverless Jenkins X Pipelines (Tekton + Prow)
- [ ] Classic Jenkins
### Kubernetes cluster
<!--
What kind of Kubernetes cluster are you using & how did you create it?
-->
Self-created with kubespray
### Operating system / Environment
<!--
In which environment are you running the jx CLI?
-->
Running the CLI on my MacBook Pro (OS X)
|
non_people
|
unable to update resources for webhook change during jx upgrade ingress summary jx upgrade ingress removes ingress configurations and doesn t recreate them steps to reproduce the behavior jx upgrade ingress existing ingress rules found in current namespace confirm to delete and recreate them yes choose yes expected behavior upgrade successful actual behavior existing ingress rules found in current namespace confirm to delete and recreate them yes expose type ingress domain if your network is publicly available would you like to enable cluster wide tls yes if testing letsencrypt you should use staging as you may be rate limited using production use letsencrypt staging or production production email address to register with letsencrypt urltemplate press to keep the current value service domain using config values letsencrypt prod false ingress service domain true ok yes looking for cert manager deployment in namespace cert manager deleting ingress geeoz deck deleting ingress geeoz hook deleting ingress geeoz tide ingress rules recreated error unable to update resources for webhook change retrieving the webhook endpoint getting ingress for service hook in namespace geeoz ingresses extensions hook not found jx version the output of jx version is name version jx jenkins x platform kubernetes cluster kubectl helm client client git operating system mac os x build jenkins type select which installation type are you using serverless jenkins x pipelines tekton prow classic jenkins kubernetes cluster what kind of kubernetes cluster are you using how did you create it self created with kubespray operating system environment in which environment are you running the jx cli running the cli on my macbook pro os x
| 0
|
621,914
| 19,599,404,830
|
IssuesEvent
|
2022-01-05 22:23:19
|
microsoft/fluentui-react-native
|
https://api.github.com/repos/microsoft/fluentui-react-native
|
closed
|
Logging bug isn't an option when logging an issue
|
Type: Bug Status: In PR Priority: High Area: Eng Improvements
|
When you go to submit a new issue to this repo, the options don't show a "Report a bug" button, even though we have a template for it.
#1053 made some changes to our issues infrastructure, maybe the bug template has a problem with it? I didn't see anything obvious, though. @chrisglein and @Saadnajmi as FYI
|
1.0
|
Logging bug isn't an option when logging an issue - When you go to submit a new issue to this repo, the options don't show a "Report a bug" button, even though we have a template for it.
#1053 made some changes to our issues infrastructure, maybe the bug template has a problem with it? I didn't see anything obvious, though. @chrisglein and @Saadnajmi as FYI
|
non_people
|
logging bug isn t an option when logging an issue when you go to submit a new issue to this repo the options don t show a report a bug button even though we have a template for it made some changes to our issues infrastructure maybe the bug template has a problem with it i didn t see anything obvious though chrisglein and saadnajmi as fyi
| 0
|
239,262
| 19,832,577,085
|
IssuesEvent
|
2022-01-20 13:32:17
|
quarkusio/quarkus
|
https://api.github.com/repos/quarkusio/quarkus
|
closed
|
Testing Quarkus against different versions of GraalVM/Mandrel
|
kind/enhancement area/testing
|
## Description
It looks like our current way of testing Quarkus with different GraalVM CE and Mandrel versions is a bit flawed and might let issues go through.
I have [shared this in the quarkus-dev mailing list](https://groups.google.com/g/quarkus-dev/c/kBknz8EMz7Q/m/wZpeSg3BBwAJ) as well, but having it here makes it easier to link issues and PRs.
### Existing pipelines
I am personally aware of the following pipelines (please let me know if there are more out there):
1. Quarkus Upstream [1]
- Tests latest Quarkus with latest supported GraalVM CE (21.0.0 ATM) in a builder container.
* Runs on PRs (multiple times a day)
- Tests Quarkus releases that are still getting backports with the corresponding supported GraalVM CE (e.g. 20.3 for 1.11) in a builder container.
* Runs on PRs (rarely)
2. Mandrel Upstream
- Tests Mandrel built from source with the corresponding Quarkus releases that the version at hand supports, e.g.:
+ Mandrel 20.3 is tested with Quarkus 1.11 release and Quarkus main branch [3]
* Runs on PRs (which are rare, and no re-runs after release)
+ Mandrel 21.0 is tested with Quarkus latest release and Quarkus main branch [4]
* Runs on PRs (which are rare, and no re-runs after release)
+ Mandrel "master" (mandrel build of latest graal) is tested with Quarkus latest release and Quarkus main branch [5]
* Runs nighlty
3. Mandrel's public Jenkins instance [6]
- Our most complete set of pipelines
- Tests both Linux and Windows
- Tests both docker and podman
- Tests both builder images and hosted
- Tests same version pairs like Mandrel Upstream
- In addition to Quarkus ITs it also runs https://github.com/Karm/mandrel-integration-tests
* Runs on Mandrel code change (polls github for changes) which is rare
4. Graal Upstream [7]
- Tests latest Graal build from source with Quarkus latest release
* Runs nightly
5. Foivos' workflow [8]
- Tests any version of GraalVM CE built from source with any version of Quarkus build from source. This is actually an augmented version of the Graal Upstream workflow
* Runs on demand
### People managing the pipelines
- Quarkus Upstream: Quarkus community
- Mandrel Upstream: Mandrel community (@zakkak mostly)
- Mandrel's public Jenkins instance: @Karm and partly @zakkak
- Graal Upstream: @zakkak
- @zakkak's workflow: @zakkak (it's only a couple of weeks old though)
### People monitoring the pipelines
- Quarkus Upstream: Monitored by the Quarkus community
(mostly @gsmet, @gastaldi, and @geoand if I am not mistaken)
- Mandrel Upstream: Monitored by the Mandrel community (@zakkak mostly)
- Mandrel's public Jenkins instance: Monitored by @Karm and partly
by @zakkak
- Graal Upstream: Monitored by the GraalVM community (@zakkak mostly if not solely :) )
Note that most often the issues that pop up need to be resolved on the Quarkus side, so the GraalVM community can't do much about it.
- @zakkak's workflow: @zakkak (it's only a couple of weeks old though)
### Issues with the current state
1. Testing is happening in multiple places, so it's hard to get the full picture.
2. Our most complete set of pipelines is in Mandrel's public Jenkins instance, which unfortunately runs on limited resources and is thus not a good fit for scheduling all the tests we need. Mandrel's public Jenkins instance is meant to be used for building and testing upstream Mandrel releases and not for continuous testing.
3. We are missing test-cases/scenarios:
1. Mandrel Quarkus builder image is not tested by Quarkus upstream (it's only tested by the Mandrel team before Mandrel releases or on demand)
2. Quarkus latest is not being tested with 20.3.
4. Most pipelines are monitored mostly by the Mandrel team. I believe both teams should keep an eye on the pipelines and depending on the nature of the failure take action or ensure that the right people are aware of the failure.
5. Due to having the pipelines in multiple places it is hard to ensure that they are in sync, and they are actually testing what they should.
6. Native tests take pretty long to run (~2h with 8 parallel executors). We might not be able to do much about this but maybe we can prioritize tests (and even combine some?).
## Implementation Ideas
1. Gather the results of all native-image related testing to a single place:
- https://status.quarkus.io/ seems like a good place for this
- Enhance our github pipelines to perform tests previously performed by Mandrel's public Jenkins instance.
- Split the pipelines between Quarkus and GraalVM organization to avoid saturating either.
- Find a way to de-duplicate pipelines
- In GH we can use scheduled builds and https://github.com/marketplace/actions/workflow-dispatch for triggering builds from other workflows or to perform on-demand parameterized builds like I do in [8]
2. Send notifications to at least one person from the Mandrel team and one person from the Quarkus team when a scheduled workflow fails (failures of jobs triggered by PRs should be treated differently, ideally blocking the corresponding PR).
3. Reduce the coverage of (or retire entirely) the Upstream Graal pipeline [7]. My experience so far is that the graalvm community is not really paying attention to it and keeping it there just adds complexity (since we need to keep it in sync and wait for someone from the graalvm team to review and merge changes, which is understandably not a high priority for them)
4. We might want to come with a subset of native tests and configurations that we want to run on PRs or some other events and only run the full set once per week or on some other schedule.
5. Explore the potential of combining the tested functionality of multiple native integration tests in a single native image. E.g., for gRPC we currently build 8 native images. Can we have the same coverage with less native images? Discussed in #16439
Please share your opinion, ideas, and any potential info I might have left out.
Thanks for reading that far!
[1]
https://github.com/quarkusio/quarkus/actions/workflows/ci-actions-incremental.yml
[2]
https://github.com/graalvm/mandrel/blob/mandrel/20.1/.github/workflows/mandrel.yml
[3]
https://github.com/graalvm/mandrel/blob/mandrel/20.3/.github/workflows/mandrel.yml
[4]
https://github.com/graalvm/mandrel/blob/mandrel/21.0/.github/workflows/mandrel.yml
[5]
https://github.com/graalvm/mandrel/blob/default/.github/workflows/mandrel.yml
[6] https://ci.modcluster.io/view/Mandrel/
[7] https://github.com/oracle/graal/actions/workflows/quarkus.yml
[8] https://github.com/zakkak/graalvm-quarkus-ci/actions/workflows/quarkus.yml
|
1.0
|
Testing Quarkus against different versions of GraalVM/Mandrel - ## Description
It looks like our current way of testing Quarkus with different GraalVM CE and Mandrel versions is a bit flawed and might let issues go through.
I have [shared this in the quarkus-dev mailing list](https://groups.google.com/g/quarkus-dev/c/kBknz8EMz7Q/m/wZpeSg3BBwAJ) as well, but having it here makes it easier to link issues and PRs.
### Existing pipelines
I am personally aware of the following pipelines (please let me know if there are more out there):
1. Quarkus Upstream [1]
- Tests latest Quarkus with latest supported GraalVM CE (21.0.0 ATM) in a builder container.
* Runs on PRs (multiple times a day)
- Tests Quarkus releases that are still getting backports with the corresponding supported GraalVM CE (e.g. 20.3 for 1.11) in a builder container.
* Runs on PRs (rarely)
2. Mandrel Upstream
- Tests Mandrel built from source with the corresponding Quarkus releases that the version at hand supports, e.g.:
+ Mandrel 20.3 is tested with Quarkus 1.11 release and Quarkus main branch [3]
* Runs on PRs (which are rare, and no re-runs after release)
+ Mandrel 21.0 is tested with Quarkus latest release and Quarkus main branch [4]
* Runs on PRs (which are rare, and no re-runs after release)
+ Mandrel "master" (mandrel build of latest graal) is tested with Quarkus latest release and Quarkus main branch [5]
* Runs nighlty
3. Mandrel's public Jenkins instance [6]
- Our most complete set of pipelines
- Tests both Linux and Windows
- Tests both docker and podman
- Tests both builder images and hosted
- Tests same version pairs like Mandrel Upstream
- In addition to Quarkus ITs it also runs https://github.com/Karm/mandrel-integration-tests
* Runs on Mandrel code change (polls github for changes) which is rare
4. Graal Upstream [7]
- Tests latest Graal build from source with Quarkus latest release
* Runs nightly
5. Foivos' workflow [8]
- Tests any version of GraalVM CE built from source with any version of Quarkus build from source. This is actually an augmented version of the Graal Upstream workflow
* Runs on demand
### People managing the pipelines
- Quarkus Upstream: Quarkus community
- Mandrel Upstream: Mandrel community (@zakkak mostly)
- Mandrel's public Jenkins instance: @Karm and partly @zakkak
- Graal Upstream: @zakkak
- @zakkak's workflow: @zakkak (it's only a couple of weeks old though)
### People monitoring the pipelines
- Quarkus Upstream: Monitored by the Quarkus community
(mostly @gsmet, @gastaldi, and @geoand if I am not mistaken)
- Mandrel Upstream: Monitored by the Mandrel community (@zakkak mostly)
- Mandrel's public Jenkins instance: Monitored by @Karm and partly
by @zakkak
- Graal Upstream: Monitored by the GraalVM community (@zakkak mostly if not solely :) )
Note that most often the issues that pop up need to be resolved on the Quarkus side, so the GraalVM community can't do much about it.
- @zakkak's workflow: @zakkak (it's only a couple of weeks old though)
### Issues with the current state
1. Testing is happening in multiple places, so it's hard to get the full picture.
2. Our most complete set of pipelines is in Mandrel's public Jenkins instance, which unfortunately runs on limited resources and is thus not a good fit for scheduling all the tests we need. Mandrel's public Jenkins instance is meant to be used for building and testing upstream Mandrel releases and not for continuous testing.
3. We are missing test-cases/scenarios:
1. Mandrel Quarkus builder image is not tested by Quarkus upstream (it's only tested by the Mandrel team before Mandrel releases or on demand)
2. Quarkus latest is not being tested with 20.3.
4. Most pipelines are monitored mostly by the Mandrel team. I believe both teams should keep an eye on the pipelines and depending on the nature of the failure take action or ensure that the right people are aware of the failure.
5. Due to having the pipelines in multiple places it is hard to ensure that they are in sync, and they are actually testing what they should.
6. Native tests take pretty long to run (~2h with 8 parallel executors). We might not be able to do much about this but maybe we can prioritize tests (and even combine some?).
## Implementation Ideas
1. Gather the results of all native-image related testing to a single place:
- https://status.quarkus.io/ seems like a good place for this
- Enhance our github pipelines to perform tests previously performed by Mandrel's public Jenkins instance.
- Split the pipelines between Quarkus and GraalVM organization to avoid saturating either.
- Find a way to de-duplicate pipelines
- In GH we can use scheduled builds and https://github.com/marketplace/actions/workflow-dispatch for triggering builds from other workflows or to perform on-demand parameterized builds like I do in [8]
2. Send notifications to at least one person from the Mandrel team and one person from the Quarkus team when a scheduled workflow fails (failures of jobs triggered by PRs should be treated differently, ideally blocking the corresponding PR).
3. Reduce the coverage of (or retire entirely) the Upstream Graal pipeline [7]. My experience so far is that the graalvm community is not really paying attention to it and keeping it there just adds complexity (since we need to keep it in sync and wait for someone from the graalvm team to review and merge changes, which is understandably not a high priority for them)
4. We might want to come with a subset of native tests and configurations that we want to run on PRs or some other events and only run the full set once per week or on some other schedule.
5. Explore the potential of combining the tested functionality of multiple native integration tests in a single native image. E.g., for gRPC we currently build 8 native images. Can we have the same coverage with less native images? Discussed in #16439
Please share your opinion, ideas, and any potential info I might have left out.
Thanks for reading that far!
[1]
https://github.com/quarkusio/quarkus/actions/workflows/ci-actions-incremental.yml
[2]
https://github.com/graalvm/mandrel/blob/mandrel/20.1/.github/workflows/mandrel.yml
[3]
https://github.com/graalvm/mandrel/blob/mandrel/20.3/.github/workflows/mandrel.yml
[4]
https://github.com/graalvm/mandrel/blob/mandrel/21.0/.github/workflows/mandrel.yml
[5]
https://github.com/graalvm/mandrel/blob/default/.github/workflows/mandrel.yml
[6] https://ci.modcluster.io/view/Mandrel/
[7] https://github.com/oracle/graal/actions/workflows/quarkus.yml
[8] https://github.com/zakkak/graalvm-quarkus-ci/actions/workflows/quarkus.yml
|
non_people
|
testing quarkus against different versions of graalvm mandrel description it looks like our current way of testing quarkus with different graalvm ce and mandrel versions is a bit flawed and might let issues go through i have as well but having it here makes it easier to link issues and prs existing pipelines i am personally aware of the following pipelines please let me know if there are more out there quarkus upstream tests latest quarkus with latest supported graalvm ce atm in a builder container runs on prs multiple times a day tests quarkus releases that are still getting backports with the corresponding supported graalvm ce e g for in a builder container runs on prs rarely mandrel upstream tests mandrel built from source with the corresponding quarkus releases that the version at hand supports e g mandrel is tested with quarkus release and quarkus main branch runs on prs which are rare and no re runs after release mandrel is tested with quarkus latest release and quarkus main branch runs on prs which are rare and no re runs after release mandrel master mandrel build of latest graal is tested with quarkus latest release and quarkus main branch runs nighlty mandrel s public jenkins instance our most complete set of pipelines tests both linux and windows tests both docker and podman tests both builder images and hosted tests same version pairs like mandrel upstream in addition to quarkus its it also runs runs on mandrel code change polls github for changes which is rare graal upstream tests latest graal build from source with quarkus latest release runs nightly foivos workflow tests any version of graalvm ce built from source with any version of quarkus build from source this is actually an augmented version of the graal upstream workflow runs on demand people managing the pipelines quarkus upstream quarkus community mandrel upstream mandrel community zakkak mostly mandrel s public jenkins instance karm and partly zakkak graal upstream zakkak zakkak s workflow zakkak it s only a couple of weeks old though people monitoring the pipelines quarkus upstream monitored by the quarkus community mostly gsmet gastaldi and geoand if i am not mistaken mandrel upstream monitored by the mandrel community zakkak mostly mandrel s public jenkins instance monitored by karm and partly by zakkak graal upstream monitored by the graalvm community zakkak mostly if not solely note that most often the issues that pop up need to be resolved on the quarkus side so the graalvm community can t do much about it zakkak s workflow zakkak it s only a couple of weeks old though issues with the current state testing is happening in multiple places so it s hard to get the full picture our most complete set of pipelines is in mandrel s public jenkins instance which unfortunately runs on limited resources and is thus not a good fit for scheduling all the tests we need mandrel s public jenkins instance is meant to be used for building and testing upstream mandrel releases and not for continuous testing we are missing test cases scenarios mandrel quarkus builder image is not tested by quarkus upstream it s only tested by the mandrel team before mandrel releases or on demand quarkus latest is not being tested with most pipelines are monitored mostly by the mandrel team i believe both teams should keep an eye on the pipelines and depending on the nature of the failure take action or ensure that the right people are aware of the failure due to having the pipelines in multiple places it is hard to ensure that they are in sync and they are actually testing what they should native tests take pretty long to run with parallel executors we might not be able to do much about this but maybe we can prioritize tests and even combine some implementation ideas gather the results of all native image related testing to a single place seems like a good place for this enhance our github pipelines to perform tests previously performed by mandrel s public jenkins instance split the pipelines between quarkus and graalvm organization to avoid saturating either find a way to de duplicate pipelines in gh we can use scheduled builds and for triggering builds from other workflows or to perform on demand parameterized builds like i do in send notifications to at least one person from the mandrel team and one person from the quarkus team when a scheduled workflow fails failures of jobs triggered by prs should be treated differently ideally blocking the corresponding pr reduce the coverage of or retire entirely the upstream graal pipeline my experience so far is that the graalvm community is not really paying attention to it and keeping it there just adds complexity since we need to keep it in sync and wait for someone from the graalvm team to review and merge changes which is understandably not a high priority for them we might want to come with a subset of native tests and configurations that we want to run on prs or some other events and only run the full set once per week or on some other schedule explore the potential of combining the tested functionality of multiple native integration tests in a single native image e g for grpc we currently build native images can we have the same coverage with less native images discussed in please share your opinion ideas and any potential info i might have left out thanks for reading that far
| 0
|
342,618
| 10,319,731,559
|
IssuesEvent
|
2019-08-30 18:21:29
|
javaee/jta-spec
|
https://api.github.com/repos/javaee/jta-spec
|
closed
|
elaborate on ordering semantics for Synchronization calls in a distributed transaction
|
Priority: Major Type: Improvement
|
This is being opened to track the topic and whether it warrants elaborating in the spec.
Email exchange between Paul Parkinson and Ian Robinson...
Paul:
"
Something I've always thought of, especially since the TransactionSynchronizationRegistry was introduced, is whether we should mention anything in the spec about the ordering semantics for Synchronization calls in a transaction that is distributed across multiple transaction managers/processes.
As far as I can tell all transaction managers in existence issue Synchronization.beforeCompletion calls locally just before the prepare calls on each node of a transaction and there is no "0/beforeCompletion phase" whereby all Synchronization.beforeCompletion calls are made down the entire transaction/process tree before starting the prepare calls down the entire transaction/process tree.
This is no surprise as the performance cost would be significant, however, the spec states "The Synchronization.beforeCompletion method is called prior to the start of the two-phase transaction commit process" and the javadoc for registerInterposedSynchronization) states "beforeCompletion will be called after all SessionSynchronization beforeCompletion callbacks and callbacks registered directly with the Transaction, but before the 2-phase commit process starts"
So one might argue that it is a violation to call prepare from/on one node of a transaction when Synchronization.beforeCompletion calls have not been made on another node involved in the same transaction.
Any thoughts?
"
Ian:
"
This is right - as you say, the ordering of Synchronizations and XAResources are always localized within the scope of a JVM which may be one branch of a distributed transaction. In all the implementations I know, only the first and second phase are strictly distributed across the whole tree with the volatile (Synchronization) work always ordered wrt 2PC only within the local JVM. OTS itself supports distributing before/afterCompletion but I don't know anyone who pays the performance price to do that.
Its a similar consideration for JCA connection sharing - different components that access the same resource provider in the same global transaction should share a Connection but that is only true if the application components are deployed to the same AppServer (JVM).
The Synchronization ordering is safe so long as you DON'T share connections or join (tightly couple) transaction branches between servers (JVMs) in a global transaction. If you did that then you would need to worry about work-after-prepare in the downstream nodes.
So I don't think we have anything to worry about here unless you think this needs clarification. I certainly wouldn't want to require any change in behaviour.
"
|
1.0
|
elaborate on ordering semantics for Synchronization calls in a distributed transaction - This is being opened to track the topic and whether it warrants elaborating in the spec.
Email exchange between Paul Parkinson and Ian Robinson...
Paul:
"
Something I've always thought of, especially since the TransactionSynchronizationRegistry was introduced, is whether we should mention anything in the spec about the ordering semantics for Synchronization calls in a transaction that is distributed across multiple transaction managers/processes.
As far as I can tell all transaction managers in existence issue Synchronization.beforeCompletion calls locally just before the prepare calls on each node of a transaction and there is no "0/beforeCompletion phase" whereby all Synchronization.beforeCompletion calls are made down the entire transaction/process tree before starting the prepare calls down the entire transaction/process tree.
This is no surprise as the performance cost would be significant, however, the spec states "The Synchronization.beforeCompletion method is called prior to the start of the two-phase transaction commit process" and the javadoc for registerInterposedSynchronization) states "beforeCompletion will be called after all SessionSynchronization beforeCompletion callbacks and callbacks registered directly with the Transaction, but before the 2-phase commit process starts"
So one might argue that it is a violation to call prepare from/on one node of a transaction when Synchronization.beforeCompletion calls have not been made on another node involved in the same transaction.
Any thoughts?
"
Ian:
"
This is right - as you say, the ordering of Synchronizations and XAResources are always localized within the scope of a JVM which may be one branch of a distributed transaction. In all the implementations I know, only the first and second phase are strictly distributed across the whole tree with the volatile (Synchronization) work always ordered wrt 2PC only within the local JVM. OTS itself supports distributing before/afterCompletion but I don't know anyone who pays the performance price to do that.
Its a similar consideration for JCA connection sharing - different components that access the same resource provider in the same global transaction should share a Connection but that is only true if the application components are deployed to the same AppServer (JVM).
The Synchronization ordering is safe so long as you DON'T share connections or join (tightly couple) transaction branches between servers (JVMs) in a global transaction. If you did that then you would need to worry about work-after-prepare in the downstream nodes.
So I don't think we have anything to worry about here unless you think this needs clarification. I certainly wouldn't want to require any change in behaviour.
"
|
non_people
|
elaborate on ordering semantics for synchronization calls in a distributed transaction this is being opened to track the topic and whether it warrants elaborating in the spec email exchange between paul parkinson and ian robinson paul something i ve always thought of especially since the transactionsynchronizationregistry was introduced is whether we should mention anything in the spec about the ordering semantics for synchronization calls in a transaction that is distributed across multiple transaction managers processes as far as i can tell all transaction managers in existence issue synchronization beforecompletion calls locally just before the prepare calls on each node of a transaction and there is no beforecompletion phase whereby all synchronization beforecompletion calls are made down the entire transaction process tree before starting the prepare calls down the entire transaction process tree this is no surprise as the performance cost would be significant however the spec states the synchronization beforecompletion method is called prior to the start of the two phase transaction commit process and the javadoc for registerinterposedsynchronization states beforecompletion will be called after all sessionsynchronization beforecompletion callbacks and callbacks registered directly with the transaction but before the phase commit process starts so one might argue that it is a violation to call prepare from on one node of a transaction when synchronization beforecompletion calls have not been made on another node involved in the same transaction any thoughts ian this is right as you say the ordering of synchronizations and xaresources are always localized within the scope of a jvm which may be one branch of a distributed transaction in all the implementations i know only the first and second phase are strictly distributed across the whole tree with the volatile synchronization work always ordered wrt only within the local jvm ots itself supports distributing before aftercompletion but i don t know anyone who pays the performance price to do that its a similar consideration for jca connection sharing different components that access the same resource provider in the same global transaction should share a connection but that is only true if the application components are deployed to the same appserver jvm the synchronization ordering is safe so long as you don t share connections or join tightly couple transaction branches between servers jvms in a global transaction if you did that then you would need to worry about work after prepare in the downstream nodes so i don t think we have anything to worry about here unless you think this needs clarification i certainly wouldn t want to require any change in behaviour
| 0
|
158,469
| 24,846,520,802
|
IssuesEvent
|
2022-10-26 16:17:24
|
ThreeSixtyGiving/grantnav
|
https://api.github.com/repos/ThreeSixtyGiving/grantnav
|
closed
|
As Publisher - Datasets table is missing information from ‘Funders Covered’
|
bug - not as designed Org pages
|
**Describe the bug**
A clear and concise description of what the bug is.
On the As Publisher section, where it's available, the Datasets table column for Funders Covered is blank. It should contain a list of all the Funders covered in the dataset, as in live GrantNav.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Funder search
2. Select any funder with a Publisher section, e.g. Sport England
3. Scroll to As Publisher section to view Datasets table
**Expected behavior**
A clear and concise description of what you expected to happen.
The Datasets table Funders Covered column should contain a list of all the Funders covered in the dataset, as in live GrantNav.
**Screenshots**
If applicable, add screenshots to help explain your problem.
Dev GrantNav Publisher section - Sport England:
Live GrantNav Publisher page - Sport England:
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
|
1.0
|
As Publisher - Datasets table is missing information from ‘Funders Covered’ - **Describe the bug**
A clear and concise description of what the bug is.
On the As Publisher section, where it's available, the Datasets table column for Funders Covered is blank. It should contain a list of all the Funders covered in the dataset, as in live GrantNav.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Funder search
2. Select any funder with a Publisher section, e.g. Sport England
3. Scroll to As Publisher section to view Datasets table
**Expected behavior**
A clear and concise description of what you expected to happen.
The Datasets table Funders Covered column should contain a list of all the Funders covered in the dataset, as in live GrantNav.
**Screenshots**
If applicable, add screenshots to help explain your problem.
Dev GrantNav Publisher section - Sport England:
Live GrantNav Publisher page - Sport England:
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
|
non_people
|
as publisher datasets table is missing information from ‘funders covered’ describe the bug a clear and concise description of what the bug is on the as publisher section where it s available the datasets table column for funders covered is blank it should contain a list of all the funders covered in the dataset as in live grantnav to reproduce steps to reproduce the behavior go to funder search select any funder with a publisher section e g sport england scroll to as publisher section to view datasets table expected behavior a clear and concise description of what you expected to happen the datasets table funders covered column should contain a list of all the funders covered in the dataset as in live grantnav screenshots if applicable add screenshots to help explain your problem dev grantnav publisher section sport england live grantnav publisher page sport england desktop please complete the following information os browser version smartphone please complete the following information device os browser version additional context add any other context about the problem here
| 0
|
41
| 2,658,170,961
|
IssuesEvent
|
2015-03-18 14:17:46
|
fskreuz/Tree-Trail
|
https://api.github.com/repos/fskreuz/Tree-Trail
|
closed
|
Add Close functionality to sidebar
|
QA people! Test these!
|
As a guest user, when I click an approved badge and a sidebar appears, I should be able to have an option to close the sidebar para dili samok ig navigate sa map.
|
1.0
|
Add Close functionality to sidebar - As a guest user, when I click an approved badge and a sidebar appears, I should be able to have an option to close the sidebar para dili samok ig navigate sa map.
|
people
|
add close functionality to sidebar as a guest user when i click an approved badge and a sidebar appears i should be able to have an option to close the sidebar para dili samok ig navigate sa map
| 1
|
665
| 11,884,954,505
|
IssuesEvent
|
2020-03-27 18:37:58
|
microsoftgraph/microsoft-graph-toolkit
|
https://api.github.com/repos/microsoftgraph/microsoft-graph-toolkit
|
closed
|
[BUG] people-picker flyout in mgt-tasks opens of screen
|
Component: people-picker Component: tasks Priority: 0 State: In Review bug
|
<!-- Please make sure you are posting an issue pertaining to the Microsoft Graph Toolkit. -->
<!-- ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION. -->
**Describe the bug**
When using the people picker inside the mgt-tasks component, when starting to type, the flyout opens to the right of screen.
**To Reproduce**
Steps to reproduce the behavior:
1. Add mgt-tasks to the page and make sure it is set to planner
2. On a task, click on the assigned people and start typing to assign more people
3. Notice the suggested people flyout will not open under the people picker, but instead open off screen
**Expected behavior**
The people picker should open under (or over) the people picker
**Screenshots**
**Environment (please complete the following information):**
- OS: [e.g. iOS] Windows
- Browser [e.g. edge, chrome, safari] new Edge
- Framework [e.g. react, vue, none] none - also validated in Storybook
- Context [e.g. Microsoft Teams, SharePoint, Office Add-ins, Web]: web
- Version [e.g. 0.1]: latest
|
1.0
|
[BUG] people-picker flyout in mgt-tasks opens of screen - <!-- Please make sure you are posting an issue pertaining to the Microsoft Graph Toolkit. -->
<!-- ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION. -->
**Describe the bug**
When using the people picker inside the mgt-tasks component, when starting to type, the flyout opens to the right of screen.
**To Reproduce**
Steps to reproduce the behavior:
1. Add mgt-tasks to the page and make sure it is set to planner
2. On a task, click on the assigned people and start typing to assign more people
3. Notice the suggested people flyout will not open under the people picker, but instead open off screen
**Expected behavior**
The people picker should open under (or over) the people picker
**Screenshots**
**Environment (please complete the following information):**
- OS: [e.g. iOS] Windows
- Browser [e.g. edge, chrome, safari] new Edge
- Framework [e.g. react, vue, none] none - also validated in Storybook
- Context [e.g. Microsoft Teams, SharePoint, Office Add-ins, Web]: web
- Version [e.g. 0.1]: latest
|
people
|
people picker flyout in mgt tasks opens of screen describe the bug when using the people picker inside the mgt tasks component when starting to type the flyout opens to the right of screen to reproduce steps to reproduce the behavior add mgt tasks to the page and make sure it is set to planner on a task click on the assigned people and start typing to assign more people notice the suggested people flyout will not open under the people picker but instead open off screen expected behavior the people picker should open under or over the people picker screenshots environment please complete the following information os windows browser new edge framework none also validated in storybook context web version latest
| 1
|
529
| 9,303,252,265
|
IssuesEvent
|
2019-03-24 16:07:56
|
JohnnySn0w/MoD
|
https://api.github.com/repos/JohnnySn0w/MoD
|
closed
|
Get access to dynamo web interface on host system
|
people and learning
|
Dynamo has a web interface, but we need to be able to access it on the host, so there should be some way to passthrough that connection.
|
1.0
|
Get access to dynamo web interface on host system - Dynamo has a web interface, but we need to be able to access it on the host, so there should be some way to passthrough that connection.
|
people
|
get access to dynamo web interface on host system dynamo has a web interface but we need to be able to access it on the host so there should be some way to passthrough that connection
| 1
|
48,503
| 5,961,203,531
|
IssuesEvent
|
2017-05-29 16:24:35
|
RachelDavids/RuleChecker
|
https://api.github.com/repos/RachelDavids/RuleChecker
|
closed
|
new rule ? redundant check
|
enhancement test case
|
code in screenshot was originally in release build - the Debug.Writeline call was eliminated so we had an isinst followed by pop - redundant
|
1.0
|
new rule ? redundant check - code in screenshot was originally in release build - the Debug.Writeline call was eliminated so we had an isinst followed by pop - redundant
|
non_people
|
new rule redundant check code in screenshot was originally in release build the debug writeline call was eliminated so we had an isinst followed by pop redundant
| 0
|
746
| 13,460,766,068
|
IssuesEvent
|
2020-09-09 14:00:55
|
planningcenter/developers
|
https://api.github.com/repos/planningcenter/developers
|
closed
|
502 Bad Gateway
|
People
|
**Affected Product**
Which product does this bug affect?
People
**Describe the bug**
Just recently, getting a series of 502 Bad Gateway across our live application when trying to get a response from planning center to attach a file to person.
System.Net.Http.HttpRequestException: Response status code does not indicate success: 502 (Bad Gateway).
Stack Trace:
HttpResponseMessage.EnsureSuccessStatusCode()
<UploadAndAttachPortraitFile>d__18.MoveNext() line 560
--- End of stack trace from previous location where exception was thrown ---
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
TaskAwaiter.GetResult()
<TestUploadFileAndAttachToPerson>d__17.MoveNext() line 496
--- End of stack trace from previous location where exception was thrown ---
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
TaskAwaiter.GetResult()
**Expected behavior**
Get a successful response from planning center.
## I have..
- [x] Reviewed the documentation found at https://developer.planning.center/docs
- [x] Searched for previous issues reporting this bug
- [x] Removed all private information from this issue (credentials, tokens, emails, phone numbers, etc.)
- [x] Reviewed my issue for completeness
|
1.0
|
502 Bad Gateway - **Affected Product**
Which product does this bug affect?
People
**Describe the bug**
Just recently, getting a series of 502 Bad Gateway across our live application when trying to get a response from planning center to attach a file to person.
System.Net.Http.HttpRequestException: Response status code does not indicate success: 502 (Bad Gateway).
Stack Trace:
HttpResponseMessage.EnsureSuccessStatusCode()
<UploadAndAttachPortraitFile>d__18.MoveNext() line 560
--- End of stack trace from previous location where exception was thrown ---
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
TaskAwaiter.GetResult()
<TestUploadFileAndAttachToPerson>d__17.MoveNext() line 496
--- End of stack trace from previous location where exception was thrown ---
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
TaskAwaiter.GetResult()
**Expected behavior**
Get a successful response from planning center.
## I have..
- [x] Reviewed the documentation found at https://developer.planning.center/docs
- [x] Searched for previous issues reporting this bug
- [x] Removed all private information from this issue (credentials, tokens, emails, phone numbers, etc.)
- [x] Reviewed my issue for completeness
|
people
|
bad gateway affected product which product does this bug affect people describe the bug just recently getting a series of bad gateway across our live application when trying to get a response from planning center to attach a file to person system net http httprequestexception response status code does not indicate success bad gateway stack trace httpresponsemessage ensuresuccessstatuscode d movenext line end of stack trace from previous location where exception was thrown taskawaiter throwfornonsuccess task task taskawaiter handlenonsuccessanddebuggernotification task task taskawaiter getresult d movenext line end of stack trace from previous location where exception was thrown taskawaiter throwfornonsuccess task task taskawaiter handlenonsuccessanddebuggernotification task task taskawaiter getresult expected behavior get a successful response from planning center i have reviewed the documentation found at searched for previous issues reporting this bug removed all private information from this issue credentials tokens emails phone numbers etc reviewed my issue for completeness
| 1
|
78
| 3,316,455,601
|
IssuesEvent
|
2015-11-06 16:58:11
|
Princeton-CDH/mapping-expatriate-paris
|
https://api.github.com/repos/Princeton-CDH/mapping-expatriate-paris
|
closed
|
Bernheim Card
|
not in personography two people merged in one card folder
|
Mme. Antoinette also present on s4: Françoise's sister?
Also, s17 and s20-22 are attributed to PROT, Alina
She appears to live next door to F. Bernheim (81 - 83 rue de Lille)
|
1.0
|
Bernheim Card - Mme. Antoinette also present on s4: Françoise's sister?
Also, s17 and s20-22 are attributed to PROT, Alina
She appears to live next door to F. Bernheim (81 - 83 rue de Lille)
|
people
|
bernheim card mme antoinette also present on françoise s sister also and are attributed to prot alina she appears to live next door to f bernheim rue de lille
| 1
|
287,598
| 8,817,169,003
|
IssuesEvent
|
2018-12-30 20:14:24
|
NaomiProject/Naomi
|
https://api.github.com/repos/NaomiProject/Naomi
|
closed
|
Coveralls & Codacy Badges
|
Priority: Low Status: Completed Type: Maintenance
|
<!--- Provide a general summary of the issue in the Title above -->
## Description
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
Remove coveralls since it is no longer integrated, as well as fix the codacy badge to reflect what it actually is.
## Expected Behavior
<!--- Tell us what should happen -->
Readme to be up to date
## Actual Behavior
<!--- Tell us what happens instead -->
Readme badges are out of date
## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
Just remove the coveralls <a> tag and replace codacy hyperlinks to the correct links
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
Not Relevant...
## Context
<!--- How has this bug affected you? What were you trying to accomplish? -->
Wanting an always current readme.
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
Not Relevant...
|
1.0
|
Coveralls & Codacy Badges - <!--- Provide a general summary of the issue in the Title above -->
## Description
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
Remove coveralls since it is no longer integrated, as well as fix the codacy badge to reflect what it actually is.
## Expected Behavior
<!--- Tell us what should happen -->
Readme to be up to date
## Actual Behavior
<!--- Tell us what happens instead -->
Readme badges are out of date
## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
Just remove the coveralls <a> tag and replace codacy hyperlinks to the correct links
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
Not Relevant...
## Context
<!--- How has this bug affected you? What were you trying to accomplish? -->
Wanting an always current readme.
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
Not Relevant...
|
non_people
|
coveralls codacy badges description remove coveralls since it is no longer integrated as well as fix the codacy badge to reflect what it actually is expected behavior readme to be up to date actual behavior readme badges are out of date possible fix just remove the coveralls tag and replace codacy hyperlinks to the correct links steps to reproduce not relevant context wanting an always current readme your environment not relevant
| 0
|
669
| 11,923,587,421
|
IssuesEvent
|
2020-04-01 08:06:39
|
Crevette/Test
|
https://api.github.com/repos/Crevette/Test
|
opened
|
Migration ECM Staging-EU - 20.4
|
DB - peopleask Deployment Env - staging-eu
|
Could you deploy the 20.4 version of the SQL for ECM on Staging-EU. Thank you !
|
1.0
|
Migration ECM Staging-EU - 20.4 - Could you deploy the 20.4 version of the SQL for ECM on Staging-EU. Thank you !
|
people
|
migration ecm staging eu could you deploy the version of the sql for ecm on staging eu thank you
| 1
|
224,178
| 17,669,463,232
|
IssuesEvent
|
2021-08-23 02:29:40
|
woodruffw/mollusc
|
https://api.github.com/repos/woodruffw/mollusc
|
opened
|
Randomized testing with `llvm-stress`
|
C:bitstream C:mapper testing
|
Opening this issue so I remember to do it.
The CI should generate a decent number of test inputs using `llvm-stress` and feed them into both the bitstream parser and the higher-level mapping components (once the latter is finished). That'll improve (my) confidence in both levels.
|
1.0
|
Randomized testing with `llvm-stress` - Opening this issue so I remember to do it.
The CI should generate a decent number of test inputs using `llvm-stress` and feed them into both the bitstream parser and the higher-level mapping components (once the latter is finished). That'll improve (my) confidence in both levels.
|
non_people
|
randomized testing with llvm stress opening this issue so i remember to do it the ci should generate a decent number of test inputs using llvm stress and feed them into both the bitstream parser and the higher level mapping components once the latter is finished that ll improve my confidence in both levels
| 0
|
296
| 5,613,622,444
|
IssuesEvent
|
2017-04-03 09:48:17
|
PopulateTools/gobierto
|
https://api.github.com/repos/PopulateTools/gobierto
|
closed
|
Events political group filters
|
gobierto-people
|
There are a few issues related with events political groups filters:
1. calendar events should be filterd by the political group. Example: in a site without directives, if I filter in the events page the calendar shows past and future events but the list of events in the main column is empty.
2. when I'm in the filter "Past Events" and I click into another political group filter this filter should be maintained. Right now, it changes to "Future events"
3. people list should be filterd by the political group. Right now in that list I can see everybody in the list
|
1.0
|
Events political group filters - There are a few issues related with events political groups filters:
1. calendar events should be filterd by the political group. Example: in a site without directives, if I filter in the events page the calendar shows past and future events but the list of events in the main column is empty.
2. when I'm in the filter "Past Events" and I click into another political group filter this filter should be maintained. Right now, it changes to "Future events"
3. people list should be filterd by the political group. Right now in that list I can see everybody in the list
|
people
|
events political group filters there are a few issues related with events political groups filters calendar events should be filterd by the political group example in a site without directives if i filter in the events page the calendar shows past and future events but the list of events in the main column is empty when i m in the filter past events and i click into another political group filter this filter should be maintained right now it changes to future events people list should be filterd by the political group right now in that list i can see everybody in the list
| 1
|
124
| 3,575,192,918
|
IssuesEvent
|
2016-01-27 15:08:18
|
Automattic/wp-calypso
|
https://api.github.com/repos/Automattic/wp-calypso
|
opened
|
People: Accepting a follower invitation doesn't respect the default delivery settings
|
People Management [Type] Bug
|
When you follow a site, your delivery settings for notifications from that site should match your Default Email Delivery setting here: https://wordpress.com/me/notifications/subscriptions
I confirmed that when I follow a site normally, my default delivery settings are respected. However, if I am invited to follow a site, after I accept the invitation the site is always set to delivery instant email notifications.
Steps to reproduce:
1. On a test account, set your Default Email Delivery setting to something other than "Send email instantly"
2. From your account, send an invitation to the test account to follow a public blog
3. Accept the invitation from your test account
4. Check your notification settings for the followed site at https://wordpress.com/following/edit
Result: The "Emails for new posts" setting is always enabled, with instant notifications selected
|
1.0
|
People: Accepting a follower invitation doesn't respect the default delivery settings - When you follow a site, your delivery settings for notifications from that site should match your Default Email Delivery setting here: https://wordpress.com/me/notifications/subscriptions
I confirmed that when I follow a site normally, my default delivery settings are respected. However, if I am invited to follow a site, after I accept the invitation the site is always set to delivery instant email notifications.
Steps to reproduce:
1. On a test account, set your Default Email Delivery setting to something other than "Send email instantly"
2. From your account, send an invitation to the test account to follow a public blog
3. Accept the invitation from your test account
4. Check your notification settings for the followed site at https://wordpress.com/following/edit
Result: The "Emails for new posts" setting is always enabled, with instant notifications selected
|
people
|
people accepting a follower invitation doesn t respect the default delivery settings when you follow a site your delivery settings for notifications from that site should match your default email delivery setting here i confirmed that when i follow a site normally my default delivery settings are respected however if i am invited to follow a site after i accept the invitation the site is always set to delivery instant email notifications steps to reproduce on a test account set your default email delivery setting to something other than send email instantly from your account send an invitation to the test account to follow a public blog accept the invitation from your test account check your notification settings for the followed site at result the emails for new posts setting is always enabled with instant notifications selected
| 1
|
443,554
| 30,923,434,345
|
IssuesEvent
|
2023-08-06 07:22:46
|
PyPSA/pypsa-eur
|
https://api.github.com/repos/PyPSA/pypsa-eur
|
closed
|
Document existing and planned validation
|
help wanted documentation
|
PyPSA-Eur(-Sec) can be validated against historical data about the energy system to see if it reproduces energy balances, energy prices, import/export flows, curtailment, redispatch and various other energy system statistics. Several validations have already been done, and some are planned. The different validations should be collected here, and then added to a new page "Validation" in the [documentation for PyPSA-Eur](https://pypsa-eur.readthedocs.io/en/latest/). Since PyPSA-Eur-Sec will be [merged into PyPSA-Eur](https://github.com/PyPSA/pypsa-eur/issues/463), we include issues affected other energy sectors too.
## Existing validation
- [PyPSA-Eur paper](https://arxiv.org/abs/1806.01613) includes validation of circuit lengths, network topology and matching of load to grid (looking at load shedding)
- @martacki [paper validating historical curtailment in German transmission network](https://arxiv.org/abs/2009.03801)
- validation of historical redispatch in Germany by ETH Zürich group (in Willem Laumen Master thesis)
- some validation of curtailment in [DLR paper](https://arxiv.org/abs/2208.04716) by @FabianHofmann and @p-glaum
- [validation by Freiburg group](https://freidok.uni-freiburg.de/data/227624) by Freddie, Mirko and Anke, for import/export flows and load distribution
- @matteodefelice [modelling of European system with ENTSO-E data (no PyPSA-Eur)](https://www.matteodefelice.name/post/pypsa-entsoe/), including price time series where peaks are missed (probably because of missing unit commitment)
## Ongoing and planned validation
- [Validation of power system against 2019](https://github.com/PyPSA/pypsa-eur/issues/363) - should include electricity price time series with linearised unit commitment, ramping, CO2 certificate price time series from historical, heat-led CHP and updated varied efficiencies of gas plants
- [Improved differentiation of vehicle types in transport model in PyPSA-Eur-Sec](https://github.com/PyPSA/pypsa-eur/issues/491)
- [Improved spatial distribution of district heating, particularly in Germany](https://github.com/PyPSA/pypsa-eur/issues/490)
- Improved development of RE over 2020-2050 (e.g. going from existing power plants to those with higher hub height, smaller generator to rotor ratio and larger size for wind, and axis tracking for PV with lower AC-DC ratio)
- Comparison of network impedances with [Core FBMC model](https://www.jao.eu/core-fb-mc), see @fneum [Core TSO project](https://github.com/fneum/core-tso-data)
- Redispatch again following [SciGRID redispatch example](https://pypsa.readthedocs.io/en/latest/examples/scigrid-redispatch.html)
- Comparison with [CORE grid model](https://www.jao.eu/static-grid-model) and OSM from PyPSA-Earth
- [TYNDP projects PR](https://github.com/PyPSA/pypsa-eur/pull/626) from @grecht
|
1.0
|
Document existing and planned validation - PyPSA-Eur(-Sec) can be validated against historical data about the energy system to see if it reproduces energy balances, energy prices, import/export flows, curtailment, redispatch and various other energy system statistics. Several validations have already been done, and some are planned. The different validations should be collected here, and then added to a new page "Validation" in the [documentation for PyPSA-Eur](https://pypsa-eur.readthedocs.io/en/latest/). Since PyPSA-Eur-Sec will be [merged into PyPSA-Eur](https://github.com/PyPSA/pypsa-eur/issues/463), we include issues affected other energy sectors too.
## Existing validation
- [PyPSA-Eur paper](https://arxiv.org/abs/1806.01613) includes validation of circuit lengths, network topology and matching of load to grid (looking at load shedding)
- @martacki [paper validating historical curtailment in German transmission network](https://arxiv.org/abs/2009.03801)
- validation of historical redispatch in Germany by ETH Zürich group (in Willem Laumen Master thesis)
- some validation of curtailment in [DLR paper](https://arxiv.org/abs/2208.04716) by @FabianHofmann and @p-glaum
- [validation by Freiburg group](https://freidok.uni-freiburg.de/data/227624) by Freddie, Mirko and Anke, for import/export flows and load distribution
- @matteodefelice [modelling of European system with ENTSO-E data (no PyPSA-Eur)](https://www.matteodefelice.name/post/pypsa-entsoe/), including price time series where peaks are missed (probably because of missing unit commitment)
## Ongoing and planned validation
- [Validation of power system against 2019](https://github.com/PyPSA/pypsa-eur/issues/363) - should include electricity price time series with linearised unit commitment, ramping, CO2 certificate price time series from historical, heat-led CHP and updated varied efficiencies of gas plants
- [Improved differentiation of vehicle types in transport model in PyPSA-Eur-Sec](https://github.com/PyPSA/pypsa-eur/issues/491)
- [Improved spatial distribution of district heating, particularly in Germany](https://github.com/PyPSA/pypsa-eur/issues/490)
- Improved development of RE over 2020-2050 (e.g. going from existing power plants to those with higher hub height, smaller generator to rotor ratio and larger size for wind, and axis tracking for PV with lower AC-DC ratio)
- Comparison of network impedances with [Core FBMC model](https://www.jao.eu/core-fb-mc), see @fneum [Core TSO project](https://github.com/fneum/core-tso-data)
- Redispatch again following [SciGRID redispatch example](https://pypsa.readthedocs.io/en/latest/examples/scigrid-redispatch.html)
- Comparison with [CORE grid model](https://www.jao.eu/static-grid-model) and OSM from PyPSA-Earth
- [TYNDP projects PR](https://github.com/PyPSA/pypsa-eur/pull/626) from @grecht
|
non_people
|
document existing and planned validation pypsa eur sec can be validated against historical data about the energy system to see if it reproduces energy balances energy prices import export flows curtailment redispatch and various other energy system statistics several validations have already been done and some are planned the different validations should be collected here and then added to a new page validation in the since pypsa eur sec will be we include issues affected other energy sectors too existing validation includes validation of circuit lengths network topology and matching of load to grid looking at load shedding martacki validation of historical redispatch in germany by eth zürich group in willem laumen master thesis some validation of curtailment in by fabianhofmann and p glaum by freddie mirko and anke for import export flows and load distribution matteodefelice including price time series where peaks are missed probably because of missing unit commitment ongoing and planned validation should include electricity price time series with linearised unit commitment ramping certificate price time series from historical heat led chp and updated varied efficiencies of gas plants improved development of re over e g going from existing power plants to those with higher hub height smaller generator to rotor ratio and larger size for wind and axis tracking for pv with lower ac dc ratio comparison of network impedances with see fneum redispatch again following comparison with and osm from pypsa earth from grecht
| 0
|
1,082
| 26,367,396,461
|
IssuesEvent
|
2023-01-11 17:38:10
|
openstates/issues
|
https://api.github.com/repos/openstates/issues
|
opened
|
New MS Committee Scraper
|
good first issue component:people-data good first scraper
|
### We need a new committee scraper written in [spatula](https://jamesturk.github.io/spatula/) for Mississippi.
It should scrape this [webpage for Senate Committees](http://www.legislature.ms.gov/committees/senate-committees/) and this [webpage for House Committees](http://www.legislature.ms.gov/committees/house-committees/) to get:
- **name**
- “Small Business”, “Agriculture”, etc.
- **chamber**
- “upper”, “lower”, or “legislature” (when joint, etc.)
- **classification**
- ex: "committee", "subcommittee"
- **parent**
- *only if it is a subcommittee* - scraper should have a way to determine this
- ex: parent="Natural Resources" when *sub*committee name="Forestry"
- **sources**
- each added using `add_source()` method on instance of `ScrapeCommittee` type object
- ex: home page for list of committees, specific page for that committee, etc.
- **members**
- - each added using `add_member()`method on instance of `ScrapeCommittee` type object
- *Attributes:*
- **name**: “Jane Doe”, “John Smith”, etc.
- **role** (where applicable): “Chair”, “Ranking Member”, etc.
#### [Here is helpful documentation](https://docs.openstates.org/contributing/writing-a-committee-scraper/) for writing a committee scraper
### Useful scrapers for reference
An [old non-spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers/ms/committees.py) that may be helpful in understanding how we have captured the data in the past.
A [spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers_next/nd/people.py) that also scrapes an HTML List Page (using HtmlListPage and HtmlPage spatula classes) for reference.
- *Note: due to simplicity of this page, you'll only need either HtmlListPage or HtmlPage, not both. Also, the bold (`<b>`) tags will be your best friend on this one.*
- As in the other spatula scraper, you will need to set the session variable separately (rather than depend on the `__init__.py`).
### Other useful resources
You can reference the [object models for committee scrapers](https://github.com/openstates/openstates-core/blob/main/openstates/models/committees.py) in the Open States Core repo.
Further documentation on running spatula scrapers in the command line can be found [here](https://docs.openstates.org/contributing/scrapers/#running-spatula-scrapers).
|
1.0
|
New MS Committee Scraper - ### We need a new committee scraper written in [spatula](https://jamesturk.github.io/spatula/) for Mississippi.
It should scrape this [webpage for Senate Committees](http://www.legislature.ms.gov/committees/senate-committees/) and this [webpage for House Committees](http://www.legislature.ms.gov/committees/house-committees/) to get:
- **name**
- “Small Business”, “Agriculture”, etc.
- **chamber**
- “upper”, “lower”, or “legislature” (when joint, etc.)
- **classification**
- ex: "committee", "subcommittee"
- **parent**
- *only if it is a subcommittee* - scraper should have a way to determine this
- ex: parent="Natural Resources" when *sub*committee name="Forestry"
- **sources**
- each added using `add_source()` method on instance of `ScrapeCommittee` type object
- ex: home page for list of committees, specific page for that committee, etc.
- **members**
- - each added using `add_member()`method on instance of `ScrapeCommittee` type object
- *Attributes:*
- **name**: “Jane Doe”, “John Smith”, etc.
- **role** (where applicable): “Chair”, “Ranking Member”, etc.
#### [Here is helpful documentation](https://docs.openstates.org/contributing/writing-a-committee-scraper/) for writing a committee scraper
### Useful scrapers for reference
An [old non-spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers/ms/committees.py) that may be helpful in understanding how we have captured the data in the past.
A [spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers_next/nd/people.py) that also scrapes an HTML List Page (using HtmlListPage and HtmlPage spatula classes) for reference.
- *Note: due to simplicity of this page, you'll only need either HtmlListPage or HtmlPage, not both. Also, the bold (`<b>`) tags will be your best friend on this one.*
- As in the other spatula scraper, you will need to set the session variable separately (rather than depend on the `__init__.py`).
### Other useful resources
You can reference the [object models for committee scrapers](https://github.com/openstates/openstates-core/blob/main/openstates/models/committees.py) in the Open States Core repo.
Further documentation on running spatula scrapers in the command line can be found [here](https://docs.openstates.org/contributing/scrapers/#running-spatula-scrapers).
|
people
|
new ms committee scraper we need a new committee scraper written in for mississippi it should scrape this and this to get name “small business” “agriculture” etc chamber “upper” “lower” or “legislature” when joint etc classification ex committee subcommittee parent only if it is a subcommittee scraper should have a way to determine this ex parent natural resources when sub committee name forestry sources each added using add source method on instance of scrapecommittee type object ex home page for list of committees specific page for that committee etc members each added using add member method on instance of scrapecommittee type object attributes name “jane doe” “john smith” etc role where applicable “chair” “ranking member” etc for writing a committee scraper useful scrapers for reference an that may be helpful in understanding how we have captured the data in the past a that also scrapes an html list page using htmllistpage and htmlpage spatula classes for reference note due to simplicity of this page you ll only need either htmllistpage or htmlpage not both also the bold tags will be your best friend on this one as in the other spatula scraper you will need to set the session variable separately rather than depend on the init py other useful resources you can reference the in the open states core repo further documentation on running spatula scrapers in the command line can be found
| 1
|
352
| 6,673,432,014
|
IssuesEvent
|
2017-10-04 15:03:12
|
PopulateTools/gobierto
|
https://api.github.com/repos/PopulateTools/gobierto
|
opened
|
Allow an admin user to edit only specific People
|
gobierto-admin gobierto-people
|
- [ ] Markup
- [ ] Implementation (define tasks)
|
1.0
|
Allow an admin user to edit only specific People - - [ ] Markup
- [ ] Implementation (define tasks)
|
people
|
allow an admin user to edit only specific people markup implementation define tasks
| 1
|
47,788
| 2,985,234,924
|
IssuesEvent
|
2015-07-18 20:41:59
|
uwdata/vega-lite
|
https://api.github.com/repos/uwdata/vega-lite
|
closed
|
Binning Bug
|
Priority/1-Critical
|
Somehow binned scale was now weirdly sorted.
I tried to fix with `sort:true` but that makes vertical bin axes incorrect.
I will probably need to apply `reverse:true`, but I remember that it was broken earlier.
|
1.0
|
Binning Bug - Somehow binned scale was now weirdly sorted.
I tried to fix with `sort:true` but that makes vertical bin axes incorrect.
I will probably need to apply `reverse:true`, but I remember that it was broken earlier.
|
non_people
|
binning bug somehow binned scale was now weirdly sorted i tried to fix with sort true but that makes vertical bin axes incorrect i will probably need to apply reverse true but i remember that it was broken earlier
| 0
|
1,101
| 26,813,721,823
|
IssuesEvent
|
2023-02-02 01:29:26
|
openstates/issues
|
https://api.github.com/repos/openstates/issues
|
closed
|
New UT Committee Scraper
|
good first issue component:people-data good first scraper
|
### We need a new committee scraper written in [spatula](https://jamesturk.github.io/spatula/) for Utah.
*Helpful note: Chamber-specific committee names start with "House" or "Senate"; all others are joint.*
It should scrape this [JSON webpage of House, Senate, and Joint Committees](https://le.utah.gov/data/committees.json) to get:
- **name**
- “Small Business”, “Agriculture”, etc.
- **chamber**
- “upper”, “lower”, or “legislature” (when joint, etc.)
- **classification**
- ex: "committee", "subcommittee"
- **parent**
- *only if it is a subcommittee* - scraper should have a way to determine this
- ex: parent="Natural Resources" when *sub*committee name="Forestry"
- **sources**
- each added using `add_source()` method on instance of `ScrapeCommittee` type object
- ex: home page for list of committees, specific page for that committee, etc.
- **members**
- - each added using `add_member()`method on instance of `ScrapeCommittee` type object
- *Attributes:*
- **name**: “Jane Doe”, “John Smith”, etc.
- **role** (where applicable): “Chair”, “Ranking Member”, etc.
#### [Here is helpful documentation](https://docs.openstates.org/contributing/writing-a-committee-scraper/) for writing a committee scraper
### Useful scrapers for reference
An [old non-spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers/ut/committees.py) that may be helpful in understanding how we have captured the data in the past.
A [spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers_next/ga/committees.py) that also parses a JSON page for reference.
- As in the other spatula scraper, you will need to set the session variable separately (rather than depend on the `__init__.py`).
### Other useful resources
You can reference the [object models for committee scrapers](https://github.com/openstates/openstates-core/blob/main/openstates/models/committees.py) in the Open States Core repo.
Further documentation on running spatula scrapers in the command line can be found [here](https://docs.openstates.org/contributing/scrapers/#running-spatula-scrapers).
|
1.0
|
New UT Committee Scraper - ### We need a new committee scraper written in [spatula](https://jamesturk.github.io/spatula/) for Utah.
*Helpful note: Chamber-specific committee names start with "House" or "Senate"; all others are joint.*
It should scrape this [JSON webpage of House, Senate, and Joint Committees](https://le.utah.gov/data/committees.json) to get:
- **name**
- “Small Business”, “Agriculture”, etc.
- **chamber**
- “upper”, “lower”, or “legislature” (when joint, etc.)
- **classification**
- ex: "committee", "subcommittee"
- **parent**
- *only if it is a subcommittee* - scraper should have a way to determine this
- ex: parent="Natural Resources" when *sub*committee name="Forestry"
- **sources**
- each added using `add_source()` method on instance of `ScrapeCommittee` type object
- ex: home page for list of committees, specific page for that committee, etc.
- **members**
- - each added using `add_member()`method on instance of `ScrapeCommittee` type object
- *Attributes:*
- **name**: “Jane Doe”, “John Smith”, etc.
- **role** (where applicable): “Chair”, “Ranking Member”, etc.
#### [Here is helpful documentation](https://docs.openstates.org/contributing/writing-a-committee-scraper/) for writing a committee scraper
### Useful scrapers for reference
An [old non-spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers/ut/committees.py) that may be helpful in understanding how we have captured the data in the past.
A [spatula-based scraper](https://github.com/openstates/openstates-scrapers/blob/main/scrapers_next/ga/committees.py) that also parses a JSON page for reference.
- As in the other spatula scraper, you will need to set the session variable separately (rather than depend on the `__init__.py`).
### Other useful resources
You can reference the [object models for committee scrapers](https://github.com/openstates/openstates-core/blob/main/openstates/models/committees.py) in the Open States Core repo.
Further documentation on running spatula scrapers in the command line can be found [here](https://docs.openstates.org/contributing/scrapers/#running-spatula-scrapers).
|
people
|
new ut committee scraper we need a new committee scraper written in for utah helpful note chamber specific committee names start with house or senate all others are joint it should scrape this to get name “small business” “agriculture” etc chamber “upper” “lower” or “legislature” when joint etc classification ex committee subcommittee parent only if it is a subcommittee scraper should have a way to determine this ex parent natural resources when sub committee name forestry sources each added using add source method on instance of scrapecommittee type object ex home page for list of committees specific page for that committee etc members each added using add member method on instance of scrapecommittee type object attributes name “jane doe” “john smith” etc role where applicable “chair” “ranking member” etc for writing a committee scraper useful scrapers for reference an that may be helpful in understanding how we have captured the data in the past a that also parses a json page for reference as in the other spatula scraper you will need to set the session variable separately rather than depend on the init py other useful resources you can reference the in the open states core repo further documentation on running spatula scrapers in the command line can be found
| 1
|
40,866
| 6,875,139,440
|
IssuesEvent
|
2017-11-19 10:08:31
|
react-community/react-navigation
|
https://api.github.com/repos/react-community/react-navigation
|
closed
|
CardStack docs or examples
|
7 days countdown documentation question
|
I searched through the examples and documentation, and can't find any examples of CardStack usage. I'm trying to upgrade the `@shoutem/ui` library to pull the CardStack and Card components from this library, since they were deprecated and moved from NavigationExperimental, but can't find any documentation or examples on which to base it on (which would be OK if the API hadn't changed). Could someone point me to a working example of CardStack?
Thanks!
|
1.0
|
CardStack docs or examples - I searched through the examples and documentation, and can't find any examples of CardStack usage. I'm trying to upgrade the `@shoutem/ui` library to pull the CardStack and Card components from this library, since they were deprecated and moved from NavigationExperimental, but can't find any documentation or examples on which to base it on (which would be OK if the API hadn't changed). Could someone point me to a working example of CardStack?
Thanks!
|
non_people
|
cardstack docs or examples i searched through the examples and documentation and can t find any examples of cardstack usage i m trying to upgrade the shoutem ui library to pull the cardstack and card components from this library since they were deprecated and moved from navigationexperimental but can t find any documentation or examples on which to base it on which would be ok if the api hadn t changed could someone point me to a working example of cardstack thanks
| 0
|
158,091
| 12,402,001,443
|
IssuesEvent
|
2020-05-21 11:02:04
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: acceptance/cli/node-status failed
|
C-test-failure O-roachtest O-robot branch-master release-blocker
|
[(roachtest).acceptance/cli/node-status failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=1944755&tab=buildLog) on [master@f66ff29e25bc546ee239867e316485528e11e3dc](https://github.com/cockroachdb/cockroach/commits/f66ff29e25bc546ee239867e316485528e11e3dc):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/cli/node-status/run_1
cluster.go:2138,cluster.go:2157,cluster.go:2261,cli.go:24,acceptance.go:94,test_runner.go:753: pgurl for nodes [] empty: :1 from
stdout:
stderr:
```
<details><summary>More</summary><p>
Artifacts: [/acceptance/cli/node-status](https://teamcity.cockroachdb.com/viewLog.html?buildId=1944755&tab=artifacts#/acceptance/cli/node-status)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aacceptance%2Fcli%2Fnode-status.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
2.0
|
roachtest: acceptance/cli/node-status failed - [(roachtest).acceptance/cli/node-status failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=1944755&tab=buildLog) on [master@f66ff29e25bc546ee239867e316485528e11e3dc](https://github.com/cockroachdb/cockroach/commits/f66ff29e25bc546ee239867e316485528e11e3dc):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/cli/node-status/run_1
cluster.go:2138,cluster.go:2157,cluster.go:2261,cli.go:24,acceptance.go:94,test_runner.go:753: pgurl for nodes [] empty: :1 from
stdout:
stderr:
```
<details><summary>More</summary><p>
Artifacts: [/acceptance/cli/node-status](https://teamcity.cockroachdb.com/viewLog.html?buildId=1944755&tab=artifacts#/acceptance/cli/node-status)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aacceptance%2Fcli%2Fnode-status.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
non_people
|
roachtest acceptance cli node status failed on the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts acceptance cli node status run cluster go cluster go cluster go cli go acceptance go test runner go pgurl for nodes empty from stdout stderr more artifacts powered by
| 0
|
378,488
| 26,322,867,812
|
IssuesEvent
|
2023-01-10 02:14:38
|
apache/arrow
|
https://api.github.com/repos/apache/arrow
|
closed
|
[Documentation] Add PR template
|
Type: enhancement Component: Documentation
|
### Describe the enhancement requested
See #15232
### Component(s)
Documentation
|
1.0
|
[Documentation] Add PR template - ### Describe the enhancement requested
See #15232
### Component(s)
Documentation
|
non_people
|
add pr template describe the enhancement requested see component s documentation
| 0
|
322,529
| 9,818,985,163
|
IssuesEvent
|
2019-06-13 20:42:24
|
mozilla/addons-frontend
|
https://api.github.com/repos/mozilla/addons-frontend
|
closed
|
Category buttons do not use proper palette
|
component: ux contrib: good first bug contrib: mentor assigned priority: p4 project: amo triaged type: papercut
|
The category buttons on the top level Extensions and Themes pages do not use the full palette provided.
Current:
<img width="1039" alt="screen shot 2017-10-20 at 3 09 08 pm" src="https://user-images.githubusercontent.com/6797635/31843604-d692264c-b5a8-11e7-9aea-7aa6ff25ea7b.png">
<img width="1039" alt="screen shot 2017-10-20 at 3 10 31 pm" src="https://user-images.githubusercontent.com/6797635/31843610-ea1d0646-b5a8-11e7-9540-5dc9d5abd5b8.png">
Mocks:
<img width="961" alt="screen shot 2017-10-20 at 3 09 18 pm" src="https://user-images.githubusercontent.com/6797635/31843619-f1ebbbd8-b5a8-11e7-8b40-0d067889cd6a.png">
<img width="956" alt="screen shot 2017-10-20 at 3 11 36 pm" src="https://user-images.githubusercontent.com/6797635/31843628-fe1963d8-b5a8-11e7-8743-4bb5cde34fc3.png">
Palette:
<img width="1343" alt="screen shot 2017-10-20 at 3 12 23 pm" src="https://user-images.githubusercontent.com/6797635/31843653-215a8b1a-b5a9-11e7-9f2a-95e9abdc45be.png">
<img width="1340" alt="screen shot 2017-10-20 at 3 12 33 pm" src="https://user-images.githubusercontent.com/6797635/31843655-2440d726-b5a9-11e7-9107-ba9f926c792e.png">
|
1.0
|
Category buttons do not use proper palette - The category buttons on the top level Extensions and Themes pages do not use the full palette provided.
Current:
<img width="1039" alt="screen shot 2017-10-20 at 3 09 08 pm" src="https://user-images.githubusercontent.com/6797635/31843604-d692264c-b5a8-11e7-9aea-7aa6ff25ea7b.png">
<img width="1039" alt="screen shot 2017-10-20 at 3 10 31 pm" src="https://user-images.githubusercontent.com/6797635/31843610-ea1d0646-b5a8-11e7-9540-5dc9d5abd5b8.png">
Mocks:
<img width="961" alt="screen shot 2017-10-20 at 3 09 18 pm" src="https://user-images.githubusercontent.com/6797635/31843619-f1ebbbd8-b5a8-11e7-8b40-0d067889cd6a.png">
<img width="956" alt="screen shot 2017-10-20 at 3 11 36 pm" src="https://user-images.githubusercontent.com/6797635/31843628-fe1963d8-b5a8-11e7-8743-4bb5cde34fc3.png">
Palette:
<img width="1343" alt="screen shot 2017-10-20 at 3 12 23 pm" src="https://user-images.githubusercontent.com/6797635/31843653-215a8b1a-b5a9-11e7-9f2a-95e9abdc45be.png">
<img width="1340" alt="screen shot 2017-10-20 at 3 12 33 pm" src="https://user-images.githubusercontent.com/6797635/31843655-2440d726-b5a9-11e7-9107-ba9f926c792e.png">
|
non_people
|
category buttons do not use proper palette the category buttons on the top level extensions and themes pages do not use the full palette provided current img width alt screen shot at pm src img width alt screen shot at pm src mocks img width alt screen shot at pm src img width alt screen shot at pm src palette img width alt screen shot at pm src img width alt screen shot at pm src
| 0
|
37,159
| 18,160,044,171
|
IssuesEvent
|
2021-09-27 08:34:52
|
ItJustWorksTM/EiffelVis
|
https://api.github.com/repos/ItJustWorksTM/EiffelVis
|
opened
|
lazy load graph
|
Performance Frontend
|
avoid load the entire graph at once. load the data as it comes to the viewport
|
True
|
lazy load graph - avoid load the entire graph at once. load the data as it comes to the viewport
|
non_people
|
lazy load graph avoid load the entire graph at once load the data as it comes to the viewport
| 0
|
638
| 11,431,436,429
|
IssuesEvent
|
2020-02-04 12:08:48
|
techtolentino/randytolentinocom
|
https://api.github.com/repos/techtolentino/randytolentinocom
|
opened
|
The Unoffical Leader
|
article people team
|
One can be exhibit leadership qualities without having the title
it's about the behavioral patterns and qualities of the individual
Companies need to spot these people and train them, because if they
already have a following, you, as a business, want to inherit that following.
Think of the upcoming generation of employees, consider how they communicate
how they behave. Think about social media and how it has _influencers_... then tie that back to your organization.
Who are your influencers, how do you, as a corporation, take these influencers
and have them help your business.
If there's one thing social media has taught us, is that people follow people they
relate to or aspire to be.
Look around you. Think about the people in your area that are the influencers
on your team. If they're inspiring others, if they're solving problems,
then you might be looking at your
next set of leaders.
Qualities
- caring for people in a holistic way, and understanding how that relates to the business
- they listen for needs across the team, growth wise, daily... it's the act of listening
- people go to them for advice
- they advocate for others, they help others shine, speak,
- transparency of failure, how they handle it, and how they show they've learned from it
- the art of feedback: seek, acknowledge, and learn from it
|
1.0
|
The Unoffical Leader - One can be exhibit leadership qualities without having the title
it's about the behavioral patterns and qualities of the individual
Companies need to spot these people and train them, because if they
already have a following, you, as a business, want to inherit that following.
Think of the upcoming generation of employees, consider how they communicate
how they behave. Think about social media and how it has _influencers_... then tie that back to your organization.
Who are your influencers, how do you, as a corporation, take these influencers
and have them help your business.
If there's one thing social media has taught us, is that people follow people they
relate to or aspire to be.
Look around you. Think about the people in your area that are the influencers
on your team. If they're inspiring others, if they're solving problems,
then you might be looking at your
next set of leaders.
Qualities
- caring for people in a holistic way, and understanding how that relates to the business
- they listen for needs across the team, growth wise, daily... it's the act of listening
- people go to them for advice
- they advocate for others, they help others shine, speak,
- transparency of failure, how they handle it, and how they show they've learned from it
- the art of feedback: seek, acknowledge, and learn from it
|
people
|
the unoffical leader one can be exhibit leadership qualities without having the title it s about the behavioral patterns and qualities of the individual companies need to spot these people and train them because if they already have a following you as a business want to inherit that following think of the upcoming generation of employees consider how they communicate how they behave think about social media and how it has influencers then tie that back to your organization who are your influencers how do you as a corporation take these influencers and have them help your business if there s one thing social media has taught us is that people follow people they relate to or aspire to be look around you think about the people in your area that are the influencers on your team if they re inspiring others if they re solving problems then you might be looking at your next set of leaders qualities caring for people in a holistic way and understanding how that relates to the business they listen for needs across the team growth wise daily it s the act of listening people go to them for advice they advocate for others they help others shine speak transparency of failure how they handle it and how they show they ve learned from it the art of feedback seek acknowledge and learn from it
| 1
|
End of preview. Expand
in Data Studio
- Downloads last month
- 17
Size of downloaded dataset files:
3.72 MB
Size of the auto-converted Parquet files:
3.72 MB
Number of rows:
2,020