Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 2
665
| labels
stringlengths 4
554
| body
stringlengths 3
235k
| index
stringclasses 6
values | text_combine
stringlengths 96
235k
| label
stringclasses 2
values | text
stringlengths 96
196k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
24,650
| 17,552,189,998
|
IssuesEvent
|
2021-08-13 00:10:51
|
scala-js/scala-js-dom
|
https://api.github.com/repos/scala-js/scala-js-dom
|
closed
|
GH Action Release fails
|
infrastructure
|
@armanbilge Release failed on the `series/v1.x` branch, seemingly cos of SJS 0.6.x. I know it's just SNAPSHOT release but if it doesn't work, pushing a v1.2.0 tag wont work either sadly.
https://github.com/scala-js/scala-js-dom/actions/runs/1125835306
|
1.0
|
GH Action Release fails - @armanbilge Release failed on the `series/v1.x` branch, seemingly cos of SJS 0.6.x. I know it's just SNAPSHOT release but if it doesn't work, pushing a v1.2.0 tag wont work either sadly.
https://github.com/scala-js/scala-js-dom/actions/runs/1125835306
|
infrastructure
|
gh action release fails armanbilge release failed on the series x branch seemingly cos of sjs x i know it s just snapshot release but if it doesn t work pushing a tag wont work either sadly
| 1
|
4,055
| 4,789,239,172
|
IssuesEvent
|
2016-10-30 23:27:34
|
dst-academy/docker-dontstarvetogether
|
https://api.github.com/repos/dst-academy/docker-dontstarvetogether
|
closed
|
Optimize repository names
|
enhancement infrastructure
|
For a better forking experience and better identification overall we should rename the repository before releasing the final version. In addition the Docker Hub name should be clearer.
Suggestions for GitHub:
- `dst-academy/dst-server-docker`
- `dst-academy/docker-dst-server`
- `dst-academy/dont-starve-together-docker`
Suggestions for Docker Hub:
- `dstacademy/dont-starve-together`
- `dstacademy/dont-starve-together-server`
- `dstacademy/dst-server`
|
1.0
|
Optimize repository names - For a better forking experience and better identification overall we should rename the repository before releasing the final version. In addition the Docker Hub name should be clearer.
Suggestions for GitHub:
- `dst-academy/dst-server-docker`
- `dst-academy/docker-dst-server`
- `dst-academy/dont-starve-together-docker`
Suggestions for Docker Hub:
- `dstacademy/dont-starve-together`
- `dstacademy/dont-starve-together-server`
- `dstacademy/dst-server`
|
infrastructure
|
optimize repository names for a better forking experience and better identification overall we should rename the repository before releasing the final version in addition the docker hub name should be clearer suggestions for github dst academy dst server docker dst academy docker dst server dst academy dont starve together docker suggestions for docker hub dstacademy dont starve together dstacademy dont starve together server dstacademy dst server
| 1
|
2,634
| 3,790,108,481
|
IssuesEvent
|
2016-03-21 20:17:49
|
elmsln/elmsln
|
https://api.github.com/repos/elmsln/elmsln
|
closed
|
support drush concurrency in elmsln-upgrade-sites
|
enhancement infrastructure scale / performance
|
server specs:
2 processors, 6 gigs of ram
php 5.6 mysql 5.5 opcache in place
drush has built in support for concurrency so that you can process multiple calls in a alias target. As elmsln's upgrade routine is built on @ elmsln which is a lazy loaded, very big alias grouping (of sub-groupings of sites) we could stand to run some of these in parallel to speed up the time this takes.
real world example: `drush rr @coruses-all` concurrency 1
```
real 15m44.714s
user 10m10.198s
sys 1m19.843s
```
real world example: `drush rr @coruses-all` concurrency 10
```
real 5m11.379s
user 7m16.322s
sys 0m54.630s
```
The cost of something like 10 might be too high though. in reviewing NR data during each run you can see how much the server suffered from this aggressive rebuilding call:
As we can see the server gets mad during the 10 concurrent window but not the 1 concurrency. Looking at memory / cpu:
Again here we see that the 10 concurrent balloons PHP memory and REALLY taxes its processing capabilities while 1 is almost unnoticed. Perhaps shooting for a value like 6 may help achieve a happy balance between speeding up the upgrade routine sweeps and ensuring the server doesn't get angry. We also could increase concurrency of SOME parts of the process / break up our current workflow in some areas; vsetting all sites to be offline for example, then run the updates concurrency 10, then , vset all back online, then drush rr 6, and the drup commands at 5. This could help achieve a balance of resource vs efficiency.
|
1.0
|
support drush concurrency in elmsln-upgrade-sites - server specs:
2 processors, 6 gigs of ram
php 5.6 mysql 5.5 opcache in place
drush has built in support for concurrency so that you can process multiple calls in a alias target. As elmsln's upgrade routine is built on @ elmsln which is a lazy loaded, very big alias grouping (of sub-groupings of sites) we could stand to run some of these in parallel to speed up the time this takes.
real world example: `drush rr @coruses-all` concurrency 1
```
real 15m44.714s
user 10m10.198s
sys 1m19.843s
```
real world example: `drush rr @coruses-all` concurrency 10
```
real 5m11.379s
user 7m16.322s
sys 0m54.630s
```
The cost of something like 10 might be too high though. in reviewing NR data during each run you can see how much the server suffered from this aggressive rebuilding call:
As we can see the server gets mad during the 10 concurrent window but not the 1 concurrency. Looking at memory / cpu:
Again here we see that the 10 concurrent balloons PHP memory and REALLY taxes its processing capabilities while 1 is almost unnoticed. Perhaps shooting for a value like 6 may help achieve a happy balance between speeding up the upgrade routine sweeps and ensuring the server doesn't get angry. We also could increase concurrency of SOME parts of the process / break up our current workflow in some areas; vsetting all sites to be offline for example, then run the updates concurrency 10, then , vset all back online, then drush rr 6, and the drup commands at 5. This could help achieve a balance of resource vs efficiency.
|
infrastructure
|
support drush concurrency in elmsln upgrade sites server specs processors gigs of ram php mysql opcache in place drush has built in support for concurrency so that you can process multiple calls in a alias target as elmsln s upgrade routine is built on elmsln which is a lazy loaded very big alias grouping of sub groupings of sites we could stand to run some of these in parallel to speed up the time this takes real world example drush rr coruses all concurrency real user sys real world example drush rr coruses all concurrency real user sys the cost of something like might be too high though in reviewing nr data during each run you can see how much the server suffered from this aggressive rebuilding call as we can see the server gets mad during the concurrent window but not the concurrency looking at memory cpu again here we see that the concurrent balloons php memory and really taxes its processing capabilities while is almost unnoticed perhaps shooting for a value like may help achieve a happy balance between speeding up the upgrade routine sweeps and ensuring the server doesn t get angry we also could increase concurrency of some parts of the process break up our current workflow in some areas vsetting all sites to be offline for example then run the updates concurrency then vset all back online then drush rr and the drup commands at this could help achieve a balance of resource vs efficiency
| 1
|
1,564
| 3,268,382,207
|
IssuesEvent
|
2015-10-23 11:07:22
|
dart-lang/sdk
|
https://api.github.com/repos/dart-lang/sdk
|
closed
|
Please merge revision 1a7528174263af0a95d7edf51c01a2b3d1b568ff into dev channel
|
Area-Infrastructure MergeToDev
|
@ricowind @whesse @kasperl
This fixes a constant evaluation bug which could cause an analyzer crash when analyzing code containing malformed constant expressions. See #24645.
Revision to be merged: 1a7528174263af0a95d7edf51c01a2b3d1b568ff
There is a minor merge conflict. I've uploaded a CL with the correct merge here: https://codereview.chromium.org/1415523003/
|
1.0
|
Please merge revision 1a7528174263af0a95d7edf51c01a2b3d1b568ff into dev channel - @ricowind @whesse @kasperl
This fixes a constant evaluation bug which could cause an analyzer crash when analyzing code containing malformed constant expressions. See #24645.
Revision to be merged: 1a7528174263af0a95d7edf51c01a2b3d1b568ff
There is a minor merge conflict. I've uploaded a CL with the correct merge here: https://codereview.chromium.org/1415523003/
|
infrastructure
|
please merge revision into dev channel ricowind whesse kasperl this fixes a constant evaluation bug which could cause an analyzer crash when analyzing code containing malformed constant expressions see revision to be merged there is a minor merge conflict i ve uploaded a cl with the correct merge here
| 1
|
31,587
| 25,903,311,165
|
IssuesEvent
|
2022-12-15 08:12:19
|
deckhouse/deckhouse
|
https://api.github.com/repos/deckhouse/deckhouse
|
opened
|
[cloud-provider-aws] Add disable_api_termination to master nodes
|
type/enhancement area/cluster-and-infrastructure source/internal-client status/needs-triage
|
### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/deckhouse/deckhouse/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://github.com/deckhouse/deckhouse/issues) for an issue that matches the one I want to file, without success.
### Use case. Why is this important?
There was a case when all control-plane nodes were accidentally removed from cluster by manual user action.
### Proposed Solution
Add `disable_api_termination` in terraform. But then we will have a problem with deleting control-plane vms using terraform. Maybe it's just better to add documentation how to do it using web interface.
### Additional Information
_No response_
|
1.0
|
[cloud-provider-aws] Add disable_api_termination to master nodes - ### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/deckhouse/deckhouse/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://github.com/deckhouse/deckhouse/issues) for an issue that matches the one I want to file, without success.
### Use case. Why is this important?
There was a case when all control-plane nodes were accidentally removed from cluster by manual user action.
### Proposed Solution
Add `disable_api_termination` in terraform. But then we will have a problem with deleting control-plane vms using terraform. Maybe it's just better to add documentation how to do it using web interface.
### Additional Information
_No response_
|
infrastructure
|
add disable api termination to master nodes preflight checklist i agree to follow the that this project adheres to i have searched the for an issue that matches the one i want to file without success use case why is this important there was a case when all control plane nodes were accidentally removed from cluster by manual user action proposed solution add disable api termination in terraform but then we will have a problem with deleting control plane vms using terraform maybe it s just better to add documentation how to do it using web interface additional information no response
| 1
|
12,373
| 9,753,863,178
|
IssuesEvent
|
2019-06-04 10:07:05
|
Altinn/altinn-studio
|
https://api.github.com/repos/Altinn/altinn-studio
|
closed
|
Set up load balancing for SBL Bridge
|
draft infrastructure sbl sbl-bridge team-steam team-tamagotchi user-story
|
**Functional architect/designer:** @-mention
**Technical architect:** @-mention
**Description**
The platform integration application should be loadbalanced between the portal servers in the test environment.
**Technical considerations**
- Which loadbalancer will we use?
- Should only be aviable internal
**Acceptance criterea**
- Only available from Altinn Studio Apps
**Tasks**
- [ ] Set up load balancing and updated scripts for load balancer
|
1.0
|
Set up load balancing for SBL Bridge - **Functional architect/designer:** @-mention
**Technical architect:** @-mention
**Description**
The platform integration application should be loadbalanced between the portal servers in the test environment.
**Technical considerations**
- Which loadbalancer will we use?
- Should only be aviable internal
**Acceptance criterea**
- Only available from Altinn Studio Apps
**Tasks**
- [ ] Set up load balancing and updated scripts for load balancer
|
infrastructure
|
set up load balancing for sbl bridge functional architect designer mention technical architect mention description the platform integration application should be loadbalanced between the portal servers in the test environment technical considerations which loadbalancer will we use should only be aviable internal acceptance criterea only available from altinn studio apps tasks set up load balancing and updated scripts for load balancer
| 1
|
6,217
| 6,258,907,792
|
IssuesEvent
|
2017-07-14 16:43:12
|
servo/servo
|
https://api.github.com/repos/servo/servo
|
closed
|
Add tidy to support crates' CI
|
A-infrastructure B-meta
|
Superseding https://github.com/servo/servo/issues/861
- [ ] set up CI to automatically deploy new tidy versions to pypi when the source is changed
- [ ] Update list of all support crates and add it here
- [ ] check whether tidy is run by their CI and add it if not
|
1.0
|
Add tidy to support crates' CI - Superseding https://github.com/servo/servo/issues/861
- [ ] set up CI to automatically deploy new tidy versions to pypi when the source is changed
- [ ] Update list of all support crates and add it here
- [ ] check whether tidy is run by their CI and add it if not
|
infrastructure
|
add tidy to support crates ci superseding set up ci to automatically deploy new tidy versions to pypi when the source is changed update list of all support crates and add it here check whether tidy is run by their ci and add it if not
| 1
|
11,804
| 9,430,400,017
|
IssuesEvent
|
2019-04-12 08:56:38
|
vsechnovcloudu/chaosgunsonline
|
https://api.github.com/repos/vsechnovcloudu/chaosgunsonline
|
opened
|
Containerization and deployment of server
|
infrastructure
|
Dockerfile ready, but we need to deploy it somewhere.
Proposal: AWS Fargate
|
1.0
|
Containerization and deployment of server - Dockerfile ready, but we need to deploy it somewhere.
Proposal: AWS Fargate
|
infrastructure
|
containerization and deployment of server dockerfile ready but we need to deploy it somewhere proposal aws fargate
| 1
|
20,404
| 3,812,082,739
|
IssuesEvent
|
2016-03-27 09:29:49
|
QualiSystems/vCenterShell
|
https://api.github.com/repos/QualiSystems/vCenterShell
|
closed
|
Delete a resource that is endpoint of a CVC - vlan is held in vlan pool till reservation ends
|
bug Connectivity P2 ready to test
|
### Issue details
Delete resource that is part of active P2P connection such that its VLAN should be released.
VLAN is still held in Vlan Items table until reservation ends, if delete VM resource (not remove, but delete through client or API)
### Steps to reproduce
Have a P2P connection between two apps. Connect.
Now delete one of the VMs in resource explorer or through API.
Now check if VlanItems table has released the row for this vlan.
If not, bug reproduces.
### Affected versions:
vCenterShell version _Please fill in affected version_
CloudShell version _Please fill in affected version_
### Affected platforms
- [ ] Virtual Environment
_Please fill additional environment specific configuration_
|
1.0
|
Delete a resource that is endpoint of a CVC - vlan is held in vlan pool till reservation ends - ### Issue details
Delete resource that is part of active P2P connection such that its VLAN should be released.
VLAN is still held in Vlan Items table until reservation ends, if delete VM resource (not remove, but delete through client or API)
### Steps to reproduce
Have a P2P connection between two apps. Connect.
Now delete one of the VMs in resource explorer or through API.
Now check if VlanItems table has released the row for this vlan.
If not, bug reproduces.
### Affected versions:
vCenterShell version _Please fill in affected version_
CloudShell version _Please fill in affected version_
### Affected platforms
- [ ] Virtual Environment
_Please fill additional environment specific configuration_
|
non_infrastructure
|
delete a resource that is endpoint of a cvc vlan is held in vlan pool till reservation ends issue details delete resource that is part of active connection such that its vlan should be released vlan is still held in vlan items table until reservation ends if delete vm resource not remove but delete through client or api steps to reproduce have a connection between two apps connect now delete one of the vms in resource explorer or through api now check if vlanitems table has released the row for this vlan if not bug reproduces affected versions vcentershell version please fill in affected version cloudshell version please fill in affected version affected platforms virtual environment please fill additional environment specific configuration
| 0
|
11,357
| 9,115,980,832
|
IssuesEvent
|
2019-02-22 07:28:58
|
radare/radare2
|
https://api.github.com/repos/radare/radare2
|
opened
|
Automate merging easy and test-passing pull requests
|
infrastructure question
|
For example if all tests are passing, coverage is not decreased, amount of changes is not big, PR was reviewed, it can merge automatically.
There is a bot for that:
https://mergify.io/
https://github.com/apps/mergify
|
1.0
|
Automate merging easy and test-passing pull requests - For example if all tests are passing, coverage is not decreased, amount of changes is not big, PR was reviewed, it can merge automatically.
There is a bot for that:
https://mergify.io/
https://github.com/apps/mergify
|
infrastructure
|
automate merging easy and test passing pull requests for example if all tests are passing coverage is not decreased amount of changes is not big pr was reviewed it can merge automatically there is a bot for that
| 1
|
31,769
| 26,107,086,998
|
IssuesEvent
|
2022-12-27 14:33:22
|
treeverse/lakeFS
|
https://api.github.com/repos/treeverse/lakeFS
|
closed
|
RouterFS: should we use "provided" for hadoop- dependencies?
|
infrastructure area/client/spark team/ecosystem
|
In RouterFS:
- Check if it makes sense to use provided dependencies.
- If we use provided, how do we compile?
- ~For hadoopFs~ and RouterFS (lower priority)
EDIT: was already done for HadoopFS (#4357)
|
1.0
|
RouterFS: should we use "provided" for hadoop- dependencies? - In RouterFS:
- Check if it makes sense to use provided dependencies.
- If we use provided, how do we compile?
- ~For hadoopFs~ and RouterFS (lower priority)
EDIT: was already done for HadoopFS (#4357)
|
infrastructure
|
routerfs should we use provided for hadoop dependencies in routerfs check if it makes sense to use provided dependencies if we use provided how do we compile for hadoopfs and routerfs lower priority edit was already done for hadoopfs
| 1
|
344,889
| 10,349,714,597
|
IssuesEvent
|
2019-09-04 23:36:23
|
oslc-op/oslc-specs
|
https://api.github.com/repos/oslc-op/oslc-specs
|
opened
|
Consider defining a more general approach than a fixed JSON-LD format
|
Core: TRS Jira: access-control Priority: High Xtra: Jira
|
For the TRS spec, can we use a more general approach?
Jim says it is brittle...
---
_Migrated from https://issues.oasis-open.org/browse/OSLCCORE-79 (opened by @sarabura; previously assigned to @jamsden)_
|
1.0
|
Consider defining a more general approach than a fixed JSON-LD format - For the TRS spec, can we use a more general approach?
Jim says it is brittle...
---
_Migrated from https://issues.oasis-open.org/browse/OSLCCORE-79 (opened by @sarabura; previously assigned to @jamsden)_
|
non_infrastructure
|
consider defining a more general approach than a fixed json ld format for the trs spec can we use a more general approach jim says it is brittle migrated from opened by sarabura previously assigned to jamsden
| 0
|
504,609
| 14,620,295,026
|
IssuesEvent
|
2020-12-22 19:27:20
|
googleapis/elixir-google-api
|
https://api.github.com/repos/googleapis/elixir-google-api
|
closed
|
Synthesis failed for Content
|
autosynth failure priority: p1 type: bug
|
Hello! Autosynth couldn't regenerate Content. :broken_heart:
Here's the output from running `synth.py`:
```
ionsListResponse to clients/content/lib/google_api/content/v21/model/settlementtransactions_list_response.ex.
Writing ShipmentInvoice to clients/content/lib/google_api/content/v21/model/shipment_invoice.ex.
Writing ShipmentInvoiceLineItemInvoice to clients/content/lib/google_api/content/v21/model/shipment_invoice_line_item_invoice.ex.
Writing ShipmentTrackingInfo to clients/content/lib/google_api/content/v21/model/shipment_tracking_info.ex.
Writing ShippingSettings to clients/content/lib/google_api/content/v21/model/shipping_settings.ex.
Writing ShippingsettingsCustomBatchRequest to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_request.ex.
Writing ShippingsettingsCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_request_entry.ex.
Writing ShippingsettingsCustomBatchResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_response.ex.
Writing ShippingsettingsCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_response_entry.ex.
Writing ShippingsettingsGetSupportedCarriersResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_carriers_response.ex.
Writing ShippingsettingsGetSupportedHolidaysResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_holidays_response.ex.
Writing ShippingsettingsGetSupportedPickupServicesResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_pickup_services_response.ex.
Writing ShippingsettingsListResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_list_response.ex.
Writing Table to clients/content/lib/google_api/content/v21/model/table.ex.
Writing TestOrder to clients/content/lib/google_api/content/v21/model/test_order.ex.
Writing TestOrderAddress to clients/content/lib/google_api/content/v21/model/test_order_address.ex.
Writing TestOrderDeliveryDetails to clients/content/lib/google_api/content/v21/model/test_order_delivery_details.ex.
Writing TestOrderLineItem to clients/content/lib/google_api/content/v21/model/test_order_line_item.ex.
Writing TestOrderLineItemProduct to clients/content/lib/google_api/content/v21/model/test_order_line_item_product.ex.
Writing TestOrderPickupDetails to clients/content/lib/google_api/content/v21/model/test_order_pickup_details.ex.
Writing TestOrderPickupDetailsPickupPerson to clients/content/lib/google_api/content/v21/model/test_order_pickup_details_pickup_person.ex.
Writing TimeZone to clients/content/lib/google_api/content/v21/model/time_zone.ex.
Writing TransitTable to clients/content/lib/google_api/content/v21/model/transit_table.ex.
Writing TransitTableTransitTimeRow to clients/content/lib/google_api/content/v21/model/transit_table_transit_time_row.ex.
Writing TransitTableTransitTimeRowTransitTimeValue to clients/content/lib/google_api/content/v21/model/transit_table_transit_time_row_transit_time_value.ex.
Writing UnitInvoice to clients/content/lib/google_api/content/v21/model/unit_invoice.ex.
Writing UnitInvoiceAdditionalCharge to clients/content/lib/google_api/content/v21/model/unit_invoice_additional_charge.ex.
Writing UnitInvoiceTaxLine to clients/content/lib/google_api/content/v21/model/unit_invoice_tax_line.ex.
Writing Value to clients/content/lib/google_api/content/v21/model/value.ex.
Writing Weight to clients/content/lib/google_api/content/v21/model/weight.ex.
Writing Accounts to clients/content/lib/google_api/content/v21/api/accounts.ex.
Writing Accountstatuses to clients/content/lib/google_api/content/v21/api/accountstatuses.ex.
Writing Accounttax to clients/content/lib/google_api/content/v21/api/accounttax.ex.
Writing Csses to clients/content/lib/google_api/content/v21/api/csses.ex.
Writing Datafeeds to clients/content/lib/google_api/content/v21/api/datafeeds.ex.
Writing Datafeedstatuses to clients/content/lib/google_api/content/v21/api/datafeedstatuses.ex.
Writing Liasettings to clients/content/lib/google_api/content/v21/api/liasettings.ex.
Writing Localinventory to clients/content/lib/google_api/content/v21/api/localinventory.ex.
Writing Orderinvoices to clients/content/lib/google_api/content/v21/api/orderinvoices.ex.
Writing Orderreports to clients/content/lib/google_api/content/v21/api/orderreports.ex.
Writing Orderreturns to clients/content/lib/google_api/content/v21/api/orderreturns.ex.
Writing Orders to clients/content/lib/google_api/content/v21/api/orders.ex.
Writing Ordertrackingsignals to clients/content/lib/google_api/content/v21/api/ordertrackingsignals.ex.
Writing Pos to clients/content/lib/google_api/content/v21/api/pos.ex.
Writing Products to clients/content/lib/google_api/content/v21/api/products.ex.
Writing Productstatuses to clients/content/lib/google_api/content/v21/api/productstatuses.ex.
Writing Pubsubnotificationsettings to clients/content/lib/google_api/content/v21/api/pubsubnotificationsettings.ex.
Writing Regionalinventory to clients/content/lib/google_api/content/v21/api/regionalinventory.ex.
Writing Regions to clients/content/lib/google_api/content/v21/api/regions.ex.
Writing Repricingrules to clients/content/lib/google_api/content/v21/api/repricingrules.ex.
Writing Returnaddress to clients/content/lib/google_api/content/v21/api/returnaddress.ex.
Writing Returnpolicy to clients/content/lib/google_api/content/v21/api/returnpolicy.ex.
Writing Settlementreports to clients/content/lib/google_api/content/v21/api/settlementreports.ex.
Writing Settlementtransactions to clients/content/lib/google_api/content/v21/api/settlementtransactions.ex.
Writing Shippingsettings to clients/content/lib/google_api/content/v21/api/shippingsettings.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
13:43:13.777 [info] Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
main()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
spec.loader.exec_module(synth_module) # type: ignore
File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
self.observer.stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
self.on_thread_stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
self.unschedule_all()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
self._clear_emitters()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
emitter.stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
self.on_thread_stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
self._inotify.close()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
self.stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
self.on_thread_stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
self._inotify.close()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-18 05:43:16,902 autosynth [ERROR] > Synthesis failed
2020-12-18 05:43:16,902 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
main()
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
return _inner_main(temp_dir)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
).synthesize(synth_log_path / "sponge_log.log")
File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
synth_proc.check_returncode() # Raise an exception.
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/content/synth.metadata', 'synth.py', '--', 'Content']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](http://sponge2/results/invocations/3a455424-7540-46a9-bb77-8265c8f04c06/targets/github%2Fsynthtool;config=default/tests;query=elixir-google-api;failed=false).
|
1.0
|
Synthesis failed for Content - Hello! Autosynth couldn't regenerate Content. :broken_heart:
Here's the output from running `synth.py`:
```
ionsListResponse to clients/content/lib/google_api/content/v21/model/settlementtransactions_list_response.ex.
Writing ShipmentInvoice to clients/content/lib/google_api/content/v21/model/shipment_invoice.ex.
Writing ShipmentInvoiceLineItemInvoice to clients/content/lib/google_api/content/v21/model/shipment_invoice_line_item_invoice.ex.
Writing ShipmentTrackingInfo to clients/content/lib/google_api/content/v21/model/shipment_tracking_info.ex.
Writing ShippingSettings to clients/content/lib/google_api/content/v21/model/shipping_settings.ex.
Writing ShippingsettingsCustomBatchRequest to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_request.ex.
Writing ShippingsettingsCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_request_entry.ex.
Writing ShippingsettingsCustomBatchResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_response.ex.
Writing ShippingsettingsCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_response_entry.ex.
Writing ShippingsettingsGetSupportedCarriersResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_carriers_response.ex.
Writing ShippingsettingsGetSupportedHolidaysResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_holidays_response.ex.
Writing ShippingsettingsGetSupportedPickupServicesResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_pickup_services_response.ex.
Writing ShippingsettingsListResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_list_response.ex.
Writing Table to clients/content/lib/google_api/content/v21/model/table.ex.
Writing TestOrder to clients/content/lib/google_api/content/v21/model/test_order.ex.
Writing TestOrderAddress to clients/content/lib/google_api/content/v21/model/test_order_address.ex.
Writing TestOrderDeliveryDetails to clients/content/lib/google_api/content/v21/model/test_order_delivery_details.ex.
Writing TestOrderLineItem to clients/content/lib/google_api/content/v21/model/test_order_line_item.ex.
Writing TestOrderLineItemProduct to clients/content/lib/google_api/content/v21/model/test_order_line_item_product.ex.
Writing TestOrderPickupDetails to clients/content/lib/google_api/content/v21/model/test_order_pickup_details.ex.
Writing TestOrderPickupDetailsPickupPerson to clients/content/lib/google_api/content/v21/model/test_order_pickup_details_pickup_person.ex.
Writing TimeZone to clients/content/lib/google_api/content/v21/model/time_zone.ex.
Writing TransitTable to clients/content/lib/google_api/content/v21/model/transit_table.ex.
Writing TransitTableTransitTimeRow to clients/content/lib/google_api/content/v21/model/transit_table_transit_time_row.ex.
Writing TransitTableTransitTimeRowTransitTimeValue to clients/content/lib/google_api/content/v21/model/transit_table_transit_time_row_transit_time_value.ex.
Writing UnitInvoice to clients/content/lib/google_api/content/v21/model/unit_invoice.ex.
Writing UnitInvoiceAdditionalCharge to clients/content/lib/google_api/content/v21/model/unit_invoice_additional_charge.ex.
Writing UnitInvoiceTaxLine to clients/content/lib/google_api/content/v21/model/unit_invoice_tax_line.ex.
Writing Value to clients/content/lib/google_api/content/v21/model/value.ex.
Writing Weight to clients/content/lib/google_api/content/v21/model/weight.ex.
Writing Accounts to clients/content/lib/google_api/content/v21/api/accounts.ex.
Writing Accountstatuses to clients/content/lib/google_api/content/v21/api/accountstatuses.ex.
Writing Accounttax to clients/content/lib/google_api/content/v21/api/accounttax.ex.
Writing Csses to clients/content/lib/google_api/content/v21/api/csses.ex.
Writing Datafeeds to clients/content/lib/google_api/content/v21/api/datafeeds.ex.
Writing Datafeedstatuses to clients/content/lib/google_api/content/v21/api/datafeedstatuses.ex.
Writing Liasettings to clients/content/lib/google_api/content/v21/api/liasettings.ex.
Writing Localinventory to clients/content/lib/google_api/content/v21/api/localinventory.ex.
Writing Orderinvoices to clients/content/lib/google_api/content/v21/api/orderinvoices.ex.
Writing Orderreports to clients/content/lib/google_api/content/v21/api/orderreports.ex.
Writing Orderreturns to clients/content/lib/google_api/content/v21/api/orderreturns.ex.
Writing Orders to clients/content/lib/google_api/content/v21/api/orders.ex.
Writing Ordertrackingsignals to clients/content/lib/google_api/content/v21/api/ordertrackingsignals.ex.
Writing Pos to clients/content/lib/google_api/content/v21/api/pos.ex.
Writing Products to clients/content/lib/google_api/content/v21/api/products.ex.
Writing Productstatuses to clients/content/lib/google_api/content/v21/api/productstatuses.ex.
Writing Pubsubnotificationsettings to clients/content/lib/google_api/content/v21/api/pubsubnotificationsettings.ex.
Writing Regionalinventory to clients/content/lib/google_api/content/v21/api/regionalinventory.ex.
Writing Regions to clients/content/lib/google_api/content/v21/api/regions.ex.
Writing Repricingrules to clients/content/lib/google_api/content/v21/api/repricingrules.ex.
Writing Returnaddress to clients/content/lib/google_api/content/v21/api/returnaddress.ex.
Writing Returnpolicy to clients/content/lib/google_api/content/v21/api/returnpolicy.ex.
Writing Settlementreports to clients/content/lib/google_api/content/v21/api/settlementreports.ex.
Writing Settlementtransactions to clients/content/lib/google_api/content/v21/api/settlementtransactions.ex.
Writing Shippingsettings to clients/content/lib/google_api/content/v21/api/shippingsettings.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
13:43:13.777 [info] Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
main()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
spec.loader.exec_module(synth_module) # type: ignore
File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
self.observer.stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
self.on_thread_stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
self.unschedule_all()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
self._clear_emitters()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
emitter.stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
self.on_thread_stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
self._inotify.close()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
self.stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
self.on_thread_stop()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
self._inotify.close()
File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-18 05:43:16,902 autosynth [ERROR] > Synthesis failed
2020-12-18 05:43:16,902 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
main()
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
return _inner_main(temp_dir)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
).synthesize(synth_log_path / "sponge_log.log")
File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
synth_proc.check_returncode() # Raise an exception.
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/content/synth.metadata', 'synth.py', '--', 'Content']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](http://sponge2/results/invocations/3a455424-7540-46a9-bb77-8265c8f04c06/targets/github%2Fsynthtool;config=default/tests;query=elixir-google-api;failed=false).
|
non_infrastructure
|
synthesis failed for content hello autosynth couldn t regenerate content broken heart here s the output from running synth py ionslistresponse to clients content lib google api content model settlementtransactions list response ex writing shipmentinvoice to clients content lib google api content model shipment invoice ex writing shipmentinvoicelineiteminvoice to clients content lib google api content model shipment invoice line item invoice ex writing shipmenttrackinginfo to clients content lib google api content model shipment tracking info ex writing shippingsettings to clients content lib google api content model shipping settings ex writing shippingsettingscustombatchrequest to clients content lib google api content model shippingsettings custom batch request ex writing shippingsettingscustombatchrequestentry to clients content lib google api content model shippingsettings custom batch request entry ex writing shippingsettingscustombatchresponse to clients content lib google api content model shippingsettings custom batch response ex writing shippingsettingscustombatchresponseentry to clients content lib google api content model shippingsettings custom batch response entry ex writing shippingsettingsgetsupportedcarriersresponse to clients content lib google api content model shippingsettings get supported carriers response ex writing shippingsettingsgetsupportedholidaysresponse to clients content lib google api content model shippingsettings get supported holidays response ex writing shippingsettingsgetsupportedpickupservicesresponse to clients content lib google api content model shippingsettings get supported pickup services response ex writing shippingsettingslistresponse to clients content lib google api content model shippingsettings list response ex writing table to clients content lib google api content model table ex writing testorder to clients content lib google api content model test order ex writing testorderaddress to clients content lib google api content model test order address ex writing testorderdeliverydetails to clients content lib google api content model test order delivery details ex writing testorderlineitem to clients content lib google api content model test order line item ex writing testorderlineitemproduct to clients content lib google api content model test order line item product ex writing testorderpickupdetails to clients content lib google api content model test order pickup details ex writing testorderpickupdetailspickupperson to clients content lib google api content model test order pickup details pickup person ex writing timezone to clients content lib google api content model time zone ex writing transittable to clients content lib google api content model transit table ex writing transittabletransittimerow to clients content lib google api content model transit table transit time row ex writing transittabletransittimerowtransittimevalue to clients content lib google api content model transit table transit time row transit time value ex writing unitinvoice to clients content lib google api content model unit invoice ex writing unitinvoiceadditionalcharge to clients content lib google api content model unit invoice additional charge ex writing unitinvoicetaxline to clients content lib google api content model unit invoice tax line ex writing value to clients content lib google api content model value ex writing weight to clients content lib google api content model weight ex writing accounts to clients content lib google api content api accounts ex writing accountstatuses to clients content lib google api content api accountstatuses ex writing accounttax to clients content lib google api content api accounttax ex writing csses to clients content lib google api content api csses ex writing datafeeds to clients content lib google api content api datafeeds ex writing datafeedstatuses to clients content lib google api content api datafeedstatuses ex writing liasettings to clients content lib google api content api liasettings ex writing localinventory to clients content lib google api content api localinventory ex writing orderinvoices to clients content lib google api content api orderinvoices ex writing orderreports to clients content lib google api content api orderreports ex writing orderreturns to clients content lib google api content api orderreturns ex writing orders to clients content lib google api content api orders ex writing ordertrackingsignals to clients content lib google api content api ordertrackingsignals ex writing pos to clients content lib google api content api pos ex writing products to clients content lib google api content api products ex writing productstatuses to clients content lib google api content api productstatuses ex writing pubsubnotificationsettings to clients content lib google api content api pubsubnotificationsettings ex writing regionalinventory to clients content lib google api content api regionalinventory ex writing regions to clients content lib google api content api regions ex writing repricingrules to clients content lib google api content api repricingrules ex writing returnaddress to clients content lib google api content api returnaddress ex writing returnpolicy to clients content lib google api content api returnpolicy ex writing settlementreports to clients content lib google api content api settlementreports ex writing settlementtransactions to clients content lib google api content api settlementtransactions ex writing shippingsettings to clients content lib google api content api shippingsettings ex writing connection ex writing metadata ex writing mix exs writing readme md writing license writing gitignore writing config config exs writing test test helper exs found only discovery revision and or formatting changes not significant enough for a pr fixing file permissions traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src github synthtool synthtool main py line in main file tmpfs src github synthtool env lib site packages click core py line in call return self main args kwargs file tmpfs src github synthtool env lib site packages click core py line in main rv self invoke ctx file tmpfs src github synthtool env lib site packages click core py line in invoke return ctx invoke self callback ctx params file tmpfs src github synthtool env lib site packages click core py line in invoke return callback args kwargs file tmpfs src github synthtool synthtool main py line in main spec loader exec module synth module type ignore file tmpfs src github synthtool synthtool metadata py line in exit self observer stop file tmpfs src github synthtool env lib site packages watchdog utils init py line in stop self on thread stop file tmpfs src github synthtool env lib site packages watchdog observers api py line in on thread stop self unschedule all file tmpfs src github synthtool env lib site packages watchdog observers api py line in unschedule all self clear emitters file tmpfs src github synthtool env lib site packages watchdog observers api py line in clear emitters emitter stop file tmpfs src github synthtool env lib site packages watchdog utils init py line in stop self on thread stop file tmpfs src github synthtool env lib site packages watchdog observers inotify py line in on thread stop self inotify close file tmpfs src github synthtool env lib site packages watchdog observers inotify buffer py line in close self stop file tmpfs src github synthtool env lib site packages watchdog utils init py line in stop self on thread stop file tmpfs src github synthtool env lib site packages watchdog observers inotify buffer py line in on thread stop self inotify close file tmpfs src github synthtool env lib site packages watchdog observers inotify c py line in close os close self inotify fd oserror bad file descriptor autosynth synthesis failed autosynth running git clean fdx removing pycache traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src github synthtool autosynth synth py line in main file tmpfs src github synthtool autosynth synth py line in main return inner main temp dir file tmpfs src github synthtool autosynth synth py line in inner main synthesize synth log path sponge log log file tmpfs src github synthtool autosynth synthesizer py line in synthesize synth proc check returncode raise an exception file home kbuilder pyenv versions lib subprocess py line in check returncode self stderr subprocess calledprocesserror command returned non zero exit status google internal developers can see the full log
| 0
|
5,093
| 5,435,260,130
|
IssuesEvent
|
2017-03-05 15:33:03
|
AdguardTeam/AdguardFilters
|
https://api.github.com/repos/AdguardTeam/AdguardFilters
|
closed
|
adblock.ro filter
|
Infrastructure
|
Want to inform this is a new Romanian filter list https://www.adblock.ro/, on our website you can find all details, may need to use translation tools because is written in Romanian. This is a Public list, and anyone can contribute on our GitHub open project.
Our Website: https://www.adblock.ro/
Github Project: https://github.com/tcptomato/ROad-Block
|
1.0
|
adblock.ro filter -
Want to inform this is a new Romanian filter list https://www.adblock.ro/, on our website you can find all details, may need to use translation tools because is written in Romanian. This is a Public list, and anyone can contribute on our GitHub open project.
Our Website: https://www.adblock.ro/
Github Project: https://github.com/tcptomato/ROad-Block
|
infrastructure
|
adblock ro filter want to inform this is a new romanian filter list on our website you can find all details may need to use translation tools because is written in romanian this is a public list and anyone can contribute on our github open project our website github project
| 1
|
3,286
| 4,187,972,579
|
IssuesEvent
|
2016-06-23 19:09:41
|
SemanticMediaWiki/SemanticMediaWiki
|
https://api.github.com/repos/SemanticMediaWiki/SemanticMediaWiki
|
closed
|
Leave SourceForge?
|
discussion infrastructure
|
SourceForge has become a rather controversial provider of software downloads [0][1][2] and is now routinely blocked by e.g. uBlock [3] as well as at least one corporate firewall I know.
Would it make sense to leave SourceForge and use GitHub to distribute tar balls instead?
[0] http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/
[1] http://libregraphicsworld.org/blog/entry/anatomy-of-sourceforge-gimp-controversy
[2] http://www.ghacks.net/2015/06/15/popular-software-projects-leave-sourceforge/
[3] https://github.com/gorhill/uBlock/commit/c4e82357efaf18bac3f04900efb304f5a092ffe0
|
1.0
|
Leave SourceForge? - SourceForge has become a rather controversial provider of software downloads [0][1][2] and is now routinely blocked by e.g. uBlock [3] as well as at least one corporate firewall I know.
Would it make sense to leave SourceForge and use GitHub to distribute tar balls instead?
[0] http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/
[1] http://libregraphicsworld.org/blog/entry/anatomy-of-sourceforge-gimp-controversy
[2] http://www.ghacks.net/2015/06/15/popular-software-projects-leave-sourceforge/
[3] https://github.com/gorhill/uBlock/commit/c4e82357efaf18bac3f04900efb304f5a092ffe0
|
infrastructure
|
leave sourceforge sourceforge has become a rather controversial provider of software downloads and is now routinely blocked by e g ublock as well as at least one corporate firewall i know would it make sense to leave sourceforge and use github to distribute tar balls instead
| 1
|
6,279
| 8,652,736,797
|
IssuesEvent
|
2018-11-27 08:59:54
|
gooddata/gooddata-java
|
https://api.github.com/repos/gooddata/gooddata-java
|
opened
|
Mutable DTOs can't honour equals semantics
|
backward incompatible
|
The core concept of gooddata-java - mutable dtos is effectively preventing such objects to have valid `equals` method. It's a question how this issue should be resolved:
:question: make the DTOs immutable and provide copy constrcutors/builders
:question: stay on the current state - the equals is only implemented on objects which has sensible immutable id
:question: something else
|
True
|
Mutable DTOs can't honour equals semantics - The core concept of gooddata-java - mutable dtos is effectively preventing such objects to have valid `equals` method. It's a question how this issue should be resolved:
:question: make the DTOs immutable and provide copy constrcutors/builders
:question: stay on the current state - the equals is only implemented on objects which has sensible immutable id
:question: something else
|
non_infrastructure
|
mutable dtos can t honour equals semantics the core concept of gooddata java mutable dtos is effectively preventing such objects to have valid equals method it s a question how this issue should be resolved question make the dtos immutable and provide copy constrcutors builders question stay on the current state the equals is only implemented on objects which has sensible immutable id question something else
| 0
|
31,384
| 25,601,993,145
|
IssuesEvent
|
2022-12-01 21:07:07
|
gothick/omm
|
https://api.github.com/repos/gothick/omm
|
opened
|
Should we persist beanstalkd?
|
infrastructure beanstalk
|
Should we persist beanstalkd? (if we do, there’s a recommended cookbook: https://github.com/djoos-cookbooks/beanstalkd) “Yes; if you choose, you can use the “-b” option, and beanstalkd will write all jobs to a binlog. If the power goes out, you can restart beanstalkd with the same option and it will recover the contents of the log.”
On the other hand, our jobs are pretty ephemeral and everything can be quickly manually regenerated in the event of a disaster.
|
1.0
|
Should we persist beanstalkd? - Should we persist beanstalkd? (if we do, there’s a recommended cookbook: https://github.com/djoos-cookbooks/beanstalkd) “Yes; if you choose, you can use the “-b” option, and beanstalkd will write all jobs to a binlog. If the power goes out, you can restart beanstalkd with the same option and it will recover the contents of the log.”
On the other hand, our jobs are pretty ephemeral and everything can be quickly manually regenerated in the event of a disaster.
|
infrastructure
|
should we persist beanstalkd should we persist beanstalkd if we do there’s a recommended cookbook “yes if you choose you can use the “ b” option and beanstalkd will write all jobs to a binlog if the power goes out you can restart beanstalkd with the same option and it will recover the contents of the log ” on the other hand our jobs are pretty ephemeral and everything can be quickly manually regenerated in the event of a disaster
| 1
|
417,204
| 28,110,195,695
|
IssuesEvent
|
2023-03-31 06:26:02
|
dsja612/ped
|
https://api.github.com/repos/dsja612/ped
|
opened
|
[UG] The image showed in the `Deleting a person` section is outdated
|
severity.Low type.DocumentationBug
|
The image showed in the `Deleting a person` section is outdated, and does not reflect the changes in the new UI.
### DG Screenshot
### ModCheck Screenshot
<!--session: 1680242262112-1218d913-3618-4389-b304-06d56e0308d2-->
<!--Version: Web v3.4.7-->
|
1.0
|
[UG] The image showed in the `Deleting a person` section is outdated - The image showed in the `Deleting a person` section is outdated, and does not reflect the changes in the new UI.
### DG Screenshot
### ModCheck Screenshot
<!--session: 1680242262112-1218d913-3618-4389-b304-06d56e0308d2-->
<!--Version: Web v3.4.7-->
|
non_infrastructure
|
the image showed in the deleting a person section is outdated the image showed in the deleting a person section is outdated and does not reflect the changes in the new ui dg screenshot modcheck screenshot
| 0
|
529,312
| 15,386,160,488
|
IssuesEvent
|
2021-03-03 07:47:37
|
wso2/product-apim
|
https://api.github.com/repos/wso2/product-apim
|
opened
|
Error when creating a new API from scratch by a user with Creator only permission
|
API-M 4.0.0 Priority/High Type/Bug
|
### Description:
Below error popup is displayed in Publisher UI when a user with Creator only permissions creates an API from scratch at the point of clicking on the CREATE button.
The browser console shows the following two calls being made to the revision rest API
Since the revision REST API resources require Publisher permissions these calls fail with 401 being returned.
### Steps to reproduce:
1. Login to the Publisher UI with a user who only has Creator permissions.
2. Fill in the fields required for a new REST API from scratch and click on the "CREATE" button
|
1.0
|
Error when creating a new API from scratch by a user with Creator only permission - ### Description:
Below error popup is displayed in Publisher UI when a user with Creator only permissions creates an API from scratch at the point of clicking on the CREATE button.
The browser console shows the following two calls being made to the revision rest API
Since the revision REST API resources require Publisher permissions these calls fail with 401 being returned.
### Steps to reproduce:
1. Login to the Publisher UI with a user who only has Creator permissions.
2. Fill in the fields required for a new REST API from scratch and click on the "CREATE" button
|
non_infrastructure
|
error when creating a new api from scratch by a user with creator only permission description below error popup is displayed in publisher ui when a user with creator only permissions creates an api from scratch at the point of clicking on the create button the browser console shows the following two calls being made to the revision rest api since the revision rest api resources require publisher permissions these calls fail with being returned steps to reproduce login to the publisher ui with a user who only has creator permissions fill in the fields required for a new rest api from scratch and click on the create button
| 0
|
12,489
| 9,806,940,471
|
IssuesEvent
|
2019-06-12 12:40:37
|
EticaAI/forum
|
https://api.github.com/repos/EticaAI/forum
|
opened
|
VPS Águia Pescadora Alpha
|
infrastructure-vps
|
- https://github.com/fititnt/cplp-aiops/issues/17 <sup>(Portuguese)</sup>
---
_TODO: add basic details about this VPS on next weeks_
|
1.0
|
VPS Águia Pescadora Alpha - - https://github.com/fititnt/cplp-aiops/issues/17 <sup>(Portuguese)</sup>
---
_TODO: add basic details about this VPS on next weeks_
|
infrastructure
|
vps águia pescadora alpha portuguese todo add basic details about this vps on next weeks
| 1
|
117,582
| 11,950,458,110
|
IssuesEvent
|
2020-04-03 15:14:15
|
Azure/azure-devops-cli-extension
|
https://api.github.com/repos/Azure/azure-devops-cli-extension
|
opened
|
[Documentation] Include azure devops documentation in top level command group details.
|
documentation
|
In each of the top level commands - az boards, az pipelines, az repos, az artifacts and az devops, we include the line indicating that this command is a part of azure-devops extension. In addition to this, we need to include the link out to the documentation - https://docs.microsoft.com/en-us/azure/devops/cli/?view=azure-devops as well.
https://github.com/Azure/azure-cli-extensions/issues/1454
|
1.0
|
[Documentation] Include azure devops documentation in top level command group details. - In each of the top level commands - az boards, az pipelines, az repos, az artifacts and az devops, we include the line indicating that this command is a part of azure-devops extension. In addition to this, we need to include the link out to the documentation - https://docs.microsoft.com/en-us/azure/devops/cli/?view=azure-devops as well.
https://github.com/Azure/azure-cli-extensions/issues/1454
|
non_infrastructure
|
include azure devops documentation in top level command group details in each of the top level commands az boards az pipelines az repos az artifacts and az devops we include the line indicating that this command is a part of azure devops extension in addition to this we need to include the link out to the documentation as well
| 0
|
32,572
| 26,802,892,813
|
IssuesEvent
|
2023-02-01 16:13:54
|
microsoft/WindowsAppSDK
|
https://api.github.com/repos/microsoft/WindowsAppSDK
|
closed
|
DevCheck doesn't verify VS components
|
feature area-Infrastructure
|
`tools\DevCheck.ps1` (conveniently accessible by running `tools\DevCheck.cmd`) verifies the local development environment is ready and often can (and will) update the environment as needed e.g. make sure the TAEF service is installed.
Building ProjectReunion.sln and others in the repository require many Visual Studio components, not all of them obvious. Trying to build without the right components installed can be a frustrating experience to identify what's missing and which of Visual Studio Updater's zillions of options are needed. DevCheck needs to verify the required components are present. This includes the right versions of the Windows SDK, .NET Core and other components. These can be detected via [vswhere.exe](https://github.com/Microsoft/vswhere) to check for the expected [workload and component IDs](https://docs.microsoft.com/en-us/visualstudio/install/workload-and-component-ids?view=vs-2019).
DevCheck currently pulls down the latest vswhere to do checks (unless -Offline is specified). It can also be found at `%ProgramFiles%\Microsoft Visual Studio\Installer\vswhere.exe`. DevCheck should use the local copy by default and grab and use the remote copy if -VSWhere:Latest is specified.
|
1.0
|
DevCheck doesn't verify VS components - `tools\DevCheck.ps1` (conveniently accessible by running `tools\DevCheck.cmd`) verifies the local development environment is ready and often can (and will) update the environment as needed e.g. make sure the TAEF service is installed.
Building ProjectReunion.sln and others in the repository require many Visual Studio components, not all of them obvious. Trying to build without the right components installed can be a frustrating experience to identify what's missing and which of Visual Studio Updater's zillions of options are needed. DevCheck needs to verify the required components are present. This includes the right versions of the Windows SDK, .NET Core and other components. These can be detected via [vswhere.exe](https://github.com/Microsoft/vswhere) to check for the expected [workload and component IDs](https://docs.microsoft.com/en-us/visualstudio/install/workload-and-component-ids?view=vs-2019).
DevCheck currently pulls down the latest vswhere to do checks (unless -Offline is specified). It can also be found at `%ProgramFiles%\Microsoft Visual Studio\Installer\vswhere.exe`. DevCheck should use the local copy by default and grab and use the remote copy if -VSWhere:Latest is specified.
|
infrastructure
|
devcheck doesn t verify vs components tools devcheck conveniently accessible by running tools devcheck cmd verifies the local development environment is ready and often can and will update the environment as needed e g make sure the taef service is installed building projectreunion sln and others in the repository require many visual studio components not all of them obvious trying to build without the right components installed can be a frustrating experience to identify what s missing and which of visual studio updater s zillions of options are needed devcheck needs to verify the required components are present this includes the right versions of the windows sdk net core and other components these can be detected via to check for the expected devcheck currently pulls down the latest vswhere to do checks unless offline is specified it can also be found at programfiles microsoft visual studio installer vswhere exe devcheck should use the local copy by default and grab and use the remote copy if vswhere latest is specified
| 1
|
81,478
| 3,591,421,460
|
IssuesEvent
|
2016-02-01 11:41:02
|
thesgc/chembiohub_helpdesk
|
https://api.github.com/repos/thesgc/chembiohub_helpdesk
|
closed
|
Asked to define assays in the sub project - which I can only select one. Then when I add an assay I
|
app: AssayReg For Andy and Paul Review name: Karen priority: Medium status: New
|
Asked to define assays in the sub project - which I can only select one. Then when I add an assay I can choose a template of any type - shouldn't they be restricted to the assay type I've defined?
|
1.0
|
Asked to define assays in the sub project - which I can only select one. Then when I add an assay I - Asked to define assays in the sub project - which I can only select one. Then when I add an assay I can choose a template of any type - shouldn't they be restricted to the assay type I've defined?
|
non_infrastructure
|
asked to define assays in the sub project which i can only select one then when i add an assay i asked to define assays in the sub project which i can only select one then when i add an assay i can choose a template of any type shouldn t they be restricted to the assay type i ve defined
| 0
|
287,863
| 24,869,061,963
|
IssuesEvent
|
2022-10-27 14:02:15
|
iho-ohi/S-101_Portrayal-Catalogue
|
https://api.github.com/repos/iho-ohi/S-101_Portrayal-Catalogue
|
closed
|
Measured Distance Value (row 61 main)
|
enhancement test PC 1.0.2
|
Rule update DistanceMark.lua.
NOTE: Sanchez, Alvaro MR:
Display the abbreviation of the unit of measurement in use preceeding waterwayDistance.
(DistanceMark.zip) New symbol here from Holger: https://github.com/S-101-Portrayal-subWG/Working-Documents/issues/39
From duplicate issue #35
categoryOfDistanceMark was removed in FC 1.0.2 and distanceMarkVisible was added.
|
1.0
|
Measured Distance Value (row 61 main) - 
Rule update DistanceMark.lua.
NOTE: Sanchez, Alvaro MR:
Display the abbreviation of the unit of measurement in use preceeding waterwayDistance.
(DistanceMark.zip) New symbol here from Holger: https://github.com/S-101-Portrayal-subWG/Working-Documents/issues/39
From duplicate issue #35
categoryOfDistanceMark was removed in FC 1.0.2 and distanceMarkVisible was added.
|
non_infrastructure
|
measured distance value row main rule update distancemark lua note sanchez alvaro mr display the abbreviation of the unit of measurement in use preceeding waterwaydistance distancemark zip new symbol here from holger from duplicate issue categoryofdistancemark was removed in fc and distancemarkvisible was added
| 0
|
4,013
| 4,769,216,667
|
IssuesEvent
|
2016-10-26 11:48:59
|
camunda/camunda-modeler
|
https://api.github.com/repos/camunda/camunda-modeler
|
opened
|
Error during build process with npm version>=3
|
infrastructure
|
Uncaught Exception: Error: Cannot find module 'concat-map'
|
1.0
|
Error during build process with npm version>=3 - Uncaught Exception: Error: Cannot find module 'concat-map'
|
infrastructure
|
error during build process with npm version uncaught exception error cannot find module concat map
| 1
|
52,502
| 7,767,979,166
|
IssuesEvent
|
2018-06-03 13:12:22
|
Adobe-Marketing-Cloud/aem-core-wcm-components
|
https://api.github.com/repos/Adobe-Marketing-Cloud/aem-core-wcm-components
|
opened
|
[Image] Document the SVG behavior
|
documentation
|
We should document the SVG support that was recently added to the image component in https://github.com/Adobe-Marketing-Cloud/aem-core-wcm-components/pull/171, to describe its behavior in relation to adaptive image widths.
|
1.0
|
[Image] Document the SVG behavior - We should document the SVG support that was recently added to the image component in https://github.com/Adobe-Marketing-Cloud/aem-core-wcm-components/pull/171, to describe its behavior in relation to adaptive image widths.
|
non_infrastructure
|
document the svg behavior we should document the svg support that was recently added to the image component in to describe its behavior in relation to adaptive image widths
| 0
|
647,578
| 21,111,498,698
|
IssuesEvent
|
2022-04-05 02:29:35
|
mskcc/pluto-cwl
|
https://api.github.com/repos/mskcc/pluto-cwl
|
closed
|
clean up env.sh
|
low priority
|
Right now, the `toil` recipe in the `env.juno.sh` file is the only one that is really used anymore. Many others have become extraneous and outdated. So, updated the script to simplify it and remove those old outdated recipes
|
1.0
|
clean up env.sh - Right now, the `toil` recipe in the `env.juno.sh` file is the only one that is really used anymore. Many others have become extraneous and outdated. So, updated the script to simplify it and remove those old outdated recipes
|
non_infrastructure
|
clean up env sh right now the toil recipe in the env juno sh file is the only one that is really used anymore many others have become extraneous and outdated so updated the script to simplify it and remove those old outdated recipes
| 0
|
166,375
| 26,345,623,824
|
IssuesEvent
|
2023-01-10 21:46:41
|
gotogether-s/gotogether-s
|
https://api.github.com/repos/gotogether-s/gotogether-s
|
closed
|
SignUp
|
design
|
## About
Update style of signup page
## To do list
- [x] Sort import lines of signup page
- [x] Organize code lines of signup page
- [x] Reduce paddingBottom from 1rem to 0.5rem in signin page
- [x] Reduce paddingTop value of error message in signin page
- [x] Reduce marginBottom value of input wrapper box
- [x] Remove marginTop value of signup link
- [x] Reduce default marginBottom value to 2rem
- [x] Add style to Button on hover
- [x] Replace HTML with MUI, Update style and Delete SignUp.scss
- [x] Reduce size of icon and Increase fontSize of page title
|
1.0
|
SignUp - ## About
Update style of signup page
## To do list
- [x] Sort import lines of signup page
- [x] Organize code lines of signup page
- [x] Reduce paddingBottom from 1rem to 0.5rem in signin page
- [x] Reduce paddingTop value of error message in signin page
- [x] Reduce marginBottom value of input wrapper box
- [x] Remove marginTop value of signup link
- [x] Reduce default marginBottom value to 2rem
- [x] Add style to Button on hover
- [x] Replace HTML with MUI, Update style and Delete SignUp.scss
- [x] Reduce size of icon and Increase fontSize of page title
|
non_infrastructure
|
signup about update style of signup page to do list sort import lines of signup page organize code lines of signup page reduce paddingbottom from to in signin page reduce paddingtop value of error message in signin page reduce marginbottom value of input wrapper box remove margintop value of signup link reduce default marginbottom value to add style to button on hover replace html with mui update style and delete signup scss reduce size of icon and increase fontsize of page title
| 0
|
247,418
| 26,707,692,228
|
IssuesEvent
|
2023-01-27 19:49:16
|
kferrara1313/da-react-challenge
|
https://api.github.com/repos/kferrara1313/da-react-challenge
|
opened
|
Django-3.2-py3-none-any.whl: 16 vulnerabilities (highest severity is: 9.8)
|
security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (Django version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-34265](https://www.mend.io/vulnerability-database/CVE-2022-34265) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | Django - 3.2.14,4.0.6 | ✅ |
| [CVE-2022-28346](https://www.mend.io/vulnerability-database/CVE-2022-28346) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | 3.2.13 | ✅ |
| [CVE-2022-28347](https://www.mend.io/vulnerability-database/CVE-2022-28347) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | 3.2.13 | ✅ |
| [CVE-2021-35042](https://www.mend.io/vulnerability-database/CVE-2021-35042) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | Django - 3.1.13,3.2.5 | ✅ |
| [CVE-2022-36359](https://www.mend.io/vulnerability-database/CVE-2022-36359) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | Django-3.2-py3-none-any.whl | Direct | Django -3.2.15,4.0.7,4.1 | ✅ |
| [CVE-2022-41323](https://www.mend.io/vulnerability-database/CVE-2022-41323) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | 3.2.16 | ✅ |
| [CVE-2021-45115](https://www.mend.io/vulnerability-database/CVE-2021-45115) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | 3.2.11 | ✅ |
| [CVE-2022-23833](https://www.mend.io/vulnerability-database/CVE-2022-23833) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.27,3.2.12,4.0.2 | ✅ |
| [CVE-2021-31542](https://www.mend.io/vulnerability-database/CVE-2021-31542) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.21,3.1.9,3.2.1 | ✅ |
| [CVE-2021-33571](https://www.mend.io/vulnerability-database/CVE-2021-33571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.24, 3.1.12, 3.2.4 | ✅ |
| [CVE-2021-45116](https://www.mend.io/vulnerability-database/CVE-2021-45116) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | 3.2.11 | ✅ |
| [CVE-2021-44420](https://www.mend.io/vulnerability-database/CVE-2021-44420) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.25,3.1.14,3.2.10 | ✅ |
| [CVE-2022-22818](https://www.mend.io/vulnerability-database/CVE-2022-22818) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.27,3.2.12,4.0.2 | ✅ |
| [CVE-2021-32052](https://www.mend.io/vulnerability-database/CVE-2021-32052) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.22,3.1.10,3.2.2 | ✅ |
| [CVE-2021-45452](https://www.mend.io/vulnerability-database/CVE-2021-45452) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | Django-3.2-py3-none-any.whl | Direct | 3.2.11 | ✅ |
| [CVE-2021-33203](https://www.mend.io/vulnerability-database/CVE-2021-33203) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.9 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.24, 3.1.12, 3.2.4 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2022-34265</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.
Mend Note: After conducting further research, Mend has determined that all versions of Django before version 3.2.14 and before 4.0.6 are vulnerable to CVE-2022-34265.
<p>Publish Date: 2022-07-04
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34265>CVE-2022-34265</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/jul/04/security-releases/">https://www.djangoproject.com/weblog/2022/jul/04/security-releases/</a></p>
<p>Release Date: 2022-07-04</p>
<p>Fix Resolution: Django - 3.2.14,4.0.6</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2022-28346</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra() methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed **kwargs.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-28346>CVE-2022-28346</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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: 2022-04-12</p>
<p>Fix Resolution: 3.2.13</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2022-28347</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. This occurs by passing a crafted dictionary (with dictionary expansion) as the **options argument, and placing the injection payload in an option name.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-28347>CVE-2022-28347</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28347">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28347</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution: 3.2.13</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2021-35042</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.
<p>Publish Date: 2021-07-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-35042>CVE-2021-35042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2021/jul/01/security-releases/">https://www.djangoproject.com/weblog/2021/jul/01/security-releases/</a></p>
<p>Release Date: 2021-07-02</p>
<p>Fix Resolution: Django - 3.1.13,3.2.5</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-36359</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in the HTTP FileResponse class in Django 3.2 before 3.2.15 and 4.0 before 4.0.7. An application is vulnerable to a reflected file download (RFD) attack that sets the Content-Disposition header of a FileResponse when the filename is derived from user-supplied input.
<p>Publish Date: 2022-08-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-36359>CVE-2022-36359</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/aug/03/security-releases/">https://www.djangoproject.com/weblog/2022/aug/03/security-releases/</a></p>
<p>Release Date: 2022-08-03</p>
<p>Fix Resolution: Django -3.2.15,4.0.7,4.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-41323</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service attack via the locale parameter, which is treated as a regular expression.
<p>Publish Date: 2022-10-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41323>CVE-2022-41323</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41323">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41323</a></p>
<p>Release Date: 2022-10-16</p>
<p>Fix Resolution: 3.2.16</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-45115</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. UserAttributeSimilarityValidator incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values. In a situation where access to user registration was unrestricted, this provided a potential vector for a denial-of-service attack.
<p>Publish Date: 2022-01-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45115>CVE-2021-45115</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://www.djangoproject.com/weblog/2022/jan/04/security-releases/">https://www.djangoproject.com/weblog/2022/jan/04/security-releases/</a></p>
<p>Release Date: 2022-01-05</p>
<p>Fix Resolution: 3.2.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23833</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2. Passing certain inputs to multipart forms could result in an infinite loop when parsing files.
<p>Publish Date: 2022-02-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23833>CVE-2022-23833</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://www.djangoproject.com/weblog/2022/feb/01/security-releases/">https://www.djangoproject.com/weblog/2022/feb/01/security-releases/</a></p>
<p>Release Date: 2022-02-03</p>
<p>Fix Resolution: Django - 2.2.27,3.2.12,4.0.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-31542</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.
<p>Publish Date: 2021-05-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-31542>CVE-2021-31542</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2021/may/04/security-releases/">https://www.djangoproject.com/weblog/2021/may/04/security-releases/</a></p>
<p>Release Date: 2021-05-05</p>
<p>Fix Resolution: Django - 2.2.21,3.1.9,3.2.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-33571</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+..) .
<p>Publish Date: 2021-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33571>CVE-2021-33571</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2021/jun/02/security-releases/">https://www.djangoproject.com/weblog/2021/jun/02/security-releases/</a></p>
<p>Release Date: 2021-06-08</p>
<p>Fix Resolution: Django - 2.2.24, 3.1.12, 3.2.4</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-45116</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. Due to leveraging the Django Template Language's variable resolution logic, the dictsort template filter was potentially vulnerable to information disclosure, or an unintended method call, if passed a suitably crafted key.
<p>Publish Date: 2022-01-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45116>CVE-2021-45116</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/jan/04/security-releases/">https://www.djangoproject.com/weblog/2022/jan/04/security-releases/</a></p>
<p>Release Date: 2022-01-05</p>
<p>Fix Resolution: 3.2.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44420</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths.
<p>Publish Date: 2021-12-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44420>CVE-2021-44420</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://docs.djangoproject.com/en/3.2/releases/security/">https://docs.djangoproject.com/en/3.2/releases/security/</a></p>
<p>Release Date: 2021-12-08</p>
<p>Fix Resolution: Django - 2.2.25,3.1.14,3.2.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22818</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The {% debug %} template tag in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2 does not properly encode the current context. This may lead to XSS.
<p>Publish Date: 2022-02-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22818>CVE-2022-22818</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/feb/01/security-releases/">https://www.djangoproject.com/weblog/2022/feb/01/security-releases/</a></p>
<p>Release Date: 2022-02-03</p>
<p>Fix Resolution: Django - 2.2.27,3.2.12,4.0.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-32052</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers.
<p>Publish Date: 2021-05-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-32052>CVE-2021-32052</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052</a></p>
<p>Release Date: 2021-05-06</p>
<p>Fix Resolution: Django - 2.2.22,3.1.10,3.2.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-45452</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Storage.save in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows directory traversal if crafted filenames are directly passed to it.
<p>Publish Date: 2022-01-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45452>CVE-2021-45452</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/jan/04/security-releases/">https://www.djangoproject.com/weblog/2022/jan/04/security-releases/</a></p>
<p>Release Date: 2022-01-05</p>
<p>Fix Resolution: 3.2.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-33203</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.
<p>Publish Date: 2021-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33203>CVE-2021-33203</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.9</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: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://docs.djangoproject.com/en/3.2/releases/security/">https://docs.djangoproject.com/en/3.2/releases/security/</a></p>
<p>Release Date: 2021-06-08</p>
<p>Fix Resolution: Django - 2.2.24, 3.1.12, 3.2.4</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
|
True
|
Django-3.2-py3-none-any.whl: 16 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (Django version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-34265](https://www.mend.io/vulnerability-database/CVE-2022-34265) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | Django - 3.2.14,4.0.6 | ✅ |
| [CVE-2022-28346](https://www.mend.io/vulnerability-database/CVE-2022-28346) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | 3.2.13 | ✅ |
| [CVE-2022-28347](https://www.mend.io/vulnerability-database/CVE-2022-28347) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | 3.2.13 | ✅ |
| [CVE-2021-35042](https://www.mend.io/vulnerability-database/CVE-2021-35042) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> Critical | 9.8 | Django-3.2-py3-none-any.whl | Direct | Django - 3.1.13,3.2.5 | ✅ |
| [CVE-2022-36359](https://www.mend.io/vulnerability-database/CVE-2022-36359) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | Django-3.2-py3-none-any.whl | Direct | Django -3.2.15,4.0.7,4.1 | ✅ |
| [CVE-2022-41323](https://www.mend.io/vulnerability-database/CVE-2022-41323) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | 3.2.16 | ✅ |
| [CVE-2021-45115](https://www.mend.io/vulnerability-database/CVE-2021-45115) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | 3.2.11 | ✅ |
| [CVE-2022-23833](https://www.mend.io/vulnerability-database/CVE-2022-23833) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.27,3.2.12,4.0.2 | ✅ |
| [CVE-2021-31542](https://www.mend.io/vulnerability-database/CVE-2021-31542) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.21,3.1.9,3.2.1 | ✅ |
| [CVE-2021-33571](https://www.mend.io/vulnerability-database/CVE-2021-33571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.24, 3.1.12, 3.2.4 | ✅ |
| [CVE-2021-45116](https://www.mend.io/vulnerability-database/CVE-2021-45116) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Django-3.2-py3-none-any.whl | Direct | 3.2.11 | ✅ |
| [CVE-2021-44420](https://www.mend.io/vulnerability-database/CVE-2021-44420) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.25,3.1.14,3.2.10 | ✅ |
| [CVE-2022-22818](https://www.mend.io/vulnerability-database/CVE-2022-22818) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.27,3.2.12,4.0.2 | ✅ |
| [CVE-2021-32052](https://www.mend.io/vulnerability-database/CVE-2021-32052) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.22,3.1.10,3.2.2 | ✅ |
| [CVE-2021-45452](https://www.mend.io/vulnerability-database/CVE-2021-45452) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | Django-3.2-py3-none-any.whl | Direct | 3.2.11 | ✅ |
| [CVE-2021-33203](https://www.mend.io/vulnerability-database/CVE-2021-33203) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.9 | Django-3.2-py3-none-any.whl | Direct | Django - 2.2.24, 3.1.12, 3.2.4 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2022-34265</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.
Mend Note: After conducting further research, Mend has determined that all versions of Django before version 3.2.14 and before 4.0.6 are vulnerable to CVE-2022-34265.
<p>Publish Date: 2022-07-04
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34265>CVE-2022-34265</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/jul/04/security-releases/">https://www.djangoproject.com/weblog/2022/jul/04/security-releases/</a></p>
<p>Release Date: 2022-07-04</p>
<p>Fix Resolution: Django - 3.2.14,4.0.6</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2022-28346</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra() methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed **kwargs.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-28346>CVE-2022-28346</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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: 2022-04-12</p>
<p>Fix Resolution: 3.2.13</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2022-28347</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. This occurs by passing a crafted dictionary (with dictionary expansion) as the **options argument, and placing the injection payload in an option name.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-28347>CVE-2022-28347</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28347">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28347</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution: 3.2.13</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png' width=19 height=20> CVE-2021-35042</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.
<p>Publish Date: 2021-07-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-35042>CVE-2021-35042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2021/jul/01/security-releases/">https://www.djangoproject.com/weblog/2021/jul/01/security-releases/</a></p>
<p>Release Date: 2021-07-02</p>
<p>Fix Resolution: Django - 3.1.13,3.2.5</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-36359</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in the HTTP FileResponse class in Django 3.2 before 3.2.15 and 4.0 before 4.0.7. An application is vulnerable to a reflected file download (RFD) attack that sets the Content-Disposition header of a FileResponse when the filename is derived from user-supplied input.
<p>Publish Date: 2022-08-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-36359>CVE-2022-36359</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/aug/03/security-releases/">https://www.djangoproject.com/weblog/2022/aug/03/security-releases/</a></p>
<p>Release Date: 2022-08-03</p>
<p>Fix Resolution: Django -3.2.15,4.0.7,4.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-41323</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service attack via the locale parameter, which is treated as a regular expression.
<p>Publish Date: 2022-10-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41323>CVE-2022-41323</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41323">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41323</a></p>
<p>Release Date: 2022-10-16</p>
<p>Fix Resolution: 3.2.16</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-45115</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. UserAttributeSimilarityValidator incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values. In a situation where access to user registration was unrestricted, this provided a potential vector for a denial-of-service attack.
<p>Publish Date: 2022-01-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45115>CVE-2021-45115</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://www.djangoproject.com/weblog/2022/jan/04/security-releases/">https://www.djangoproject.com/weblog/2022/jan/04/security-releases/</a></p>
<p>Release Date: 2022-01-05</p>
<p>Fix Resolution: 3.2.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23833</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2. Passing certain inputs to multipart forms could result in an infinite loop when parsing files.
<p>Publish Date: 2022-02-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23833>CVE-2022-23833</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://www.djangoproject.com/weblog/2022/feb/01/security-releases/">https://www.djangoproject.com/weblog/2022/feb/01/security-releases/</a></p>
<p>Release Date: 2022-02-03</p>
<p>Fix Resolution: Django - 2.2.27,3.2.12,4.0.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-31542</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.
<p>Publish Date: 2021-05-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-31542>CVE-2021-31542</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2021/may/04/security-releases/">https://www.djangoproject.com/weblog/2021/may/04/security-releases/</a></p>
<p>Release Date: 2021-05-05</p>
<p>Fix Resolution: Django - 2.2.21,3.1.9,3.2.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-33571</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+..) .
<p>Publish Date: 2021-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33571>CVE-2021-33571</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2021/jun/02/security-releases/">https://www.djangoproject.com/weblog/2021/jun/02/security-releases/</a></p>
<p>Release Date: 2021-06-08</p>
<p>Fix Resolution: Django - 2.2.24, 3.1.12, 3.2.4</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-45116</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. Due to leveraging the Django Template Language's variable resolution logic, the dictsort template filter was potentially vulnerable to information disclosure, or an unintended method call, if passed a suitably crafted key.
<p>Publish Date: 2022-01-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45116>CVE-2021-45116</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/jan/04/security-releases/">https://www.djangoproject.com/weblog/2022/jan/04/security-releases/</a></p>
<p>Release Date: 2022-01-05</p>
<p>Fix Resolution: 3.2.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44420</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths.
<p>Publish Date: 2021-12-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44420>CVE-2021-44420</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://docs.djangoproject.com/en/3.2/releases/security/">https://docs.djangoproject.com/en/3.2/releases/security/</a></p>
<p>Release Date: 2021-12-08</p>
<p>Fix Resolution: Django - 2.2.25,3.1.14,3.2.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22818</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The {% debug %} template tag in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2 does not properly encode the current context. This may lead to XSS.
<p>Publish Date: 2022-02-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22818>CVE-2022-22818</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/feb/01/security-releases/">https://www.djangoproject.com/weblog/2022/feb/01/security-releases/</a></p>
<p>Release Date: 2022-02-03</p>
<p>Fix Resolution: Django - 2.2.27,3.2.12,4.0.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-32052</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers.
<p>Publish Date: 2021-05-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-32052>CVE-2021-32052</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052</a></p>
<p>Release Date: 2021-05-06</p>
<p>Fix Resolution: Django - 2.2.22,3.1.10,3.2.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-45452</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Storage.save in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows directory traversal if crafted filenames are directly passed to it.
<p>Publish Date: 2022-01-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45452>CVE-2021-45452</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2022/jan/04/security-releases/">https://www.djangoproject.com/weblog/2022/jan/04/security-releases/</a></p>
<p>Release Date: 2022-01-05</p>
<p>Fix Resolution: 3.2.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-33203</summary>
### Vulnerable Library - <b>Django-3.2-py3-none-any.whl</b></p>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl">https://files.pythonhosted.org/packages/a8/9b/fe94c509e514f6c227308e81076506eb9d67f2bfb8061ce5cdfbde0432e3/Django-3.2-py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.2-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kferrara1313/da-react-challenge/commit/94731a295f5f68e636dfeade0140eb69a43e69a0">94731a295f5f68e636dfeade0140eb69a43e69a0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.
<p>Publish Date: 2021-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33203>CVE-2021-33203</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.9</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: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://docs.djangoproject.com/en/3.2/releases/security/">https://docs.djangoproject.com/en/3.2/releases/security/</a></p>
<p>Release Date: 2021-06-08</p>
<p>Fix Resolution: Django - 2.2.24, 3.1.12, 3.2.4</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
|
non_infrastructure
|
django none any whl vulnerabilities highest severity is vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt found in head commit a href vulnerabilities cve severity cvss dependency type fixed in django version remediation available critical django none any whl direct django critical django none any whl direct critical django none any whl direct critical django none any whl direct django high django none any whl direct django high django none any whl direct high django none any whl direct high django none any whl direct django high django none any whl direct django high django none any whl direct django high django none any whl direct high django none any whl direct django medium django none any whl direct django medium django none any whl direct django medium django none any whl direct medium django none any whl direct django details cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in django before and before the trunc and extract database functions are subject to sql injection if untrusted data is used as a kind lookup name value applications that constrain the lookup name and kind choice to a known safe list are unaffected mend note after conducting further research mend has determined that all versions of django before version and before are vulnerable to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in django before before and before queryset annotate aggregate and extra methods are subject to sql injection in column aliases via a crafted dictionary with dictionary expansion as the passed kwargs publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details a sql injection issue was discovered in queryset explain in django before before and before this occurs by passing a crafted dictionary with dictionary expansion as the options argument and placing the injection payload in an option name publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details django x before and x before allows queryset order by sql injection if order by is untrusted input from a client of a web application publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in the http fileresponse class in django before and before an application is vulnerable to a reflected file download rfd attack that sets the content disposition header of a fileresponse when the filename is derived from user supplied input publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details in django before before and before internationalized urls were subject to a potential denial of service attack via the locale parameter which is treated as a regular expression publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in django before before and before userattributesimilarityvalidator incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values in a situation where access to user registration was unrestricted this provided a potential vector for a denial of service attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in multipartparser in django before before and before passing certain inputs to multipart forms could result in an infinite loop when parsing files 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 django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details in django before before and before multipartparser uploadedfile and fieldfile allowed directory traversal via uploaded files with suitably crafted file names publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details in django before x before and before urlvalidator validate address and validate address do not prohibit leading zero characters in octal literals this may allow a bypass of access control that is based on ip addresses validate address and validate address are unaffected with python publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in django before before and before due to leveraging the django template language s variable resolution logic the dictsort template filter was potentially vulnerable to information disclosure or an unintended method call if passed a suitably crafted key publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details in django before before and before http requests for urls with trailing newlines could bypass upstream access control based on url paths publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details the debug template tag in django before before and before does not properly encode the current context this may lead to xss publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details in django before before and before with python urlvalidator does not prohibit newlines and tabs unless the urlfield form field is used if an application uses values with newlines in an http response header injection can occur django itself is unaffected because httpresponse prohibits newlines in http headers publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details storage save in django before before and before allows directory traversal if crafted filenames are directly passed to it publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href found in base branch master vulnerability details django before x before and x before has a potential directory traversal via django contrib admindocs staff members could use the templatedetailview view to check the existence of arbitrary files additionally if and only if the default admindocs templates have been customized by application developers to also show file contents then not only the existence but also the file contents would have been exposed in other words there is directory traversal outside of the template root directories 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue
| 0
|
307,176
| 9,414,250,969
|
IssuesEvent
|
2019-04-10 09:42:24
|
StrangeLoopGames/EcoIssues
|
https://api.github.com/repos/StrangeLoopGames/EcoIssues
|
closed
|
Add dependencies check on first start.
|
Medium Priority
|
Add dependencies check on first game start.
All needed software installed, and available.
To exclude this situation.
Player install game from steam, installing .net is not succeed.
Result - singleplayer silence not working, return to main menu after launch.
Only after player try to launch server manually, they see error.
|
1.0
|
Add dependencies check on first start. - Add dependencies check on first game start.
All needed software installed, and available.
To exclude this situation.
Player install game from steam, installing .net is not succeed.
Result - singleplayer silence not working, return to main menu after launch.
Only after player try to launch server manually, they see error.
|
non_infrastructure
|
add dependencies check on first start add dependencies check on first game start all needed software installed and available to exclude this situation player install game from steam installing net is not succeed result singleplayer silence not working return to main menu after launch only after player try to launch server manually they see error
| 0
|
19,584
| 3,227,243,090
|
IssuesEvent
|
2015-10-11 01:10:00
|
krashanoff/cleanrip
|
https://api.github.com/repos/krashanoff/cleanrip
|
closed
|
Error checking
|
auto-migrated Priority-Medium Type-Defect
|
```
1.0.4
Would it be possible to add the option to do error checking? Since the DVD
speed is more than half slower than most USB drives this shouldn't affect
speed. Anyway this would be an option so users could turn it off. I had
problems with a corrupt FAT32 drive, only got the second chunk and the program
didn't tell me.
```
Original issue reported on code.google.com by `dominicp...@gmail.com` on 29 Sep 2010 at 2:04
|
1.0
|
Error checking - ```
1.0.4
Would it be possible to add the option to do error checking? Since the DVD
speed is more than half slower than most USB drives this shouldn't affect
speed. Anyway this would be an option so users could turn it off. I had
problems with a corrupt FAT32 drive, only got the second chunk and the program
didn't tell me.
```
Original issue reported on code.google.com by `dominicp...@gmail.com` on 29 Sep 2010 at 2:04
|
non_infrastructure
|
error checking would it be possible to add the option to do error checking since the dvd speed is more than half slower than most usb drives this shouldn t affect speed anyway this would be an option so users could turn it off i had problems with a corrupt drive only got the second chunk and the program didn t tell me original issue reported on code google com by dominicp gmail com on sep at
| 0
|
7,444
| 6,961,838,903
|
IssuesEvent
|
2017-12-08 11:04:18
|
servicecatalog/oscm
|
https://api.github.com/repos/servicecatalog/oscm
|
closed
|
Remove exported projects from fb_tomee_maven branch
|
infrastructure
|
Remove projects which are exported to following repositories
https://github.com/servicecatalog/oscm-interfaces
https://github.com/servicecatalog/oscm-commons
https://github.com/servicecatalog/oscm-app
Check if unittests are also exported.
|
1.0
|
Remove exported projects from fb_tomee_maven branch - Remove projects which are exported to following repositories
https://github.com/servicecatalog/oscm-interfaces
https://github.com/servicecatalog/oscm-commons
https://github.com/servicecatalog/oscm-app
Check if unittests are also exported.
|
infrastructure
|
remove exported projects from fb tomee maven branch remove projects which are exported to following repositories check if unittests are also exported
| 1
|
28,048
| 22,783,006,371
|
IssuesEvent
|
2022-07-08 22:45:45
|
ProjectPythia/pythia-foundations
|
https://api.github.com/repos/ProjectPythia/pythia-foundations
|
opened
|
Foundations should be citable with a DOI
|
infrastructure
|
As I mused about over at https://github.com/ProjectPythiaCookbooks/projectpythiacookbooks.github.io/issues/15, the Foundations book should be citable with a DOI pointing to specific tagged versions of the book. Zenodo makes this pretty simple.
We would need to create a tagged Release of the source repo. I think this would be a good summer goal, once we get a few of the outstanding content gaps resolved, such as #232 (work in progress in #248)
|
1.0
|
Foundations should be citable with a DOI - As I mused about over at https://github.com/ProjectPythiaCookbooks/projectpythiacookbooks.github.io/issues/15, the Foundations book should be citable with a DOI pointing to specific tagged versions of the book. Zenodo makes this pretty simple.
We would need to create a tagged Release of the source repo. I think this would be a good summer goal, once we get a few of the outstanding content gaps resolved, such as #232 (work in progress in #248)
|
infrastructure
|
foundations should be citable with a doi as i mused about over at the foundations book should be citable with a doi pointing to specific tagged versions of the book zenodo makes this pretty simple we would need to create a tagged release of the source repo i think this would be a good summer goal once we get a few of the outstanding content gaps resolved such as work in progress in
| 1
|
343,106
| 10,325,343,564
|
IssuesEvent
|
2019-09-01 16:34:02
|
thonny/thonny
|
https://api.github.com/repos/thonny/thonny
|
closed
|
Investigate function call keyword argument completion
|
feature low priority
|
**[Original report](https://bitbucket.org/bitbucket-issue-migration\thonny-issues.zip/issue/300) by me.**
----------------------------------------
See https://github.com/srusskih/SublimeJEDI and https://github.com/davidhalter/jedi-vim
|
1.0
|
Investigate function call keyword argument completion - **[Original report](https://bitbucket.org/bitbucket-issue-migration\thonny-issues.zip/issue/300) by me.**
----------------------------------------
See https://github.com/srusskih/SublimeJEDI and https://github.com/davidhalter/jedi-vim
|
non_infrastructure
|
investigate function call keyword argument completion by me see and
| 0
|
19,175
| 13,198,902,050
|
IssuesEvent
|
2020-08-14 04:05:02
|
vuejs/vetur
|
https://api.github.com/repos/vuejs/vetur
|
closed
|
Clean up CI output
|
infrastructure
|
https://github.com/microsoft/vscode/blob/34dee12ff383689d9d5e62f6b263ed644e4df44d/src/vs/workbench/api/common/extHostTypes.ts#L1012-L1016
Need to validate that all symbols have a `name`
```
name must not be falsy: Error: name must not be falsy
at Function.validate (/Users/pine/Code/mine/vetur/vetur/.vscode-test/vscode-1.47.3/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:442:18)
at new x (/Users/pine/Code/mine/vetur/vetur/.vscode-test/vscode-1.47.3/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:441:950)
at new x (/Users/pine/Code/mine/vetur/vetur/.vscode-test/vscode-1.47.3/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:429:431)
at asSymbolInformation (/Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/protocolConverter.js:449:22)
at /Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/protocolConverter.js:429:42
at Array.map (<anonymous>)
at Object.asSymbolInformations (/Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/protocolConverter.js:429:23)
at /Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/client.js:1088:70
```
This can be turned off with `update.mode: "none"`
```
[main 2020-08-13T05:31:48.191Z] update#setState checking for updates
[main 2020-08-13T05:31:48.989Z] update#setState idle
```
Not sure what to do for this one.
```
stty: stdin isn't a terminal
```
Not sure what to do either. Just filter it out probably.
```
(node:6848) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
```
|
1.0
|
Clean up CI output - https://github.com/microsoft/vscode/blob/34dee12ff383689d9d5e62f6b263ed644e4df44d/src/vs/workbench/api/common/extHostTypes.ts#L1012-L1016
Need to validate that all symbols have a `name`
```
name must not be falsy: Error: name must not be falsy
at Function.validate (/Users/pine/Code/mine/vetur/vetur/.vscode-test/vscode-1.47.3/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:442:18)
at new x (/Users/pine/Code/mine/vetur/vetur/.vscode-test/vscode-1.47.3/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:441:950)
at new x (/Users/pine/Code/mine/vetur/vetur/.vscode-test/vscode-1.47.3/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:429:431)
at asSymbolInformation (/Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/protocolConverter.js:449:22)
at /Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/protocolConverter.js:429:42
at Array.map (<anonymous>)
at Object.asSymbolInformations (/Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/protocolConverter.js:429:23)
at /Users/pine/Code/mine/vetur/vetur/node_modules/vscode-languageclient/lib/client.js:1088:70
```
This can be turned off with `update.mode: "none"`
```
[main 2020-08-13T05:31:48.191Z] update#setState checking for updates
[main 2020-08-13T05:31:48.989Z] update#setState idle
```
Not sure what to do for this one.
```
stty: stdin isn't a terminal
```
Not sure what to do either. Just filter it out probably.
```
(node:6848) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
```
|
infrastructure
|
clean up ci output need to validate that all symbols have a name name must not be falsy error name must not be falsy at function validate users pine code mine vetur vetur vscode test vscode visual studio code app contents resources app out vs workbench services extensions node extensionhostprocess js at new x users pine code mine vetur vetur vscode test vscode visual studio code app contents resources app out vs workbench services extensions node extensionhostprocess js at new x users pine code mine vetur vetur vscode test vscode visual studio code app contents resources app out vs workbench services extensions node extensionhostprocess js at assymbolinformation users pine code mine vetur vetur node modules vscode languageclient lib protocolconverter js at users pine code mine vetur vetur node modules vscode languageclient lib protocolconverter js at array map at object assymbolinformations users pine code mine vetur vetur node modules vscode languageclient lib protocolconverter js at users pine code mine vetur vetur node modules vscode languageclient lib client js this can be turned off with update mode none update setstate checking for updates update setstate idle not sure what to do for this one stty stdin isn t a terminal not sure what to do either just filter it out probably node electron loading non context aware native modules in the renderer process is deprecated and will stop working at some point in the future please see for more information
| 1
|
5,420
| 5,641,613,846
|
IssuesEvent
|
2017-04-06 19:07:01
|
dotnet/roslyn
|
https://api.github.com/repos/dotnet/roslyn
|
closed
|
Tests are Hanging
|
Area-Infrastructure Flaky Test Urgency-Soon
|
There seems to be an intermittent problem with hanging vsi tests. As an example, see the logs saved in "\\mlangfs1\public\frsilb\logs\Jenkins Hang". These are from a debug and release build of https://github.com/dotnet/roslyn/pull/18454.
|
1.0
|
Tests are Hanging - There seems to be an intermittent problem with hanging vsi tests. As an example, see the logs saved in "\\mlangfs1\public\frsilb\logs\Jenkins Hang". These are from a debug and release build of https://github.com/dotnet/roslyn/pull/18454.
|
infrastructure
|
tests are hanging there seems to be an intermittent problem with hanging vsi tests as an example see the logs saved in public frsilb logs jenkins hang these are from a debug and release build of
| 1
|
20,119
| 13,673,186,408
|
IssuesEvent
|
2020-09-29 09:30:03
|
google/web-stories-wp
|
https://api.github.com/repos/google/web-stories-wp
|
opened
|
Package Reorganization
|
Pod: WP & Infra Type: Infrastructure Type: Task
|
## Task Description
Our current repository structure has organically grown over the past year to a point where we have multiple different "packages" spread across different folders. Some of them are pretty self-contained and could be easily published standalone (e.g. all the Karma packages), others are a bit more intertwined with other packages. Some are used for build tooling, others for the WordPress integration or the actual editor.
At the same time, they all share the same `package.json` file, making it difficult to know which packages actually use a certain dependency. Ideally, each package would have its own `package.json` file to declare its dependencies. While this can be achieved using [Lerna](https://lerna.js.org/) or [Yarn workspaces](https://yarnpkg.com/features/workspaces), my hope here is to eventually use [npm workspaces](https://github.com/npm/rfcs/blob/latest/accepted/0026-workspaces.md) using the upcoming npm v7 release, as it would not require new tooling or huge migration.
Anyhow, to get there we need to first get our directory structure in shape to make working with our "packages" more straightforward.
I propose making `/assets/src` the root for all our packages, containing the following directories:
* `activation-notice` (unchanged)
* `animation` (unchanged)
* `commander` (moved from `/bin`)
* `dashboard` (unchanged)
* `date` (unchanged)
* `edit-story` (unchanged)
* `fonts` (**new**, split out from `/bin`) - contains `fonts.json` and the script to update it
* `karma-fixture` (moved from `/karma/fixture`)
* `karma-cuj-reporter` (moved from `/karma`)
* `karma-puppeteer-client` (moved from `/karma`)
* `migration` (moved from `edit-story/migration`) - used also by `dashboard` and CI, now also contains the LI script to run migrations
* `karma-failed-tests-reporter` (moved from `/karma`)
* `karma-puppeteer-launcher` (moved from `/karma`)
* `story-embed-block` (unchanged)
* `tracking` (unchanged)
|
1.0
|
Package Reorganization - ## Task Description
Our current repository structure has organically grown over the past year to a point where we have multiple different "packages" spread across different folders. Some of them are pretty self-contained and could be easily published standalone (e.g. all the Karma packages), others are a bit more intertwined with other packages. Some are used for build tooling, others for the WordPress integration or the actual editor.
At the same time, they all share the same `package.json` file, making it difficult to know which packages actually use a certain dependency. Ideally, each package would have its own `package.json` file to declare its dependencies. While this can be achieved using [Lerna](https://lerna.js.org/) or [Yarn workspaces](https://yarnpkg.com/features/workspaces), my hope here is to eventually use [npm workspaces](https://github.com/npm/rfcs/blob/latest/accepted/0026-workspaces.md) using the upcoming npm v7 release, as it would not require new tooling or huge migration.
Anyhow, to get there we need to first get our directory structure in shape to make working with our "packages" more straightforward.
I propose making `/assets/src` the root for all our packages, containing the following directories:
* `activation-notice` (unchanged)
* `animation` (unchanged)
* `commander` (moved from `/bin`)
* `dashboard` (unchanged)
* `date` (unchanged)
* `edit-story` (unchanged)
* `fonts` (**new**, split out from `/bin`) - contains `fonts.json` and the script to update it
* `karma-fixture` (moved from `/karma/fixture`)
* `karma-cuj-reporter` (moved from `/karma`)
* `karma-puppeteer-client` (moved from `/karma`)
* `migration` (moved from `edit-story/migration`) - used also by `dashboard` and CI, now also contains the LI script to run migrations
* `karma-failed-tests-reporter` (moved from `/karma`)
* `karma-puppeteer-launcher` (moved from `/karma`)
* `story-embed-block` (unchanged)
* `tracking` (unchanged)
|
infrastructure
|
package reorganization task description our current repository structure has organically grown over the past year to a point where we have multiple different packages spread across different folders some of them are pretty self contained and could be easily published standalone e g all the karma packages others are a bit more intertwined with other packages some are used for build tooling others for the wordpress integration or the actual editor at the same time they all share the same package json file making it difficult to know which packages actually use a certain dependency ideally each package would have its own package json file to declare its dependencies while this can be achieved using or my hope here is to eventually use using the upcoming npm release as it would not require new tooling or huge migration anyhow to get there we need to first get our directory structure in shape to make working with our packages more straightforward i propose making assets src the root for all our packages containing the following directories activation notice unchanged animation unchanged commander moved from bin dashboard unchanged date unchanged edit story unchanged fonts new split out from bin contains fonts json and the script to update it karma fixture moved from karma fixture karma cuj reporter moved from karma karma puppeteer client moved from karma migration moved from edit story migration used also by dashboard and ci now also contains the li script to run migrations karma failed tests reporter moved from karma karma puppeteer launcher moved from karma story embed block unchanged tracking unchanged
| 1
|
25,721
| 4,424,912,298
|
IssuesEvent
|
2016-08-16 14:03:15
|
PowerDNS/pdns
|
https://api.github.com/repos/PowerDNS/pdns
|
closed
|
Boost context path and namespace changed in boost 1.61
|
defect rec
|
Reported by @IngoThierack in #4014
```
checking for Boost headers version >= 1.35.0... /opt/lib/boost/1.61-4.8//include
checking for Boost's header version... 1_61
checking for the flags needed to use pthreads... conftest.cpp: In function 'int main()':
conftest.cpp:33:24: warning: null argument where non-null required (argument 1) [-Wnonnull]
pthread_attr_init(0); pthread_cleanup_push(0, 0);
^
conftest.cpp:34:27: warning: null argument where non-null required (argument 1) [-Wnonnull]
pthread_create(0,0,0,0); pthread_cleanup_pop(0);
^
conftest.cpp:34:27: warning: null argument where non-null required (argument 3) [-Wnonnull]
conftest.cpp:32:34: warning: 'th' is used uninitialized in this function [-Wuninitialized]
pthread_t th; pthread_join(th, 0);
^
-pthread
checking for the toolset name used by Boost for g++... gcc48 -gcc
checking whether Boost is new enough to use the context library...... yes
checking boost/system/error_code.hpp usability... yes
checking boost/system/error_code.hpp presence... yes
checking for boost/system/error_code.hpp... yes
checking for the Boost system library... yes
sed: can't read conftest.o: No such file or directory
checking boost/thread.hpp usability... yes
checking boost/thread.hpp presence... yes
checking for boost/thread.hpp... yes
checking for the Boost thread library... (cached) yes
configure: checking whether the Boost context library actually links...
checking boost/context/fcontext.hpp usability... no
checking boost/context/fcontext.hpp presence... no
checking for boost/context/fcontext.hpp... no
configure: error: cannot find boost/context/fcontext.hpp
```
Problem with boost 1.61 is, the structure of the files are changed :(
the fcontext.hpp is now found under detail/
```
/opt/lib/boost/1.61-4.8/include/boost/context
[ingo@build-el7 context]$ find .
.
./execution_context.hpp
./execution_context_v2_void.ipp
./preallocated.hpp
./stack_traits.hpp
./all.hpp
./protected_fixedsize_stack.hpp
./execution_context_v1.hpp
./flags.hpp
./pooled_fixedsize_stack.hpp
./fixedsize_stack.hpp
./stack_context.hpp
./segmented_stack.hpp
./execution_context_v2.hpp
./posix
./posix/protected_fixedsize_stack.hpp
./posix/segmented_stack.hpp
./detail
./detail/disable_overload.hpp
./detail/fcontext_sparc.hpp
./detail/fcontext_x86_64_win.hpp
./detail/fcontext_ppc.hpp
./detail/tuple.hpp
./detail/apply.hpp
./detail/exchange.hpp
./detail/index_sequence.hpp
./detail/exception.hpp
./detail/fcontext_i386.hpp
./detail/fcontext_mips.hpp
./detail/fcontext_i386_win.hpp
./detail/fcontext.hpp
./detail/fcontext_arm_win.hpp
./detail/invoke.hpp
./detail/fcontext_x86_64.hpp
./detail/fcontext_arm.hpp
./detail/fcontext_arm_mac.hpp
./detail/config.hpp
./windows
./windows/protected_fixedsize_stack.hpp
```
With the fix for #4014 (in #4052), we now fallback to the old System V ucontexts. But we should ensure we still use boost fcontexts with boost 1.61 onward.
|
1.0
|
Boost context path and namespace changed in boost 1.61 - Reported by @IngoThierack in #4014
```
checking for Boost headers version >= 1.35.0... /opt/lib/boost/1.61-4.8//include
checking for Boost's header version... 1_61
checking for the flags needed to use pthreads... conftest.cpp: In function 'int main()':
conftest.cpp:33:24: warning: null argument where non-null required (argument 1) [-Wnonnull]
pthread_attr_init(0); pthread_cleanup_push(0, 0);
^
conftest.cpp:34:27: warning: null argument where non-null required (argument 1) [-Wnonnull]
pthread_create(0,0,0,0); pthread_cleanup_pop(0);
^
conftest.cpp:34:27: warning: null argument where non-null required (argument 3) [-Wnonnull]
conftest.cpp:32:34: warning: 'th' is used uninitialized in this function [-Wuninitialized]
pthread_t th; pthread_join(th, 0);
^
-pthread
checking for the toolset name used by Boost for g++... gcc48 -gcc
checking whether Boost is new enough to use the context library...... yes
checking boost/system/error_code.hpp usability... yes
checking boost/system/error_code.hpp presence... yes
checking for boost/system/error_code.hpp... yes
checking for the Boost system library... yes
sed: can't read conftest.o: No such file or directory
checking boost/thread.hpp usability... yes
checking boost/thread.hpp presence... yes
checking for boost/thread.hpp... yes
checking for the Boost thread library... (cached) yes
configure: checking whether the Boost context library actually links...
checking boost/context/fcontext.hpp usability... no
checking boost/context/fcontext.hpp presence... no
checking for boost/context/fcontext.hpp... no
configure: error: cannot find boost/context/fcontext.hpp
```
Problem with boost 1.61 is, the structure of the files are changed :(
the fcontext.hpp is now found under detail/
```
/opt/lib/boost/1.61-4.8/include/boost/context
[ingo@build-el7 context]$ find .
.
./execution_context.hpp
./execution_context_v2_void.ipp
./preallocated.hpp
./stack_traits.hpp
./all.hpp
./protected_fixedsize_stack.hpp
./execution_context_v1.hpp
./flags.hpp
./pooled_fixedsize_stack.hpp
./fixedsize_stack.hpp
./stack_context.hpp
./segmented_stack.hpp
./execution_context_v2.hpp
./posix
./posix/protected_fixedsize_stack.hpp
./posix/segmented_stack.hpp
./detail
./detail/disable_overload.hpp
./detail/fcontext_sparc.hpp
./detail/fcontext_x86_64_win.hpp
./detail/fcontext_ppc.hpp
./detail/tuple.hpp
./detail/apply.hpp
./detail/exchange.hpp
./detail/index_sequence.hpp
./detail/exception.hpp
./detail/fcontext_i386.hpp
./detail/fcontext_mips.hpp
./detail/fcontext_i386_win.hpp
./detail/fcontext.hpp
./detail/fcontext_arm_win.hpp
./detail/invoke.hpp
./detail/fcontext_x86_64.hpp
./detail/fcontext_arm.hpp
./detail/fcontext_arm_mac.hpp
./detail/config.hpp
./windows
./windows/protected_fixedsize_stack.hpp
```
With the fix for #4014 (in #4052), we now fallback to the old System V ucontexts. But we should ensure we still use boost fcontexts with boost 1.61 onward.
|
non_infrastructure
|
boost context path and namespace changed in boost reported by ingothierack in checking for boost headers version opt lib boost include checking for boost s header version checking for the flags needed to use pthreads conftest cpp in function int main conftest cpp warning null argument where non null required argument pthread attr init pthread cleanup push conftest cpp warning null argument where non null required argument pthread create pthread cleanup pop conftest cpp warning null argument where non null required argument conftest cpp warning th is used uninitialized in this function pthread t th pthread join th pthread checking for the toolset name used by boost for g gcc checking whether boost is new enough to use the context library yes checking boost system error code hpp usability yes checking boost system error code hpp presence yes checking for boost system error code hpp yes checking for the boost system library yes sed can t read conftest o no such file or directory checking boost thread hpp usability yes checking boost thread hpp presence yes checking for boost thread hpp yes checking for the boost thread library cached yes configure checking whether the boost context library actually links checking boost context fcontext hpp usability no checking boost context fcontext hpp presence no checking for boost context fcontext hpp no configure error cannot find boost context fcontext hpp problem with boost is the structure of the files are changed the fcontext hpp is now found under detail opt lib boost include boost context find execution context hpp execution context void ipp preallocated hpp stack traits hpp all hpp protected fixedsize stack hpp execution context hpp flags hpp pooled fixedsize stack hpp fixedsize stack hpp stack context hpp segmented stack hpp execution context hpp posix posix protected fixedsize stack hpp posix segmented stack hpp detail detail disable overload hpp detail fcontext sparc hpp detail fcontext win hpp detail fcontext ppc hpp detail tuple hpp detail apply hpp detail exchange hpp detail index sequence hpp detail exception hpp detail fcontext hpp detail fcontext mips hpp detail fcontext win hpp detail fcontext hpp detail fcontext arm win hpp detail invoke hpp detail fcontext hpp detail fcontext arm hpp detail fcontext arm mac hpp detail config hpp windows windows protected fixedsize stack hpp with the fix for in we now fallback to the old system v ucontexts but we should ensure we still use boost fcontexts with boost onward
| 0
|
96,511
| 10,934,396,431
|
IssuesEvent
|
2019-11-24 11:19:21
|
roundcube/roundcubemail
|
https://api.github.com/repos/roundcube/roundcubemail
|
closed
|
Wrong file ownerships after upgrade as root
|
C: Documentation C: Installer bug
|
When upgrading Roundcube as root via
```
wget https://github.com/roundcube/roundcubemail/releases/download/1.4.0/roundcubemail-1.4.0-complete.tar.gz
tar xf roundcubemail-1.4.0-complete.tar.gz
./roundcubemail-1.4.0/bin/installto.sh DESTDIR
```
the installed files have the ownership pair `501:80`, which is probably always invalid.
Please either set the ownership after the upgrade of all files in DESTDIR (e.g. to the owner of DESTDIR/index.php prior the upgrade) or print a warning at the end of the upgrade script, that the administrator might need to fix them.
|
1.0
|
Wrong file ownerships after upgrade as root - When upgrading Roundcube as root via
```
wget https://github.com/roundcube/roundcubemail/releases/download/1.4.0/roundcubemail-1.4.0-complete.tar.gz
tar xf roundcubemail-1.4.0-complete.tar.gz
./roundcubemail-1.4.0/bin/installto.sh DESTDIR
```
the installed files have the ownership pair `501:80`, which is probably always invalid.
Please either set the ownership after the upgrade of all files in DESTDIR (e.g. to the owner of DESTDIR/index.php prior the upgrade) or print a warning at the end of the upgrade script, that the administrator might need to fix them.
|
non_infrastructure
|
wrong file ownerships after upgrade as root when upgrading roundcube as root via wget tar xf roundcubemail complete tar gz roundcubemail bin installto sh destdir the installed files have the ownership pair which is probably always invalid please either set the ownership after the upgrade of all files in destdir e g to the owner of destdir index php prior the upgrade or print a warning at the end of the upgrade script that the administrator might need to fix them
| 0
|
27,224
| 21,477,294,143
|
IssuesEvent
|
2022-04-26 14:38:23
|
OpenEnergyPlatform/ontology
|
https://api.github.com/repos/OpenEnergyPlatform/ontology
|
opened
|
Locating term-tracker for imported modules
|
external ontology organisation To do ontology infrastructure
|
## Description of the issue
`term tracker items` added in PR #1086 (all related to imported ontologies) are located in the `oeo.omn`-file and not in the defining ontology. As these are the only ones located there, this grew my suspicion.
How does the general policy concerning `term tracker items` and imported ontologies look like?
Have there been any similar situations in the past?
|
1.0
|
Locating term-tracker for imported modules - ## Description of the issue
`term tracker items` added in PR #1086 (all related to imported ontologies) are located in the `oeo.omn`-file and not in the defining ontology. As these are the only ones located there, this grew my suspicion.
How does the general policy concerning `term tracker items` and imported ontologies look like?
Have there been any similar situations in the past?
|
infrastructure
|
locating term tracker for imported modules description of the issue term tracker items added in pr all related to imported ontologies are located in the oeo omn file and not in the defining ontology as these are the only ones located there this grew my suspicion how does the general policy concerning term tracker items and imported ontologies look like have there been any similar situations in the past
| 1
|
801
| 2,915,634,473
|
IssuesEvent
|
2015-06-23 13:36:53
|
deconst/deconst-docs
|
https://api.github.com/repos/deconst/deconst-docs
|
opened
|
Shipping checklist for systemd infra overhaul
|
infrastructure
|
The infrastructure overhaul in deconst/deploy#38 will take some care to :shipit:. Running Ansible on the existing hosts won't work because:
* It changes the names of server groups and load balancers because it implements #99 along the way.
* I've fiddled with the names of the systemd units that we're creating and managing, which means that we'd end up with both the old and new ones colliding unless I did a lot of tedious, error-prone, manual clean-up work.
Instead, I'm going to ship this in true immutable-infrastructure fashion, by spinning up brand-new hosts with the fancy new configuration and :hocho: the old ones. Here's the checklist:
- [ ] Update the drc production playbook repository. Modify its `credentials.yml` to include the new keys. Stash the new version of `credentials.yml` in the usual place.
- [ ] Run the new playbook on the production account. This will launch a brand-new cluster and new load balancer set.
- [ ] Edit `/etc/hosts` and poke around the new cluster to ensure that everything is present and accounted for.
- [ ] Make a note of the nodes on the new balancers. Delete the new balancers. Edit the names of the existing balancers to match the new pattern.
- [ ] Manually add nodes to the existing balancers to direct traffic to the new cluster. Drain connections from the old nodes, then delete them.
- [ ] Delete the old cluster.
- [ ] Give the playbook a final run to be sure that it's working as expected.
|
1.0
|
Shipping checklist for systemd infra overhaul - The infrastructure overhaul in deconst/deploy#38 will take some care to :shipit:. Running Ansible on the existing hosts won't work because:
* It changes the names of server groups and load balancers because it implements #99 along the way.
* I've fiddled with the names of the systemd units that we're creating and managing, which means that we'd end up with both the old and new ones colliding unless I did a lot of tedious, error-prone, manual clean-up work.
Instead, I'm going to ship this in true immutable-infrastructure fashion, by spinning up brand-new hosts with the fancy new configuration and :hocho: the old ones. Here's the checklist:
- [ ] Update the drc production playbook repository. Modify its `credentials.yml` to include the new keys. Stash the new version of `credentials.yml` in the usual place.
- [ ] Run the new playbook on the production account. This will launch a brand-new cluster and new load balancer set.
- [ ] Edit `/etc/hosts` and poke around the new cluster to ensure that everything is present and accounted for.
- [ ] Make a note of the nodes on the new balancers. Delete the new balancers. Edit the names of the existing balancers to match the new pattern.
- [ ] Manually add nodes to the existing balancers to direct traffic to the new cluster. Drain connections from the old nodes, then delete them.
- [ ] Delete the old cluster.
- [ ] Give the playbook a final run to be sure that it's working as expected.
|
infrastructure
|
shipping checklist for systemd infra overhaul the infrastructure overhaul in deconst deploy will take some care to shipit running ansible on the existing hosts won t work because it changes the names of server groups and load balancers because it implements along the way i ve fiddled with the names of the systemd units that we re creating and managing which means that we d end up with both the old and new ones colliding unless i did a lot of tedious error prone manual clean up work instead i m going to ship this in true immutable infrastructure fashion by spinning up brand new hosts with the fancy new configuration and hocho the old ones here s the checklist update the drc production playbook repository modify its credentials yml to include the new keys stash the new version of credentials yml in the usual place run the new playbook on the production account this will launch a brand new cluster and new load balancer set edit etc hosts and poke around the new cluster to ensure that everything is present and accounted for make a note of the nodes on the new balancers delete the new balancers edit the names of the existing balancers to match the new pattern manually add nodes to the existing balancers to direct traffic to the new cluster drain connections from the old nodes then delete them delete the old cluster give the playbook a final run to be sure that it s working as expected
| 1
|
179,234
| 13,852,063,504
|
IssuesEvent
|
2020-10-15 05:42:16
|
microsoft/AzureStorageExplorer
|
https://api.github.com/repos/microsoft/AzureStorageExplorer
|
closed
|
The layout of the descriptions in the 'Sign In' dialog is unsightly when using device code flow sign-in
|
:beetle: regression 🧪 testing
|
**Storage Explorer Version:** 1.16.0-dev
**Build**: 20201012.5
**Branch**: main
**Platform/OS:** Windows 10/ MacOS Catalina
**Architecture**: ia32/x64
**Regression From:** Previous release (1.15.1)
**Steps to reproduce:**
1. Launch Storage Explorer -> Open 'Settings -> Application' -> Enable the setting 'Use device code flow sign-in'.
2. Open connect dialog -> Click 'Next' -> Check the popped dialog.
**Expect Experience:**
The layout of the descriptions in the dialog is normal.
**Actual Experience:**
The layout of the descriptions in the dialog is unsightly.
|
1.0
|
The layout of the descriptions in the 'Sign In' dialog is unsightly when using device code flow sign-in - **Storage Explorer Version:** 1.16.0-dev
**Build**: 20201012.5
**Branch**: main
**Platform/OS:** Windows 10/ MacOS Catalina
**Architecture**: ia32/x64
**Regression From:** Previous release (1.15.1)
**Steps to reproduce:**
1. Launch Storage Explorer -> Open 'Settings -> Application' -> Enable the setting 'Use device code flow sign-in'.
2. Open connect dialog -> Click 'Next' -> Check the popped dialog.
**Expect Experience:**
The layout of the descriptions in the dialog is normal.
**Actual Experience:**
The layout of the descriptions in the dialog is unsightly.
|
non_infrastructure
|
the layout of the descriptions in the sign in dialog is unsightly when using device code flow sign in storage explorer version dev build branch main platform os windows macos catalina architecture regression from previous release steps to reproduce launch storage explorer open settings application enable the setting use device code flow sign in open connect dialog click next check the popped dialog expect experience the layout of the descriptions in the dialog is normal actual experience the layout of the descriptions in the dialog is unsightly
| 0
|
162,049
| 20,164,363,796
|
IssuesEvent
|
2022-02-10 01:45:43
|
kapseliboi/dapp
|
https://api.github.com/repos/kapseliboi/dapp
|
opened
|
CVE-2021-27290 (High) detected in ssri-7.1.0.tgz, ssri-6.0.1.tgz
|
security vulnerability
|
## CVE-2021-27290 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ssri-7.1.0.tgz</b>, <b>ssri-6.0.1.tgz</b></p></summary>
<p>
<details><summary><b>ssri-7.1.0.tgz</b></p></summary>
<p>Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ssri/-/ssri-7.1.0.tgz">https://registry.npmjs.org/ssri/-/ssri-7.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ssri/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.2.tgz (Root Library)
- terser-webpack-plugin-2.3.5.tgz
- cacache-13.0.1.tgz
- :x: **ssri-7.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ssri-6.0.1.tgz</b></p></summary>
<p>Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz">https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/webpack/node_modules/ssri/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.2.tgz (Root Library)
- webpack-4.42.0.tgz
- terser-webpack-plugin-1.4.4.tgz
- cacache-12.0.4.tgz
- :x: **ssri-6.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27290>CVE-2021-27290</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-vx3p-948g-6vhq">https://github.com/advisories/GHSA-vx3p-948g-6vhq</a></p>
<p>Release Date: 2021-03-12</p>
<p>Fix Resolution: ssri - 6.0.2,7.1.1,8.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-27290 (High) detected in ssri-7.1.0.tgz, ssri-6.0.1.tgz - ## CVE-2021-27290 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ssri-7.1.0.tgz</b>, <b>ssri-6.0.1.tgz</b></p></summary>
<p>
<details><summary><b>ssri-7.1.0.tgz</b></p></summary>
<p>Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ssri/-/ssri-7.1.0.tgz">https://registry.npmjs.org/ssri/-/ssri-7.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ssri/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.2.tgz (Root Library)
- terser-webpack-plugin-2.3.5.tgz
- cacache-13.0.1.tgz
- :x: **ssri-7.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ssri-6.0.1.tgz</b></p></summary>
<p>Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz">https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/webpack/node_modules/ssri/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.2.tgz (Root Library)
- webpack-4.42.0.tgz
- terser-webpack-plugin-1.4.4.tgz
- cacache-12.0.4.tgz
- :x: **ssri-6.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27290>CVE-2021-27290</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-vx3p-948g-6vhq">https://github.com/advisories/GHSA-vx3p-948g-6vhq</a></p>
<p>Release Date: 2021-03-12</p>
<p>Fix Resolution: ssri - 6.0.2,7.1.1,8.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_infrastructure
|
cve high detected in ssri tgz ssri tgz cve high severity vulnerability vulnerable libraries ssri tgz ssri tgz ssri tgz standard subresource integrity library parses serializes generates and verifies integrity metadata according to the sri spec library home page a href path to dependency file package json path to vulnerable library node modules ssri package json dependency hierarchy react scripts tgz root library terser webpack plugin tgz cacache tgz x ssri tgz vulnerable library ssri tgz standard subresource integrity library parses serializes generates and verifies integrity metadata according to the sri spec library home page a href path to dependency file package json path to vulnerable library node modules webpack node modules ssri package json dependency hierarchy react scripts tgz root library webpack tgz terser webpack plugin tgz cacache tgz x ssri tgz vulnerable library found in base branch master vulnerability details ssri fixed in processes sris using a regular expression which is vulnerable to a denial of service malicious sris could take an extremely long time to process leading to denial of service this issue only affects consumers using the strict option 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 ssri step up your open source security game with whitesource
| 0
|
159,681
| 25,031,477,935
|
IssuesEvent
|
2022-11-04 12:46:19
|
webaverse/app
|
https://api.github.com/repos/webaverse/app
|
closed
|
Art: Title Deeds
|
design
|
A special type of Card is the Title Deed, which grants the right to use (and restrict access to) real estate on The Street.
The information it might display include:
* Season / Zone at the top
* Title name
* Transaction date
* Hash string
* Certified to ___
* Description
* Signed by ___ on [date]
* Signature
* Stamp seal (QR code)
Example title deed from meatspace:
Old
New
https://www.govtech.com/biz/heres-what-a-blockchain-property-deed-looks-like.html
|
1.0
|
Art: Title Deeds - A special type of Card is the Title Deed, which grants the right to use (and restrict access to) real estate on The Street.
The information it might display include:
* Season / Zone at the top
* Title name
* Transaction date
* Hash string
* Certified to ___
* Description
* Signed by ___ on [date]
* Signature
* Stamp seal (QR code)
Example title deed from meatspace:
Old
New
https://www.govtech.com/biz/heres-what-a-blockchain-property-deed-looks-like.html
|
non_infrastructure
|
art title deeds a special type of card is the title deed which grants the right to use and restrict access to real estate on the street the information it might display include season zone at the top title name transaction date hash string certified to description signed by on signature stamp seal qr code example title deed from meatspace old new
| 0
|
28,030
| 22,773,601,863
|
IssuesEvent
|
2022-07-08 12:29:02
|
airyhq/airy
|
https://api.github.com/repos/airyhq/airy
|
closed
|
Create endpoints to install components
|
infrastructure
|
Create an endpoint that receives a request to install a component and then the controller would deploy the appropriate helm chart for it
|
1.0
|
Create endpoints to install components - Create an endpoint that receives a request to install a component and then the controller would deploy the appropriate helm chart for it
|
infrastructure
|
create endpoints to install components create an endpoint that receives a request to install a component and then the controller would deploy the appropriate helm chart for it
| 1
|
290,897
| 8,909,438,671
|
IssuesEvent
|
2019-01-18 06:17:04
|
artemii235/SuperNET
|
https://api.github.com/repos/artemii235/SuperNET
|
opened
|
Remove the hardcoded wait timeout in swaps.
|
High priority bug
|
Calculate it properly depending on coins used. E.G. it should be higher for BTC due to high blocktime. Current 1000 seconds timeout is not usable in many cases.
|
1.0
|
Remove the hardcoded wait timeout in swaps. - Calculate it properly depending on coins used. E.G. it should be higher for BTC due to high blocktime. Current 1000 seconds timeout is not usable in many cases.
|
non_infrastructure
|
remove the hardcoded wait timeout in swaps calculate it properly depending on coins used e g it should be higher for btc due to high blocktime current seconds timeout is not usable in many cases
| 0
|
253,547
| 19,122,949,085
|
IssuesEvent
|
2021-12-01 01:56:47
|
Encapsule/arcccore
|
https://api.github.com/repos/Encapsule/arcccore
|
closed
|
arccore.disciminator should allow override of ID, name, and description
|
enhancement documentation test discriminator
|
... so it's even remotely feasible to differentiate between different discriminator filter instances at runtime under the debugger without having to compare the associated target filter arrays.
|
1.0
|
arccore.disciminator should allow override of ID, name, and description - ... so it's even remotely feasible to differentiate between different discriminator filter instances at runtime under the debugger without having to compare the associated target filter arrays.
|
non_infrastructure
|
arccore disciminator should allow override of id name and description so it s even remotely feasible to differentiate between different discriminator filter instances at runtime under the debugger without having to compare the associated target filter arrays
| 0
|
635,991
| 20,516,812,337
|
IssuesEvent
|
2022-03-01 12:39:39
|
kytos-ng/topology
|
https://api.github.com/repos/kytos-ng/topology
|
opened
|
PortMod should be sent when an interface is disabled or enabled
|
enhancement priority_major
|
Currently, when an interface is disabled even tough the `enabled` state will be set as false, a `PortMod` OpenFlow message isn't being sent, as a result it's possible to have an interface `enabled: False`, and `active: True`, since it won't actually administratively disable the interface on the switch.
When implementing this feature, the `PortConfig` config should correctly use the `OFPPC_PORT_DOWN` flag, and the advertise capability shouldn't be impacted. This also should be tested with NoviFlow switches to make sure it'll work as intended and no side effect is observed, simulating a disable/enable should bring up a link correctly. Also, an end-to-end test should be added to make sure we have it covered for OvS OF 1.3.
An existing workaround, even though it won't send the actual `PortMod` message, but if an operator were also to shut down via another management plane that would have an equivalent effect, but it's not that practical to keep doing this.
|
1.0
|
PortMod should be sent when an interface is disabled or enabled - Currently, when an interface is disabled even tough the `enabled` state will be set as false, a `PortMod` OpenFlow message isn't being sent, as a result it's possible to have an interface `enabled: False`, and `active: True`, since it won't actually administratively disable the interface on the switch.
When implementing this feature, the `PortConfig` config should correctly use the `OFPPC_PORT_DOWN` flag, and the advertise capability shouldn't be impacted. This also should be tested with NoviFlow switches to make sure it'll work as intended and no side effect is observed, simulating a disable/enable should bring up a link correctly. Also, an end-to-end test should be added to make sure we have it covered for OvS OF 1.3.
An existing workaround, even though it won't send the actual `PortMod` message, but if an operator were also to shut down via another management plane that would have an equivalent effect, but it's not that practical to keep doing this.
|
non_infrastructure
|
portmod should be sent when an interface is disabled or enabled currently when an interface is disabled even tough the enabled state will be set as false a portmod openflow message isn t being sent as a result it s possible to have an interface enabled false and active true since it won t actually administratively disable the interface on the switch when implementing this feature the portconfig config should correctly use the ofppc port down flag and the advertise capability shouldn t be impacted this also should be tested with noviflow switches to make sure it ll work as intended and no side effect is observed simulating a disable enable should bring up a link correctly also an end to end test should be added to make sure we have it covered for ovs of an existing workaround even though it won t send the actual portmod message but if an operator were also to shut down via another management plane that would have an equivalent effect but it s not that practical to keep doing this
| 0
|
233,516
| 17,868,202,384
|
IssuesEvent
|
2021-09-06 12:11:36
|
reactor/reactor-core
|
https://api.github.com/repos/reactor/reactor-core
|
closed
|
errorContinue javadoc sometimes badly placed within `@TAGS` section
|
type/documentation
|
Since #2333, the onDiscard support and onErrorContinue support tags have been turned into plain paragraphs.
Unfortunately, some of the old tags were not placed at the beginning of the tags section, and the search-and-replacement has left these as paragraphs inside the block tag section.
These paragraphs are still visible in the javadoc, but are randomly appended to whichever tag is above the paragraph, which interrupts the tag block (params, return clause, etc...)
Example: https://projectreactor.io/docs/core/3.4.9/api/reactor/core/publisher/Flux.html#filter-java.util.function.Predicate-
These occurrences should be hunted down and fixed by just moving the paragraphs one line above the first javadoc block tag.
|
1.0
|
errorContinue javadoc sometimes badly placed within `@TAGS` section - Since #2333, the onDiscard support and onErrorContinue support tags have been turned into plain paragraphs.
Unfortunately, some of the old tags were not placed at the beginning of the tags section, and the search-and-replacement has left these as paragraphs inside the block tag section.
These paragraphs are still visible in the javadoc, but are randomly appended to whichever tag is above the paragraph, which interrupts the tag block (params, return clause, etc...)
Example: https://projectreactor.io/docs/core/3.4.9/api/reactor/core/publisher/Flux.html#filter-java.util.function.Predicate-
These occurrences should be hunted down and fixed by just moving the paragraphs one line above the first javadoc block tag.
|
non_infrastructure
|
errorcontinue javadoc sometimes badly placed within tags section since the ondiscard support and onerrorcontinue support tags have been turned into plain paragraphs unfortunately some of the old tags were not placed at the beginning of the tags section and the search and replacement has left these as paragraphs inside the block tag section these paragraphs are still visible in the javadoc but are randomly appended to whichever tag is above the paragraph which interrupts the tag block params return clause etc example these occurrences should be hunted down and fixed by just moving the paragraphs one line above the first javadoc block tag
| 0
|
99,026
| 11,103,419,997
|
IssuesEvent
|
2019-12-17 03:47:00
|
pytorch/fairseq
|
https://api.github.com/repos/pytorch/fairseq
|
closed
|
Please correct the minimum required Python version
|
documentation
|
The main [README file](https://github.com/pytorch/fairseq/blob/50cf3bb596abba70a0770ad2308fed0f4d32a002/README.md#requirements-and-installation) of this repo claims the minimum required Python version is 3.5, but the code occasionally uses a trailing comma at the end of a function's argument list and that's a syntax feature that was [only introduced in Python 3.6](https://bugs.python.org/issue9232). Here is an example: https://github.com/pytorch/fairseq/blob/50cf3bb596abba70a0770ad2308fed0f4d32a002/fairseq/models/transformer.py#L257
Therefore, the code currently does not run under Python 3.5.
Please either update the README file to set the minimum required Python version to 3.6 or modify the code to remove all syntax that is incompatible with Python 3.5.
|
1.0
|
Please correct the minimum required Python version - The main [README file](https://github.com/pytorch/fairseq/blob/50cf3bb596abba70a0770ad2308fed0f4d32a002/README.md#requirements-and-installation) of this repo claims the minimum required Python version is 3.5, but the code occasionally uses a trailing comma at the end of a function's argument list and that's a syntax feature that was [only introduced in Python 3.6](https://bugs.python.org/issue9232). Here is an example: https://github.com/pytorch/fairseq/blob/50cf3bb596abba70a0770ad2308fed0f4d32a002/fairseq/models/transformer.py#L257
Therefore, the code currently does not run under Python 3.5.
Please either update the README file to set the minimum required Python version to 3.6 or modify the code to remove all syntax that is incompatible with Python 3.5.
|
non_infrastructure
|
please correct the minimum required python version the main of this repo claims the minimum required python version is but the code occasionally uses a trailing comma at the end of a function s argument list and that s a syntax feature that was here is an example therefore the code currently does not run under python please either update the readme file to set the minimum required python version to or modify the code to remove all syntax that is incompatible with python
| 0
|
4,716
| 2,610,143,801
|
IssuesEvent
|
2015-02-26 18:45:19
|
chrsmith/hedgewars
|
https://api.github.com/repos/chrsmith/hedgewars
|
closed
|
bad team name filtering while editing
|
auto-migrated Priority-Low Type-Defect
|
```
i try to set team name which contains special characters. the ones that are not
allowed in windows's file names make team disappear from the list when saved.
no warnings are raised.
team name effect
------------------------------------------------------
\team saves as "team". seems to be ok
.\team saves as "team" also
..\team disappears
/team disappears
:team disappears
also tried to create team wich has forbidden file name "con" (upper\lower case)
and it does disappear too
run on xpsp3 x86.
regards
```
-----
Original issue reported on code.google.com by `push....@gmail.com` on 4 Jan 2011 at 6:34
* Blocking: #189
|
1.0
|
bad team name filtering while editing - ```
i try to set team name which contains special characters. the ones that are not
allowed in windows's file names make team disappear from the list when saved.
no warnings are raised.
team name effect
------------------------------------------------------
\team saves as "team". seems to be ok
.\team saves as "team" also
..\team disappears
/team disappears
:team disappears
also tried to create team wich has forbidden file name "con" (upper\lower case)
and it does disappear too
run on xpsp3 x86.
regards
```
-----
Original issue reported on code.google.com by `push....@gmail.com` on 4 Jan 2011 at 6:34
* Blocking: #189
|
non_infrastructure
|
bad team name filtering while editing i try to set team name which contains special characters the ones that are not allowed in windows s file names make team disappear from the list when saved no warnings are raised team name effect team saves as team seems to be ok team saves as team also team disappears team disappears team disappears also tried to create team wich has forbidden file name con upper lower case and it does disappear too run on regards original issue reported on code google com by push gmail com on jan at blocking
| 0
|
35,507
| 31,770,011,955
|
IssuesEvent
|
2023-09-12 11:10:07
|
Tonomy-Foundation/Tonomy-ID-Management
|
https://api.github.com/repos/Tonomy-Foundation/Tonomy-ID-Management
|
opened
|
Telos UK onboarding - learn their tech stack
|
infrastructure
|
Acceptance criteria
- [ ] read the wiki http://wiki.advantapro.com/index.php?title=Main_Page
- [ ] go through source repositories:
- [ ] https://gitlab.com/advantaproductions/telos-configs
- [ ] https://gitlab.com/advantaproductions/ansible
- [ ] https://github.com/varilink/telos-eosio
- [ ] Get access to communication groups, introduce yourself
- [ ] get access to Hetzner (IaaS) https://robot.hetzner.com/server
https://www.notion.so/tonomy-foundation/Telos-UK-fcbba33dbecc4b949203f124b32c7a4c
|
1.0
|
Telos UK onboarding - learn their tech stack - Acceptance criteria
- [ ] read the wiki http://wiki.advantapro.com/index.php?title=Main_Page
- [ ] go through source repositories:
- [ ] https://gitlab.com/advantaproductions/telos-configs
- [ ] https://gitlab.com/advantaproductions/ansible
- [ ] https://github.com/varilink/telos-eosio
- [ ] Get access to communication groups, introduce yourself
- [ ] get access to Hetzner (IaaS) https://robot.hetzner.com/server
https://www.notion.so/tonomy-foundation/Telos-UK-fcbba33dbecc4b949203f124b32c7a4c
|
infrastructure
|
telos uk onboarding learn their tech stack acceptance criteria read the wiki go through source repositories get access to communication groups introduce yourself get access to hetzner iaas
| 1
|
31,047
| 25,293,239,522
|
IssuesEvent
|
2022-11-17 03:11:56
|
alan-turing-institute/the-turing-way
|
https://api.github.com/repos/alan-turing-institute/the-turing-way
|
opened
|
Proposal: delete `figure_list.md`
|
idea-for-discussion infrastructure
|
https://github.com/alan-turing-institute/the-turing-way/blob/main/book/website/figures/_figure-list.md
---
- When the book started, it had [17 different figures](https://github.com/alan-turing-institute/the-turing-way/blob/840067db4839e59019183f84853a2fa4efca2413/website/_site/assets/figures/figure_list.md). As of today, it has [roughly 200](https://github.com/alan-turing-institute/the-turing-way/tree/main/book/website/figures).
- Despite [guidance indicating that all figures should be added to `figure_list.md`](https://the-turing-way.netlify.app/community-handbook/style/style-figures.html#image-type-file-name-size-and-location), that file is only [infrequently updated](https://github.com/alan-turing-institute/the-turing-way/commits/main/book/website/figures/_figure-list.md).
- It is currently [not listed in the TOC](https://github.com/alan-turing-institute/the-turing-way/issues/2611).
I argue that instead of updating it, we remove it, since I am not convinced of its utility.
|
1.0
|
Proposal: delete `figure_list.md` - https://github.com/alan-turing-institute/the-turing-way/blob/main/book/website/figures/_figure-list.md
---
- When the book started, it had [17 different figures](https://github.com/alan-turing-institute/the-turing-way/blob/840067db4839e59019183f84853a2fa4efca2413/website/_site/assets/figures/figure_list.md). As of today, it has [roughly 200](https://github.com/alan-turing-institute/the-turing-way/tree/main/book/website/figures).
- Despite [guidance indicating that all figures should be added to `figure_list.md`](https://the-turing-way.netlify.app/community-handbook/style/style-figures.html#image-type-file-name-size-and-location), that file is only [infrequently updated](https://github.com/alan-turing-institute/the-turing-way/commits/main/book/website/figures/_figure-list.md).
- It is currently [not listed in the TOC](https://github.com/alan-turing-institute/the-turing-way/issues/2611).
I argue that instead of updating it, we remove it, since I am not convinced of its utility.
|
infrastructure
|
proposal delete figure list md when the book started it had as of today it has despite that file is only it is currently i argue that instead of updating it we remove it since i am not convinced of its utility
| 1
|
717,811
| 24,692,062,106
|
IssuesEvent
|
2022-10-19 09:16:18
|
frequenz-floss/frequenz-sdk-python
|
https://api.github.com/repos/frequenz-floss/frequenz-sdk-python
|
opened
|
Fix typing for Actor's `join()` method
|
priority:low type:bug part:actor
|
### What happened?
When calling the `join()` method of an actor (or `_stop()` or probably any method defined by the `@actor` decorator) we get an error from `mypy` complaining about the method not existing in the actor class, for example:
```
test.py:10: error: "SampleActor" has no attribute "join"
```
### What did you expect instead?
No errors when calling the method.
### Affected version(s)
All
### Affected part(s)
I don't know (part:❓)
### Extra information
The `typing_extensions` package (#19), in particular the `@dataclass_transform()` decorator, might help with this, it needs further investigation.
|
1.0
|
Fix typing for Actor's `join()` method - ### What happened?
When calling the `join()` method of an actor (or `_stop()` or probably any method defined by the `@actor` decorator) we get an error from `mypy` complaining about the method not existing in the actor class, for example:
```
test.py:10: error: "SampleActor" has no attribute "join"
```
### What did you expect instead?
No errors when calling the method.
### Affected version(s)
All
### Affected part(s)
I don't know (part:❓)
### Extra information
The `typing_extensions` package (#19), in particular the `@dataclass_transform()` decorator, might help with this, it needs further investigation.
|
non_infrastructure
|
fix typing for actor s join method what happened when calling the join method of an actor or stop or probably any method defined by the actor decorator we get an error from mypy complaining about the method not existing in the actor class for example test py error sampleactor has no attribute join what did you expect instead no errors when calling the method affected version s all affected part s i don t know part ❓ extra information the typing extensions package in particular the dataclass transform decorator might help with this it needs further investigation
| 0
|
101,217
| 12,675,514,227
|
IssuesEvent
|
2020-06-19 01:58:36
|
greatnewcls/KNLWKKGOTE62XGFSVAZIMVUH
|
https://api.github.com/repos/greatnewcls/KNLWKKGOTE62XGFSVAZIMVUH
|
closed
|
P3+H8jpQDZrmhv17Y2SazyIhJ9i9GmieyftaV8IHUhQFmz0xlCtfn32XcVCpYv/aYW3ZVkIF1wZm4vpWsgEpEiNnMRQ4OlYi3f5d2w6hL7U2sk43WFYZjwfnkbh6Jhu8R721lmOpsjtqmlR80gD7ohXHJZ3KXr9LCmzT80t4E4g=
|
design
|
+k4fzIXQSVCCeujhvJiVjcG8e+QbeH+ne+b+zGtk1PmC5ywkwjGHrYEOViTZeCHxfcjWVBl0IMf4VjoBSWf60d/ZnEeJ8esS+W19MpO679SuDnBLjReeVd4/dsjzj1LyNmj9ivHeVLQ0ylOMUgVW0fC8MWEEK7PheutnK2DAT7GItL1wno87570FyQoSry4lziTn6CO8kr6u8Z4U7Fg5HgfJOWcyKIk1QBB29DIXBwD+fHtascDmyaNm4ltdw/oK4UAqz/FU4DfB4GEb5LtEY30JambpnvjOoKq+PjWzvan7IaMkigaifSYY9ePk87KgBp9LjTcU4zpZpwyHDGO7TYrFLOqLwIMzP2EAVkbriB1fc1LlceTMb/xOWb96IfHfukkqZIyTQBUYZ+RrHHgRAFBKDRE/ROd3drM4CrSw4cmYprSeNGYLM7tx4G2HuZVW5l1pam6tF7Yp9Lvd1zaCaz3PkxyF9VAOX7IWkLS4jerbr2PexnR6uwgYfzGmNPR6vuiXlQCupEiiIUQfBXGihrDZXwedgyWFea6qXwUH9oiVEhuI6VOyDsK518ljJhAtbswlzEyu8/ZFiB3XtVpC52glgsmkLpTS41yqlmqiN5IJrfwvVMDz+9DejMuosOUcGfnmyW/gLxNbXYXN0kcwefUMNv+MRmUPCY4rwayNc1PP49DQYHJs38riCFxd97VIuw3s4V61umFBlXrtShm8jDjtr/OaqX130gxWMosDsiGKxSzqi8CDMz9hAFZG64gdisdtAV45QiERh5yZ6zTdLEK8KnE+0w6IoVBJbJkzgzkGQJkPmrih8s5uMM0ky692oNFiL6O5XFRthsYeSMMTiwiGBsX3RkME3yktiSS7ppQG2++DVgpADxJAkJNpguv6PuUHoHqPfl1nOdIsTJAusCkF3UJP3ur+jtU7HGGquwCKxSzqi8CDMz9hAFZG64gd2JcKFAFvFRlIi1ehwTf6IaiAQ/rQ1aWveTi1WX5+cpRKyc6LfhUTX+LRLnhPG5RAxCP8Y4cOlLk9t9uCVW/Oy5mTWUWCu7l/Ewf/2Wb1KHKC5RiEMn8963I69np7iBIy0VBojyGNkpCz9m+1EpfAjTLjoweP/lBmKnSnIWTWsXsEeMjt7tYl4LwE4Nf6AbZJhaRkJvGb+7Llt0mKBGDjAaXwjiXVcetzs3/urjX+ZUHd8rRZz0K9zgbVLOP8yVBu6PDH6k2ZAPQHcLfoe9jRdP+3du0OINfU4euoyVIq4fLNgLUXiV8C2eZvCqybkVQXisUs6ovAgzM/YQBWRuuIHQVunXzbHp1EqXX/u+ljCArjJ8QKn8ReiVicCh7JyXZtNEIl2LmJ+9oRM8fsc+XEAypQaU2KA6IaAie95AsrnCO2cNBztgYMwLIZL8LQwxIJAiIhKRZIftSODoKGssv+Cdnq6bYvUDjg8UsT8wVyNuO8PVKbc9rHw2nq696l6sj2Du2B54G6TonGT6JYlV8RuAaWSv08s0l2jQ7vhk+AS60OBeA2Ydop3A3tYVh9bT8psNBsSMshROfCOdKaB2Hu0fsulaH5tbOnS5HKcLOpwqbx1u9Tu4ZnmI6apY1FyKKLwrdEi1c3FfM/W4SmdewWv89/oHPjBGOlv7iujWSkWO9miwiKxBr02035hpdVOhRQv352UUsw9WcHqHyplFrCB6csnTQQ6kdzaDfVwxdyZMQbiDOz3Xlkwp6nPQXF/CQqBl64QlwK0UhyyeqKDD7SDvfi1/DH2OaIS1iUrBwqKZ1J97tsUcOPuv+pIkRgOlH+kkoF6SBQfzCjyvMc+6lM25l/VPvBnNMCxKZzYJ92zno+Bu6NkSqow9W4nJ5oFnKscsKmubx6Ck4rWCD84k+5qyS3TpOr2sZJe9OsoNtqDWnZeKswOLRf0OUOg0svwSCMLvnmlCauazBOsukyf2kPcay4KSXV8ST4upZbsrjcsyG0mqijrieaIEy6EUxp5BWxWVqFHQTk66yXDB45V2+mk69YokglNg9I+Rz/eA/D3QeYEZk6r9qCBKeFa3pvhIXENEIl2LmJ+9oRM8fsc+XEA7S396e+KR2lshlGKRctAh8bZivd4rIs4zsQCL1cE9HeF7iJzg8xZBWJXwHVN35Gf5Sd4Z0rtlGkAZuQaHwcIG8Pjmfv1sZlRaR4VU0mlZpFNEIl2LmJ+9oRM8fsc+XEAxiDAhm3yN3t+7UI4gAHZGtmHgpIJgUAPtJiwU7eZQWq3KZD3JNXH+uDSdJY3njJZYJONHfiMeCdT1McVQdhLbq4cFO4yaRCGUr8QRgBlGLlPk8EXsOAVHyMWebZa+fRK/iPZUjVoxUvneXp36ZkFhZ9a5NASfYccmLJFJ6zW3T2UwIUfaPBzmwV2B9Pk0uRH0HoaiLw62lLbrrVcFYCt8RFE9/T6PhjkU4DLdT5sKgGx6a+PW9R95JrKfn5/Z7oV2HuGMu8EqoYxhx1SQum83i7qQJtx0zxjfNKPRssCFC3A8KA17pKG3OyVmu9S2FpaQwMvOM2yDmb3EynZqO/K9g6hZZKy3SIQrcCadoJVB7wuaT3O6LAvX7upgWoffOy23yU7lcZ+LrPgE2uENZH0NUPKvkIQ45Qnyl5ebYsYswrrsmtvnynDP6r+UHYDZ7JIWL4Av+qhBxhyWBb23VJ8OlCiJ+LnrB2z771l07h+xlctMSbIaE/GP3tu0NXXabyDi50pRbWNtleciaLT/udHaz3AYJuE42+RJhOMYMcUWauE9Vgmug3I6TudCBdRErMVjPJNHdpQWazS2dAh+YOn+Ggurc5yUVBe9AR2xR6pqpoKibT2psdbvDV2Q9n3P8MlTPzZRnPhElu413QGaWzIrIZZ3rf5iQBGYRYY519ULyTH/HukMCsNlo4nx3HD+Q+EZq+EY01UFM1nYNKW6Z42AjP7nEqhnpjWULGXOlRibgTG3Oj87qkwsC/xQxMrv0dlG//1RK0WdyTNKeuAzINBk3Trv68VT8v1qtu25gqzYKtTLuQzeG9lRyiYKJ9hOgqcBKq5s0iN9sWr0ii4pCWpJUth+Rqe3xxODl1SmO96fG/4Gy7YkpvegNkh9XfHiAfY0pbDPDKzjxrchW9aW44mD9zAGlzjK4eV2ZWLxVzt6P+OF7YwV9S4XOhVxzXeOkD49NzZwQGiPQu+7AZEd28+qUQHCbitm0ODz8DqccUNtcYBeZaAggmoNrob5Xdx5FmHJYKTuXlkZlUWPLsyHhJjicnmTf3ZxTiR+qCpd7HgDYqgmsM6WBUQg1GphLpm+K/PJzEqp0ZiHTyBeLOTZxewQqnccu+O9zcnDhuqzA9Tk5EvykX3eXq7bq3jH/PxEJMfmklLXoT/nEl3maWydS7TPly6SXi9GkgDGvNXKYva5NX4k3ZHJAcvV5pFubWXkP5KYB3ztSe43lJasEvMviae6HK0z9CB+O2pWmHeMzkxb63ipf5CwcmrYhRYOQzDCr1fR07C3D9Zeg/vV6cH5EFn1WOX1CK3SlNzCPvwprNJB2xCfSREzp37rxkR3GdHeOBWUt+Xryqy19Ci1GLDbsp4BEGyjknjO3bgFPYoecBSjuHqT0xZAESib/yjwgbeaubdKFJXzwTq5FMlpkc8P1nhkOwKMfrCcjCPbCxptgtCfa9ipf5CwcmrYhRYOQzDCr1fSA5V2VYGxm5Ta1YUUuQYoKubfVPrvdeRH7lgzikekOjr57GTvbg5FvntM5oFfAlZj9dYUq4jmjC41o8gMo6WRZicQIZSWMnoFt163sib4++FuwiCAoF8To3Hh+4FiYLdWQ/qrIcVucoWINxY8U0x+0fZ30JIHDqT9maqx0255xNhZMeC0fn9UbsAmWveLWHeX+iJ069H+UzFucVAmpQh2WKxSzqi8CDMz9hAFZG64gd0Ymk+GWq5FS2NvBfXAJVua3e7qJlDfVnPRQOO0SL1cm2q3LuJikkLtBTi7EXBN8oVW/0bbM2ARrLUeYWYN47MG2yr7oh+RrKG40nLaX0/EuKxSzqi8CDMz9hAFZG64gdqQMR6GFXRTIzKqWDk6fNuFfZ03fs/J/0S1BQVvFX+gwsVslz6Mey+6ZRiyKpELBujegeT1zqzz2wK1d+qP/WPPwbXE6cBT1jJvN669UhLtTceip5QKwmCUweOAiW/mnNrYTEXaiqS6GrO+tfZjjb2orFLOqLwIMzP2EAVkbriB3MPk85nahjXKYDhy545z+t+DFFoeF8ax8QuFxrn8HIfB4DRMyHQMjPLPB+nGCloTuKl/kLByatiFFg5DMMKvV94I7y5BgRow5HWUtXtNA5oDGPrTJe/vdq1jkAbzeIBTwqPTP8CUs4WGgaDPRarSiPkbRO17O8BUn6QP9rpd0v4EVYasblVIWXzSOw60xCudET1WCa6DcjpO50IF1ESsxWmFpnYkHQJ2CBm1VUTc45G5zUhTdHOw+tUNbB7SgpOI8x2H35QseXUiq8p5/Ia+aHHPUNV+jwRenq0dKJ2+zXI7jF3KeGfdtNfryNq94Leji0k3JNaBDypwZP1tlmDg2VlM1ymOnXIFeXx+fWv86NLTA4DHz6S0F13aDp+vYyAv+t8JNVxGPa+9H2FpqCpXqX140Uhkc6EkUR/e9S553s64SksyX5jTOOMwKxGchcZoIAECVUNf+NU9i/3nwX+oRt6bzatHkH82B1A/5C7cQqDhUV0h7Hz/tJ627Pbx6//sBrSx96WPpDpIYJYolRqCvOisUs6ovAgzM/YQBWRuuIHQeQd93UKHEIP90iPNym+bn7m7zUhKtx/irLhU+E4kTYrlAk12HHmTRB1NSGL3KZCF0rgqzoHq69UYpH4qPfw4Qmx4OcfHQSGWjJVDMPr63vkcvFuSF7sm5IJttWK0WV2am2uc9DDz2F2yPPfUiv1lzUvXX3G+g9vGje2CNrKhpSmz1uNhgnsBImJuBWR4uBkl3ilrejQtSCNObvMVYPaQs=
|
1.0
|
P3+H8jpQDZrmhv17Y2SazyIhJ9i9GmieyftaV8IHUhQFmz0xlCtfn32XcVCpYv/aYW3ZVkIF1wZm4vpWsgEpEiNnMRQ4OlYi3f5d2w6hL7U2sk43WFYZjwfnkbh6Jhu8R721lmOpsjtqmlR80gD7ohXHJZ3KXr9LCmzT80t4E4g= - +k4fzIXQSVCCeujhvJiVjcG8e+QbeH+ne+b+zGtk1PmC5ywkwjGHrYEOViTZeCHxfcjWVBl0IMf4VjoBSWf60d/ZnEeJ8esS+W19MpO679SuDnBLjReeVd4/dsjzj1LyNmj9ivHeVLQ0ylOMUgVW0fC8MWEEK7PheutnK2DAT7GItL1wno87570FyQoSry4lziTn6CO8kr6u8Z4U7Fg5HgfJOWcyKIk1QBB29DIXBwD+fHtascDmyaNm4ltdw/oK4UAqz/FU4DfB4GEb5LtEY30JambpnvjOoKq+PjWzvan7IaMkigaifSYY9ePk87KgBp9LjTcU4zpZpwyHDGO7TYrFLOqLwIMzP2EAVkbriB1fc1LlceTMb/xOWb96IfHfukkqZIyTQBUYZ+RrHHgRAFBKDRE/ROd3drM4CrSw4cmYprSeNGYLM7tx4G2HuZVW5l1pam6tF7Yp9Lvd1zaCaz3PkxyF9VAOX7IWkLS4jerbr2PexnR6uwgYfzGmNPR6vuiXlQCupEiiIUQfBXGihrDZXwedgyWFea6qXwUH9oiVEhuI6VOyDsK518ljJhAtbswlzEyu8/ZFiB3XtVpC52glgsmkLpTS41yqlmqiN5IJrfwvVMDz+9DejMuosOUcGfnmyW/gLxNbXYXN0kcwefUMNv+MRmUPCY4rwayNc1PP49DQYHJs38riCFxd97VIuw3s4V61umFBlXrtShm8jDjtr/OaqX130gxWMosDsiGKxSzqi8CDMz9hAFZG64gdisdtAV45QiERh5yZ6zTdLEK8KnE+0w6IoVBJbJkzgzkGQJkPmrih8s5uMM0ky692oNFiL6O5XFRthsYeSMMTiwiGBsX3RkME3yktiSS7ppQG2++DVgpADxJAkJNpguv6PuUHoHqPfl1nOdIsTJAusCkF3UJP3ur+jtU7HGGquwCKxSzqi8CDMz9hAFZG64gd2JcKFAFvFRlIi1ehwTf6IaiAQ/rQ1aWveTi1WX5+cpRKyc6LfhUTX+LRLnhPG5RAxCP8Y4cOlLk9t9uCVW/Oy5mTWUWCu7l/Ewf/2Wb1KHKC5RiEMn8963I69np7iBIy0VBojyGNkpCz9m+1EpfAjTLjoweP/lBmKnSnIWTWsXsEeMjt7tYl4LwE4Nf6AbZJhaRkJvGb+7Llt0mKBGDjAaXwjiXVcetzs3/urjX+ZUHd8rRZz0K9zgbVLOP8yVBu6PDH6k2ZAPQHcLfoe9jRdP+3du0OINfU4euoyVIq4fLNgLUXiV8C2eZvCqybkVQXisUs6ovAgzM/YQBWRuuIHQVunXzbHp1EqXX/u+ljCArjJ8QKn8ReiVicCh7JyXZtNEIl2LmJ+9oRM8fsc+XEAypQaU2KA6IaAie95AsrnCO2cNBztgYMwLIZL8LQwxIJAiIhKRZIftSODoKGssv+Cdnq6bYvUDjg8UsT8wVyNuO8PVKbc9rHw2nq696l6sj2Du2B54G6TonGT6JYlV8RuAaWSv08s0l2jQ7vhk+AS60OBeA2Ydop3A3tYVh9bT8psNBsSMshROfCOdKaB2Hu0fsulaH5tbOnS5HKcLOpwqbx1u9Tu4ZnmI6apY1FyKKLwrdEi1c3FfM/W4SmdewWv89/oHPjBGOlv7iujWSkWO9miwiKxBr02035hpdVOhRQv352UUsw9WcHqHyplFrCB6csnTQQ6kdzaDfVwxdyZMQbiDOz3Xlkwp6nPQXF/CQqBl64QlwK0UhyyeqKDD7SDvfi1/DH2OaIS1iUrBwqKZ1J97tsUcOPuv+pIkRgOlH+kkoF6SBQfzCjyvMc+6lM25l/VPvBnNMCxKZzYJ92zno+Bu6NkSqow9W4nJ5oFnKscsKmubx6Ck4rWCD84k+5qyS3TpOr2sZJe9OsoNtqDWnZeKswOLRf0OUOg0svwSCMLvnmlCauazBOsukyf2kPcay4KSXV8ST4upZbsrjcsyG0mqijrieaIEy6EUxp5BWxWVqFHQTk66yXDB45V2+mk69YokglNg9I+Rz/eA/D3QeYEZk6r9qCBKeFa3pvhIXENEIl2LmJ+9oRM8fsc+XEA7S396e+KR2lshlGKRctAh8bZivd4rIs4zsQCL1cE9HeF7iJzg8xZBWJXwHVN35Gf5Sd4Z0rtlGkAZuQaHwcIG8Pjmfv1sZlRaR4VU0mlZpFNEIl2LmJ+9oRM8fsc+XEAxiDAhm3yN3t+7UI4gAHZGtmHgpIJgUAPtJiwU7eZQWq3KZD3JNXH+uDSdJY3njJZYJONHfiMeCdT1McVQdhLbq4cFO4yaRCGUr8QRgBlGLlPk8EXsOAVHyMWebZa+fRK/iPZUjVoxUvneXp36ZkFhZ9a5NASfYccmLJFJ6zW3T2UwIUfaPBzmwV2B9Pk0uRH0HoaiLw62lLbrrVcFYCt8RFE9/T6PhjkU4DLdT5sKgGx6a+PW9R95JrKfn5/Z7oV2HuGMu8EqoYxhx1SQum83i7qQJtx0zxjfNKPRssCFC3A8KA17pKG3OyVmu9S2FpaQwMvOM2yDmb3EynZqO/K9g6hZZKy3SIQrcCadoJVB7wuaT3O6LAvX7upgWoffOy23yU7lcZ+LrPgE2uENZH0NUPKvkIQ45Qnyl5ebYsYswrrsmtvnynDP6r+UHYDZ7JIWL4Av+qhBxhyWBb23VJ8OlCiJ+LnrB2z771l07h+xlctMSbIaE/GP3tu0NXXabyDi50pRbWNtleciaLT/udHaz3AYJuE42+RJhOMYMcUWauE9Vgmug3I6TudCBdRErMVjPJNHdpQWazS2dAh+YOn+Ggurc5yUVBe9AR2xR6pqpoKibT2psdbvDV2Q9n3P8MlTPzZRnPhElu413QGaWzIrIZZ3rf5iQBGYRYY519ULyTH/HukMCsNlo4nx3HD+Q+EZq+EY01UFM1nYNKW6Z42AjP7nEqhnpjWULGXOlRibgTG3Oj87qkwsC/xQxMrv0dlG//1RK0WdyTNKeuAzINBk3Trv68VT8v1qtu25gqzYKtTLuQzeG9lRyiYKJ9hOgqcBKq5s0iN9sWr0ii4pCWpJUth+Rqe3xxODl1SmO96fG/4Gy7YkpvegNkh9XfHiAfY0pbDPDKzjxrchW9aW44mD9zAGlzjK4eV2ZWLxVzt6P+OF7YwV9S4XOhVxzXeOkD49NzZwQGiPQu+7AZEd28+qUQHCbitm0ODz8DqccUNtcYBeZaAggmoNrob5Xdx5FmHJYKTuXlkZlUWPLsyHhJjicnmTf3ZxTiR+qCpd7HgDYqgmsM6WBUQg1GphLpm+K/PJzEqp0ZiHTyBeLOTZxewQqnccu+O9zcnDhuqzA9Tk5EvykX3eXq7bq3jH/PxEJMfmklLXoT/nEl3maWydS7TPly6SXi9GkgDGvNXKYva5NX4k3ZHJAcvV5pFubWXkP5KYB3ztSe43lJasEvMviae6HK0z9CB+O2pWmHeMzkxb63ipf5CwcmrYhRYOQzDCr1fR07C3D9Zeg/vV6cH5EFn1WOX1CK3SlNzCPvwprNJB2xCfSREzp37rxkR3GdHeOBWUt+Xryqy19Ci1GLDbsp4BEGyjknjO3bgFPYoecBSjuHqT0xZAESib/yjwgbeaubdKFJXzwTq5FMlpkc8P1nhkOwKMfrCcjCPbCxptgtCfa9ipf5CwcmrYhRYOQzDCr1fSA5V2VYGxm5Ta1YUUuQYoKubfVPrvdeRH7lgzikekOjr57GTvbg5FvntM5oFfAlZj9dYUq4jmjC41o8gMo6WRZicQIZSWMnoFt163sib4++FuwiCAoF8To3Hh+4FiYLdWQ/qrIcVucoWINxY8U0x+0fZ30JIHDqT9maqx0255xNhZMeC0fn9UbsAmWveLWHeX+iJ069H+UzFucVAmpQh2WKxSzqi8CDMz9hAFZG64gd0Ymk+GWq5FS2NvBfXAJVua3e7qJlDfVnPRQOO0SL1cm2q3LuJikkLtBTi7EXBN8oVW/0bbM2ARrLUeYWYN47MG2yr7oh+RrKG40nLaX0/EuKxSzqi8CDMz9hAFZG64gdqQMR6GFXRTIzKqWDk6fNuFfZ03fs/J/0S1BQVvFX+gwsVslz6Mey+6ZRiyKpELBujegeT1zqzz2wK1d+qP/WPPwbXE6cBT1jJvN669UhLtTceip5QKwmCUweOAiW/mnNrYTEXaiqS6GrO+tfZjjb2orFLOqLwIMzP2EAVkbriB3MPk85nahjXKYDhy545z+t+DFFoeF8ax8QuFxrn8HIfB4DRMyHQMjPLPB+nGCloTuKl/kLByatiFFg5DMMKvV94I7y5BgRow5HWUtXtNA5oDGPrTJe/vdq1jkAbzeIBTwqPTP8CUs4WGgaDPRarSiPkbRO17O8BUn6QP9rpd0v4EVYasblVIWXzSOw60xCudET1WCa6DcjpO50IF1ESsxWmFpnYkHQJ2CBm1VUTc45G5zUhTdHOw+tUNbB7SgpOI8x2H35QseXUiq8p5/Ia+aHHPUNV+jwRenq0dKJ2+zXI7jF3KeGfdtNfryNq94Leji0k3JNaBDypwZP1tlmDg2VlM1ymOnXIFeXx+fWv86NLTA4DHz6S0F13aDp+vYyAv+t8JNVxGPa+9H2FpqCpXqX140Uhkc6EkUR/e9S553s64SksyX5jTOOMwKxGchcZoIAECVUNf+NU9i/3nwX+oRt6bzatHkH82B1A/5C7cQqDhUV0h7Hz/tJ627Pbx6//sBrSx96WPpDpIYJYolRqCvOisUs6ovAgzM/YQBWRuuIHQeQd93UKHEIP90iPNym+bn7m7zUhKtx/irLhU+E4kTYrlAk12HHmTRB1NSGL3KZCF0rgqzoHq69UYpH4qPfw4Qmx4OcfHQSGWjJVDMPr63vkcvFuSF7sm5IJttWK0WV2am2uc9DDz2F2yPPfUiv1lzUvXX3G+g9vGje2CNrKhpSmz1uNhgnsBImJuBWR4uBkl3ilrejQtSCNObvMVYPaQs=
|
non_infrastructure
|
qbeh ne b rrhhgrafbkdre ewf urjx u pikrgolh rz ea frk xlctmsbiae yon q ezq k pxejmfmkllxot j qp t ngclotukl ia ahhpunv vyyav irlhu
| 0
|
45,260
| 5,916,237,250
|
IssuesEvent
|
2017-05-22 09:59:00
|
canonical-ols/build.snapcraft.io
|
https://api.github.com/repos/canonical-ols/build.snapcraft.io
|
closed
|
[footer] social media icons are warm grey
|
Status: Triaged Visual design
|
The footer is still using the warm grey from old ubuntu.com
---
Copied from Trello card: https://trello.com/c/AyjUMqTc/297-footer-social-media-icons-are-warm-grey
Labels: design
|
1.0
|
[footer] social media icons are warm grey - The footer is still using the warm grey from old ubuntu.com
---
Copied from Trello card: https://trello.com/c/AyjUMqTc/297-footer-social-media-icons-are-warm-grey
Labels: design
|
non_infrastructure
|
social media icons are warm grey the footer is still using the warm grey from old ubuntu com copied from trello card labels design
| 0
|
7,590
| 7,979,283,560
|
IssuesEvent
|
2018-07-17 21:09:18
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Backup and restore
|
assigned-to-author container-service/svc doc-enhancement in-progress triaged
|
Hi,
I am using a persistent volume with an Azure disk in an Azure Kubernetes Service AKS cluster.
How do I backup and restore that disk?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: d1ac572f-c613-71fc-580a-2805b740b793
* Version Independent ID: b4aeef15-7b0f-abc7-872e-28051e10d6ca
* Content: [Create persistent volumes with Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/azure-disks-dynamic-pv)
* Content Source: [articles/aks/azure-disks-dynamic-pv.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/azure-disks-dynamic-pv.md)
* Service: **container-service**
* GitHub Login: @iainfoulds
* Microsoft Alias: **iainfou**
|
1.0
|
Backup and restore - Hi,
I am using a persistent volume with an Azure disk in an Azure Kubernetes Service AKS cluster.
How do I backup and restore that disk?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: d1ac572f-c613-71fc-580a-2805b740b793
* Version Independent ID: b4aeef15-7b0f-abc7-872e-28051e10d6ca
* Content: [Create persistent volumes with Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/azure-disks-dynamic-pv)
* Content Source: [articles/aks/azure-disks-dynamic-pv.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/azure-disks-dynamic-pv.md)
* Service: **container-service**
* GitHub Login: @iainfoulds
* Microsoft Alias: **iainfou**
|
non_infrastructure
|
backup and restore hi i am using a persistent volume with an azure disk in an azure kubernetes service aks cluster how do i backup and restore that disk document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service container service github login iainfoulds microsoft alias iainfou
| 0
|
958
| 3,010,756,528
|
IssuesEvent
|
2015-07-28 14:45:09
|
dotnet/wcf
|
https://api.github.com/repos/dotnet/wcf
|
opened
|
Move code to ensure the Bridge is running into a custom build task
|
Infrastructure test bug
|
Currently the code to check whether the Bridge is running and launch it lives in ensureBridge.ps1, and it is called via CMD files from build.cmd.
This task is to create a custom build task that does the same work. Reasons are:
- MSBuild command line properties are available (such as BridgeURL)
- The Bridge will launch when a project that requires it builds, allowing more flexible launching of the Bridge depending on kinds of builds (e.g. F5)
|
1.0
|
Move code to ensure the Bridge is running into a custom build task - Currently the code to check whether the Bridge is running and launch it lives in ensureBridge.ps1, and it is called via CMD files from build.cmd.
This task is to create a custom build task that does the same work. Reasons are:
- MSBuild command line properties are available (such as BridgeURL)
- The Bridge will launch when a project that requires it builds, allowing more flexible launching of the Bridge depending on kinds of builds (e.g. F5)
|
infrastructure
|
move code to ensure the bridge is running into a custom build task currently the code to check whether the bridge is running and launch it lives in ensurebridge and it is called via cmd files from build cmd this task is to create a custom build task that does the same work reasons are msbuild command line properties are available such as bridgeurl the bridge will launch when a project that requires it builds allowing more flexible launching of the bridge depending on kinds of builds e g
| 1
|
29,931
| 24,404,247,157
|
IssuesEvent
|
2022-10-05 06:12:49
|
dart-lang/site-www
|
https://api.github.com/repos/dart-lang/site-www
|
closed
|
Fix or remove html_proof.rb
|
infrastructure p3-low help wanted e1-hours
|
As of April 16, 2019, `./deploy/html_proof.rb` fails. It hasn't changed, so I suspect a ruby change. Here's the output (with `./` substituted for my directory path details):
```
$ ./deploy/html_proof.rb
./deploy/urls/get_all.rb:3:in `require_relative': cannot load such file --
./deploy/urls/old_site_urls (LoadError)
from ./deploy/urls/get_all.rb:3:in `<top (required)>'
from ./deploy/html_proof.rb:7:in `require_relative'
from ./deploy/html_proof.rb:7:in `<main>'
```
|
1.0
|
Fix or remove html_proof.rb - As of April 16, 2019, `./deploy/html_proof.rb` fails. It hasn't changed, so I suspect a ruby change. Here's the output (with `./` substituted for my directory path details):
```
$ ./deploy/html_proof.rb
./deploy/urls/get_all.rb:3:in `require_relative': cannot load such file --
./deploy/urls/old_site_urls (LoadError)
from ./deploy/urls/get_all.rb:3:in `<top (required)>'
from ./deploy/html_proof.rb:7:in `require_relative'
from ./deploy/html_proof.rb:7:in `<main>'
```
|
infrastructure
|
fix or remove html proof rb as of april deploy html proof rb fails it hasn t changed so i suspect a ruby change here s the output with substituted for my directory path details deploy html proof rb deploy urls get all rb in require relative cannot load such file deploy urls old site urls loaderror from deploy urls get all rb in from deploy html proof rb in require relative from deploy html proof rb in
| 1
|
13,883
| 10,519,890,614
|
IssuesEvent
|
2019-09-29 21:07:37
|
oppia/oppia-android
|
https://api.github.com/repos/oppia/oppia-android
|
closed
|
Introduce interface for ExplorationDataController
|
Priority: Essential Status: In implementation Type: Improvement Where: Infrastructure Workstream: Domain Interface
|
This is tracking introducing a stubbed interface for #113 without the real implementation being complete.
|
1.0
|
Introduce interface for ExplorationDataController - This is tracking introducing a stubbed interface for #113 without the real implementation being complete.
|
infrastructure
|
introduce interface for explorationdatacontroller this is tracking introducing a stubbed interface for without the real implementation being complete
| 1
|
21,444
| 14,570,381,506
|
IssuesEvent
|
2020-12-17 14:19:22
|
cds-snc/covid-alert-server-staging-terraform
|
https://api.github.com/repos/cds-snc/covid-alert-server-staging-terraform
|
closed
|
Upgrade to 0.14.2 terraform
|
high priority infrastructure unplanned work
|
Due to a known issue with TF and WAFv2 upgrading to the latest TF version 0.14.2 should speed up plan's and applys.
https://github.com/hashicorp/terraform-provider-aws/issues/14062
|
1.0
|
Upgrade to 0.14.2 terraform - Due to a known issue with TF and WAFv2 upgrading to the latest TF version 0.14.2 should speed up plan's and applys.
https://github.com/hashicorp/terraform-provider-aws/issues/14062
|
infrastructure
|
upgrade to terraform due to a known issue with tf and upgrading to the latest tf version should speed up plan s and applys
| 1
|
32,033
| 26,371,984,876
|
IssuesEvent
|
2023-01-11 21:33:11
|
ejgallego/coq-serapi
|
https://api.github.com/repos/ejgallego/coq-serapi
|
closed
|
Missing build dependency on mathcomp's ssreflect
|
kind: bug kind: testing kind: infrastructure
|
While trying to package coq-serapi for Debian, it turns out tests/genarg/move.v wants mathcomp's ssrnat and eqtype.
I guess the opam file needs a dep on coq-mathcomp-ssreflect in addition to what is already declared.
|
1.0
|
Missing build dependency on mathcomp's ssreflect - While trying to package coq-serapi for Debian, it turns out tests/genarg/move.v wants mathcomp's ssrnat and eqtype.
I guess the opam file needs a dep on coq-mathcomp-ssreflect in addition to what is already declared.
|
infrastructure
|
missing build dependency on mathcomp s ssreflect while trying to package coq serapi for debian it turns out tests genarg move v wants mathcomp s ssrnat and eqtype i guess the opam file needs a dep on coq mathcomp ssreflect in addition to what is already declared
| 1
|
26,517
| 20,187,799,050
|
IssuesEvent
|
2022-02-11 00:44:05
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
Disable BlazorTemplates.Tests from running in quarantined pipelines
|
task area-infrastructure area-blazor
|
These tests were disabled in the helix environment via https://github.com/dotnet/aspnetcore/pull/38814/files#diff-0ccc4599c1cd44580f93ef1ab4182e747b297872577a970d651be18220d91768R13. This issue tracks disabling the tests from the quarantined pipelines as well until we're able to make some improvements to the underlying test suite.
Related: https://github.com/dotnet/aspnetcore/issues/38818
|
1.0
|
Disable BlazorTemplates.Tests from running in quarantined pipelines - These tests were disabled in the helix environment via https://github.com/dotnet/aspnetcore/pull/38814/files#diff-0ccc4599c1cd44580f93ef1ab4182e747b297872577a970d651be18220d91768R13. This issue tracks disabling the tests from the quarantined pipelines as well until we're able to make some improvements to the underlying test suite.
Related: https://github.com/dotnet/aspnetcore/issues/38818
|
infrastructure
|
disable blazortemplates tests from running in quarantined pipelines these tests were disabled in the helix environment via this issue tracks disabling the tests from the quarantined pipelines as well until we re able to make some improvements to the underlying test suite related
| 1
|
211,429
| 23,823,171,297
|
IssuesEvent
|
2022-09-05 12:58:27
|
hugo-fixit/FixIt
|
https://api.github.com/repos/hugo-fixit/FixIt
|
opened
|
Fix code scanning alert - Potentially unsafe external link
|
security
|
<!-- Warning: The suggested title contains the alert rule name. This can expose security information. -->
Tracking issue for:
- [ ] https://github.com/hugo-fixit/FixIt/security/code-scanning/6
Salution:
- [ ] Using built-in link template
- [ ] Add front matter `[noreferrer=true]` only for `friends` type
|
True
|
Fix code scanning alert - Potentially unsafe external link - <!-- Warning: The suggested title contains the alert rule name. This can expose security information. -->
Tracking issue for:
- [ ] https://github.com/hugo-fixit/FixIt/security/code-scanning/6
Salution:
- [ ] Using built-in link template
- [ ] Add front matter `[noreferrer=true]` only for `friends` type
|
non_infrastructure
|
fix code scanning alert potentially unsafe external link tracking issue for salution using built in link template add front matter only for friends type
| 0
|
527,029
| 15,307,350,856
|
IssuesEvent
|
2021-02-24 20:46:25
|
hetic-newsroom/heticiens.news
|
https://api.github.com/repos/hetic-newsroom/heticiens.news
|
closed
|
Optimize SEO
|
UI enhancement low-priority
|
Add JSON-LD Schema tags to improve ranking.
Suggested tags: Article, Organization
Look at schema.org
|
1.0
|
Optimize SEO - Add JSON-LD Schema tags to improve ranking.
Suggested tags: Article, Organization
Look at schema.org
|
non_infrastructure
|
optimize seo add json ld schema tags to improve ranking suggested tags article organization look at schema org
| 0
|
9,200
| 7,867,042,770
|
IssuesEvent
|
2018-06-23 02:40:40
|
dotnet/corefx
|
https://api.github.com/repos/dotnet/corefx
|
closed
|
crossgen.sh: line 80: $2: unbound variable
|
area-Infrastructure bug os-windows-wsl
|
When trying to run `build.sh` on a clean check out from WSL.
|
1.0
|
crossgen.sh: line 80: $2: unbound variable - When trying to run `build.sh` on a clean check out from WSL.
|
infrastructure
|
crossgen sh line unbound variable when trying to run build sh on a clean check out from wsl
| 1
|
17,393
| 12,339,840,249
|
IssuesEvent
|
2020-05-14 18:50:18
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Restore failing intermittently on build
|
area-Infrastructure blocking-clean-ci untriaged
|
Restore is failing intermittently
```
F:\workspace\_work\1\s\.dotnet\sdk\5.0.100-preview.5.20251.2\NuGet.targets(128,5): error : Cannot create a file when that file already exists. [F:\workspace\_work\1\s\src\libraries\restore\binplacePackages\binplacePackages.depproj]
##[error].dotnet\sdk\5.0.100-preview.5.20251.2\NuGet.targets(128,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) Cannot create a file when that file already exists.
```
Looks like a race that is hitting the "Libraries Build Windows_NT allConfigurations x64 Debug" the most often.
Note: if you are looking into this bug make sure to look at all attempts of this leg. About 1/2 of the PRs here retried this failure and it succeeded on retry. Hence looking at the final state of the build will not display this error.
<!-- runfo report start -->
|Build|Kind|Job Name|
|---|---|---|
|[640103](https://dev.azure.com/dnceng/public/_build/results?buildId=640103)|[PR 36242](https://github.com/dotnet/runtime/pull/36242)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[637444](https://dev.azure.com/dnceng/public/_build/results?buildId=637444)|[PR 36150](https://github.com/dotnet/runtime/pull/36150)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[637444](https://dev.azure.com/dnceng/public/_build/results?buildId=637444)|[PR 36150](https://github.com/dotnet/runtime/pull/36150)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[637444](https://dev.azure.com/dnceng/public/_build/results?buildId=637444)|[PR 36150](https://github.com/dotnet/runtime/pull/36150)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638863](https://dev.azure.com/dnceng/public/_build/results?buildId=638863)|[PR 36098](https://github.com/dotnet/runtime/pull/36098)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638863](https://dev.azure.com/dnceng/public/_build/results?buildId=638863)|[PR 36098](https://github.com/dotnet/runtime/pull/36098)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638849](https://dev.azure.com/dnceng/public/_build/results?buildId=638849)|[PR 36175](https://github.com/dotnet/runtime/pull/36175)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638786](https://dev.azure.com/dnceng/public/_build/results?buildId=638786)|Rolling|Libraries Build Windows_NT net472 x64 Release|
|[638313](https://dev.azure.com/dnceng/public/_build/results?buildId=638313)|[PR 36098](https://github.com/dotnet/runtime/pull/36098)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638357](https://dev.azure.com/dnceng/public/_build/results?buildId=638357)|[PR 35366](https://github.com/dotnet/runtime/pull/35366)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638198](https://dev.azure.com/dnceng/public/_build/results?buildId=638198)|Rolling|Libraries Build Windows_NT allConfigurations x64 Release|
<!-- runfo report end -->
|
1.0
|
Restore failing intermittently on build - Restore is failing intermittently
```
F:\workspace\_work\1\s\.dotnet\sdk\5.0.100-preview.5.20251.2\NuGet.targets(128,5): error : Cannot create a file when that file already exists. [F:\workspace\_work\1\s\src\libraries\restore\binplacePackages\binplacePackages.depproj]
##[error].dotnet\sdk\5.0.100-preview.5.20251.2\NuGet.targets(128,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) Cannot create a file when that file already exists.
```
Looks like a race that is hitting the "Libraries Build Windows_NT allConfigurations x64 Debug" the most often.
Note: if you are looking into this bug make sure to look at all attempts of this leg. About 1/2 of the PRs here retried this failure and it succeeded on retry. Hence looking at the final state of the build will not display this error.
<!-- runfo report start -->
|Build|Kind|Job Name|
|---|---|---|
|[640103](https://dev.azure.com/dnceng/public/_build/results?buildId=640103)|[PR 36242](https://github.com/dotnet/runtime/pull/36242)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[637444](https://dev.azure.com/dnceng/public/_build/results?buildId=637444)|[PR 36150](https://github.com/dotnet/runtime/pull/36150)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[637444](https://dev.azure.com/dnceng/public/_build/results?buildId=637444)|[PR 36150](https://github.com/dotnet/runtime/pull/36150)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[637444](https://dev.azure.com/dnceng/public/_build/results?buildId=637444)|[PR 36150](https://github.com/dotnet/runtime/pull/36150)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638863](https://dev.azure.com/dnceng/public/_build/results?buildId=638863)|[PR 36098](https://github.com/dotnet/runtime/pull/36098)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638863](https://dev.azure.com/dnceng/public/_build/results?buildId=638863)|[PR 36098](https://github.com/dotnet/runtime/pull/36098)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638849](https://dev.azure.com/dnceng/public/_build/results?buildId=638849)|[PR 36175](https://github.com/dotnet/runtime/pull/36175)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638786](https://dev.azure.com/dnceng/public/_build/results?buildId=638786)|Rolling|Libraries Build Windows_NT net472 x64 Release|
|[638313](https://dev.azure.com/dnceng/public/_build/results?buildId=638313)|[PR 36098](https://github.com/dotnet/runtime/pull/36098)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638357](https://dev.azure.com/dnceng/public/_build/results?buildId=638357)|[PR 35366](https://github.com/dotnet/runtime/pull/35366)|Libraries Build Windows_NT allConfigurations x64 Debug|
|[638198](https://dev.azure.com/dnceng/public/_build/results?buildId=638198)|Rolling|Libraries Build Windows_NT allConfigurations x64 Release|
<!-- runfo report end -->
|
infrastructure
|
restore failing intermittently on build restore is failing intermittently f workspace work s dotnet sdk preview nuget targets error cannot create a file when that file already exists dotnet sdk preview nuget targets error netcore engineering telemetry restore cannot create a file when that file already exists looks like a race that is hitting the libraries build windows nt allconfigurations debug the most often note if you are looking into this bug make sure to look at all attempts of this leg about of the prs here retried this failure and it succeeded on retry hence looking at the final state of the build will not display this error build kind job name build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt release build windows nt allconfigurations debug build windows nt allconfigurations debug build windows nt allconfigurations release
| 1
|
22,229
| 15,054,631,312
|
IssuesEvent
|
2021-02-03 17:41:03
|
google/web-stories-wp
|
https://api.github.com/repos/google/web-stories-wp
|
closed
|
PHP 8 Compatibility
|
Epic Group: WordPress P1 Pod: WP & Infra Type: Infrastructure Type: Task
|
<!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Task Description
Once PHP 8 is out and the WordPress PHPUnit test suite supports it, we should make sure the plugin works smoothly on PHP 8.
- [x] CI: Ensure unit tests can be run with PHP 8 (#5608)
- [ ] ~Update local dev environment to support PHP 8~ - necessary?
- [ ] ~Update E2E tests to run in PHP 8 in GHA~ - necessary?
- [x] Fix any issues with code found in testing. (#5609)
- [x] Update / fix any composer dependencies affected by upgrade. (#5608)
See also: #4788 #5344
|
1.0
|
PHP 8 Compatibility - <!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Task Description
Once PHP 8 is out and the WordPress PHPUnit test suite supports it, we should make sure the plugin works smoothly on PHP 8.
- [x] CI: Ensure unit tests can be run with PHP 8 (#5608)
- [ ] ~Update local dev environment to support PHP 8~ - necessary?
- [ ] ~Update E2E tests to run in PHP 8 in GHA~ - necessary?
- [x] Fix any issues with code found in testing. (#5609)
- [x] Update / fix any composer dependencies affected by upgrade. (#5608)
See also: #4788 #5344
|
infrastructure
|
php compatibility task description once php is out and the wordpress phpunit test suite supports it we should make sure the plugin works smoothly on php ci ensure unit tests can be run with php update local dev environment to support php necessary update tests to run in php in gha necessary fix any issues with code found in testing update fix any composer dependencies affected by upgrade see also
| 1
|
2,482
| 3,699,050,107
|
IssuesEvent
|
2016-02-28 18:53:17
|
m-labs/artiq
|
https://api.github.com/repos/m-labs/artiq
|
closed
|
use Xvnc with QEMU
|
area:infrastructure prio:1-low
|
Having to compile and install the hacky VNC client is inconvenient, and it lacks features like mouse motion events plus special keys get stuck at times.
Alternatively, fix the QEMU VNC bugs.
|
1.0
|
use Xvnc with QEMU - Having to compile and install the hacky VNC client is inconvenient, and it lacks features like mouse motion events plus special keys get stuck at times.
Alternatively, fix the QEMU VNC bugs.
|
infrastructure
|
use xvnc with qemu having to compile and install the hacky vnc client is inconvenient and it lacks features like mouse motion events plus special keys get stuck at times alternatively fix the qemu vnc bugs
| 1
|
16,062
| 11,812,374,512
|
IssuesEvent
|
2020-03-19 20:02:24
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Changes to CoreCLR workflow
|
Discussion area-Infrastructure-coreclr
|
PR #31701 is changing the developer workflow for CoreCLR to help increase reliability, reduce local build times, and move us closer to a place where we can better parallelize CI to improve build times.
The largest part of the change is that the `build.cmd` and `build.sh` scripts under `src/coreclr` will be **deprecated** and later (probably in a few weeks) **removed**. The `src/coreclr/src/build.proj` file will also become unused and will be deleted. To build the coreclr product, the supported path will be to build from the root build script.
For those who strongly dislike building with MSBuild, the native runtime build will still be buildable with new `build-runtime.cmd` and `build-runtime.sh` scripts in `src/coreclr` that only build the native runtime build and the cross-arch native build. There will also be separate scripts available for running crossgen on System.Private.CoreLib. All managed builds will be driven exclusively through the Arcade scripting.
The way to control what parts of the CoreCLR build you run will be via the "subsets" infrastructure. See #31701 for specific subset names.
Below are some examples of commands for common workflows:
- Build CoreCLR runtime, System.Private.CoreLib, crossgen System.Private.CoreLib all in Debug. Build all of Libraries in Release. (Common workflow when syncing)
```
./build -subsetcategory coreclr-libraries -subset runtime-corelib-nativecorelib-all -c Release -runtimeconfiguration Debug
```
- Build CoreCLR runtime
```
./build -subsetcategory coreclr -subset runtime
```
- Build CoreCLR runtime (build-runtime version)
```
src/coreclr/build-runtime
```
- Build CoreCLR runtime and Crossgen2
```
./build -subsetcategory coreclr -subset runtime-tools
```
The subsets should give as much fine-grained control as was previously provided within the managed components. The native build scripts continue to have some finer-grained control and the build-runtime scripts are available for those who need it.
|
1.0
|
Changes to CoreCLR workflow - PR #31701 is changing the developer workflow for CoreCLR to help increase reliability, reduce local build times, and move us closer to a place where we can better parallelize CI to improve build times.
The largest part of the change is that the `build.cmd` and `build.sh` scripts under `src/coreclr` will be **deprecated** and later (probably in a few weeks) **removed**. The `src/coreclr/src/build.proj` file will also become unused and will be deleted. To build the coreclr product, the supported path will be to build from the root build script.
For those who strongly dislike building with MSBuild, the native runtime build will still be buildable with new `build-runtime.cmd` and `build-runtime.sh` scripts in `src/coreclr` that only build the native runtime build and the cross-arch native build. There will also be separate scripts available for running crossgen on System.Private.CoreLib. All managed builds will be driven exclusively through the Arcade scripting.
The way to control what parts of the CoreCLR build you run will be via the "subsets" infrastructure. See #31701 for specific subset names.
Below are some examples of commands for common workflows:
- Build CoreCLR runtime, System.Private.CoreLib, crossgen System.Private.CoreLib all in Debug. Build all of Libraries in Release. (Common workflow when syncing)
```
./build -subsetcategory coreclr-libraries -subset runtime-corelib-nativecorelib-all -c Release -runtimeconfiguration Debug
```
- Build CoreCLR runtime
```
./build -subsetcategory coreclr -subset runtime
```
- Build CoreCLR runtime (build-runtime version)
```
src/coreclr/build-runtime
```
- Build CoreCLR runtime and Crossgen2
```
./build -subsetcategory coreclr -subset runtime-tools
```
The subsets should give as much fine-grained control as was previously provided within the managed components. The native build scripts continue to have some finer-grained control and the build-runtime scripts are available for those who need it.
|
infrastructure
|
changes to coreclr workflow pr is changing the developer workflow for coreclr to help increase reliability reduce local build times and move us closer to a place where we can better parallelize ci to improve build times the largest part of the change is that the build cmd and build sh scripts under src coreclr will be deprecated and later probably in a few weeks removed the src coreclr src build proj file will also become unused and will be deleted to build the coreclr product the supported path will be to build from the root build script for those who strongly dislike building with msbuild the native runtime build will still be buildable with new build runtime cmd and build runtime sh scripts in src coreclr that only build the native runtime build and the cross arch native build there will also be separate scripts available for running crossgen on system private corelib all managed builds will be driven exclusively through the arcade scripting the way to control what parts of the coreclr build you run will be via the subsets infrastructure see for specific subset names below are some examples of commands for common workflows build coreclr runtime system private corelib crossgen system private corelib all in debug build all of libraries in release common workflow when syncing build subsetcategory coreclr libraries subset runtime corelib nativecorelib all c release runtimeconfiguration debug build coreclr runtime build subsetcategory coreclr subset runtime build coreclr runtime build runtime version src coreclr build runtime build coreclr runtime and build subsetcategory coreclr subset runtime tools the subsets should give as much fine grained control as was previously provided within the managed components the native build scripts continue to have some finer grained control and the build runtime scripts are available for those who need it
| 1
|
87,705
| 3,757,176,058
|
IssuesEvent
|
2016-03-13 20:40:18
|
svof/svof
|
https://api.github.com/repos/svof/svof
|
opened
|
Consider new tree scenario against 2 handed
|
enhancement low priority medium difficulty up for grabs
|
reported by Aerek
> A Touch Tree scenario for curing when you ONLY have 2H fractures and no other affs would be useful. I can't figure out how to script this, myself
|
1.0
|
Consider new tree scenario against 2 handed - reported by Aerek
> A Touch Tree scenario for curing when you ONLY have 2H fractures and no other affs would be useful. I can't figure out how to script this, myself
|
non_infrastructure
|
consider new tree scenario against handed reported by aerek a touch tree scenario for curing when you only have fractures and no other affs would be useful i can t figure out how to script this myself
| 0
|
630
| 2,798,583,331
|
IssuesEvent
|
2015-05-12 19:23:24
|
new-day-international/reddit
|
https://api.github.com/repos/new-day-international/reddit
|
closed
|
Investigate using fewer cloud search instances
|
Infrastructure
|
From @inflector
> Attached please find the usage report for September. It looks like we've got stuff firing off every hour uploading and somehow querying CloudSearch, what might be causing this? Are we getting spiders doing searches?
> Also, we seem to be getting separate charges for each of the different dev, test, and production searches, I thought we'd only be using one instance. We certainly don't need three actual machines for our work.
|
1.0
|
Investigate using fewer cloud search instances - From @inflector
> Attached please find the usage report for September. It looks like we've got stuff firing off every hour uploading and somehow querying CloudSearch, what might be causing this? Are we getting spiders doing searches?
> Also, we seem to be getting separate charges for each of the different dev, test, and production searches, I thought we'd only be using one instance. We certainly don't need three actual machines for our work.
|
infrastructure
|
investigate using fewer cloud search instances from inflector attached please find the usage report for september it looks like we ve got stuff firing off every hour uploading and somehow querying cloudsearch what might be causing this are we getting spiders doing searches also we seem to be getting separate charges for each of the different dev test and production searches i thought we d only be using one instance we certainly don t need three actual machines for our work
| 1
|
217,405
| 24,334,897,568
|
IssuesEvent
|
2022-10-01 01:07:10
|
H-459/test4Gal
|
https://api.github.com/repos/H-459/test4Gal
|
closed
|
CVE-2020-7692 (High) detected in google-oauth-client-1.25.0.jar - autoclosed
|
security vulnerability
|
## CVE-2020-7692 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>google-oauth-client-1.25.0.jar</b></p></summary>
<p>Google OAuth Client Library for Java. Functionality that works on all supported Java platforms,
including Java 5 (or higher) desktop (SE) and web (EE), Android, and Google App Engine.</p>
<p>Library home page: <a href="https://github.com/google/google-oauth-java-client">https://github.com/google/google-oauth-java-client</a></p>
<p>Path to dependency file: /BaragonService/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/oauth-client/google-oauth-client/1.25.0/google-oauth-client-1.25.0.jar</p>
<p>
Dependency Hierarchy:
- google-api-client-1.25.0.jar (Root Library)
- :x: **google-oauth-client-1.25.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/H-459/test4Gal/commit/659aa3eb63f125f4e5cbe927376da658f670c874">659aa3eb63f125f4e5cbe927376da658f670c874</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.
<p>Publish Date: 2020-07-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7692>CVE-2020-7692</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-07-09</p>
<p>Fix Resolution (com.google.oauth-client:google-oauth-client): 1.31.0</p>
<p>Direct dependency fix Resolution (com.google.api-client:google-api-client): 1.30.10</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
|
True
|
CVE-2020-7692 (High) detected in google-oauth-client-1.25.0.jar - autoclosed - ## CVE-2020-7692 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>google-oauth-client-1.25.0.jar</b></p></summary>
<p>Google OAuth Client Library for Java. Functionality that works on all supported Java platforms,
including Java 5 (or higher) desktop (SE) and web (EE), Android, and Google App Engine.</p>
<p>Library home page: <a href="https://github.com/google/google-oauth-java-client">https://github.com/google/google-oauth-java-client</a></p>
<p>Path to dependency file: /BaragonService/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/oauth-client/google-oauth-client/1.25.0/google-oauth-client-1.25.0.jar</p>
<p>
Dependency Hierarchy:
- google-api-client-1.25.0.jar (Root Library)
- :x: **google-oauth-client-1.25.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/H-459/test4Gal/commit/659aa3eb63f125f4e5cbe927376da658f670c874">659aa3eb63f125f4e5cbe927376da658f670c874</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.
<p>Publish Date: 2020-07-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7692>CVE-2020-7692</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-07-09</p>
<p>Fix Resolution (com.google.oauth-client:google-oauth-client): 1.31.0</p>
<p>Direct dependency fix Resolution (com.google.api-client:google-api-client): 1.30.10</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
|
non_infrastructure
|
cve high detected in google oauth client jar autoclosed cve high severity vulnerability vulnerable library google oauth client jar google oauth client library for java functionality that works on all supported java platforms including java or higher desktop se and web ee android and google app engine library home page a href path to dependency file baragonservice pom xml path to vulnerable library home wss scanner repository com google oauth client google oauth client google oauth client jar dependency hierarchy google api client jar root library x google oauth client jar vulnerable library found in head commit a href found in base branch master vulnerability details pkce support is not implemented in accordance with the rfc for oauth for native apps without the use of pkce the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized an attacker is able to obtain the authorization code using a malicious app on the client side and use it to gain authorization to the protected resource this affects the package com google oauth client google oauth client before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution com google oauth client google oauth client direct dependency fix resolution com google api client google api client check this box to open an automated fix pr
| 0
|
16,419
| 5,233,716,001
|
IssuesEvent
|
2017-01-30 13:47:18
|
SemsTestOrg/combinearchive-web
|
https://api.github.com/repos/SemsTestOrg/combinearchive-web
|
closed
|
fetch instead of upload
|
code feature request fixed migrated minor
|
## Trac Ticket #133
**component:** code
**owner:** somebody
**reporter:** martin
**created:** 2015-09-23 09:30:48
**milestone:**
**type:** feature request
**version:**
**keywords:**
add an option to fetch a file from URL. users do not need to download model from eg biomodels, but can simply provide a link..
however, this is just minor request
## comment 1
**time:** 2015-10-06 10:21:57
**author:** martin
and annotate that as ```pav:wasRetrievedFrom``` (when etc) in the meta data (as soon as this is possible)
## comment 2
**time:** 2015-10-15 13:12:16
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/39ccc2842c3ba59f9cad1ba4118907f1f3ddb2c0):
```CommitTicketReference repository="" revision="39ccc2842c3ba59f9cad1ba4118907f1f3ddb2c0"
added ui support for fetching files [see #133]
```
## comment 3
**time:** 2015-10-15 14:43:47
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/c4c90cf387539cca2f6c3ef2ac10152679d32329):
```CommitTicketReference repository="" revision="c4c90cf387539cca2f6c3ef2ac10152679d32329"
added basic structure to RestApi [see #133]
```
## comment 4
**time:** 2015-10-19 20:18:40
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/aff229dbba043610d1c4c28bff78de8c3bd43201):
```CommitTicketReference repository="" revision="aff229dbba043610d1c4c28bff78de8c3bd43201"
removed list of urls again from FetchRequest, now just passing multiple
requests as list (js pending) [see #133]
```
## comment 5
**time:** 2015-10-19 20:18:42
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/224a94b2aeb6429428f2bb1853dcbec7841fec86):
```CommitTicketReference repository="" revision="224a94b2aeb6429428f2bb1853dcbec7841fec86"
more fetch api [see #133]
```
## comment 6
**time:** 2015-10-19 20:18:43
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/ac9e57e06bf206fdfc70d88b359c3ca7fd495deb):
```CommitTicketReference repository="" revision="ac9e57e06bf206fdfc70d88b359c3ca7fd495deb"
impl custom copy method (due to class conflict) [see #133]
```
## comment 7
**time:** 2015-10-19 20:53:28
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/1fdab8c88a85e14f381f47a2b1806422b72bd45d):
```CommitTicketReference repository="" revision="1fdab8c88a85e14f381f47a2b1806422b72bd45d"
finished RestApi integration of fetch file [see #133]
```
## comment 8
**time:** 2015-10-19 21:17:10
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/73598eb7202830407eb8f1e196b2747515b96cc2):
```CommitTicketReference repository="" revision="73598eb7202830407eb8f1e196b2747515b96cc2"
updated js for new fetch request dataholder [see #133]
```
## comment 9
**time:** 2015-10-19 21:17:12
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/53c22ed3da95d9bed1226765d07dd4e980ad392f):
```CommitTicketReference repository="" revision="53c22ed3da95d9bed1226765d07dd4e980ad392f"
fixed js for fetching files [see #133]
```
## comment 10
**time:** 2015-10-19 21:17:13
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/bf57fab23180de847ec2f98f7a7f66e2e5ab098d):
```CommitTicketReference repository="" revision="bf57fab23180de847ec2f98f7a7f66e2e5ab098d"
adding Description from fetched files [see #133]
```
## comment 11
**time:** 2015-10-20 11:19:39
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/141836211aa3d7580b9d27c4c2f5a7984e8cc1e2):
```CommitTicketReference repository="" revision="141836211aa3d7580b9d27c4c2f5a7984e8cc1e2"
removed template for fetch dialog [see #133]
```
## comment 12
**time:** 2015-10-20 11:19:41
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/f87573d372c8742e0d78e44b076f3da5f7cc1010):
```CommitTicketReference repository="" revision="f87573d372c8742e0d78e44b076f3da5f7cc1010"
some polishment on fetch dialog [see #133]
```
## comment 13
**time:** 2016-12-12 11:52:22
**author:** martinP
This is actually implemented. Just forgot to close this ticket...
## comment 14
**time:** 2016-12-12 11:52:22
**author:** martinP
Updated **resolution** to **fixed**
## comment 15
**time:** 2016-12-12 11:52:22
**author:** martinP
Updated **status** to **closed**
|
1.0
|
fetch instead of upload - ## Trac Ticket #133
**component:** code
**owner:** somebody
**reporter:** martin
**created:** 2015-09-23 09:30:48
**milestone:**
**type:** feature request
**version:**
**keywords:**
add an option to fetch a file from URL. users do not need to download model from eg biomodels, but can simply provide a link..
however, this is just minor request
## comment 1
**time:** 2015-10-06 10:21:57
**author:** martin
and annotate that as ```pav:wasRetrievedFrom``` (when etc) in the meta data (as soon as this is possible)
## comment 2
**time:** 2015-10-15 13:12:16
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/39ccc2842c3ba59f9cad1ba4118907f1f3ddb2c0):
```CommitTicketReference repository="" revision="39ccc2842c3ba59f9cad1ba4118907f1f3ddb2c0"
added ui support for fetching files [see #133]
```
## comment 3
**time:** 2015-10-15 14:43:47
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/c4c90cf387539cca2f6c3ef2ac10152679d32329):
```CommitTicketReference repository="" revision="c4c90cf387539cca2f6c3ef2ac10152679d32329"
added basic structure to RestApi [see #133]
```
## comment 4
**time:** 2015-10-19 20:18:40
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/aff229dbba043610d1c4c28bff78de8c3bd43201):
```CommitTicketReference repository="" revision="aff229dbba043610d1c4c28bff78de8c3bd43201"
removed list of urls again from FetchRequest, now just passing multiple
requests as list (js pending) [see #133]
```
## comment 5
**time:** 2015-10-19 20:18:42
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/224a94b2aeb6429428f2bb1853dcbec7841fec86):
```CommitTicketReference repository="" revision="224a94b2aeb6429428f2bb1853dcbec7841fec86"
more fetch api [see #133]
```
## comment 6
**time:** 2015-10-19 20:18:43
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/ac9e57e06bf206fdfc70d88b359c3ca7fd495deb):
```CommitTicketReference repository="" revision="ac9e57e06bf206fdfc70d88b359c3ca7fd495deb"
impl custom copy method (due to class conflict) [see #133]
```
## comment 7
**time:** 2015-10-19 20:53:28
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/1fdab8c88a85e14f381f47a2b1806422b72bd45d):
```CommitTicketReference repository="" revision="1fdab8c88a85e14f381f47a2b1806422b72bd45d"
finished RestApi integration of fetch file [see #133]
```
## comment 8
**time:** 2015-10-19 21:17:10
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/73598eb7202830407eb8f1e196b2747515b96cc2):
```CommitTicketReference repository="" revision="73598eb7202830407eb8f1e196b2747515b96cc2"
updated js for new fetch request dataholder [see #133]
```
## comment 9
**time:** 2015-10-19 21:17:12
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/53c22ed3da95d9bed1226765d07dd4e980ad392f):
```CommitTicketReference repository="" revision="53c22ed3da95d9bed1226765d07dd4e980ad392f"
fixed js for fetching files [see #133]
```
## comment 10
**time:** 2015-10-19 21:17:13
**author:** Martin Peters <martin.peters3@uni-rostock.de>
In [None](/bf57fab23180de847ec2f98f7a7f66e2e5ab098d):
```CommitTicketReference repository="" revision="bf57fab23180de847ec2f98f7a7f66e2e5ab098d"
adding Description from fetched files [see #133]
```
## comment 11
**time:** 2015-10-20 11:19:39
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/141836211aa3d7580b9d27c4c2f5a7984e8cc1e2):
```CommitTicketReference repository="" revision="141836211aa3d7580b9d27c4c2f5a7984e8cc1e2"
removed template for fetch dialog [see #133]
```
## comment 12
**time:** 2015-10-20 11:19:41
**author:** mp487 <martin.peters3@uni-rostock.de>
In [None](/f87573d372c8742e0d78e44b076f3da5f7cc1010):
```CommitTicketReference repository="" revision="f87573d372c8742e0d78e44b076f3da5f7cc1010"
some polishment on fetch dialog [see #133]
```
## comment 13
**time:** 2016-12-12 11:52:22
**author:** martinP
This is actually implemented. Just forgot to close this ticket...
## comment 14
**time:** 2016-12-12 11:52:22
**author:** martinP
Updated **resolution** to **fixed**
## comment 15
**time:** 2016-12-12 11:52:22
**author:** martinP
Updated **status** to **closed**
|
non_infrastructure
|
fetch instead of upload trac ticket component code owner somebody reporter martin created milestone type feature request version keywords add an option to fetch a file from url users do not need to download model from eg biomodels but can simply provide a link however this is just minor request comment time author martin and annotate that as pav wasretrievedfrom when etc in the meta data as soon as this is possible comment time author in committicketreference repository revision added ui support for fetching files comment time author martin peters in committicketreference repository revision added basic structure to restapi comment time author in committicketreference repository revision removed list of urls again from fetchrequest now just passing multiple requests as list js pending comment time author in committicketreference repository revision more fetch api comment time author in committicketreference repository revision impl custom copy method due to class conflict comment time author martin peters in committicketreference repository revision finished restapi integration of fetch file comment time author martin peters in committicketreference repository revision updated js for new fetch request dataholder comment time author martin peters in committicketreference repository revision fixed js for fetching files comment time author martin peters in committicketreference repository revision adding description from fetched files comment time author in committicketreference repository revision removed template for fetch dialog comment time author in committicketreference repository revision some polishment on fetch dialog comment time author martinp this is actually implemented just forgot to close this ticket comment time author martinp updated resolution to fixed comment time author martinp updated status to closed
| 0
|
15,227
| 11,423,150,998
|
IssuesEvent
|
2020-02-03 15:25:31
|
reservix-ui/marigold
|
https://api.github.com/repos/reservix-ui/marigold
|
closed
|
Setup jest + testing-library
|
infrastructure
|
We can base it on the following setup form `tsdx`:
https://github.com/jaredpalmer/tsdx/blob/ce3ff8e23b77515ca09d32cb01273531acebf9ab/src/createJestConfig.ts#L5-L19
Also, install `@testing-library`!
|
1.0
|
Setup jest + testing-library - We can base it on the following setup form `tsdx`:
https://github.com/jaredpalmer/tsdx/blob/ce3ff8e23b77515ca09d32cb01273531acebf9ab/src/createJestConfig.ts#L5-L19
Also, install `@testing-library`!
|
infrastructure
|
setup jest testing library we can base it on the following setup form tsdx also install testing library
| 1
|
14,360
| 10,765,263,091
|
IssuesEvent
|
2019-11-01 10:32:18
|
tunapanda/swag
|
https://api.github.com/repos/tunapanda/swag
|
closed
|
Database structure & design
|
backend points:5 priority:highest type:infrastructure
|
As an engineer, I would like a database with a logical structure to store the relational data for Wikonnect.
- [ ] Knex migrations
|
1.0
|
Database structure & design - As an engineer, I would like a database with a logical structure to store the relational data for Wikonnect.
- [ ] Knex migrations
|
infrastructure
|
database structure design as an engineer i would like a database with a logical structure to store the relational data for wikonnect knex migrations
| 1
|
653,011
| 21,568,612,099
|
IssuesEvent
|
2022-05-02 04:19:24
|
solgenomics/sgn
|
https://api.github.com/repos/solgenomics/sgn
|
closed
|
Implement a generation advancement tool
|
Type: Feature Request Priority: High
|
Expected Behavior <!-- Describe the desired or expected behavour here. -->
--------------------------------------------------------------------------
An important feature for breeders is to track generation advancement of populations (F1,F2, F3....)
A useful feature would be to include automatically this F level incrementation to progenies generated from cross/population. It usually goes from F1 -> F8.
A further feature would reflect the generation level in the pedigree tree
For Bugs:
---------
### Environment
<!-- Where did you encounter the error. -->
#### Steps to Reproduce
<!-- Provide an example, or an unambiguous set of steps to reproduce -->
<!-- this bug. Include code to reproduce, if relevant. -->
|
1.0
|
Implement a generation advancement tool - Expected Behavior <!-- Describe the desired or expected behavour here. -->
--------------------------------------------------------------------------
An important feature for breeders is to track generation advancement of populations (F1,F2, F3....)
A useful feature would be to include automatically this F level incrementation to progenies generated from cross/population. It usually goes from F1 -> F8.
A further feature would reflect the generation level in the pedigree tree
For Bugs:
---------
### Environment
<!-- Where did you encounter the error. -->
#### Steps to Reproduce
<!-- Provide an example, or an unambiguous set of steps to reproduce -->
<!-- this bug. Include code to reproduce, if relevant. -->
|
non_infrastructure
|
implement a generation advancement tool expected behavior an important feature for breeders is to track generation advancement of populations a useful feature would be to include automatically this f level incrementation to progenies generated from cross population it usually goes from a further feature would reflect the generation level in the pedigree tree for bugs environment steps to reproduce
| 0
|
11,595
| 9,306,961,366
|
IssuesEvent
|
2019-03-25 11:00:12
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
[InfraUI] Infrastructure UI not loading in Kibana 7.0
|
:Infra UI :infrastructure
|
As part of Beats testing I was trying a variety of Elasticsearch / Kibana / Beats versions, which led me to discover the Infrastructure UI isn't working in Kibana `7.0` (Logs is unaffected).
The Infrastructure UI renders fine in Kibana `6.7`, `7.x` and `master` but **not** `7.0`.
On `7.0` I see the following:
<img width="1680" alt="Screenshot 2019-03-21 12 49 57" src="https://user-images.githubusercontent.com/471693/54755416-d41c7080-4bdd-11e9-8561-b804b859780d.png">
One thing to note is `<route />` could very easily point to the recent navigation changes, however these were merged to `7.x` and `master` only, so aren't to blame here.
|
1.0
|
[InfraUI] Infrastructure UI not loading in Kibana 7.0 - As part of Beats testing I was trying a variety of Elasticsearch / Kibana / Beats versions, which led me to discover the Infrastructure UI isn't working in Kibana `7.0` (Logs is unaffected).
The Infrastructure UI renders fine in Kibana `6.7`, `7.x` and `master` but **not** `7.0`.
On `7.0` I see the following:
<img width="1680" alt="Screenshot 2019-03-21 12 49 57" src="https://user-images.githubusercontent.com/471693/54755416-d41c7080-4bdd-11e9-8561-b804b859780d.png">
One thing to note is `<route />` could very easily point to the recent navigation changes, however these were merged to `7.x` and `master` only, so aren't to blame here.
|
infrastructure
|
infrastructure ui not loading in kibana as part of beats testing i was trying a variety of elasticsearch kibana beats versions which led me to discover the infrastructure ui isn t working in kibana logs is unaffected the infrastructure ui renders fine in kibana x and master but not on i see the following img width alt screenshot src one thing to note is could very easily point to the recent navigation changes however these were merged to x and master only so aren t to blame here
| 1
|
1,173
| 3,061,982,734
|
IssuesEvent
|
2015-08-16 04:10:14
|
jquery/esprima
|
https://api.github.com/repos/jquery/esprima
|
closed
|
Integrate codecov.io
|
infrastructure
|
With [Codecov.io](https://codecov.io/) integration, there can be two benefits:
* Coverage information is prominent in every pull request
* Code coverage dashboard is available for more detailed information
Any possible coverage regression can be easily tracked.
|
1.0
|
Integrate codecov.io - With [Codecov.io](https://codecov.io/) integration, there can be two benefits:
* Coverage information is prominent in every pull request
* Code coverage dashboard is available for more detailed information
Any possible coverage regression can be easily tracked.
|
infrastructure
|
integrate codecov io with integration there can be two benefits coverage information is prominent in every pull request code coverage dashboard is available for more detailed information any possible coverage regression can be easily tracked
| 1
|
294,736
| 9,040,107,654
|
IssuesEvent
|
2019-02-10 13:37:22
|
opencv/opencv
|
https://api.github.com/repos/opencv/opencv
|
opened
|
G-API: vagrind tests crashed
|
bug category: g-api priority: high
|
[Build](http://pullrequest.opencv.org/buildbot/builders/master_valgrind-lin64-debug/builds/10146).
opencv_test_gapi:
```
[ RUN ] SobelXYTestFluid/SobelXYTest.AccuracyTest/0, where GetParam() = (compare_f, 8UC1, 3, 1280x720, -1, 1, 0, 0, { gapi.kernel_package })
==13111== Warning: set address range perms: large range [0x395d8080, 0x719d8080) (undefined)
==13111== Warning: set address range perms: large range [0x719d9080, 0xa9dd9080) (undefined)
Process returned: -9
```
opencv_perf_gapi:
```
[ RUN ] SobelXYPerfTestFluid/SobelXYPerfTest.TestPerformance/12, where GetParam() = (compare_f, 8UC1, 3, 1920x1080, -1, 1, { gapi.kernel_package })
==13692== Warning: set address range perms: large range [0x395d8080, 0xb7ed8080) (undefined)
==13692== Warning: set address range perms: large range [0xb7ed9080, 0x1367d9080) (undefined)
Process returned: -9
```
|
1.0
|
G-API: vagrind tests crashed - [Build](http://pullrequest.opencv.org/buildbot/builders/master_valgrind-lin64-debug/builds/10146).
opencv_test_gapi:
```
[ RUN ] SobelXYTestFluid/SobelXYTest.AccuracyTest/0, where GetParam() = (compare_f, 8UC1, 3, 1280x720, -1, 1, 0, 0, { gapi.kernel_package })
==13111== Warning: set address range perms: large range [0x395d8080, 0x719d8080) (undefined)
==13111== Warning: set address range perms: large range [0x719d9080, 0xa9dd9080) (undefined)
Process returned: -9
```
opencv_perf_gapi:
```
[ RUN ] SobelXYPerfTestFluid/SobelXYPerfTest.TestPerformance/12, where GetParam() = (compare_f, 8UC1, 3, 1920x1080, -1, 1, { gapi.kernel_package })
==13692== Warning: set address range perms: large range [0x395d8080, 0xb7ed8080) (undefined)
==13692== Warning: set address range perms: large range [0xb7ed9080, 0x1367d9080) (undefined)
Process returned: -9
```
|
non_infrastructure
|
g api vagrind tests crashed opencv test gapi sobelxytestfluid sobelxytest accuracytest where getparam compare f gapi kernel package warning set address range perms large range undefined warning set address range perms large range undefined process returned opencv perf gapi sobelxyperftestfluid sobelxyperftest testperformance where getparam compare f gapi kernel package warning set address range perms large range undefined warning set address range perms large range undefined process returned
| 0
|
152,328
| 23,952,709,560
|
IssuesEvent
|
2022-09-12 12:51:00
|
kedro-org/kedro-viz
|
https://api.github.com/repos/kedro-org/kedro-viz
|
closed
|
Develop a brief to inform our approach for branding
|
Issue: Feature Request Design: Research
|
## Description
We're doing a holistic evaluation of the Kedro brand to understand our positioning and messaging. The outcome of this exercise will be a brief that would be used to answer:
- Why are we doing this? Why is this exercise important?
- What pain points we have with our current brand?
- What key messages we would like to communicate?
- What assets need to be created or what are our brand touch points?
- Who are our key stakeholders when developing this brand?
- Who is our audience?
- What risks are present and how will we mitigate them?
- What does success look like?
- How far we can go with this redesign: brand evolution or revolution?
|
1.0
|
Develop a brief to inform our approach for branding - ## Description
We're doing a holistic evaluation of the Kedro brand to understand our positioning and messaging. The outcome of this exercise will be a brief that would be used to answer:
- Why are we doing this? Why is this exercise important?
- What pain points we have with our current brand?
- What key messages we would like to communicate?
- What assets need to be created or what are our brand touch points?
- Who are our key stakeholders when developing this brand?
- Who is our audience?
- What risks are present and how will we mitigate them?
- What does success look like?
- How far we can go with this redesign: brand evolution or revolution?
|
non_infrastructure
|
develop a brief to inform our approach for branding description we re doing a holistic evaluation of the kedro brand to understand our positioning and messaging the outcome of this exercise will be a brief that would be used to answer why are we doing this why is this exercise important what pain points we have with our current brand what key messages we would like to communicate what assets need to be created or what are our brand touch points who are our key stakeholders when developing this brand who is our audience what risks are present and how will we mitigate them what does success look like how far we can go with this redesign brand evolution or revolution
| 0
|
19,533
| 13,261,772,275
|
IssuesEvent
|
2020-08-20 20:30:22
|
icecube-trac/tix4
|
https://api.github.com/repos/icecube-trac/tix4
|
closed
|
remove the need for svn:externals (and merge the icetray repository back into the main one) (Trac #1546)
|
Migrated from Trac enhancement infrastructure
|
We discussed the possibility of removing the need for svn:externals in the usual meta-projects at the software session in Copenhagen (they might still make sense for more specialized uses and/or meta-projects). The idea is to move all relevant project trunks directly into "combo" and start releasing the whole meta-projects. This makes branching/merging/... work in a sane way.
The process requires re-integrating the "icetray" repository into the main repository. A way that makes this work without breaking old meta-projects using externals is to clone our main meta-project and set the existing ones to read-only. The new meta project would exist at a new URL, something like http://code.icecube.wisc.edu/icecube instead of http://code.icecube.wisc.edu/svn and http://code.icecube.wisc.edu/icetray .
Attached is a working list of commands that would need to be run to make this work. I tested them on a cobalt yesterday. You can find a repository created this way on cobalt02 in /scratch/ckopper/ (the repository URL is file:///scratch/ckopper/restored_dump (on cobalt02, not on a shared filesystem because Lustre is very, very slow when storing these).
With SVN sparse checkouts users can retrieve partial copies of the meta-project. An example is shown at the end of the attached script.
Please send comments on what you think about this. I think it would make the release process a lot easier and allow for things like svn diffs of whole meta-projects.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1546">https://code.icecube.wisc.edu/projects/icecube/ticket/1546</a>, reported by claudio.kopperand owned by nega</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:15:23",
"_ts": "1550067323910946",
"description": "We discussed the possibility of removing the need for svn:externals in the usual meta-projects at the software session in Copenhagen (they might still make sense for more specialized uses and/or meta-projects). The idea is to move all relevant project trunks directly into \"combo\" and start releasing the whole meta-projects. This makes branching/merging/... work in a sane way.\n\nThe process requires re-integrating the \"icetray\" repository into the main repository. A way that makes this work without breaking old meta-projects using externals is to clone our main meta-project and set the existing ones to read-only. The new meta project would exist at a new URL, something like http://code.icecube.wisc.edu/icecube instead of http://code.icecube.wisc.edu/svn and http://code.icecube.wisc.edu/icetray .\n\nAttached is a working list of commands that would need to be run to make this work. I tested them on a cobalt yesterday. You can find a repository created this way on cobalt02 in /scratch/ckopper/ (the repository URL is file:///scratch/ckopper/restored_dump (on cobalt02, not on a shared filesystem because Lustre is very, very slow when storing these).\n\nWith SVN sparse checkouts users can retrieve partial copies of the meta-project. An example is shown at the end of the attached script.\n\nPlease send comments on what you think about this. I think it would make the release process a lot easier and allow for things like svn diffs of whole meta-projects.",
"reporter": "claudio.kopper",
"cc": "",
"resolution": "duplicate",
"time": "2016-02-12T19:20:59",
"component": "infrastructure",
"summary": "remove the need for svn:externals (and merge the icetray repository back into the main one)",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "nega",
"type": "enhancement"
}
```
</p>
</details>
|
1.0
|
remove the need for svn:externals (and merge the icetray repository back into the main one) (Trac #1546) - We discussed the possibility of removing the need for svn:externals in the usual meta-projects at the software session in Copenhagen (they might still make sense for more specialized uses and/or meta-projects). The idea is to move all relevant project trunks directly into "combo" and start releasing the whole meta-projects. This makes branching/merging/... work in a sane way.
The process requires re-integrating the "icetray" repository into the main repository. A way that makes this work without breaking old meta-projects using externals is to clone our main meta-project and set the existing ones to read-only. The new meta project would exist at a new URL, something like http://code.icecube.wisc.edu/icecube instead of http://code.icecube.wisc.edu/svn and http://code.icecube.wisc.edu/icetray .
Attached is a working list of commands that would need to be run to make this work. I tested them on a cobalt yesterday. You can find a repository created this way on cobalt02 in /scratch/ckopper/ (the repository URL is file:///scratch/ckopper/restored_dump (on cobalt02, not on a shared filesystem because Lustre is very, very slow when storing these).
With SVN sparse checkouts users can retrieve partial copies of the meta-project. An example is shown at the end of the attached script.
Please send comments on what you think about this. I think it would make the release process a lot easier and allow for things like svn diffs of whole meta-projects.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1546">https://code.icecube.wisc.edu/projects/icecube/ticket/1546</a>, reported by claudio.kopperand owned by nega</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:15:23",
"_ts": "1550067323910946",
"description": "We discussed the possibility of removing the need for svn:externals in the usual meta-projects at the software session in Copenhagen (they might still make sense for more specialized uses and/or meta-projects). The idea is to move all relevant project trunks directly into \"combo\" and start releasing the whole meta-projects. This makes branching/merging/... work in a sane way.\n\nThe process requires re-integrating the \"icetray\" repository into the main repository. A way that makes this work without breaking old meta-projects using externals is to clone our main meta-project and set the existing ones to read-only. The new meta project would exist at a new URL, something like http://code.icecube.wisc.edu/icecube instead of http://code.icecube.wisc.edu/svn and http://code.icecube.wisc.edu/icetray .\n\nAttached is a working list of commands that would need to be run to make this work. I tested them on a cobalt yesterday. You can find a repository created this way on cobalt02 in /scratch/ckopper/ (the repository URL is file:///scratch/ckopper/restored_dump (on cobalt02, not on a shared filesystem because Lustre is very, very slow when storing these).\n\nWith SVN sparse checkouts users can retrieve partial copies of the meta-project. An example is shown at the end of the attached script.\n\nPlease send comments on what you think about this. I think it would make the release process a lot easier and allow for things like svn diffs of whole meta-projects.",
"reporter": "claudio.kopper",
"cc": "",
"resolution": "duplicate",
"time": "2016-02-12T19:20:59",
"component": "infrastructure",
"summary": "remove the need for svn:externals (and merge the icetray repository back into the main one)",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "nega",
"type": "enhancement"
}
```
</p>
</details>
|
infrastructure
|
remove the need for svn externals and merge the icetray repository back into the main one trac we discussed the possibility of removing the need for svn externals in the usual meta projects at the software session in copenhagen they might still make sense for more specialized uses and or meta projects the idea is to move all relevant project trunks directly into combo and start releasing the whole meta projects this makes branching merging work in a sane way the process requires re integrating the icetray repository into the main repository a way that makes this work without breaking old meta projects using externals is to clone our main meta project and set the existing ones to read only the new meta project would exist at a new url something like instead of and attached is a working list of commands that would need to be run to make this work i tested them on a cobalt yesterday you can find a repository created this way on in scratch ckopper the repository url is file scratch ckopper restored dump on not on a shared filesystem because lustre is very very slow when storing these with svn sparse checkouts users can retrieve partial copies of the meta project an example is shown at the end of the attached script please send comments on what you think about this i think it would make the release process a lot easier and allow for things like svn diffs of whole meta projects migrated from json status closed changetime ts description we discussed the possibility of removing the need for svn externals in the usual meta projects at the software session in copenhagen they might still make sense for more specialized uses and or meta projects the idea is to move all relevant project trunks directly into combo and start releasing the whole meta projects this makes branching merging work in a sane way n nthe process requires re integrating the icetray repository into the main repository a way that makes this work without breaking old meta projects using externals is to clone our main meta project and set the existing ones to read only the new meta project would exist at a new url something like instead of and n nattached is a working list of commands that would need to be run to make this work i tested them on a cobalt yesterday you can find a repository created this way on in scratch ckopper the repository url is file scratch ckopper restored dump on not on a shared filesystem because lustre is very very slow when storing these n nwith svn sparse checkouts users can retrieve partial copies of the meta project an example is shown at the end of the attached script n nplease send comments on what you think about this i think it would make the release process a lot easier and allow for things like svn diffs of whole meta projects reporter claudio kopper cc resolution duplicate time component infrastructure summary remove the need for svn externals and merge the icetray repository back into the main one priority normal keywords milestone owner nega type enhancement
| 1
|
28,924
| 23,613,070,552
|
IssuesEvent
|
2022-08-24 13:53:14
|
spring-projects/spring-batch
|
https://api.github.com/repos/spring-projects/spring-batch
|
closed
|
Deprecate Hibernate support
|
type: task in: infrastructure
|
Due to https://github.com/spring-projects/spring-framework/issues/28813, we are intending to deprecate Hibernate support in Spring Batch in v5.0 for removal in v5.2.
|
1.0
|
Deprecate Hibernate support - Due to https://github.com/spring-projects/spring-framework/issues/28813, we are intending to deprecate Hibernate support in Spring Batch in v5.0 for removal in v5.2.
|
infrastructure
|
deprecate hibernate support due to we are intending to deprecate hibernate support in spring batch in for removal in
| 1
|
5,211
| 5,521,091,881
|
IssuesEvent
|
2017-03-19 12:42:50
|
Daniel-Mietchen/ideas
|
https://api.github.com/repos/Daniel-Mietchen/ideas
|
opened
|
Ideas for "resolve authors"
|
5min far-future infrastructure Wikidata
|
as per
https://tools.wmflabs.org/sourcemd/new_resolve_authors.php
- add "toggle all"
- display author names known via P50
|
1.0
|
Ideas for "resolve authors" - as per
https://tools.wmflabs.org/sourcemd/new_resolve_authors.php
- add "toggle all"
- display author names known via P50
|
infrastructure
|
ideas for resolve authors as per add toggle all display author names known via
| 1
|
49,813
| 3,004,504,077
|
IssuesEvent
|
2015-07-26 00:58:50
|
wwivbbs/wwiv
|
https://api.github.com/repos/wwivbbs/wwiv
|
closed
|
Taglines, OpenEdit/MSGINFO editor
|
5.0 auto-migrated FSED low priority sourceforge TAGLINES
|
Build 1099
OS Win7 32
Taglines are no longer generated with OpenEdit. Taglines are configured on, but they don't present.
Original comment by: mmunson79
|
1.0
|
Taglines, OpenEdit/MSGINFO editor - Build 1099
OS Win7 32
Taglines are no longer generated with OpenEdit. Taglines are configured on, but they don't present.
Original comment by: mmunson79
|
non_infrastructure
|
taglines openedit msginfo editor build os taglines are no longer generated with openedit taglines are configured on but they don t present original comment by
| 0
|
26,945
| 13,160,493,601
|
IssuesEvent
|
2020-08-10 17:42:12
|
yalelibrary/YUL-DC
|
https://api.github.com/repos/yalelibrary/YUL-DC
|
closed
|
deploy-sql and deploy-solr not working through cam tool
|
bug performance team
|
# Acceptant #
These two scripts should run the same both in and out of the camerata cli and produce the same results either way.
|
True
|
deploy-sql and deploy-solr not working through cam tool - # Acceptant #
These two scripts should run the same both in and out of the camerata cli and produce the same results either way.
|
non_infrastructure
|
deploy sql and deploy solr not working through cam tool acceptant these two scripts should run the same both in and out of the camerata cli and produce the same results either way
| 0
|
97,889
| 28,962,238,926
|
IssuesEvent
|
2023-05-10 04:15:50
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
`pytorch setup.py develop` fails on M1 macbooks with `fatal error: 'omp.h' file not found`
|
module: build triaged module: macos module: arm
|
### 🐛 Describe the bug
On my M1 macbook, running `pytorch setup.py develop` with a clean build resulted in the error `fatal error: 'omp.h' file not found`
To get the build to successfully run, I had to instead invoke `USE_OPENMP=0 python setup.py develop`
The error message:
```
(base) ➜ pytorch git:(zainr/reorder-tests) ✗ python setup.py develop
Building wheel torch-2.1.0a0+git812cadf
-- Building version 2.1.0a0+git812cadf
cmake --build . --target install --config Release
[1/440] Building OBJCXX object caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o
FAILED: caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o
/Library/Developer/CommandLineTools/usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DCAFFE2_BUILD_MAIN_LIB -DCPUINFO_SUPPORTED_PLATFORM=1 -DFMT_HEADER_ONLY=1 -DFXDIV_USE_INLINE_ASSEMBLY=0 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DNNP_CONVOLUTION_ONLY=0 -DNNP_INFERENCE_ONLY=0 -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx_torch -DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=64 -Dtorch_cpu_EXPORTS -I/Users/zainr/pytorch/build/aten/src -I/Users/zainr/pytorch/aten/src -I/Users/zainr/pytorch/build -I/Users/zainr/pytorch -I/Users/zainr/pytorch/cmake/../third_party/benchmark/include -I/Users/zainr/pytorch/third_party/onnx -I/Users/zainr/pytorch/build/third_party/onnx -I/Users/zainr/pytorch/third_party/foxi -I/Users/zainr/pytorch/build/third_party/foxi -I/Users/zainr/pytorch/torch/csrc/api -I/Users/zainr/pytorch/torch/csrc/api/include -I/Users/zainr/pytorch/caffe2/aten/src/TH -I/Users/zainr/pytorch/build/caffe2/aten/src/TH -I/Users/zainr/pytorch/build/caffe2/aten/src -I/Users/zainr/pytorch/build/caffe2/../aten/src -I/Users/zainr/pytorch/torch/csrc -I/Users/zainr/pytorch/third_party/miniz-2.1.0 -I/Users/zainr/pytorch/third_party/kineto/libkineto/include -I/Users/zainr/pytorch/third_party/kineto/libkineto/src -I/Users/zainr/pytorch/aten/src/ATen/.. -I/Users/zainr/pytorch/third_party/FXdiv/include -I/Users/zainr/pytorch/c10/.. -I/Users/zainr/pytorch/third_party/pthreadpool/include -I/Users/zainr/pytorch/third_party/cpuinfo/include -I/Users/zainr/pytorch/aten/src/ATen/native/quantized/cpu/qnnpack/include -I/Users/zainr/pytorch/aten/src/ATen/native/quantized/cpu/qnnpack/src -I/Users/zainr/pytorch/third_party/cpuinfo/deps/clog/include -I/Users/zainr/pytorch/third_party/NNPACK/include -I/Users/zainr/pytorch/third_party/FP16/include -I/Users/zainr/pytorch/third_party/fmt/include -I/Users/zainr/pytorch/third_party/flatbuffers/include -isystem /Users/zainr/pytorch/cmake/../third_party/googletest/googlemock/include -isystem /Users/zainr/pytorch/cmake/../third_party/googletest/googletest/include -isystem /Users/zainr/pytorch/third_party/protobuf/src -isystem /Users/zainr/pytorch/third_party/XNNPACK/include -isystem /Users/zainr/pytorch/cmake/../third_party/eigen -isystem /Users/zainr/pytorch/build/include -x objective-c++ -DUSE_MPS -O3 -DNDEBUG -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk -fPIC -mfpu=neon -D__NEON__ -DTH_HAVE_THREAD -std=gnu++17 -MD -MT caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o -MF caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o.d -o caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o -c /Users/zainr/pytorch/aten/src/ATen/native/mps/operations/Indexing.mm
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
In file included from /Users/zainr/pytorch/aten/src/ATen/native/mps/operations/Indexing.mm:16:
In file included from /Users/zainr/pytorch/aten/src/ATen/native/TensorAdvancedIndexing.h:9:
/Users/zainr/pytorch/aten/src/ATen/native/cpu/radix_sort.h:25:10: fatal error: 'omp.h' file not found
#include <omp.h>
^~~~~~~
1 error generated.
```
### Versions
(base) ➜ pytorch git:(zainr/reorder-tests) ✗ python collect_env.py
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: macOS 13.3.1 (arm64)
GCC version: Could not collect
Clang version: 14.0.3 (clang-1403.0.22.14.1)
CMake version: version 3.22.1
Libc version: N/A
Python version: 3.9.12 (main, Apr 5 2022, 01:52:34) [Clang 12.0.0 ] (64-bit runtime)
Python platform: macOS-13.3.1-arm64-arm-64bit
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
CPU:
Apple M1 Pro
Versions of relevant libraries:
[pip3] flake8==6.0.0
[pip3] flake8-bugbear==23.3.23
[pip3] flake8-comprehensions==3.11.1
[pip3] flake8-executable==2.1.3
[pip3] flake8-logging-format==0.9.0
[pip3] flake8-pyi==23.3.1
[pip3] flake8-simplify==0.19.3
[pip3] mypy==0.960
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.23.1
[conda] numpy
cc @malfet @seemethere @albanD
|
1.0
|
`pytorch setup.py develop` fails on M1 macbooks with `fatal error: 'omp.h' file not found` - ### 🐛 Describe the bug
On my M1 macbook, running `pytorch setup.py develop` with a clean build resulted in the error `fatal error: 'omp.h' file not found`
To get the build to successfully run, I had to instead invoke `USE_OPENMP=0 python setup.py develop`
The error message:
```
(base) ➜ pytorch git:(zainr/reorder-tests) ✗ python setup.py develop
Building wheel torch-2.1.0a0+git812cadf
-- Building version 2.1.0a0+git812cadf
cmake --build . --target install --config Release
[1/440] Building OBJCXX object caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o
FAILED: caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o
/Library/Developer/CommandLineTools/usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DCAFFE2_BUILD_MAIN_LIB -DCPUINFO_SUPPORTED_PLATFORM=1 -DFMT_HEADER_ONLY=1 -DFXDIV_USE_INLINE_ASSEMBLY=0 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DNNP_CONVOLUTION_ONLY=0 -DNNP_INFERENCE_ONLY=0 -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx_torch -DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=64 -Dtorch_cpu_EXPORTS -I/Users/zainr/pytorch/build/aten/src -I/Users/zainr/pytorch/aten/src -I/Users/zainr/pytorch/build -I/Users/zainr/pytorch -I/Users/zainr/pytorch/cmake/../third_party/benchmark/include -I/Users/zainr/pytorch/third_party/onnx -I/Users/zainr/pytorch/build/third_party/onnx -I/Users/zainr/pytorch/third_party/foxi -I/Users/zainr/pytorch/build/third_party/foxi -I/Users/zainr/pytorch/torch/csrc/api -I/Users/zainr/pytorch/torch/csrc/api/include -I/Users/zainr/pytorch/caffe2/aten/src/TH -I/Users/zainr/pytorch/build/caffe2/aten/src/TH -I/Users/zainr/pytorch/build/caffe2/aten/src -I/Users/zainr/pytorch/build/caffe2/../aten/src -I/Users/zainr/pytorch/torch/csrc -I/Users/zainr/pytorch/third_party/miniz-2.1.0 -I/Users/zainr/pytorch/third_party/kineto/libkineto/include -I/Users/zainr/pytorch/third_party/kineto/libkineto/src -I/Users/zainr/pytorch/aten/src/ATen/.. -I/Users/zainr/pytorch/third_party/FXdiv/include -I/Users/zainr/pytorch/c10/.. -I/Users/zainr/pytorch/third_party/pthreadpool/include -I/Users/zainr/pytorch/third_party/cpuinfo/include -I/Users/zainr/pytorch/aten/src/ATen/native/quantized/cpu/qnnpack/include -I/Users/zainr/pytorch/aten/src/ATen/native/quantized/cpu/qnnpack/src -I/Users/zainr/pytorch/third_party/cpuinfo/deps/clog/include -I/Users/zainr/pytorch/third_party/NNPACK/include -I/Users/zainr/pytorch/third_party/FP16/include -I/Users/zainr/pytorch/third_party/fmt/include -I/Users/zainr/pytorch/third_party/flatbuffers/include -isystem /Users/zainr/pytorch/cmake/../third_party/googletest/googlemock/include -isystem /Users/zainr/pytorch/cmake/../third_party/googletest/googletest/include -isystem /Users/zainr/pytorch/third_party/protobuf/src -isystem /Users/zainr/pytorch/third_party/XNNPACK/include -isystem /Users/zainr/pytorch/cmake/../third_party/eigen -isystem /Users/zainr/pytorch/build/include -x objective-c++ -DUSE_MPS -O3 -DNDEBUG -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk -fPIC -mfpu=neon -D__NEON__ -DTH_HAVE_THREAD -std=gnu++17 -MD -MT caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o -MF caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o.d -o caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/mps/operations/Indexing.mm.o -c /Users/zainr/pytorch/aten/src/ATen/native/mps/operations/Indexing.mm
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
In file included from /Users/zainr/pytorch/aten/src/ATen/native/mps/operations/Indexing.mm:16:
In file included from /Users/zainr/pytorch/aten/src/ATen/native/TensorAdvancedIndexing.h:9:
/Users/zainr/pytorch/aten/src/ATen/native/cpu/radix_sort.h:25:10: fatal error: 'omp.h' file not found
#include <omp.h>
^~~~~~~
1 error generated.
```
### Versions
(base) ➜ pytorch git:(zainr/reorder-tests) ✗ python collect_env.py
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: macOS 13.3.1 (arm64)
GCC version: Could not collect
Clang version: 14.0.3 (clang-1403.0.22.14.1)
CMake version: version 3.22.1
Libc version: N/A
Python version: 3.9.12 (main, Apr 5 2022, 01:52:34) [Clang 12.0.0 ] (64-bit runtime)
Python platform: macOS-13.3.1-arm64-arm-64bit
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
CPU:
Apple M1 Pro
Versions of relevant libraries:
[pip3] flake8==6.0.0
[pip3] flake8-bugbear==23.3.23
[pip3] flake8-comprehensions==3.11.1
[pip3] flake8-executable==2.1.3
[pip3] flake8-logging-format==0.9.0
[pip3] flake8-pyi==23.3.1
[pip3] flake8-simplify==0.19.3
[pip3] mypy==0.960
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.23.1
[conda] numpy
cc @malfet @seemethere @albanD
|
non_infrastructure
|
pytorch setup py develop fails on macbooks with fatal error omp h file not found 🐛 describe the bug on my macbook running pytorch setup py develop with a clean build resulted in the error fatal error omp h file not found to get the build to successfully run i had to instead invoke use openmp python setup py develop the error message base ➜ pytorch git zainr reorder tests ✗ python setup py develop building wheel torch building version cmake build target install config release building objcxx object cmakefiles torch cpu dir aten src aten native mps operations indexing mm o failed cmakefiles torch cpu dir aten src aten native mps operations indexing mm o library developer commandlinetools usr bin c dat per operator headers build main lib dcpuinfo supported platform dfmt header only dfxdiv use inline assembly dhave mmap dhave shm open dhave shm unlink dminiz disable zip reader checks dnnp convolution only dnnp inference only donnxifi enable ext donnx ml donnx namespace onnx torch duse external mzcrc d file offset bits dtorch cpu exports i users zainr pytorch build aten src i users zainr pytorch aten src i users zainr pytorch build i users zainr pytorch i users zainr pytorch cmake third party benchmark include i users zainr pytorch third party onnx i users zainr pytorch build third party onnx i users zainr pytorch third party foxi i users zainr pytorch build third party foxi i users zainr pytorch torch csrc api i users zainr pytorch torch csrc api include i users zainr pytorch aten src th i users zainr pytorch build aten src th i users zainr pytorch build aten src i users zainr pytorch build aten src i users zainr pytorch torch csrc i users zainr pytorch third party miniz i users zainr pytorch third party kineto libkineto include i users zainr pytorch third party kineto libkineto src i users zainr pytorch aten src aten i users zainr pytorch third party fxdiv include i users zainr pytorch i users zainr pytorch third party pthreadpool include i users zainr pytorch third party cpuinfo include i users zainr pytorch aten src aten native quantized cpu qnnpack include i users zainr pytorch aten src aten native quantized cpu qnnpack src i users zainr pytorch third party cpuinfo deps clog include i users zainr pytorch third party nnpack include i users zainr pytorch third party include i users zainr pytorch third party fmt include i users zainr pytorch third party flatbuffers include isystem users zainr pytorch cmake third party googletest googlemock include isystem users zainr pytorch cmake third party googletest googletest include isystem users zainr pytorch third party protobuf src isystem users zainr pytorch third party xnnpack include isystem users zainr pytorch cmake third party eigen isystem users zainr pytorch build include x objective c duse mps dndebug arch isysroot library developer commandlinetools sdks sdk fpic mfpu neon d neon dth have thread std gnu md mt cmakefiles torch cpu dir aten src aten native mps operations indexing mm o mf cmakefiles torch cpu dir aten src aten native mps operations indexing mm o d o cmakefiles torch cpu dir aten src aten native mps operations indexing mm o c users zainr pytorch aten src aten native mps operations indexing mm clang warning argument unused during compilation mfpu neon in file included from users zainr pytorch aten src aten native mps operations indexing mm in file included from users zainr pytorch aten src aten native tensoradvancedindexing h users zainr pytorch aten src aten native cpu radix sort h fatal error omp h file not found include error generated versions base ➜ pytorch git zainr reorder tests ✗ python collect env py collecting environment information pytorch version n a is debug build n a cuda used to build pytorch n a rocm used to build pytorch n a os macos gcc version could not collect clang version clang cmake version version libc version n a python version main apr bit runtime python platform macos arm is cuda available n a cuda runtime version could not collect cuda module loading set to n a gpu models and configuration could not collect nvidia driver version could not collect cudnn version could not collect hip runtime version n a miopen runtime version n a is xnnpack available n a cpu apple pro versions of relevant libraries bugbear comprehensions executable logging format pyi simplify mypy mypy extensions numpy numpy cc malfet seemethere alband
| 0
|
83,181
| 3,631,622,060
|
IssuesEvent
|
2016-02-11 02:54:11
|
umple/umple
|
https://api.github.com/repos/umple/umple
|
closed
|
Have myenv default to `local` when building
|
Diffic-Easy enhancement Maintainability Priority-Low
|
## Description
Currently, myenv defaults to `cc`. This is a very specific case and most people are building via local developments. When building this way, one often types commands by hand.
In contrast, when working with a build environment when scripting, e.g. Travis, or CC, you're writing scripts where it is straight forward to add the -Dmyenv=local to the script parameters.
## Suggested fix
Change (`_template.xml`):
```xml
<property name="myenv" value="cc" />
```
to:
```xml
<property name="myenv" value="local" />
```
## Known issues
This may require changes to the CC scripts. I do not have access to them, thus I have no idea about the scope of this change.
Opening this as a discussion.
|
1.0
|
Have myenv default to `local` when building - ## Description
Currently, myenv defaults to `cc`. This is a very specific case and most people are building via local developments. When building this way, one often types commands by hand.
In contrast, when working with a build environment when scripting, e.g. Travis, or CC, you're writing scripts where it is straight forward to add the -Dmyenv=local to the script parameters.
## Suggested fix
Change (`_template.xml`):
```xml
<property name="myenv" value="cc" />
```
to:
```xml
<property name="myenv" value="local" />
```
## Known issues
This may require changes to the CC scripts. I do not have access to them, thus I have no idea about the scope of this change.
Opening this as a discussion.
|
non_infrastructure
|
have myenv default to local when building description currently myenv defaults to cc this is a very specific case and most people are building via local developments when building this way one often types commands by hand in contrast when working with a build environment when scripting e g travis or cc you re writing scripts where it is straight forward to add the dmyenv local to the script parameters suggested fix change template xml xml to xml known issues this may require changes to the cc scripts i do not have access to them thus i have no idea about the scope of this change opening this as a discussion
| 0
|
256,248
| 27,557,388,492
|
IssuesEvent
|
2023-03-07 19:02:21
|
occmundial/atomic-icons
|
https://api.github.com/repos/occmundial/atomic-icons
|
closed
|
CVE-2022-21681 (High) detected in marked-2.1.3.tgz - autoclosed
|
security vulnerability
|
## CVE-2022-21681 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-2.1.3.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-2.1.3.tgz">https://registry.npmjs.org/marked/-/marked-2.1.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-17.4.4.tgz (Root Library)
- :x: **marked-2.1.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/occmundial/atomic-icons/commit/4f36497e21048c2145796a4a67ef30d245dd9eee">4f36497e21048c2145796a4a67ef30d245dd9eee</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Marked is a markdown parser and compiler. Prior to version 4.0.10, the regular expression `inline.reflinkSearch` may cause catastrophic backtracking against some strings and lead to a denial of service (DoS). Anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected. This issue is patched in version 4.0.10. As a workaround, avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
<p>Publish Date: 2022-01-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21681>CVE-2022-21681</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-5v2h-r2cx-5xgj">https://github.com/advisories/GHSA-5v2h-r2cx-5xgj</a></p>
<p>Release Date: 2022-01-14</p>
<p>Fix Resolution (marked): 4.0.10</p>
<p>Direct dependency fix Resolution (semantic-release): 19.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-21681 (High) detected in marked-2.1.3.tgz - autoclosed - ## CVE-2022-21681 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-2.1.3.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-2.1.3.tgz">https://registry.npmjs.org/marked/-/marked-2.1.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-17.4.4.tgz (Root Library)
- :x: **marked-2.1.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/occmundial/atomic-icons/commit/4f36497e21048c2145796a4a67ef30d245dd9eee">4f36497e21048c2145796a4a67ef30d245dd9eee</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Marked is a markdown parser and compiler. Prior to version 4.0.10, the regular expression `inline.reflinkSearch` may cause catastrophic backtracking against some strings and lead to a denial of service (DoS). Anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected. This issue is patched in version 4.0.10. As a workaround, avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
<p>Publish Date: 2022-01-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21681>CVE-2022-21681</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-5v2h-r2cx-5xgj">https://github.com/advisories/GHSA-5v2h-r2cx-5xgj</a></p>
<p>Release Date: 2022-01-14</p>
<p>Fix Resolution (marked): 4.0.10</p>
<p>Direct dependency fix Resolution (semantic-release): 19.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_infrastructure
|
cve high detected in marked tgz autoclosed cve high severity vulnerability vulnerable library marked tgz a markdown parser built for speed library home page a href path to dependency file package json path to vulnerable library node modules marked package json dependency hierarchy semantic release tgz root library x marked tgz vulnerable library found in head commit a href found in base branch main vulnerability details marked is a markdown parser and compiler prior to version the regular expression inline reflinksearch may cause catastrophic backtracking against some strings and lead to a denial of service dos anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected this issue is patched in version as a workaround avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources 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 marked direct dependency fix resolution semantic release step up your open source security game with mend
| 0
|
7,259
| 6,808,939,520
|
IssuesEvent
|
2017-11-04 10:50:29
|
HaCSBCU/hacsbcu.github.io
|
https://api.github.com/repos/HaCSBCU/hacsbcu.github.io
|
opened
|
HTTP Strict Transport Security
|
SECURITY
|
HTTP Strict Transport Security (HSTS) header not implemented.
https://wiki.mozilla.org/Security/Guidelines/Web_Security#HTTP_Strict_Transport_Security
|
True
|
HTTP Strict Transport Security - HTTP Strict Transport Security (HSTS) header not implemented.
https://wiki.mozilla.org/Security/Guidelines/Web_Security#HTTP_Strict_Transport_Security
|
non_infrastructure
|
http strict transport security http strict transport security hsts header not implemented
| 0
|
18,376
| 12,961,009,816
|
IssuesEvent
|
2020-07-20 15:06:33
|
gnosis/safe-ios
|
https://api.github.com/repos/gnosis/safe-ios
|
opened
|
Remove non-inclusive language
|
infrastructure
|
- "master" branch -> "main" branch
- "masterCopy" -> "primaryCopy"
- "whitelist" -> "allow list"
- "blacklist" -> "deny list"
|
1.0
|
Remove non-inclusive language - - "master" branch -> "main" branch
- "masterCopy" -> "primaryCopy"
- "whitelist" -> "allow list"
- "blacklist" -> "deny list"
|
infrastructure
|
remove non inclusive language master branch main branch mastercopy primarycopy whitelist allow list blacklist deny list
| 1
|
211,866
| 23,850,202,518
|
IssuesEvent
|
2022-09-06 17:10:53
|
CMSgov/mdct-mcr
|
https://api.github.com/repos/CMSgov/mdct-mcr
|
closed
|
SHF - mdct-mcr - main - MEDIUM - S3.12 S3 access control lists (ACLs) should not be used to manage user access to buckets
|
security-hub main
|
**************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Id: arn:aws:securityhub:us-east-1:446712541566:subscription/aws-foundational-security-best-practices/v/1.0.0/S3.12/finding/631bf8e3-eaed-448c-9204-300421715eee
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
S3.12 S3 access control lists (ACLs) should not be used to manage user access to buckets
## Id:
arn:aws:securityhub:us-east-1:446712541566:subscription/aws-foundational-security-best-practices/v/1.0.0/S3.12/finding/631bf8e3-eaed-448c-9204-300421715eee
(You may use this ID to lookup this finding's details in Security Hub)
## Description
This control checks if S3 buckets allow user permissions via access control lists (ACLs). This control fails if ACLs are configured for user access on S3 Bucket.
## Remediation
https://docs.aws.amazon.com/console/securityhub/S3.12/remediation
## AC:
- The security hub finding is resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed.
|
True
|
SHF - mdct-mcr - main - MEDIUM - S3.12 S3 access control lists (ACLs) should not be used to manage user access to buckets - **************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Id: arn:aws:securityhub:us-east-1:446712541566:subscription/aws-foundational-security-best-practices/v/1.0.0/S3.12/finding/631bf8e3-eaed-448c-9204-300421715eee
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
S3.12 S3 access control lists (ACLs) should not be used to manage user access to buckets
## Id:
arn:aws:securityhub:us-east-1:446712541566:subscription/aws-foundational-security-best-practices/v/1.0.0/S3.12/finding/631bf8e3-eaed-448c-9204-300421715eee
(You may use this ID to lookup this finding's details in Security Hub)
## Description
This control checks if S3 buckets allow user permissions via access control lists (ACLs). This control fails if ACLs are configured for user access on S3 Bucket.
## Remediation
https://docs.aws.amazon.com/console/securityhub/S3.12/remediation
## AC:
- The security hub finding is resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed.
|
non_infrastructure
|
shf mdct mcr main medium access control lists acls should not be used to manage user access to buckets this issue was generated from security hub data and is managed through automation please do not edit the title or body of this issue or remove the security hub tag all other edits comments are welcome finding id arn aws securityhub us east subscription aws foundational security best practices v finding eaed type of issue security hub finding title access control lists acls should not be used to manage user access to buckets id arn aws securityhub us east subscription aws foundational security best practices v finding eaed you may use this id to lookup this finding s details in security hub description this control checks if buckets allow user permissions via access control lists acls this control fails if acls are configured for user access on bucket remediation ac the security hub finding is resolved or suppressed indicated by a workflow status of resolved or suppressed
| 0
|
49,974
| 10,436,936,378
|
IssuesEvent
|
2019-09-17 20:44:05
|
eclipse/che
|
https://api.github.com/repos/eclipse/che
|
closed
|
Cover "Dashboard / Workspace Details / Overview" part of test plan by selenium test
|
kind/task lifecycle/stale status/code-review team/che-qe
|
### Description
We have the test plan where described all use cases for dashboard:
https://docs.google.com/document/d/1aXUAWFOOylrk-_nO5Iqm77M0Viu8ykCjaQMtJuEBvUA/edit#heading=h.wf4eguoewmmg
We should cover the "Dashboard / Workspace Details / Overview" page by selenium test according to use cases which described in the test plan.
|
1.0
|
Cover "Dashboard / Workspace Details / Overview" part of test plan by selenium test - ### Description
We have the test plan where described all use cases for dashboard:
https://docs.google.com/document/d/1aXUAWFOOylrk-_nO5Iqm77M0Viu8ykCjaQMtJuEBvUA/edit#heading=h.wf4eguoewmmg
We should cover the "Dashboard / Workspace Details / Overview" page by selenium test according to use cases which described in the test plan.
|
non_infrastructure
|
cover dashboard workspace details overview part of test plan by selenium test description we have the test plan where described all use cases for dashboard we should cover the dashboard workspace details overview page by selenium test according to use cases which described in the test plan
| 0
|
15,916
| 11,765,443,123
|
IssuesEvent
|
2020-03-14 17:25:12
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Microsoft.Bcl.AsyncInterfaces
|
area-Infrastructure-libraries customer assistance
|
Microsoft.Bcl.AsyncInterfaces has dependency on System.Threading.Tasks.Extensions >= 4.5.2, and it works fine with 4.5.2 version. However if upgraded to 4.5.3 app will throw below exception
```
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=4.2.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manif
est definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
```
|
1.0
|
Microsoft.Bcl.AsyncInterfaces -
Microsoft.Bcl.AsyncInterfaces has dependency on System.Threading.Tasks.Extensions >= 4.5.2, and it works fine with 4.5.2 version. However if upgraded to 4.5.3 app will throw below exception
```
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=4.2.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manif
est definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
```
|
infrastructure
|
microsoft bcl asyncinterfaces microsoft bcl asyncinterfaces has dependency on system threading tasks extensions and it works fine with version however if upgraded to app will throw below exception unhandled exception system io fileloadexception could not load file or assembly system threading tasks extensions version culture neutral publickeytoken or one of its dependencies the located assembly s manif est definition does not match the assembly reference exception from hresult
| 1
|
34,715
| 6,367,713,826
|
IssuesEvent
|
2017-08-01 07:15:52
|
symfony/symfony-docs
|
https://api.github.com/repos/symfony/symfony-docs
|
closed
|
[BrowserKit] Emulate back/forward browser navigation
|
BrowserKit hasPR Missing Documentation
|
See https://github.com/symfony/symfony/pull/22341.
BrowserKit now behaves as normal browsers, so let's check if we mention anywhere the old behavior as something specific to Symfony.
|
1.0
|
[BrowserKit] Emulate back/forward browser navigation - See https://github.com/symfony/symfony/pull/22341.
BrowserKit now behaves as normal browsers, so let's check if we mention anywhere the old behavior as something specific to Symfony.
|
non_infrastructure
|
emulate back forward browser navigation see browserkit now behaves as normal browsers so let s check if we mention anywhere the old behavior as something specific to symfony
| 0
|
42,895
| 12,958,898,562
|
IssuesEvent
|
2020-07-20 12:10:11
|
mdsaj/LP-AngularSpring
|
https://api.github.com/repos/mdsaj/LP-AngularSpring
|
closed
|
CVE-2019-14379 (High) detected in jackson-databind-2.9.7.jar
|
security vulnerability
|
## CVE-2019-14379 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.7.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/LP-AngularSpring/AngularSpring/bin/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.7/jackson-databind-2.9.7.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.1.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.1.RELEASE.jar
- :x: **jackson-databind-2.9.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/mdsaj/LP-AngularSpring/commit/4e7f828d4ba904c93c26ef7d7af0f753a3c44a38">4e7f828d4ba904c93c26ef7d7af0f753a3c44a38</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.
<p>Publish Date: 2019-07-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14379>CVE-2019-14379</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379</a></p>
<p>Release Date: 2019-07-29</p>
<p>Fix Resolution: 2.9.9.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-14379 (High) detected in jackson-databind-2.9.7.jar - ## CVE-2019-14379 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.7.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/LP-AngularSpring/AngularSpring/bin/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.7/jackson-databind-2.9.7.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.1.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.1.RELEASE.jar
- :x: **jackson-databind-2.9.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/mdsaj/LP-AngularSpring/commit/4e7f828d4ba904c93c26ef7d7af0f753a3c44a38">4e7f828d4ba904c93c26ef7d7af0f753a3c44a38</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.
<p>Publish Date: 2019-07-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14379>CVE-2019-14379</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379</a></p>
<p>Release Date: 2019-07-29</p>
<p>Fix Resolution: 2.9.9.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_infrastructure
|
cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file tmp ws scm lp angularspring angularspring bin pom xml path to vulnerable library root repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter web release jar root library spring boot starter json release jar x jackson databind jar vulnerable library found in head commit a href vulnerability details subtypevalidator java in fasterxml jackson databind before mishandles default typing when ehcache is used because of net sf ehcache transaction manager defaulttransactionmanagerlookup leading to remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
27,015
| 21,006,088,770
|
IssuesEvent
|
2022-03-29 22:50:19
|
opensearch-project/k-NN
|
https://api.github.com/repos/opensearch-project/k-NN
|
closed
|
Apply spotless on whole project and get rid of ratchet
|
Infrastructure
|
Currently, we only apply spotless check on files that are touched only by the PR. The goal of this was to maintain git history.
However, I think we should just make one large spotless apply commit (as suggested here https://github.com/opensearch-project/k-NN/pull/328#discussion_r836714040) so that PRs dont contain changes unrelated to the PRs.
What are your thoughts @VijayanB @martin-gaievski ?
|
1.0
|
Apply spotless on whole project and get rid of ratchet - Currently, we only apply spotless check on files that are touched only by the PR. The goal of this was to maintain git history.
However, I think we should just make one large spotless apply commit (as suggested here https://github.com/opensearch-project/k-NN/pull/328#discussion_r836714040) so that PRs dont contain changes unrelated to the PRs.
What are your thoughts @VijayanB @martin-gaievski ?
|
infrastructure
|
apply spotless on whole project and get rid of ratchet currently we only apply spotless check on files that are touched only by the pr the goal of this was to maintain git history however i think we should just make one large spotless apply commit as suggested here so that prs dont contain changes unrelated to the prs what are your thoughts vijayanb martin gaievski
| 1
|
19,161
| 13,196,120,149
|
IssuesEvent
|
2020-08-13 20:00:45
|
microsoft/react-native-windows
|
https://api.github.com/repos/microsoft/react-native-windows
|
closed
|
Support direct debugging when using Chakra in VS Code.
|
Area: Debug Infrastructure Proposal
|
<!-- This is a template for new feature or API proposals for React Native Windows. Use this to submit new API/component requests or behavior updates that are specific to Windows-only. For feature requests to React Native, go [here](https://github.com/react-native-community/discussions-and-proposals) instead.
It's fine if you don't have all the details for the template below: you can start with the Summary and Rationale. Read more about React Native for Windows proposal process [here](https://github.com/microsoft/react-native-windows/tree/master/vnext/proposals)
-->
# Proposal: Support direct debugging in visual studio code
<!-- Add a title for your feature or API proposal. Please be short and descriptive -->
## Summary
<!-- Brief explanation of the new API or change. -->
You can use VS Code for direct debugging when using V8/Hermes, but not for Chakra. This issue is for adding support.
## Motivation
<!-- Why are we doing this? What use cases does it support? What is the expected outcome? Why should this be done for Windows-only?
Please focus on explaining the motivation so that if this proposal is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind. -->
The only way to do direct debugging with Chakra is through Visual Studio. Adding support for VS Code would allow developers to pick the tool that better suits their needs.
## Basic example
<!-- [Optional] If the proposal involves a new or changed API, include a basic code example. Omit this section if it's not applicable. -->
## Open Questions
<!-- Please list any open issues that you think still need to be addressed.
These could include areas you think would benefit from community or the react-native-windows team input -->
|
1.0
|
Support direct debugging when using Chakra in VS Code. - <!-- This is a template for new feature or API proposals for React Native Windows. Use this to submit new API/component requests or behavior updates that are specific to Windows-only. For feature requests to React Native, go [here](https://github.com/react-native-community/discussions-and-proposals) instead.
It's fine if you don't have all the details for the template below: you can start with the Summary and Rationale. Read more about React Native for Windows proposal process [here](https://github.com/microsoft/react-native-windows/tree/master/vnext/proposals)
-->
# Proposal: Support direct debugging in visual studio code
<!-- Add a title for your feature or API proposal. Please be short and descriptive -->
## Summary
<!-- Brief explanation of the new API or change. -->
You can use VS Code for direct debugging when using V8/Hermes, but not for Chakra. This issue is for adding support.
## Motivation
<!-- Why are we doing this? What use cases does it support? What is the expected outcome? Why should this be done for Windows-only?
Please focus on explaining the motivation so that if this proposal is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind. -->
The only way to do direct debugging with Chakra is through Visual Studio. Adding support for VS Code would allow developers to pick the tool that better suits their needs.
## Basic example
<!-- [Optional] If the proposal involves a new or changed API, include a basic code example. Omit this section if it's not applicable. -->
## Open Questions
<!-- Please list any open issues that you think still need to be addressed.
These could include areas you think would benefit from community or the react-native-windows team input -->
|
infrastructure
|
support direct debugging when using chakra in vs code this is a template for new feature or api proposals for react native windows use this to submit new api component requests or behavior updates that are specific to windows only for feature requests to react native go instead it s fine if you don t have all the details for the template below you can start with the summary and rationale read more about react native for windows proposal process proposal support direct debugging in visual studio code summary you can use vs code for direct debugging when using hermes but not for chakra this issue is for adding support motivation why are we doing this what use cases does it support what is the expected outcome why should this be done for windows only please focus on explaining the motivation so that if this proposal is not accepted the motivation could be used to develop alternative solutions in other words enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind the only way to do direct debugging with chakra is through visual studio adding support for vs code would allow developers to pick the tool that better suits their needs basic example open questions please list any open issues that you think still need to be addressed these could include areas you think would benefit from community or the react native windows team input
| 1
|
18,761
| 13,096,273,699
|
IssuesEvent
|
2020-08-03 15:25:03
|
knative/docs
|
https://api.github.com/repos/knative/docs
|
closed
|
First Eventing Example is Too Complicated
|
kind/epic kind/eventing kind/infrastructure kind/sample lifecycle/frozen
|
**Describe the change you'd like to see**
The landing page points to an eventing example that deals with the kubernetes event source. I think it is too complicated.
A simple cronjob event source should suffice. It would avoid having to setup service accounts and role binding for the k8s source to work.
**Additional context**
Just going through the first 4 examples of the landing page.
|
1.0
|
First Eventing Example is Too Complicated -
**Describe the change you'd like to see**
The landing page points to an eventing example that deals with the kubernetes event source. I think it is too complicated.
A simple cronjob event source should suffice. It would avoid having to setup service accounts and role binding for the k8s source to work.
**Additional context**
Just going through the first 4 examples of the landing page.
|
infrastructure
|
first eventing example is too complicated describe the change you d like to see the landing page points to an eventing example that deals with the kubernetes event source i think it is too complicated a simple cronjob event source should suffice it would avoid having to setup service accounts and role binding for the source to work additional context just going through the first examples of the landing page
| 1
|
165,514
| 6,277,681,600
|
IssuesEvent
|
2017-07-18 12:50:46
|
vanilla-framework/vanilla-framework
|
https://api.github.com/repos/vanilla-framework/vanilla-framework
|
closed
|
Link to Grid page in strip documentation
|
Priority: High Status: Review
|
From [the “Strip” reference](https://docs.vanillaframework.io/en/patterns/strip): “The strip pattern provides a full width strip container in which to wrap a row. A strip can have light (`.p-strip--light`) or dark (`.p-strip--dark`) grey background. A `.p-strip` container should always be the parent of a `.row` and never the other way around.”
Okay, but what is this “row” thing? Is it a table row? The code example suggests not. So what else?
|
1.0
|
Link to Grid page in strip documentation - From [the “Strip” reference](https://docs.vanillaframework.io/en/patterns/strip): “The strip pattern provides a full width strip container in which to wrap a row. A strip can have light (`.p-strip--light`) or dark (`.p-strip--dark`) grey background. A `.p-strip` container should always be the parent of a `.row` and never the other way around.”
Okay, but what is this “row” thing? Is it a table row? The code example suggests not. So what else?
|
non_infrastructure
|
link to grid page in strip documentation from “the strip pattern provides a full width strip container in which to wrap a row a strip can have light p strip light or dark p strip dark grey background a p strip container should always be the parent of a row and never the other way around ” okay but what is this “row” thing is it a table row the code example suggests not so what else
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.