Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 1
744
| labels
stringlengths 4
574
| body
stringlengths 9
211k
| index
stringclasses 10
values | text_combine
stringlengths 96
211k
| label
stringclasses 2
values | text
stringlengths 96
188k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
14,447
| 17,500,598,774
|
IssuesEvent
|
2021-08-10 08:57:58
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[iOS] App crashes in study activities screen on completing consent review process in a scenario
|
Bug P0 iOS Process: Fixed Process: Tested QA Process: Tested dev
|
**Steps:**
1. Signing and enroll into study
2. Update consent from SB and enable 'Enforce e-consent flow again for enrolled participants'
3. Publish updates
4. Open the study and navigate to study activities
5. Don't complete the consent review.
6. Kill and relaunch the app and navigate to study activities
7. Complete the consent review process
8. Refresh the study activities after completing.
9. Observe app crashes
**Actual:** App crashes in study activities screen on completing consent review process in a scenario
**Expected:** App should not crash
Issue not observed when user completes the consent review process in the 1st try
https://user-images.githubusercontent.com/60386291/128379872-2744fb07-1abb-44a3-be79-c28ec98b3ff1.MOV
|
3.0
|
[iOS] App crashes in study activities screen on completing consent review process in a scenario - **Steps:**
1. Signing and enroll into study
2. Update consent from SB and enable 'Enforce e-consent flow again for enrolled participants'
3. Publish updates
4. Open the study and navigate to study activities
5. Don't complete the consent review.
6. Kill and relaunch the app and navigate to study activities
7. Complete the consent review process
8. Refresh the study activities after completing.
9. Observe app crashes
**Actual:** App crashes in study activities screen on completing consent review process in a scenario
**Expected:** App should not crash
Issue not observed when user completes the consent review process in the 1st try
https://user-images.githubusercontent.com/60386291/128379872-2744fb07-1abb-44a3-be79-c28ec98b3ff1.MOV
|
process
|
app crashes in study activities screen on completing consent review process in a scenario steps signing and enroll into study update consent from sb and enable enforce e consent flow again for enrolled participants publish updates open the study and navigate to study activities don t complete the consent review kill and relaunch the app and navigate to study activities complete the consent review process refresh the study activities after completing observe app crashes actual app crashes in study activities screen on completing consent review process in a scenario expected app should not crash issue not observed when user completes the consent review process in the try
| 1
|
10,299
| 2,622,141,323
|
IssuesEvent
|
2015-03-04 00:02:08
|
byzhang/spserver
|
https://api.github.com/repos/byzhang/spserver
|
closed
|
遇到执行错误，猜测是动态链接库出错
|
auto-migrated Priority-Medium Type-Defect
|
```
编译什么的都通过了，生成了可执行文件，比如说，测试使��
�的testecho，我使用ldd查看需要的动态库也都OK 但是启动时候
提示undefined symbol: _ZTI17SP_HandlerFactory
一般怎么回事？ 不知道如何去查？
```
Original issue reported on code.google.com by `rock...@gmail.com` on 30 Apr 2011 at 10:27
|
1.0
|
遇到执行错误，猜测是动态链接库出错 - ```
编译什么的都通过了，生成了可执行文件，比如说，测试使��
�的testecho，我使用ldd查看需要的动态库也都OK 但是启动时候
提示undefined symbol: _ZTI17SP_HandlerFactory
一般怎么回事？ 不知道如何去查？
```
Original issue reported on code.google.com by `rock...@gmail.com` on 30 Apr 2011 at 10:27
|
non_process
|
遇到执行错误，猜测是动态链接库出错 编译什么的都通过了，生成了可执行文件，比如说，测试使�� �的testecho，我使用ldd查看需要的动态库也都ok 但是启动时候 提示undefined symbol handlerfactory 一般怎么回事？ 不知道如何去查？ original issue reported on code google com by rock gmail com on apr at
| 0
|
780,959
| 27,416,183,249
|
IssuesEvent
|
2023-03-01 13:56:54
|
vaticle/typedb-client-rust
|
https://api.github.com/repos/vaticle/typedb-client-rust
|
closed
|
Session pulse (prevent open sessions from timing out)
|
priority: high type: bug
|
Session pulses are not yet implemented, so sessions will time out if they are left open (but inactive) for too long.
## Architectural Notes
We use a naive approach in Client Java currently. On creating a Session, we spawn a `TimerTask` that "ticks" every 5 seconds, sending a `session_pulse` request on each tick. The task gets shut down when the session is closed.
For now, the same approach is fine for Client Rust. In the future, we're going to refactor the protocol from a _session pulse_ into a single _client pulse_. This should simplify our code, and dramatically reduce the number of pulse tasks that would ever be active (from N to 1, where N is the number of open sessions)
|
1.0
|
Session pulse (prevent open sessions from timing out) - Session pulses are not yet implemented, so sessions will time out if they are left open (but inactive) for too long.
## Architectural Notes
We use a naive approach in Client Java currently. On creating a Session, we spawn a `TimerTask` that "ticks" every 5 seconds, sending a `session_pulse` request on each tick. The task gets shut down when the session is closed.
For now, the same approach is fine for Client Rust. In the future, we're going to refactor the protocol from a _session pulse_ into a single _client pulse_. This should simplify our code, and dramatically reduce the number of pulse tasks that would ever be active (from N to 1, where N is the number of open sessions)
|
non_process
|
session pulse prevent open sessions from timing out session pulses are not yet implemented so sessions will time out if they are left open but inactive for too long architectural notes we use a naive approach in client java currently on creating a session we spawn a timertask that ticks every seconds sending a session pulse request on each tick the task gets shut down when the session is closed for now the same approach is fine for client rust in the future we re going to refactor the protocol from a session pulse into a single client pulse this should simplify our code and dramatically reduce the number of pulse tasks that would ever be active from n to where n is the number of open sessions
| 0
|
447,641
| 12,891,195,271
|
IssuesEvent
|
2020-07-13 17:17:44
|
kubernetes/website
|
https://api.github.com/repos/kubernetes/website
|
closed
|
Investigate removing MaterialIcons
|
help wanted kind/cleanup priority/important-longterm
|
Umbrella issue: https://github.com/kubernetes/website/issues/22024
Investigate removing variants of MaterialIcons in `/static/fonts`.
We don't appear to use or call these files anywhere but `static/css/style_user_journeys.css`. This stylesheet isn't used now either, so I'd suggest deleting it as well.
|
1.0
|
Investigate removing MaterialIcons - Umbrella issue: https://github.com/kubernetes/website/issues/22024
Investigate removing variants of MaterialIcons in `/static/fonts`.
We don't appear to use or call these files anywhere but `static/css/style_user_journeys.css`. This stylesheet isn't used now either, so I'd suggest deleting it as well.
|
non_process
|
investigate removing materialicons umbrella issue investigate removing variants of materialicons in static fonts we don t appear to use or call these files anywhere but static css style user journeys css this stylesheet isn t used now either so i d suggest deleting it as well
| 0
|
10,832
| 13,615,611,067
|
IssuesEvent
|
2020-09-23 14:39:00
|
ORNL-AMO/AMO-Tools-Desktop
|
https://api.github.com/repos/ORNL-AMO/AMO-Tools-Desktop
|
closed
|
Upgrade to EAF algorithm
|
Process Heating enhancement important v0.7.1-release
|
What we want...
User enters "Electricity Input" in the "Energy Input" page.
This is used to calculate "Exhaust Gas Loss" (instead of calculator)
Exhaust Gas Loss = Energy Input Total - sum (all losses)
IF user enters an Exhaust Gas Loss, then modify "Other Losses"
"Other Losses" = "Other Losses form total" + Energy Input Total - sum (all losses)
On Exhaust Gas page, before the user clicks "Add Loss" show message
`This can be automatically estimated from your total energy input or estimated from data relating to your exhaust gas`
On Energy Input page. Change help text for * page * to...
`The data entered on this page is used to estimate the total energy input into the system. If data regarding the system's exhaust gas is not known, this is also used to estimate exhaust gas losses after all other losses are estimated.`
In case it isn't already, Energy Input is a required calculator.
ORIGINAL - IGNORE THIS ------
* Remove page for exhaust gas (users will rarely know this data very well, data collection is very expensive)
* Actually use input for electrical energy
Know energy inputs (electrical input + chemical inputs)
Know MOST losses (except exhaust)
Exhaust losses = sum(inputs) - sum(charge + other losses)
|
1.0
|
Upgrade to EAF algorithm - What we want...
User enters "Electricity Input" in the "Energy Input" page.
This is used to calculate "Exhaust Gas Loss" (instead of calculator)
Exhaust Gas Loss = Energy Input Total - sum (all losses)
IF user enters an Exhaust Gas Loss, then modify "Other Losses"
"Other Losses" = "Other Losses form total" + Energy Input Total - sum (all losses)
On Exhaust Gas page, before the user clicks "Add Loss" show message
`This can be automatically estimated from your total energy input or estimated from data relating to your exhaust gas`
On Energy Input page. Change help text for * page * to...
`The data entered on this page is used to estimate the total energy input into the system. If data regarding the system's exhaust gas is not known, this is also used to estimate exhaust gas losses after all other losses are estimated.`
In case it isn't already, Energy Input is a required calculator.
ORIGINAL - IGNORE THIS ------
* Remove page for exhaust gas (users will rarely know this data very well, data collection is very expensive)
* Actually use input for electrical energy
Know energy inputs (electrical input + chemical inputs)
Know MOST losses (except exhaust)
Exhaust losses = sum(inputs) - sum(charge + other losses)
|
process
|
upgrade to eaf algorithm what we want user enters electricity input in the energy input page this is used to calculate exhaust gas loss instead of calculator exhaust gas loss energy input total sum all losses if user enters an exhaust gas loss then modify other losses other losses other losses form total energy input total sum all losses on exhaust gas page before the user clicks add loss show message this can be automatically estimated from your total energy input or estimated from data relating to your exhaust gas on energy input page change help text for page to the data entered on this page is used to estimate the total energy input into the system if data regarding the system s exhaust gas is not known this is also used to estimate exhaust gas losses after all other losses are estimated in case it isn t already energy input is a required calculator original ignore this remove page for exhaust gas users will rarely know this data very well data collection is very expensive actually use input for electrical energy know energy inputs electrical input chemical inputs know most losses except exhaust exhaust losses sum inputs sum charge other losses
| 1
|
3,653
| 6,691,117,800
|
IssuesEvent
|
2017-10-09 11:56:57
|
inasafe/inasafe
|
https://api.github.com/repos/inasafe/inasafe
|
closed
|
Feature rate - post processor
|
Feature request Postprocessing
|
Some thoughts on the feature rate concept.
As well as asking users in the key words which field has the feature rate, should we also ask them the units that apply to the rate ie m2 or hectares or km 2
We should also consider that it may tke 2 fields to determine the value of something
eg in landcover there may be more than one rate one for yield in tonnes per hectare and one for crop value in currency per tonne
@fredychandra @Gustry @samnawi @timlinux
|
1.0
|
Feature rate - post processor - Some thoughts on the feature rate concept.
As well as asking users in the key words which field has the feature rate, should we also ask them the units that apply to the rate ie m2 or hectares or km 2
We should also consider that it may tke 2 fields to determine the value of something
eg in landcover there may be more than one rate one for yield in tonnes per hectare and one for crop value in currency per tonne
@fredychandra @Gustry @samnawi @timlinux
|
process
|
feature rate post processor some thoughts on the feature rate concept as well as asking users in the key words which field has the feature rate should we also ask them the units that apply to the rate ie or hectares or km we should also consider that it may tke fields to determine the value of something eg in landcover there may be more than one rate one for yield in tonnes per hectare and one for crop value in currency per tonne fredychandra gustry samnawi timlinux
| 1
|
19,948
| 26,421,908,999
|
IssuesEvent
|
2023-01-13 21:28:14
|
rusefi/rusefi_documentation
|
https://api.github.com/repos/rusefi/rusefi_documentation
|
closed
|
[Proposal] make "master" a protected branch to enforce update via PRs only
|
IMPORTANT wiki location & process change waiting-on-feedback
|
I'd recommend to enforce certain workflows for "master" branch via "protection rules"- Possible "protection rules" such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.
How to is documented in (https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)
Background:
every member of doc-team has "merge" permission and can push to "master" branch unintentionally.
|
1.0
|
[Proposal] make "master" a protected branch to enforce update via PRs only - I'd recommend to enforce certain workflows for "master" branch via "protection rules"- Possible "protection rules" such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.
How to is documented in (https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)
Background:
every member of doc-team has "merge" permission and can push to "master" branch unintentionally.
|
process
|
make master a protected branch to enforce update via prs only i d recommend to enforce certain workflows for master branch via protection rules possible protection rules such as requiring an approving review or passing status checks for all pull requests merged into the protected branch how to is documented in background every member of doc team has merge permission and can push to master branch unintentionally
| 1
|
317
| 2,522,820,741
|
IssuesEvent
|
2015-01-20 02:28:19
|
frace/git-passport
|
https://api.github.com/repos/frace/git-passport
|
closed
|
Possibly merge config_read() and config_validate()
|
code review enhancement
|
> I'd get rid of the config_validate function and do that in config_read instead, using a separate config_read_passport or so, which then uses ConfigParser.getboolean and the other get... functions with a very strict schema, so you make sure that everything coming out of the config object is properly parsed. That way you have to write less verification code (as the ConfigParser object takes care of that for you) and you can spend that on making sure that the individual passports have the correct format before handing them off to the rest of the application.
Reference: http://codereview.stackexchange.com/a/77176
@Ferada
Do you talk about to define `config_validate()` as an inner function of `config_read()`?
Possibly would it make sense to transform `config_validate()` into a decorator function which then is used to decorate `config_read()`?
|
1.0
|
Possibly merge config_read() and config_validate() - > I'd get rid of the config_validate function and do that in config_read instead, using a separate config_read_passport or so, which then uses ConfigParser.getboolean and the other get... functions with a very strict schema, so you make sure that everything coming out of the config object is properly parsed. That way you have to write less verification code (as the ConfigParser object takes care of that for you) and you can spend that on making sure that the individual passports have the correct format before handing them off to the rest of the application.
Reference: http://codereview.stackexchange.com/a/77176
@Ferada
Do you talk about to define `config_validate()` as an inner function of `config_read()`?
Possibly would it make sense to transform `config_validate()` into a decorator function which then is used to decorate `config_read()`?
|
non_process
|
possibly merge config read and config validate i d get rid of the config validate function and do that in config read instead using a separate config read passport or so which then uses configparser getboolean and the other get functions with a very strict schema so you make sure that everything coming out of the config object is properly parsed that way you have to write less verification code as the configparser object takes care of that for you and you can spend that on making sure that the individual passports have the correct format before handing them off to the rest of the application reference ferada do you talk about to define config validate as an inner function of config read possibly would it make sense to transform config validate into a decorator function which then is used to decorate config read
| 0
|
59,005
| 16,997,804,754
|
IssuesEvent
|
2021-07-01 08:45:55
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
opened
|
RoomDirectory: can't access property "trim", this.state.filterString is null
|
T-Defect
|
### Description
```
can't access property "trim", this.state.filterString is null
RoomDirectory.tsx:413
```
### Steps to reproduce
0. Be logged into Element Web.
1. Open "Explore rooms".
2. Type anything into the search. (This search term must not have any results on the server you switch to in step 3!)
3. Change the server in the Server dropdown.
4. Click the red X in the search term input.
Describe how what happens differs from what you expected.
A JavaScript error occurs and the "Explore rooms" modal closes itself.
<!-- Please send us logs for your bug report. They're very important for bugs
which are hard to reproduce. To do this, create this issue then go to your
account settings and click 'Submit Debug Logs' from the Help & About tab -->
Logs being sent: yes
<!-- Include screenshots if possible: you can drag and drop images below. -->
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: web
For the web app:
- **Browser**: Mozilla Firefox Dev Edition 90.0b4
- **OS**: Manjaro Linux (Arch repo)
- **URL**: staging.element.io 1.7.32-rc.1
|
1.0
|
RoomDirectory: can't access property "trim", this.state.filterString is null - ### Description
```
can't access property "trim", this.state.filterString is null
RoomDirectory.tsx:413
```
### Steps to reproduce
0. Be logged into Element Web.
1. Open "Explore rooms".
2. Type anything into the search. (This search term must not have any results on the server you switch to in step 3!)
3. Change the server in the Server dropdown.
4. Click the red X in the search term input.
Describe how what happens differs from what you expected.
A JavaScript error occurs and the "Explore rooms" modal closes itself.
<!-- Please send us logs for your bug report. They're very important for bugs
which are hard to reproduce. To do this, create this issue then go to your
account settings and click 'Submit Debug Logs' from the Help & About tab -->
Logs being sent: yes
<!-- Include screenshots if possible: you can drag and drop images below. -->
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: web
For the web app:
- **Browser**: Mozilla Firefox Dev Edition 90.0b4
- **OS**: Manjaro Linux (Arch repo)
- **URL**: staging.element.io 1.7.32-rc.1
|
non_process
|
roomdirectory can t access property trim this state filterstring is null description can t access property trim this state filterstring is null roomdirectory tsx steps to reproduce be logged into element web open explore rooms type anything into the search this search term must not have any results on the server you switch to in step change the server in the server dropdown click the red x in the search term input describe how what happens differs from what you expected a javascript error occurs and the explore rooms modal closes itself please send us logs for your bug report they re very important for bugs which are hard to reproduce to do this create this issue then go to your account settings and click submit debug logs from the help about tab logs being sent yes version information platform web for the web app browser mozilla firefox dev edition os manjaro linux arch repo url staging element io rc
| 0
|
28,787
| 13,807,084,763
|
IssuesEvent
|
2020-10-11 20:26:22
|
nielsmaerten/peppermint
|
https://api.github.com/repos/nielsmaerten/peppermint
|
closed
|
Redundant DB call
|
enhancement performance
|
https://github.com/nielsmaerten/peppermint/blob/bd50c1b12e5b12a81b139916f9efebabc4f1cf0f/src/agents/maintenance.ts#L117
This call to Firebase for the token is not necessary!
Thee token is already available in `this.user`
|
True
|
Redundant DB call - https://github.com/nielsmaerten/peppermint/blob/bd50c1b12e5b12a81b139916f9efebabc4f1cf0f/src/agents/maintenance.ts#L117
This call to Firebase for the token is not necessary!
Thee token is already available in `this.user`
|
non_process
|
redundant db call this call to firebase for the token is not necessary thee token is already available in this user
| 0
|
12,848
| 3,293,312,904
|
IssuesEvent
|
2015-10-30 18:21:35
|
DeKugelschieber/asl
|
https://api.github.com/repos/DeKugelschieber/asl
|
opened
|
Better error output
|
enhancement feature test
|
Add line number and column to the error output.
Do not panic on parse errors!
|
1.0
|
Better error output - Add line number and column to the error output.
Do not panic on parse errors!
|
non_process
|
better error output add line number and column to the error output do not panic on parse errors
| 0
|
19,445
| 25,719,697,374
|
IssuesEvent
|
2022-12-07 12:52:28
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Different behavior when pressing the back button in the processing tools.
|
Feedback Processing GUI/UX Bug
|
### What is the bug or the crash?
When you press the back button in the processing tools of different tools, their behavior is different.
For example:
1. In the `Merge` tool, pressing the back button saves the changes you made.
2. In the tool `Reclassify by table` pressing the back button does NOT save the changes made.
It is suggested to unify the behavior when pressing this button (save everywhere or not save everywhere).
See this [mp4 video ](https://user-images.githubusercontent.com/20655102/156310697-974ccfcf-60aa-4def-ae89-0263e3cf6e1e.mp4) as example of different behavior (Don't open in a browser, download to your local drive).
### Steps to reproduce the issue
1. Open the `Merge` tool.
2. Set any parameters of the `Input layers` and press `back` (the changes will be saved).
3. Open the `Reclassification by table` tool.
2. Set any parameters of the `Table Reclassification` and press `back` (the changes will NOT be saved).
### Versions
<!--StartFragment--><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body>
QGIS version | 3.24.0-Tisler | QGIS code revision | 6b44a42058
-- | -- | -- | --
Qt version | 5.15.2
Python version | 3.9.5
GDAL/OGR version | 3.4.1
PROJ version | 8.2.1
EPSG Registry database version | v10.041 (2021-12-03)
GEOS version | 3.10.2-CAPI-1.16.0
SQLite version | 3.37.2
PDAL version | 2.3.0
PostgreSQL client version | unknown
SpatiaLite version | 5.0.1
QWT version | 6.1.3
QScintilla2 version | 2.11.5
OS version | Windows 10 Version 2009
| | |
Active Python plugins
AppendFeaturesToLayer | 1.2.0
DigitizingTools | 1.5.1
Go2NextFeature3 | 2.1
latlontools | 3.6.2
loadthemall | 3.3.0
MapsPrinter | 0.9
PluginLoadTimes | 3.0.1
qgsAzimuth | 0.9.15
rasterstats | 0.4.3
valuetool | 3.0.15
db_manager | 0.1.20
grassprovider | 2.12.99
MetaSearch | 0.3.6
otbprovider | 2.12.99
processing | 2.12.99
</body></html><!--EndFragment-->QGIS version
3.24.0-Tisler
QGIS code revision
[6b44a42058](https://github.com/qgis/QGIS/commit/6b44a42058)
Qt version
5.15.2
Python version
3.9.5
GDAL/OGR version
3.4.1
PROJ version
8.2.1
EPSG Registry database version
v10.041 (2021-12-03)
GEOS version
3.10.2-CAPI-1.16.0
SQLite version
3.37.2
PDAL version
2.3.0
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.3
QScintilla2 version
2.11.5
OS version
Windows 10 Version 2009
Active Python plugins
AppendFeaturesToLayer
1.2.0
DigitizingTools
1.5.1
Go2NextFeature3
2.1
latlontools
3.6.2
loadthemall
3.3.0
MapsPrinter
0.9
PluginLoadTimes
3.0.1
qgsAzimuth
0.9.15
rasterstats
0.4.3
valuetool
3.0.15
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
otbprovider
2.12.99
processing
2.12.99
### Supported QGIS version
- [X] I'm running a supported QGIS version according to the roadmap.
### New profile
- [x] I tried with a new QGIS profile
### Additional context
_No response_
|
1.0
|
Different behavior when pressing the back button in the processing tools. - ### What is the bug or the crash?
When you press the back button in the processing tools of different tools, their behavior is different.
For example:
1. In the `Merge` tool, pressing the back button saves the changes you made.
2. In the tool `Reclassify by table` pressing the back button does NOT save the changes made.
It is suggested to unify the behavior when pressing this button (save everywhere or not save everywhere).
See this [mp4 video ](https://user-images.githubusercontent.com/20655102/156310697-974ccfcf-60aa-4def-ae89-0263e3cf6e1e.mp4) as example of different behavior (Don't open in a browser, download to your local drive).
### Steps to reproduce the issue
1. Open the `Merge` tool.
2. Set any parameters of the `Input layers` and press `back` (the changes will be saved).
3. Open the `Reclassification by table` tool.
2. Set any parameters of the `Table Reclassification` and press `back` (the changes will NOT be saved).
### Versions
<!--StartFragment--><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body>
QGIS version | 3.24.0-Tisler | QGIS code revision | 6b44a42058
-- | -- | -- | --
Qt version | 5.15.2
Python version | 3.9.5
GDAL/OGR version | 3.4.1
PROJ version | 8.2.1
EPSG Registry database version | v10.041 (2021-12-03)
GEOS version | 3.10.2-CAPI-1.16.0
SQLite version | 3.37.2
PDAL version | 2.3.0
PostgreSQL client version | unknown
SpatiaLite version | 5.0.1
QWT version | 6.1.3
QScintilla2 version | 2.11.5
OS version | Windows 10 Version 2009
| | |
Active Python plugins
AppendFeaturesToLayer | 1.2.0
DigitizingTools | 1.5.1
Go2NextFeature3 | 2.1
latlontools | 3.6.2
loadthemall | 3.3.0
MapsPrinter | 0.9
PluginLoadTimes | 3.0.1
qgsAzimuth | 0.9.15
rasterstats | 0.4.3
valuetool | 3.0.15
db_manager | 0.1.20
grassprovider | 2.12.99
MetaSearch | 0.3.6
otbprovider | 2.12.99
processing | 2.12.99
</body></html><!--EndFragment-->QGIS version
3.24.0-Tisler
QGIS code revision
[6b44a42058](https://github.com/qgis/QGIS/commit/6b44a42058)
Qt version
5.15.2
Python version
3.9.5
GDAL/OGR version
3.4.1
PROJ version
8.2.1
EPSG Registry database version
v10.041 (2021-12-03)
GEOS version
3.10.2-CAPI-1.16.0
SQLite version
3.37.2
PDAL version
2.3.0
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.3
QScintilla2 version
2.11.5
OS version
Windows 10 Version 2009
Active Python plugins
AppendFeaturesToLayer
1.2.0
DigitizingTools
1.5.1
Go2NextFeature3
2.1
latlontools
3.6.2
loadthemall
3.3.0
MapsPrinter
0.9
PluginLoadTimes
3.0.1
qgsAzimuth
0.9.15
rasterstats
0.4.3
valuetool
3.0.15
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
otbprovider
2.12.99
processing
2.12.99
### Supported QGIS version
- [X] I'm running a supported QGIS version according to the roadmap.
### New profile
- [x] I tried with a new QGIS profile
### Additional context
_No response_
|
process
|
different behavior when pressing the back button in the processing tools what is the bug or the crash when you press the back button in the processing tools of different tools their behavior is different for example in the merge tool pressing the back button saves the changes you made in the tool reclassify by table pressing the back button does not save the changes made it is suggested to unify the behavior when pressing this button save everywhere or not save everywhere see this as example of different behavior don t open in a browser download to your local drive steps to reproduce the issue open the merge tool set any parameters of the input layers and press back the changes will be saved open the reclassification by table tool set any parameters of the table reclassification and press back the changes will not be saved versions doctype html public dtd html en p li white space pre wrap qgis version tisler qgis code revision qt version python version gdal ogr version proj version epsg registry database version geos version capi sqlite version pdal version postgresql client version unknown spatialite version qwt version version os version windows version active python plugins appendfeaturestolayer digitizingtools latlontools loadthemall mapsprinter pluginloadtimes qgsazimuth rasterstats valuetool db manager grassprovider metasearch otbprovider processing qgis version tisler qgis code revision qt version python version gdal ogr version proj version epsg registry database version geos version capi sqlite version pdal version postgresql client version unknown spatialite version qwt version version os version windows version active python plugins appendfeaturestolayer digitizingtools latlontools loadthemall mapsprinter pluginloadtimes qgsazimuth rasterstats valuetool db manager grassprovider metasearch otbprovider processing supported qgis version i m running a supported qgis version according to the roadmap new profile i tried with a new qgis profile additional context no response
| 1
|
13,527
| 16,060,888,697
|
IssuesEvent
|
2021-04-23 12:24:19
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[PM] Security testing > Alerts found in Participant manager application
|
Bug P1 Participant manager datastore Process: Fixed Unknown backend
|
Alerts found in Participant manager application as part of security testing.
Summary of Alerts
Risk Level | No. of alerts
-- | --
High | 0
Medium | 8
Low | 9
Informational | 7
Please find attached report for detailed summary of alerts including probable solution
[PM_SecurityReport.pdf](https://github.com/GoogleCloudPlatform/fda-mystudies/files/5754469/PM_SecurityReport.pdf)
|
1.0
|
[PM] Security testing > Alerts found in Participant manager application - Alerts found in Participant manager application as part of security testing.
Summary of Alerts
Risk Level | No. of alerts
-- | --
High | 0
Medium | 8
Low | 9
Informational | 7
Please find attached report for detailed summary of alerts including probable solution
[PM_SecurityReport.pdf](https://github.com/GoogleCloudPlatform/fda-mystudies/files/5754469/PM_SecurityReport.pdf)
|
process
|
security testing alerts found in participant manager application alerts found in participant manager application as part of security testing summary of alerts risk level no of alerts high medium low informational please find attached report for detailed summary of alerts including probable solution
| 1
|
10,749
| 27,387,537,294
|
IssuesEvent
|
2023-02-28 14:17:54
|
splendo/kaluga
|
https://api.github.com/repos/splendo/kaluga
|
closed
|
Improve Compose ViewModel architecture
|
🤖android component:architecture 1.0.0
|
Our current implementation of lifecycle for Compose only works if no configuration changes occur, since our storeAndRemember method will not retain a viewModel after configuration changes.
Instead, we should defer VM creation to proper viewModelFactories/Koin and extend our ViewModelComposable method to handle retaining data. This will have an impact on some composable components, most importantly navigation. Navigation should be rewritten so a navigator can be restored on configuration changes as well.
|
1.0
|
Improve Compose ViewModel architecture - Our current implementation of lifecycle for Compose only works if no configuration changes occur, since our storeAndRemember method will not retain a viewModel after configuration changes.
Instead, we should defer VM creation to proper viewModelFactories/Koin and extend our ViewModelComposable method to handle retaining data. This will have an impact on some composable components, most importantly navigation. Navigation should be rewritten so a navigator can be restored on configuration changes as well.
|
non_process
|
improve compose viewmodel architecture our current implementation of lifecycle for compose only works if no configuration changes occur since our storeandremember method will not retain a viewmodel after configuration changes instead we should defer vm creation to proper viewmodelfactories koin and extend our viewmodelcomposable method to handle retaining data this will have an impact on some composable components most importantly navigation navigation should be rewritten so a navigator can be restored on configuration changes as well
| 0
|
18,134
| 24,175,659,491
|
IssuesEvent
|
2022-09-23 01:10:28
|
oxidecomputer/hubris
|
https://api.github.com/repos/oxidecomputer/hubris
|
closed
|
Gimlet SP shouldn't stop pay attention to SP3_TO_SP_NIC_PWREN_L
|
service processor product
|
Currently the `gimlet_seq` server pays attention to the `SP3_TO_SP_NIC_PWREN_L`to go from high to low while in the A0 state. When this happens, the SP does the following:
* Transitions to the A0+HP state
* Clears the Sequencer `NIC_CTRL` bit
After the system enters A0+HP state in the sequencer, it does not pay attention to any other changes here. This is a problem as part of the manufacturing mode to mission mode transition requires us to put the NIC back into reset to allow the GPIO change to take effect. Instead, we need to always pay attention to this transition, regardless of whether we're in A0 or A0+HP. If this is deasserted (e.g. transitions high) then we need to go back and set the appropriate bit again in `NIC_CTRL`.
|
1.0
|
Gimlet SP shouldn't stop pay attention to SP3_TO_SP_NIC_PWREN_L - Currently the `gimlet_seq` server pays attention to the `SP3_TO_SP_NIC_PWREN_L`to go from high to low while in the A0 state. When this happens, the SP does the following:
* Transitions to the A0+HP state
* Clears the Sequencer `NIC_CTRL` bit
After the system enters A0+HP state in the sequencer, it does not pay attention to any other changes here. This is a problem as part of the manufacturing mode to mission mode transition requires us to put the NIC back into reset to allow the GPIO change to take effect. Instead, we need to always pay attention to this transition, regardless of whether we're in A0 or A0+HP. If this is deasserted (e.g. transitions high) then we need to go back and set the appropriate bit again in `NIC_CTRL`.
|
process
|
gimlet sp shouldn t stop pay attention to to sp nic pwren l currently the gimlet seq server pays attention to the to sp nic pwren l to go from high to low while in the state when this happens the sp does the following transitions to the hp state clears the sequencer nic ctrl bit after the system enters hp state in the sequencer it does not pay attention to any other changes here this is a problem as part of the manufacturing mode to mission mode transition requires us to put the nic back into reset to allow the gpio change to take effect instead we need to always pay attention to this transition regardless of whether we re in or hp if this is deasserted e g transitions high then we need to go back and set the appropriate bit again in nic ctrl
| 1
|
105,532
| 16,652,752,559
|
IssuesEvent
|
2021-06-05 01:10:56
|
shantanujhalt/material-ui
|
https://api.github.com/repos/shantanujhalt/material-ui
|
opened
|
CVE-2020-28469 (Medium) detected in glob-parent-3.1.0.tgz, glob-parent-5.1.1.tgz
|
security vulnerability
|
## CVE-2020-28469 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-3.1.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: material-ui/node_modules/glob-parent/package.json</p>
<p>Path to vulnerable library: material-ui/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- cpy-cli-3.1.1.tgz (Root Library)
- cpy-8.1.1.tgz
- globby-9.2.0.tgz
- fast-glob-2.2.7.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: material-ui/node_modules/glob-parent/package.json</p>
<p>Path to vulnerable library: material-ui/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- link-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
<p>Publish Date: 2021-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469>CVE-2020-28469</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.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-2020-28469 (Medium) detected in glob-parent-3.1.0.tgz, glob-parent-5.1.1.tgz - ## CVE-2020-28469 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-3.1.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: material-ui/node_modules/glob-parent/package.json</p>
<p>Path to vulnerable library: material-ui/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- cpy-cli-3.1.1.tgz (Root Library)
- cpy-8.1.1.tgz
- globby-9.2.0.tgz
- fast-glob-2.2.7.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: material-ui/node_modules/glob-parent/package.json</p>
<p>Path to vulnerable library: material-ui/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- link-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
<p>Publish Date: 2021-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469>CVE-2020-28469</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in glob parent tgz glob parent tgz cve medium severity vulnerability vulnerable libraries glob parent tgz glob parent tgz glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file material ui node modules glob parent package json path to vulnerable library material ui node modules glob parent package json dependency hierarchy cpy cli tgz root library cpy tgz globby tgz fast glob tgz x glob parent tgz vulnerable library glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file material ui node modules glob parent package json path to vulnerable library material ui node modules glob parent package json dependency hierarchy lerna tgz root library link tgz command tgz project tgz x glob parent tgz vulnerable library found in base branch next vulnerability details this affects the package glob parent before the enclosure regex used to check for strings ending in enclosure containing path separator 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 glob parent step up your open source security game with whitesource
| 0
|
13,231
| 15,702,924,828
|
IssuesEvent
|
2021-03-26 13:15:44
|
ORNL-AMO/AMO-Tools-Desktop
|
https://api.github.com/repos/ORNL-AMO/AMO-Tools-Desktop
|
opened
|
Process Cooling Calc Overview
|
Calculator Process Cooling
|
Ideally, we would like these to run two ways
1 - single instant (fill out all the forms and get a single answer)
2 - annual aggregate: use bin analysis ("weather calculator" - lump together all the hours in the year that is is between two temps/ humiditys/etc and use the "bin range" to fill out the form (40 - 50 F --> T = 45 & the hours that are in that range = ophrs) then sum those all up to get annual savings
Right now the example calculators and I think the algo (and I fairly certain the C++) all work in the spirit of # 1.
IDK if we want to do the aggregating in the suite (as another "calculator" that gets called) or in the desktop. Depends on computation time and ease of developing.
Also, the Weather binning calculator needs to be working
Anyway, something to think about and discuss
|
1.0
|
Process Cooling Calc Overview - Ideally, we would like these to run two ways
1 - single instant (fill out all the forms and get a single answer)
2 - annual aggregate: use bin analysis ("weather calculator" - lump together all the hours in the year that is is between two temps/ humiditys/etc and use the "bin range" to fill out the form (40 - 50 F --> T = 45 & the hours that are in that range = ophrs) then sum those all up to get annual savings
Right now the example calculators and I think the algo (and I fairly certain the C++) all work in the spirit of # 1.
IDK if we want to do the aggregating in the suite (as another "calculator" that gets called) or in the desktop. Depends on computation time and ease of developing.
Also, the Weather binning calculator needs to be working
Anyway, something to think about and discuss
|
process
|
process cooling calc overview ideally we would like these to run two ways single instant fill out all the forms and get a single answer annual aggregate use bin analysis weather calculator lump together all the hours in the year that is is between two temps humiditys etc and use the bin range to fill out the form f t the hours that are in that range ophrs then sum those all up to get annual savings right now the example calculators and i think the algo and i fairly certain the c all work in the spirit of idk if we want to do the aggregating in the suite as another calculator that gets called or in the desktop depends on computation time and ease of developing also the weather binning calculator needs to be working anyway something to think about and discuss
| 1
|
334,228
| 24,409,600,196
|
IssuesEvent
|
2022-10-05 11:08:03
|
ued123/modeling
|
https://api.github.com/repos/ued123/modeling
|
closed
|
테스트 프레임워크 검토 - spock
|
documentation enhancement feature
|
## 요약
### ~~Junit~~
- 간단한 결과를 반환하는 단위 테스트에서는 사용하기 편함
- 기능이 복잡한 경우, 테스트 케이스가 많아지면 상당한 작업시간이 소요된다
- 테스트 케이스가 많아지면 명세를 하는데 상당한 고민을 할수가 있다.
### ~~Cucumber~~
- BDD 기반 프레임워크고 통합 테스트에서 많이 사용한다. 현 프로젝트는 단위 테스트 기반이기 떄문에 어울리지 않는다.
- BDD 조건의 시나리오 파일을 관리해야하고, 파일에 설정과 테스트 클래스 매핑하는 작업이 필요하기 떄문에 시간 소모가 크다.
### Spock
- BDD 기반 프레임워크
- 단위 테스트 내에서도 BDD 시나리오를 작성할수 있기 떄문에, 관리가 수월하다.
|
1.0
|
테스트 프레임워크 검토 - spock - ## 요약
### ~~Junit~~
- 간단한 결과를 반환하는 단위 테스트에서는 사용하기 편함
- 기능이 복잡한 경우, 테스트 케이스가 많아지면 상당한 작업시간이 소요된다
- 테스트 케이스가 많아지면 명세를 하는데 상당한 고민을 할수가 있다.
### ~~Cucumber~~
- BDD 기반 프레임워크고 통합 테스트에서 많이 사용한다. 현 프로젝트는 단위 테스트 기반이기 떄문에 어울리지 않는다.
- BDD 조건의 시나리오 파일을 관리해야하고, 파일에 설정과 테스트 클래스 매핑하는 작업이 필요하기 떄문에 시간 소모가 크다.
### Spock
- BDD 기반 프레임워크
- 단위 테스트 내에서도 BDD 시나리오를 작성할수 있기 떄문에, 관리가 수월하다.
|
non_process
|
테스트 프레임워크 검토 spock 요약 junit 간단한 결과를 반환하는 단위 테스트에서는 사용하기 편함 기능이 복잡한 경우 테스트 케이스가 많아지면 상당한 작업시간이 소요된다 테스트 케이스가 많아지면 명세를 하는데 상당한 고민을 할수가 있다 cucumber bdd 기반 프레임워크고 통합 테스트에서 많이 사용한다 현 프로젝트는 단위 테스트 기반이기 떄문에 어울리지 않는다 bdd 조건의 시나리오 파일을 관리해야하고 파일에 설정과 테스트 클래스 매핑하는 작업이 필요하기 떄문에 시간 소모가 크다 spock bdd 기반 프레임워크 단위 테스트 내에서도 bdd 시나리오를 작성할수 있기 떄문에 관리가 수월하다
| 0
|
27,422
| 21,706,908,803
|
IssuesEvent
|
2022-05-10 10:26:02
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Compose the shared framework without depending on OOB libraries
|
area-Infrastructure-libraries
|
Part of the shared framework are shims, generated and manual ones. The [generated shims require all reference assemblies](https://github.com/dotnet/runtime/blob/bb3cf17981b506d22be5b8e1f06084c958372e1d/src/libraries/shims/generated/Directory.Build.props#L32-L36) (both inbox and OOB ones) as an input whereas the [manual shims require all implementation assemblies](https://github.com/dotnet/runtime/blob/bb3cf17981b506d22be5b8e1f06084c958372e1d/src/libraries/shims/manual/Directory.Build.props#L19-L25) (again both inbox and OOB) as an input.
There are various reasons for a clear cut between the shared framework and OOB libraries:
1. Being able to build the shared framework is more often interesting than building OOBs (Microsoft.Extensions.* and Compat projects) for runtime developers.
2. Being able to just build the Microsoft.Extensions.* libraries incrementally and produce packages for them is more often interesting for developers that came from dotnet/extensions.
3. OOBs don't need to live next to the shared framework and could eventually be moved to another location.
cc @ericstj @safern @Anipik @jkotas
|
1.0
|
Compose the shared framework without depending on OOB libraries - Part of the shared framework are shims, generated and manual ones. The [generated shims require all reference assemblies](https://github.com/dotnet/runtime/blob/bb3cf17981b506d22be5b8e1f06084c958372e1d/src/libraries/shims/generated/Directory.Build.props#L32-L36) (both inbox and OOB ones) as an input whereas the [manual shims require all implementation assemblies](https://github.com/dotnet/runtime/blob/bb3cf17981b506d22be5b8e1f06084c958372e1d/src/libraries/shims/manual/Directory.Build.props#L19-L25) (again both inbox and OOB) as an input.
There are various reasons for a clear cut between the shared framework and OOB libraries:
1. Being able to build the shared framework is more often interesting than building OOBs (Microsoft.Extensions.* and Compat projects) for runtime developers.
2. Being able to just build the Microsoft.Extensions.* libraries incrementally and produce packages for them is more often interesting for developers that came from dotnet/extensions.
3. OOBs don't need to live next to the shared framework and could eventually be moved to another location.
cc @ericstj @safern @Anipik @jkotas
|
non_process
|
compose the shared framework without depending on oob libraries part of the shared framework are shims generated and manual ones the both inbox and oob ones as an input whereas the again both inbox and oob as an input there are various reasons for a clear cut between the shared framework and oob libraries being able to build the shared framework is more often interesting than building oobs microsoft extensions and compat projects for runtime developers being able to just build the microsoft extensions libraries incrementally and produce packages for them is more often interesting for developers that came from dotnet extensions oobs don t need to live next to the shared framework and could eventually be moved to another location cc ericstj safern anipik jkotas
| 0
|
8,712
| 11,851,973,569
|
IssuesEvent
|
2020-03-24 19:03:24
|
lukechu10/Minecraft-Box-Launcher
|
https://api.github.com/repos/lukechu10/Minecraft-Box-Launcher
|
closed
|
Identify instances using an uuid (v4)
|
enhancement renderer-process
|
Identify each instance with an uuid (v4, random) to simplify modifying renaming instances.
|
1.0
|
Identify instances using an uuid (v4) - Identify each instance with an uuid (v4, random) to simplify modifying renaming instances.
|
process
|
identify instances using an uuid identify each instance with an uuid random to simplify modifying renaming instances
| 1
|
117,605
| 25,157,981,767
|
IssuesEvent
|
2022-11-10 14:51:31
|
OD4RD/Main-Help-Desk
|
https://api.github.com/repos/OD4RD/Main-Help-Desk
|
opened
|
Obsolete ORPHAcodes: how to find them?
|
Lost code OrphaNomenclature Belgium
|
**Question received from a coder:**
"We need the list of obsolete Orpha 2021 codes if you have them, as well as the Excel table of Orpha 2020 codes (which I cannot find on the site).
Indeed, we need to do our reporting and extract our registered Orpha codes but there are some codes that no longer exist and that we can no longer make the correspondence since we no longer find their equivalent on Orphanet."
|
1.0
|
Obsolete ORPHAcodes: how to find them? - **Question received from a coder:**
"We need the list of obsolete Orpha 2021 codes if you have them, as well as the Excel table of Orpha 2020 codes (which I cannot find on the site).
Indeed, we need to do our reporting and extract our registered Orpha codes but there are some codes that no longer exist and that we can no longer make the correspondence since we no longer find their equivalent on Orphanet."
|
non_process
|
obsolete orphacodes how to find them question received from a coder we need the list of obsolete orpha codes if you have them as well as the excel table of orpha codes which i cannot find on the site indeed we need to do our reporting and extract our registered orpha codes but there are some codes that no longer exist and that we can no longer make the correspondence since we no longer find their equivalent on orphanet
| 0
|
84,260
| 7,904,601,348
|
IssuesEvent
|
2018-07-02 05:46:16
|
frappe/erpnext
|
https://api.github.com/repos/frappe/erpnext
|
closed
|
[v11] Leave Management
|
testing
|
- [x] Multiple Leave Types
- [ ] Optional Leave
- [ ] Earned Leave
- [ ] Parental Leave
- [x] Leave Period
- [x] Leave Policy
- [x] Leave Encashment
- [ ] Compensatory Leave
- [ ] Refactored Leave Application
- [ ] Approver based on department > patch
- [ ] Leave balance
|
1.0
|
[v11] Leave Management - - [x] Multiple Leave Types
- [ ] Optional Leave
- [ ] Earned Leave
- [ ] Parental Leave
- [x] Leave Period
- [x] Leave Policy
- [x] Leave Encashment
- [ ] Compensatory Leave
- [ ] Refactored Leave Application
- [ ] Approver based on department > patch
- [ ] Leave balance
|
non_process
|
leave management multiple leave types optional leave earned leave parental leave leave period leave policy leave encashment compensatory leave refactored leave application approver based on department patch leave balance
| 0
|
72,421
| 9,583,035,832
|
IssuesEvent
|
2019-05-08 03:27:28
|
moosefs/moosefs
|
https://api.github.com/repos/moosefs/moosefs
|
closed
|
[ASK] moosefs strightforward tutorial
|
community documentation question
|
hi, i'm new in distributed file system world, i wanna make a replication set + multi data center with moosefs, but i can't find strightforward tutorial for it, something like :
1. what i must do in master-server
2. what i must do in node server
3. where (the config file) and how to config master/node server
4. how other server (as client) can connect to moosefs service
5. how file path be arranged
6. more something like that
my server is ubuntu 16.04, thank you !
|
1.0
|
[ASK] moosefs strightforward tutorial - hi, i'm new in distributed file system world, i wanna make a replication set + multi data center with moosefs, but i can't find strightforward tutorial for it, something like :
1. what i must do in master-server
2. what i must do in node server
3. where (the config file) and how to config master/node server
4. how other server (as client) can connect to moosefs service
5. how file path be arranged
6. more something like that
my server is ubuntu 16.04, thank you !
|
non_process
|
moosefs strightforward tutorial hi i m new in distributed file system world i wanna make a replication set multi data center with moosefs but i can t find strightforward tutorial for it something like what i must do in master server what i must do in node server where the config file and how to config master node server how other server as client can connect to moosefs service how file path be arranged more something like that my server is ubuntu thank you
| 0
|
11,812
| 14,629,077,868
|
IssuesEvent
|
2020-12-23 15:14:47
|
ewen-lbh/portfolio
|
https://api.github.com/repos/ewen-lbh/portfolio
|
closed
|
Started and finished dates instead of created
|
processing
|
Still allow created as a shortcut for setting the finished date. Makes `wip:` obsolete, if there's a started date and not a finished date, it's wip.
|
1.0
|
Started and finished dates instead of created - Still allow created as a shortcut for setting the finished date. Makes `wip:` obsolete, if there's a started date and not a finished date, it's wip.
|
process
|
started and finished dates instead of created still allow created as a shortcut for setting the finished date makes wip obsolete if there s a started date and not a finished date it s wip
| 1
|
378,062
| 11,195,318,722
|
IssuesEvent
|
2020-01-03 05:52:37
|
wso2/product-apim
|
https://api.github.com/repos/wso2/product-apim
|
closed
|
Custom Mediation Policies get saved even without clicking the select button
|
3.0.0 3.1.0 Priority/Normal Type/React-UI Type/UX
|
1. Click edit button Message Mediation.
2. Upload the sequence file. Just after uploading the file is attached to the API. There is no use of the "Select" button of the UI dialog box.
|
1.0
|
Custom Mediation Policies get saved even without clicking the select button - 1. Click edit button Message Mediation.
2. Upload the sequence file. Just after uploading the file is attached to the API. There is no use of the "Select" button of the UI dialog box.
|
non_process
|
custom mediation policies get saved even without clicking the select button click edit button message mediation upload the sequence file just after uploading the file is attached to the api there is no use of the select button of the ui dialog box
| 0
|
14,761
| 18,041,446,487
|
IssuesEvent
|
2021-09-18 05:22:13
|
ooi-data/CE01ISSM-MFD35-06-PHSEND000-telemetered-phsen_abcdef_dcl_instrument
|
https://api.github.com/repos/ooi-data/CE01ISSM-MFD35-06-PHSEND000-telemetered-phsen_abcdef_dcl_instrument
|
opened
|
🛑 Processing failed: ResponseParserError
|
process
|
## Overview
`ResponseParserError` found in `processing_task` task during run ended on 2021-09-18T05:22:12.750077.
## Details
Flow name: `CE01ISSM-MFD35-06-PHSEND000-telemetered-phsen_abcdef_dcl_instrument`
Task name: `processing_task`
Error type: `ResponseParserError`
Error message: Unable to parse response (no element found: line 2, column 0), invalid XML received. Further retries may succeed:
b'<?xml version="1.0" encoding="UTF-8"?>\n'
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 452, in _parse_xml_string_to_dom
root = parser.close()
xml.etree.ElementTree.ParseError: no element found: line 2, column 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/ooi_harvester/processor/pipeline.py", line 101, in processing
final_path = finalize_zarr(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/ooi_harvester/processor/__init__.py", line 359, in finalize_zarr
source_store.fs.delete(source_store.root, recursive=True)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/spec.py", line 1187, in delete
return self.rm(path, recursive=recursive, maxdepth=maxdepth)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/asyn.py", line 88, in wrapper
return sync(self.loop, func, *args, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/asyn.py", line 69, in sync
raise result[0]
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/asyn.py", line 25, in _runner
result[0] = await coro
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 1677, in _rm
await asyncio.gather(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 1657, in _bulk_delete
await self._call_s3("delete_objects", kwargs, Bucket=bucket, Delete=delete_keys)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 268, in _call_s3
raise err
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 248, in _call_s3
out = await method(**additional_kwargs)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/client.py", line 141, in _make_api_call
http, parsed_response = await self._make_request(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/client.py", line 161, in _make_request
return await self._endpoint.make_request(operation_model, request_dict)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/endpoint.py", line 93, in _send_request
success_response, exception = await self._get_response(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/endpoint.py", line 112, in _get_response
success_response, exception = await self._do_get_response(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/endpoint.py", line 177, in _do_get_response
parsed_response = parser.parse(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 245, in parse
parsed = self._do_parse(response, shape)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 813, in _do_parse
self._add_modeled_parse(response, shape, final_parsed)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 822, in _add_modeled_parse
self._parse_payload(response, shape, member_shapes, final_parsed)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 862, in _parse_payload
original_parsed = self._initial_body_parse(response['body'])
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 948, in _initial_body_parse
return self._parse_xml_string_to_dom(xml_string)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 454, in _parse_xml_string_to_dom
raise ResponseParserError(
botocore.parsers.ResponseParserError: Unable to parse response (no element found: line 2, column 0), invalid XML received. Further retries may succeed:
b'<?xml version="1.0" encoding="UTF-8"?>\n'
```
</details>
|
1.0
|
🛑 Processing failed: ResponseParserError - ## Overview
`ResponseParserError` found in `processing_task` task during run ended on 2021-09-18T05:22:12.750077.
## Details
Flow name: `CE01ISSM-MFD35-06-PHSEND000-telemetered-phsen_abcdef_dcl_instrument`
Task name: `processing_task`
Error type: `ResponseParserError`
Error message: Unable to parse response (no element found: line 2, column 0), invalid XML received. Further retries may succeed:
b'<?xml version="1.0" encoding="UTF-8"?>\n'
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 452, in _parse_xml_string_to_dom
root = parser.close()
xml.etree.ElementTree.ParseError: no element found: line 2, column 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/ooi_harvester/processor/pipeline.py", line 101, in processing
final_path = finalize_zarr(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/ooi_harvester/processor/__init__.py", line 359, in finalize_zarr
source_store.fs.delete(source_store.root, recursive=True)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/spec.py", line 1187, in delete
return self.rm(path, recursive=recursive, maxdepth=maxdepth)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/asyn.py", line 88, in wrapper
return sync(self.loop, func, *args, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/asyn.py", line 69, in sync
raise result[0]
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/fsspec/asyn.py", line 25, in _runner
result[0] = await coro
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 1677, in _rm
await asyncio.gather(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 1657, in _bulk_delete
await self._call_s3("delete_objects", kwargs, Bucket=bucket, Delete=delete_keys)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 268, in _call_s3
raise err
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/s3fs/core.py", line 248, in _call_s3
out = await method(**additional_kwargs)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/client.py", line 141, in _make_api_call
http, parsed_response = await self._make_request(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/client.py", line 161, in _make_request
return await self._endpoint.make_request(operation_model, request_dict)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/endpoint.py", line 93, in _send_request
success_response, exception = await self._get_response(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/endpoint.py", line 112, in _get_response
success_response, exception = await self._do_get_response(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/aiobotocore/endpoint.py", line 177, in _do_get_response
parsed_response = parser.parse(
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 245, in parse
parsed = self._do_parse(response, shape)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 813, in _do_parse
self._add_modeled_parse(response, shape, final_parsed)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 822, in _add_modeled_parse
self._parse_payload(response, shape, member_shapes, final_parsed)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 862, in _parse_payload
original_parsed = self._initial_body_parse(response['body'])
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 948, in _initial_body_parse
return self._parse_xml_string_to_dom(xml_string)
File "/srv/conda/envs/notebook/lib/python3.8/site-packages/botocore/parsers.py", line 454, in _parse_xml_string_to_dom
raise ResponseParserError(
botocore.parsers.ResponseParserError: Unable to parse response (no element found: line 2, column 0), invalid XML received. Further retries may succeed:
b'<?xml version="1.0" encoding="UTF-8"?>\n'
```
</details>
|
process
|
🛑 processing failed responseparsererror overview responseparsererror found in processing task task during run ended on details flow name telemetered phsen abcdef dcl instrument task name processing task error type responseparsererror error message unable to parse response no element found line column invalid xml received further retries may succeed b n traceback traceback most recent call last file srv conda envs notebook lib site packages botocore parsers py line in parse xml string to dom root parser close xml etree elementtree parseerror no element found line column during handling of the above exception another exception occurred traceback most recent call last file srv conda envs notebook lib site packages ooi harvester processor pipeline py line in processing final path finalize zarr file srv conda envs notebook lib site packages ooi harvester processor init py line in finalize zarr source store fs delete source store root recursive true file srv conda envs notebook lib site packages fsspec spec py line in delete return self rm path recursive recursive maxdepth maxdepth file srv conda envs notebook lib site packages fsspec asyn py line in wrapper return sync self loop func args kwargs file srv conda envs notebook lib site packages fsspec asyn py line in sync raise result file srv conda envs notebook lib site packages fsspec asyn py line in runner result await coro file srv conda envs notebook lib site packages core py line in rm await asyncio gather file srv conda envs notebook lib site packages core py line in bulk delete await self call delete objects kwargs bucket bucket delete delete keys file srv conda envs notebook lib site packages core py line in call raise err file srv conda envs notebook lib site packages core py line in call out await method additional kwargs file srv conda envs notebook lib site packages aiobotocore client py line in make api call http parsed response await self make request file srv conda envs notebook lib site packages aiobotocore client py line in make request return await self endpoint make request operation model request dict file srv conda envs notebook lib site packages aiobotocore endpoint py line in send request success response exception await self get response file srv conda envs notebook lib site packages aiobotocore endpoint py line in get response success response exception await self do get response file srv conda envs notebook lib site packages aiobotocore endpoint py line in do get response parsed response parser parse file srv conda envs notebook lib site packages botocore parsers py line in parse parsed self do parse response shape file srv conda envs notebook lib site packages botocore parsers py line in do parse self add modeled parse response shape final parsed file srv conda envs notebook lib site packages botocore parsers py line in add modeled parse self parse payload response shape member shapes final parsed file srv conda envs notebook lib site packages botocore parsers py line in parse payload original parsed self initial body parse response file srv conda envs notebook lib site packages botocore parsers py line in initial body parse return self parse xml string to dom xml string file srv conda envs notebook lib site packages botocore parsers py line in parse xml string to dom raise responseparsererror botocore parsers responseparsererror unable to parse response no element found line column invalid xml received further retries may succeed b n
| 1
|
15,523
| 11,571,979,134
|
IssuesEvent
|
2020-02-20 22:48:00
|
grpc/grpc.io
|
https://api.github.com/repos/grpc/grpc.io
|
opened
|
Upgrade from v0.55.0 to latest Hugo version
|
infrastructure p2-medium
|
I just realized that #87 goes away when using the latest Hugo version (0.65.x), probably because of the switch (since 0.59.x) to adhering to CommonMark markdown syntax.
Of course there is some risk in switching to the latest version if Hugo in that some pages might be rendered differently. But that is partly the point, in some cases, the difference is a fix in the interpretation of the markdown. The risk can be mitigated by diffing the generated sites.
@thisisnotapril WDYT?
|
1.0
|
Upgrade from v0.55.0 to latest Hugo version - I just realized that #87 goes away when using the latest Hugo version (0.65.x), probably because of the switch (since 0.59.x) to adhering to CommonMark markdown syntax.
Of course there is some risk in switching to the latest version if Hugo in that some pages might be rendered differently. But that is partly the point, in some cases, the difference is a fix in the interpretation of the markdown. The risk can be mitigated by diffing the generated sites.
@thisisnotapril WDYT?
|
non_process
|
upgrade from to latest hugo version i just realized that goes away when using the latest hugo version x probably because of the switch since x to adhering to commonmark markdown syntax of course there is some risk in switching to the latest version if hugo in that some pages might be rendered differently but that is partly the point in some cases the difference is a fix in the interpretation of the markdown the risk can be mitigated by diffing the generated sites thisisnotapril wdyt
| 0
|
284,505
| 30,913,638,914
|
IssuesEvent
|
2023-08-05 02:28:14
|
Satheesh575555/linux-4.1.15_CVE-2022-45934
|
https://api.github.com/repos/Satheesh575555/linux-4.1.15_CVE-2022-45934
|
reopened
|
CVE-2018-1120 (Medium) detected in linuxlinux-4.6
|
Mend: dependency security vulnerability
|
## CVE-2018-1120 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/linux-4.1.15_CVE-2022-45934/commit/7c0b143b43394df131d83e9aecb3c5518edc127a">7c0b143b43394df131d83e9aecb3c5518edc127a</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found affecting the Linux kernel before version 4.17. By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc/<pid>/cmdline (or /proc/<pid>/environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks).
<p>Publish Date: 2018-06-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-1120>CVE-2018-1120</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1120">https://nvd.nist.gov/vuln/detail/CVE-2018-1120</a></p>
<p>Release Date: 2018-06-20</p>
<p>Fix Resolution: 4.17</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-2018-1120 (Medium) detected in linuxlinux-4.6 - ## CVE-2018-1120 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/linux-4.1.15_CVE-2022-45934/commit/7c0b143b43394df131d83e9aecb3c5518edc127a">7c0b143b43394df131d83e9aecb3c5518edc127a</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found affecting the Linux kernel before version 4.17. By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc/<pid>/cmdline (or /proc/<pid>/environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks).
<p>Publish Date: 2018-06-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-1120>CVE-2018-1120</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1120">https://nvd.nist.gov/vuln/detail/CVE-2018-1120</a></p>
<p>Release Date: 2018-06-20</p>
<p>Fix Resolution: 4.17</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in linuxlinux cve medium severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details a flaw was found affecting the linux kernel before version by mmap ing a fuse backed file onto a process s memory containing command line arguments or environment strings an attacker can cause utilities from psutils or procps such as ps w or any other program which makes a read call to the proc cmdline or proc environ files to block indefinitely denial of service or for some controlled time as a synchronization primitive for other attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
19,784
| 26,163,614,505
|
IssuesEvent
|
2023-01-01 00:38:22
|
devssa/onde-codar-em-salvador
|
https://api.github.com/repos/devssa/onde-codar-em-salvador
|
closed
|
[REMOTO] [AUTOMACAO] Pessoa Analista de Automação e Processos na [IVIA]
|
REMOTO MODELAGEM DE PROCESSOS HELP WANTED feature_request AUTOMAÇÃO DE PROCESSOS IBM BPM AUTOMATION ANYWHERE GESTAO POR PROCESSOS Stale
|
<!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- Pessoa Analista de Automação e Processos, Home Office.
## Local
- Remoto
## Benefícios
- Informações diretamente com o responsável/recrutador da vaga.
## Requisitos
**Obrigatórios:**
- Conhecimento em IBM BPM; Automation Anywhere;
- Conhecimento em Gestão por Processos (BPM), modelagem de processos em BPMN.
**Desejáveis:**
- Conhecimento em técnicas de análise de processos;
- Conhecimento em Metodologias ágeis;
- Conhecimento em .NET; Python; Pentaho Data Integration; Git; SQL Server; Docker; Java e PostgreSQL.
## Contratação
- a combinar
## Nossa empresa
- Fundada em 1996, a IVIA é uma empresa especializada em tecnologia da informação que desenvolve soluções que facilitem e ampliem os negócios de seus clientes, seja através da redução de custos, aumento de produtividade ou na geração de inovação. A IVIA dispõe de um excelente quadro técnico e consultores especializados, pois sabe que seu principal ativo é o capital intelectual. Sua responsabilidade social começa dentro da empresa, onde talentos são valorizados, respeitados e compensados, criando assim uma atmosfera de constante colaboração e criatividade.
- Com investimento contínuo em qualidade e processo, a IVIA é uma das poucas empresas globais que possui avaliação ISO 9001, MPS.BR e CMMI, tendo sido eleita, pelo décimo ano consecutivo, como uma das melhores empresas para trabalhar no Brasil, segundo o Great Place to Work ®. Como uma empresa contemporânea, a IVIA se preocupa com inovações tecnológicas e causas humanitárias. É uma empresa cidadã, cujo crescimento está associado ao compromisso de tornar a sociedade melhor, começando pelo respeito e incentivo permanente a seus colaboradores e parceiros.
## Como se candidatar
- [Clique aqui para se candidatar](https://mkt.ivia.com.br/pessoa-analista-de-automacao-e-processos-ho)
|
3.0
|
[REMOTO] [AUTOMACAO] Pessoa Analista de Automação e Processos na [IVIA] - <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- Pessoa Analista de Automação e Processos, Home Office.
## Local
- Remoto
## Benefícios
- Informações diretamente com o responsável/recrutador da vaga.
## Requisitos
**Obrigatórios:**
- Conhecimento em IBM BPM; Automation Anywhere;
- Conhecimento em Gestão por Processos (BPM), modelagem de processos em BPMN.
**Desejáveis:**
- Conhecimento em técnicas de análise de processos;
- Conhecimento em Metodologias ágeis;
- Conhecimento em .NET; Python; Pentaho Data Integration; Git; SQL Server; Docker; Java e PostgreSQL.
## Contratação
- a combinar
## Nossa empresa
- Fundada em 1996, a IVIA é uma empresa especializada em tecnologia da informação que desenvolve soluções que facilitem e ampliem os negócios de seus clientes, seja através da redução de custos, aumento de produtividade ou na geração de inovação. A IVIA dispõe de um excelente quadro técnico e consultores especializados, pois sabe que seu principal ativo é o capital intelectual. Sua responsabilidade social começa dentro da empresa, onde talentos são valorizados, respeitados e compensados, criando assim uma atmosfera de constante colaboração e criatividade.
- Com investimento contínuo em qualidade e processo, a IVIA é uma das poucas empresas globais que possui avaliação ISO 9001, MPS.BR e CMMI, tendo sido eleita, pelo décimo ano consecutivo, como uma das melhores empresas para trabalhar no Brasil, segundo o Great Place to Work ®. Como uma empresa contemporânea, a IVIA se preocupa com inovações tecnológicas e causas humanitárias. É uma empresa cidadã, cujo crescimento está associado ao compromisso de tornar a sociedade melhor, começando pelo respeito e incentivo permanente a seus colaboradores e parceiros.
## Como se candidatar
- [Clique aqui para se candidatar](https://mkt.ivia.com.br/pessoa-analista-de-automacao-e-processos-ho)
|
process
|
pessoa analista de automação e processos na por favor só poste se a vaga for para salvador e cidades vizinhas use desenvolvedor front end ao invés de front end developer o exemplo desenvolvedor front end na descrição da vaga pessoa analista de automação e processos home office local remoto benefícios informações diretamente com o responsável recrutador da vaga requisitos obrigatórios conhecimento em ibm bpm automation anywhere conhecimento em gestão por processos bpm modelagem de processos em bpmn desejáveis conhecimento em técnicas de análise de processos conhecimento em metodologias ágeis conhecimento em net python pentaho data integration git sql server docker java e postgresql contratação a combinar nossa empresa fundada em a ivia é uma empresa especializada em tecnologia da informação que desenvolve soluções que facilitem e ampliem os negócios de seus clientes seja através da redução de custos aumento de produtividade ou na geração de inovação a ivia dispõe de um excelente quadro técnico e consultores especializados pois sabe que seu principal ativo é o capital intelectual sua responsabilidade social começa dentro da empresa onde talentos são valorizados respeitados e compensados criando assim uma atmosfera de constante colaboração e criatividade com investimento contínuo em qualidade e processo a ivia é uma das poucas empresas globais que possui avaliação iso mps br e cmmi tendo sido eleita pelo décimo ano consecutivo como uma das melhores empresas para trabalhar no brasil segundo o great place to work ® como uma empresa contemporânea a ivia se preocupa com inovações tecnológicas e causas humanitárias é uma empresa cidadã cujo crescimento está associado ao compromisso de tornar a sociedade melhor começando pelo respeito e incentivo permanente a seus colaboradores e parceiros como se candidatar
| 1
|
602
| 2,545,367,881
|
IssuesEvent
|
2015-01-29 16:44:12
|
brian-team/brian2
|
https://api.github.com/repos/brian-team/brian2
|
opened
|
Allow comments in abstract code
|
component: codegen enhancement proposal
|
I think we don't currently allow this right? It would be good for readability I think.
|
1.0
|
Allow comments in abstract code - I think we don't currently allow this right? It would be good for readability I think.
|
non_process
|
allow comments in abstract code i think we don t currently allow this right it would be good for readability i think
| 0
|
21,749
| 30,264,034,796
|
IssuesEvent
|
2023-07-07 10:22:12
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
Cannot filter the custom column using the context menu
|
Type:Bug Priority:P2 Querying/Parameters & Variables Querying/Notebook/Custom Column .Regression/master .Team/QueryProcessor :hammer_and_wrench:
|
### Describe the bug
It is not possible to use the context menu to directly filter on the custom column anymore.
### To Reproduce
1. Open any table in the Sample Database (Reviews, for example)
2. Create a custom column (it can be as simple as referencing a column)
<img width="523" alt="image" src="https://github.com/metabase/metabase/assets/31325167/54424fa9-f5cc-4c16-a69f-8d258fb88088">
3. Click "Visualize"
4. Click on any field in the custom column and try to filter using the context menu that appears
<img width="449" alt="image" src="https://github.com/metabase/metabase/assets/31325167/d59e3b0b-29bb-476e-841e-21a50a4dc6b5">
5. Using the positive filter `IS` will result in column not found error
6. Using the negative `IS NOT` filter will result in `Function "EXPRESSION" not found` error
### Expected behavior
Context menu filter should work like other filter options do.
### Logs
## `IS` filter
```
Column "PUBLIC.REVIEWS.REVIEWER" not found; SQL statement:
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT"
FROM
(
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT",
"source"."CC Reviewer" AS "CC Reviewer"
FROM
(
SELECT
"PUBLIC"."REVIEWS"."ID" AS "ID",
"PUBLIC"."REVIEWS"."PRODUCT_ID" AS "PRODUCT_ID",
"PUBLIC"."REVIEWS"."REVIEWER" AS "REVIEWER",
"PUBLIC"."REVIEWS"."RATING" AS "RATING",
"PUBLIC"."REVIEWS"."BODY" AS "BODY",
"PUBLIC"."REVIEWS"."CREATED_AT" AS "CREATED_AT",
"PUBLIC"."REVIEWS"."REVIEWER" AS "CC Reviewer"
FROM
"PUBLIC"."REVIEWS"
) AS "source"
) AS "source"
WHERE
"PUBLIC"."REVIEWS"."REVIEWER" = ?
LIMIT
2000 [42122 - 214]
```
## `IS NOT` filter
```
Function "EXPRESSION" not found; SQL statement:
-- Metabase:: userID: 1 queryType: MBQL queryHash: fad6dfad20606663759bc83dc060f3456f56047566c656645582332a890e4d56
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT"
FROM
(
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT",
"source"."CC Reviewer" AS "CC Reviewer"
FROM
(
SELECT
"PUBLIC"."REVIEWS"."ID" AS "ID",
"PUBLIC"."REVIEWS"."PRODUCT_ID" AS "PRODUCT_ID",
"PUBLIC"."REVIEWS"."REVIEWER" AS "REVIEWER",
"PUBLIC"."REVIEWS"."RATING" AS "RATING",
"PUBLIC"."REVIEWS"."BODY" AS "BODY",
"PUBLIC"."REVIEWS"."CREATED_AT" AS "CREATED_AT",
"PUBLIC"."REVIEWS"."REVIEWER" AS "CC Reviewer"
FROM
"PUBLIC"."REVIEWS"
) AS "source"
) AS "source"
WHERE
EXPRESSION(?) <> VALUE(?, NULL)
LIMIT
2000 [90022 - 214]
```
### Information about your Metabase installation
```JSON
Metabase v1.47.0-RC2 JAR, H2, Sample Database
```
### Severity
P2 because you can still use other filter methods such as notebook editor filter or bulk modal editor.
### Additional context
Tested on `0.46.6` and it's working there. So this is a regression on `master` only.
|
1.0
|
Cannot filter the custom column using the context menu - ### Describe the bug
It is not possible to use the context menu to directly filter on the custom column anymore.
### To Reproduce
1. Open any table in the Sample Database (Reviews, for example)
2. Create a custom column (it can be as simple as referencing a column)
<img width="523" alt="image" src="https://github.com/metabase/metabase/assets/31325167/54424fa9-f5cc-4c16-a69f-8d258fb88088">
3. Click "Visualize"
4. Click on any field in the custom column and try to filter using the context menu that appears
<img width="449" alt="image" src="https://github.com/metabase/metabase/assets/31325167/d59e3b0b-29bb-476e-841e-21a50a4dc6b5">
5. Using the positive filter `IS` will result in column not found error
6. Using the negative `IS NOT` filter will result in `Function "EXPRESSION" not found` error
### Expected behavior
Context menu filter should work like other filter options do.
### Logs
## `IS` filter
```
Column "PUBLIC.REVIEWS.REVIEWER" not found; SQL statement:
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT"
FROM
(
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT",
"source"."CC Reviewer" AS "CC Reviewer"
FROM
(
SELECT
"PUBLIC"."REVIEWS"."ID" AS "ID",
"PUBLIC"."REVIEWS"."PRODUCT_ID" AS "PRODUCT_ID",
"PUBLIC"."REVIEWS"."REVIEWER" AS "REVIEWER",
"PUBLIC"."REVIEWS"."RATING" AS "RATING",
"PUBLIC"."REVIEWS"."BODY" AS "BODY",
"PUBLIC"."REVIEWS"."CREATED_AT" AS "CREATED_AT",
"PUBLIC"."REVIEWS"."REVIEWER" AS "CC Reviewer"
FROM
"PUBLIC"."REVIEWS"
) AS "source"
) AS "source"
WHERE
"PUBLIC"."REVIEWS"."REVIEWER" = ?
LIMIT
2000 [42122 - 214]
```
## `IS NOT` filter
```
Function "EXPRESSION" not found; SQL statement:
-- Metabase:: userID: 1 queryType: MBQL queryHash: fad6dfad20606663759bc83dc060f3456f56047566c656645582332a890e4d56
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT"
FROM
(
SELECT
"source"."ID" AS "ID",
"source"."PRODUCT_ID" AS "PRODUCT_ID",
"source"."REVIEWER" AS "REVIEWER",
"source"."RATING" AS "RATING",
"source"."BODY" AS "BODY",
"source"."CREATED_AT" AS "CREATED_AT",
"source"."CC Reviewer" AS "CC Reviewer"
FROM
(
SELECT
"PUBLIC"."REVIEWS"."ID" AS "ID",
"PUBLIC"."REVIEWS"."PRODUCT_ID" AS "PRODUCT_ID",
"PUBLIC"."REVIEWS"."REVIEWER" AS "REVIEWER",
"PUBLIC"."REVIEWS"."RATING" AS "RATING",
"PUBLIC"."REVIEWS"."BODY" AS "BODY",
"PUBLIC"."REVIEWS"."CREATED_AT" AS "CREATED_AT",
"PUBLIC"."REVIEWS"."REVIEWER" AS "CC Reviewer"
FROM
"PUBLIC"."REVIEWS"
) AS "source"
) AS "source"
WHERE
EXPRESSION(?) <> VALUE(?, NULL)
LIMIT
2000 [90022 - 214]
```
### Information about your Metabase installation
```JSON
Metabase v1.47.0-RC2 JAR, H2, Sample Database
```
### Severity
P2 because you can still use other filter methods such as notebook editor filter or bulk modal editor.
### Additional context
Tested on `0.46.6` and it's working there. So this is a regression on `master` only.
|
process
|
cannot filter the custom column using the context menu describe the bug it is not possible to use the context menu to directly filter on the custom column anymore to reproduce open any table in the sample database reviews for example create a custom column it can be as simple as referencing a column img width alt image src click visualize click on any field in the custom column and try to filter using the context menu that appears img width alt image src using the positive filter is will result in column not found error using the negative is not filter will result in function expression not found error expected behavior context menu filter should work like other filter options do logs is filter column public reviews reviewer not found sql statement select source id as id source product id as product id source reviewer as reviewer source rating as rating source body as body source created at as created at from select source id as id source product id as product id source reviewer as reviewer source rating as rating source body as body source created at as created at source cc reviewer as cc reviewer from select public reviews id as id public reviews product id as product id public reviews reviewer as reviewer public reviews rating as rating public reviews body as body public reviews created at as created at public reviews reviewer as cc reviewer from public reviews as source as source where public reviews reviewer limit is not filter function expression not found sql statement metabase userid querytype mbql queryhash select source id as id source product id as product id source reviewer as reviewer source rating as rating source body as body source created at as created at from select source id as id source product id as product id source reviewer as reviewer source rating as rating source body as body source created at as created at source cc reviewer as cc reviewer from select public reviews id as id public reviews product id as product id public reviews reviewer as reviewer public reviews rating as rating public reviews body as body public reviews created at as created at public reviews reviewer as cc reviewer from public reviews as source as source where expression value null limit information about your metabase installation json metabase jar sample database severity because you can still use other filter methods such as notebook editor filter or bulk modal editor additional context tested on and it s working there so this is a regression on master only
| 1
|
392,011
| 26,919,879,574
|
IssuesEvent
|
2023-02-07 09:42:23
|
Every-Time-Clone/every-time
|
https://api.github.com/repos/Every-Time-Clone/every-time
|
opened
|
found multiple declarations of @BootstrapWith for test class 에러
|
documentation
|
테스트 코드를 작성하며 발생한 에러를 처리하고 그에 관한 내용을 기록
@BootstrapWith이 중복으로 사용되어서 발생하는 에러
@SpringBootTest 와 @WebMvcTest 둘다 @BootstrapWith를 가지고 있는 어노테이션이다.
똑같은 어노테이션을 사용하는 어노테이션을 사용해서 발생한 문제
[관련커밋](https://github.com/Every-Time-Clone/every-time/commit/74d8dc5ce14a4b05762b1b4c9ca17f7f9139be24)
내 코드
```java
package com.example.everytime.controller;
import com.example.everytime.domain.posts.Post;
import com.example.everytime.domain.posts.PostRepository;
import com.example.everytime.dto.PostSaveRequestDto;
import org.junit.After;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.servlet.WebMvcTest;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.boot.test.web.client.TestRestTemplate;
import org.springframework.boot.test.web.server.LocalServerPort;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.test.context.junit.jupiter.SpringExtension;
import org.springframework.transaction.annotation.Transactional;
import java.util.List;
import java.util.UUID;
import static org.assertj.core.api.Assertions.assertThat;
@ExtendWith(SpringExtension.class)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
//@WebMvcTest(controllers = PostControllerTest.class) --> 에러가 발생한 부분
public class PostControllerTest {
@LocalServerPort
private int port;
@Autowired
private TestRestTemplate restTemplate;
@Autowired
private PostRepository postRepository;
@After
public void tearDown() throws Exception{
postRepository.deleteAll();
}
@Test
@Transactional
public void Post_등록된다() throws Exception{
//given
String title = "title";
String contents = "content";
PostSaveRequestDto requestDto = PostSaveRequestDto.builder()
.title(title)
.contents(contents)
.build();
String url = "http://localhost:"+ port + "/api/v1/posts";
//when
ResponseEntity<UUID> responseEntity = restTemplate.postForEntity(url,requestDto, UUID.class);
//then
assertThat(responseEntity.getStatusCode()).isEqualTo(HttpStatus.OK);
assertThat(responseEntity.getBody()).isNotNull();
List<Post> all = postRepository.findAll();
assertThat(all.get(0).getTitle()).isEqualTo(title);
assertThat(all.get(0).getContents()).isEqualTo(contents);
}
}
```
- **WebMvcTest 는 JPA 기능이 작동하지 않기 때문에** JPA 기능까지 한꺼번에 테스트해야할 경우 SpringBootTest 를 사용하는게 적절하다.
두 어노테이션이 어느 경우에 사용되는지, 어떤 용도로 사용되고 있는지 간단하게 알아보면
### [@SpringBootTest](https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html)
공식문서에 따르면 @BootStrapWith 가 포함되어있는 것을 확인할 수 있고.
스프링부트를 기반으로 한 테스트를 위한 클래스를 지정하는 어노테이션이다.
다음과 같은 특징을 가지고있다.
- 전체 컨텍스트를 로드하여 빈을 주입하기 때문에 속도가 느리다
- 수많은 스프링 빈을 등록하여 테스트에 필요한 것을 주입한다
- 사용자 환경 속성을 지정할 수 있다
- 애플리케이션의 모든 설정을 로드함
이러한 특징때문에 통합 테스트를 할 때 많이 사용하며, 테스트에 필요한 빈만을 등록하여 테스트를 진행하고자 하기 위해서는 @WebMvcTest 를 사용하는 것이 더 효율적임.
### [@WebMvcTest](https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/autoconfigure/web/servlet/WebMvcTest.html)
MVC를 위한 테스트이며, 웹에서 테스트하기 힘든 컨트롤러를 테스트하는데 적합하다.
이 어노테이션을 사용하면 MVC 테스트와 관련된 어노테이션만 활성화 된다. 이를테면 @Controller, @ControllerAdvice, @JsonComponent, Converter/GenericConverter, Filter 등등.. 그렇기 때문에 @SpringBootTest 어노테이션보다 가볍게 테스트할 수 있다.
전체 애플리케이션 구성을 로드하고, mockMvc를 사용할 경우 **SpringBootTest**를 사용하는 것을 고려하는게 적절하다.
|
1.0
|
found multiple declarations of @BootstrapWith for test class 에러 - 테스트 코드를 작성하며 발생한 에러를 처리하고 그에 관한 내용을 기록
@BootstrapWith이 중복으로 사용되어서 발생하는 에러
@SpringBootTest 와 @WebMvcTest 둘다 @BootstrapWith를 가지고 있는 어노테이션이다.
똑같은 어노테이션을 사용하는 어노테이션을 사용해서 발생한 문제
[관련커밋](https://github.com/Every-Time-Clone/every-time/commit/74d8dc5ce14a4b05762b1b4c9ca17f7f9139be24)
내 코드
```java
package com.example.everytime.controller;
import com.example.everytime.domain.posts.Post;
import com.example.everytime.domain.posts.PostRepository;
import com.example.everytime.dto.PostSaveRequestDto;
import org.junit.After;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.servlet.WebMvcTest;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.boot.test.web.client.TestRestTemplate;
import org.springframework.boot.test.web.server.LocalServerPort;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.test.context.junit.jupiter.SpringExtension;
import org.springframework.transaction.annotation.Transactional;
import java.util.List;
import java.util.UUID;
import static org.assertj.core.api.Assertions.assertThat;
@ExtendWith(SpringExtension.class)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
//@WebMvcTest(controllers = PostControllerTest.class) --> 에러가 발생한 부분
public class PostControllerTest {
@LocalServerPort
private int port;
@Autowired
private TestRestTemplate restTemplate;
@Autowired
private PostRepository postRepository;
@After
public void tearDown() throws Exception{
postRepository.deleteAll();
}
@Test
@Transactional
public void Post_등록된다() throws Exception{
//given
String title = "title";
String contents = "content";
PostSaveRequestDto requestDto = PostSaveRequestDto.builder()
.title(title)
.contents(contents)
.build();
String url = "http://localhost:"+ port + "/api/v1/posts";
//when
ResponseEntity<UUID> responseEntity = restTemplate.postForEntity(url,requestDto, UUID.class);
//then
assertThat(responseEntity.getStatusCode()).isEqualTo(HttpStatus.OK);
assertThat(responseEntity.getBody()).isNotNull();
List<Post> all = postRepository.findAll();
assertThat(all.get(0).getTitle()).isEqualTo(title);
assertThat(all.get(0).getContents()).isEqualTo(contents);
}
}
```
- **WebMvcTest 는 JPA 기능이 작동하지 않기 때문에** JPA 기능까지 한꺼번에 테스트해야할 경우 SpringBootTest 를 사용하는게 적절하다.
두 어노테이션이 어느 경우에 사용되는지, 어떤 용도로 사용되고 있는지 간단하게 알아보면
### [@SpringBootTest](https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html)
공식문서에 따르면 @BootStrapWith 가 포함되어있는 것을 확인할 수 있고.
스프링부트를 기반으로 한 테스트를 위한 클래스를 지정하는 어노테이션이다.
다음과 같은 특징을 가지고있다.
- 전체 컨텍스트를 로드하여 빈을 주입하기 때문에 속도가 느리다
- 수많은 스프링 빈을 등록하여 테스트에 필요한 것을 주입한다
- 사용자 환경 속성을 지정할 수 있다
- 애플리케이션의 모든 설정을 로드함
이러한 특징때문에 통합 테스트를 할 때 많이 사용하며, 테스트에 필요한 빈만을 등록하여 테스트를 진행하고자 하기 위해서는 @WebMvcTest 를 사용하는 것이 더 효율적임.
### [@WebMvcTest](https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/autoconfigure/web/servlet/WebMvcTest.html)
MVC를 위한 테스트이며, 웹에서 테스트하기 힘든 컨트롤러를 테스트하는데 적합하다.
이 어노테이션을 사용하면 MVC 테스트와 관련된 어노테이션만 활성화 된다. 이를테면 @Controller, @ControllerAdvice, @JsonComponent, Converter/GenericConverter, Filter 등등.. 그렇기 때문에 @SpringBootTest 어노테이션보다 가볍게 테스트할 수 있다.
전체 애플리케이션 구성을 로드하고, mockMvc를 사용할 경우 **SpringBootTest**를 사용하는 것을 고려하는게 적절하다.
|
non_process
|
found multiple declarations of bootstrapwith for test class 에러 테스트 코드를 작성하며 발생한 에러를 처리하고 그에 관한 내용을 기록 bootstrapwith이 중복으로 사용되어서 발생하는 에러 springboottest 와 webmvctest 둘다 bootstrapwith를 가지고 있는 어노테이션이다 똑같은 어노테이션을 사용하는 어노테이션을 사용해서 발생한 문제 내 코드 java package com example everytime controller import com example everytime domain posts post import com example everytime domain posts postrepository import com example everytime dto postsaverequestdto import org junit after import org junit jupiter api test import org junit jupiter api extension extendwith import org springframework beans factory annotation autowired import org springframework boot test autoconfigure web servlet webmvctest import org springframework boot test context springboottest import org springframework boot test web client testresttemplate import org springframework boot test web server localserverport import org springframework http httpstatus import org springframework http responseentity import org springframework test context junit jupiter springextension import org springframework transaction annotation transactional import java util list import java util uuid import static org assertj core api assertions assertthat extendwith springextension class springboottest webenvironment springboottest webenvironment random port webmvctest controllers postcontrollertest class 에러가 발생한 부분 public class postcontrollertest localserverport private int port autowired private testresttemplate resttemplate autowired private postrepository postrepository after public void teardown throws exception postrepository deleteall test transactional public void post 등록된다 throws exception given string title title string contents content postsaverequestdto requestdto postsaverequestdto builder title title contents contents build string url port api posts when responseentity responseentity resttemplate postforentity url requestdto uuid class then assertthat responseentity getstatuscode isequalto httpstatus ok assertthat responseentity getbody isnotnull list all postrepository findall assertthat all get gettitle isequalto title assertthat all get getcontents isequalto contents webmvctest 는 jpa 기능이 작동하지 않기 때문에 jpa 기능까지 한꺼번에 테스트해야할 경우 springboottest 를 사용하는게 적절하다 두 어노테이션이 어느 경우에 사용되는지 어떤 용도로 사용되고 있는지 간단하게 알아보면 공식문서에 따르면 bootstrapwith 가 포함되어있는 것을 확인할 수 있고 스프링부트를 기반으로 한 테스트를 위한 클래스를 지정하는 어노테이션이다 다음과 같은 특징을 가지고있다 전체 컨텍스트를 로드하여 빈을 주입하기 때문에 속도가 느리다 수많은 스프링 빈을 등록하여 테스트에 필요한 것을 주입한다 사용자 환경 속성을 지정할 수 있다 애플리케이션의 모든 설정을 로드함 이러한 특징때문에 통합 테스트를 할 때 많이 사용하며 테스트에 필요한 빈만을 등록하여 테스트를 진행하고자 하기 위해서는 webmvctest 를 사용하는 것이 더 효율적임 mvc를 위한 테스트이며 웹에서 테스트하기 힘든 컨트롤러를 테스트하는데 적합하다 이 어노테이션을 사용하면 mvc 테스트와 관련된 어노테이션만 활성화 된다 이를테면 controller controlleradvice jsoncomponent converter genericconverter filter 등등 그렇기 때문에 springboottest 어노테이션보다 가볍게 테스트할 수 있다 전체 애플리케이션 구성을 로드하고 mockmvc를 사용할 경우 springboottest 를 사용하는 것을 고려하는게 적절하다
| 0
|
5,511
| 8,377,095,309
|
IssuesEvent
|
2018-10-05 22:33:35
|
emacs-ess/ESS
|
https://api.github.com/repos/emacs-ess/ESS
|
closed
|
Adjust options("width") in ESS
|
process
|
I was wondering if we could adjust the `options("width")` on emacs resize. It seems like a possibility. On windows the `options("width")` is always `80`.
|
1.0
|
Adjust options("width") in ESS - I was wondering if we could adjust the `options("width")` on emacs resize. It seems like a possibility. On windows the `options("width")` is always `80`.
|
process
|
adjust options width in ess i was wondering if we could adjust the options width on emacs resize it seems like a possibility on windows the options width is always
| 1
|
17,461
| 23,285,580,379
|
IssuesEvent
|
2022-08-05 16:07:38
|
keras-team/keras-cv
|
https://api.github.com/repos/keras-team/keras-cv
|
closed
|
Support no-op `augment_bounding_boxes()` method in all of the layers that do not modify bounding boxes
|
preprocessing
|
These include:
- AutoContrast
- ChannelShuffle
- Equalization
- Grayscale
- GridMask
- Posterization
- RandomChannelShift
- RandomColorJitter
- RandomGaussianBlur
- RandomHue
- RandomSaturation
- RandomSharpness
- Solarization
- RandomJpegQuality
- RandomRescale
- RandomContrast
- RandomBrightness
After including `augment_bounding_boxes()` in all of these, we can also include a unit test suite "with_bounding_boxes_test.py" identical to "with_labels_test" but for bound boxes. (Reference: https://github.com/keras-team/keras-cv/blob/master/keras_cv/layers/preprocessing/with_labels_test.py)
Please include a test case for both dense and ragged bounding boxes, in both batched and unbatched mode.
Also include RandomRotation & RandomShear in the unit tests.
Thanks!
|
1.0
|
Support no-op `augment_bounding_boxes()` method in all of the layers that do not modify bounding boxes - These include:
- AutoContrast
- ChannelShuffle
- Equalization
- Grayscale
- GridMask
- Posterization
- RandomChannelShift
- RandomColorJitter
- RandomGaussianBlur
- RandomHue
- RandomSaturation
- RandomSharpness
- Solarization
- RandomJpegQuality
- RandomRescale
- RandomContrast
- RandomBrightness
After including `augment_bounding_boxes()` in all of these, we can also include a unit test suite "with_bounding_boxes_test.py" identical to "with_labels_test" but for bound boxes. (Reference: https://github.com/keras-team/keras-cv/blob/master/keras_cv/layers/preprocessing/with_labels_test.py)
Please include a test case for both dense and ragged bounding boxes, in both batched and unbatched mode.
Also include RandomRotation & RandomShear in the unit tests.
Thanks!
|
process
|
support no op augment bounding boxes method in all of the layers that do not modify bounding boxes these include autocontrast channelshuffle equalization grayscale gridmask posterization randomchannelshift randomcolorjitter randomgaussianblur randomhue randomsaturation randomsharpness solarization randomjpegquality randomrescale randomcontrast randombrightness after including augment bounding boxes in all of these we can also include a unit test suite with bounding boxes test py identical to with labels test but for bound boxes reference please include a test case for both dense and ragged bounding boxes in both batched and unbatched mode also include randomrotation randomshear in the unit tests thanks
| 1
|
370,279
| 25,897,024,556
|
IssuesEvent
|
2022-12-14 23:49:25
|
fga-eps-mds/2022-2-ez-docs
|
https://api.github.com/repos/fga-eps-mds/2022-2-ez-docs
|
closed
|
Funcionabilidade do pacote em diferentes versões do Python
|
documentation important Epic
|
# Descrição
Verificar e testar em quais versões do Python o pacote funiona, fazer o teste desde o Python 2.0.1 até a versão mais nova Python 3.11.1, sendo pelo menos 10 casos testes.
## Critérios de avaliação
- [x] 10 casos testes, 1 por versão
- [x] Funcionamento normal de todo, relaçao dos erros encontrados
- [x] Atualização do README
- [x] branch e pull request
|
1.0
|
Funcionabilidade do pacote em diferentes versões do Python - # Descrição
Verificar e testar em quais versões do Python o pacote funiona, fazer o teste desde o Python 2.0.1 até a versão mais nova Python 3.11.1, sendo pelo menos 10 casos testes.
## Critérios de avaliação
- [x] 10 casos testes, 1 por versão
- [x] Funcionamento normal de todo, relaçao dos erros encontrados
- [x] Atualização do README
- [x] branch e pull request
|
non_process
|
funcionabilidade do pacote em diferentes versões do python descrição verificar e testar em quais versões do python o pacote funiona fazer o teste desde o python até a versão mais nova python sendo pelo menos casos testes critérios de avaliação casos testes por versão funcionamento normal de todo relaçao dos erros encontrados atualização do readme branch e pull request
| 0
|
722,359
| 24,860,489,690
|
IssuesEvent
|
2022-10-27 07:52:37
|
input-output-hk/cardano-node
|
https://api.github.com/repos/input-output-hk/cardano-node
|
closed
|
Chairman needs to take per-node chain density into account
|
byron priority medium
|
Hydra's run of chairman's cluster in https://github.com/input-output-hk/cardano-node/pull/577 exposes an undesirable laxitude of the CI check -- as long as we lose just slightly under half the blocks, the CI is green, as chairman will accept that situation.
Citing @dcoutts:
> we simply have to check that each node made at least N blocks in the chain, for an appropriate N based on K and how long we run it for
So, the upper bound for `N` for a node's block forging performance (measured in blocks) over a period of time `T` (measured in slots), with a fraction of stake `S` seems to be independent of `K` and is simply:
```
N = T / S
```
The lower reasonable bound `n` should be a reasonably high fraction of the upper bound (given that we run the network for a sufficient amount slots), and could be something like
```
n = N * 0.95
```
..where the slack would account for the initial network block lossage that used to happen due to initial connection setup & timeouts -- remember that we're linking two segments of the cluster via a proxy, so that exacerbates the problem.
|
1.0
|
Chairman needs to take per-node chain density into account - Hydra's run of chairman's cluster in https://github.com/input-output-hk/cardano-node/pull/577 exposes an undesirable laxitude of the CI check -- as long as we lose just slightly under half the blocks, the CI is green, as chairman will accept that situation.
Citing @dcoutts:
> we simply have to check that each node made at least N blocks in the chain, for an appropriate N based on K and how long we run it for
So, the upper bound for `N` for a node's block forging performance (measured in blocks) over a period of time `T` (measured in slots), with a fraction of stake `S` seems to be independent of `K` and is simply:
```
N = T / S
```
The lower reasonable bound `n` should be a reasonably high fraction of the upper bound (given that we run the network for a sufficient amount slots), and could be something like
```
n = N * 0.95
```
..where the slack would account for the initial network block lossage that used to happen due to initial connection setup & timeouts -- remember that we're linking two segments of the cluster via a proxy, so that exacerbates the problem.
|
non_process
|
chairman needs to take per node chain density into account hydra s run of chairman s cluster in exposes an undesirable laxitude of the ci check as long as we lose just slightly under half the blocks the ci is green as chairman will accept that situation citing dcoutts we simply have to check that each node made at least n blocks in the chain for an appropriate n based on k and how long we run it for so the upper bound for n for a node s block forging performance measured in blocks over a period of time t measured in slots with a fraction of stake s seems to be independent of k and is simply n t s the lower reasonable bound n should be a reasonably high fraction of the upper bound given that we run the network for a sufficient amount slots and could be something like n n where the slack would account for the initial network block lossage that used to happen due to initial connection setup timeouts remember that we re linking two segments of the cluster via a proxy so that exacerbates the problem
| 0
|
173,693
| 27,513,756,007
|
IssuesEvent
|
2023-03-06 10:33:35
|
LuccaSA/lucca-front
|
https://api.github.com/repos/LuccaSA/lucca-front
|
closed
|
[LuPopup] Improve accessibility
|
👥 Guilde Front 👥 Guilde Design :bookmark::sparkles: Feature
|
We have multiple cases where teams are implementing forms in LuPopup for accessibility / UI purposes.
Some Modal / Side Panel properties need to be accessible on LuPopup
- [x] Implement focus trap on LuPopup
- - [x] When opening: Focus on the modal element (it should have a `tabindex="-1"` attribute)
- - [x] When closing: Focus the button that opened the modal
- - [x] Add `tabindex="-1"` on page's focusable elements (be careful to reset this attribute to its previous value for elements which had one before the modal was opened)
- [x] Add attributes `role="dialog"` et `aria-modal="true"` on modal and Side Panel
- [ ] Add `aria-hidden="true"` on `body` children elements (except for modal) (be careful to avoid removing it on elements which already had it before opening the modal)
⚠️ We need to be careful to avoid adding focus trap on other components by mistake (Dropdown...)
⚠️ Current Modal / Side Panel focus trap might be deprecated
⚠️ In some cases we might need to use `role="alertDialog"` instead of `dialog`
|
1.0
|
[LuPopup] Improve accessibility - We have multiple cases where teams are implementing forms in LuPopup for accessibility / UI purposes.
Some Modal / Side Panel properties need to be accessible on LuPopup
- [x] Implement focus trap on LuPopup
- - [x] When opening: Focus on the modal element (it should have a `tabindex="-1"` attribute)
- - [x] When closing: Focus the button that opened the modal
- - [x] Add `tabindex="-1"` on page's focusable elements (be careful to reset this attribute to its previous value for elements which had one before the modal was opened)
- [x] Add attributes `role="dialog"` et `aria-modal="true"` on modal and Side Panel
- [ ] Add `aria-hidden="true"` on `body` children elements (except for modal) (be careful to avoid removing it on elements which already had it before opening the modal)
⚠️ We need to be careful to avoid adding focus trap on other components by mistake (Dropdown...)
⚠️ Current Modal / Side Panel focus trap might be deprecated
⚠️ In some cases we might need to use `role="alertDialog"` instead of `dialog`
|
non_process
|
improve accessibility we have multiple cases where teams are implementing forms in lupopup for accessibility ui purposes some modal side panel properties need to be accessible on lupopup implement focus trap on lupopup when opening focus on the modal element it should have a tabindex attribute when closing focus the button that opened the modal add tabindex on page s focusable elements be careful to reset this attribute to its previous value for elements which had one before the modal was opened add attributes role dialog et aria modal true on modal and side panel add aria hidden true on body children elements except for modal be careful to avoid removing it on elements which already had it before opening the modal ⚠️ we need to be careful to avoid adding focus trap on other components by mistake dropdown ⚠️ current modal side panel focus trap might be deprecated ⚠️ in some cases we might need to use role alertdialog instead of dialog
| 0
|
46,142
| 24,380,126,408
|
IssuesEvent
|
2022-10-04 07:02:04
|
JuliaMolSim/DFTK.jl
|
https://api.github.com/repos/JuliaMolSim/DFTK.jl
|
closed
|
Use real FFTs
|
feature performance
|
Add an option to perform real-to-complex and complex-to-real FFTs with a kwarg, and use that to do the potentials as real arrays. Could also do dispatch on the eltype of f_real, but it's not compatible with G_to_r(f_fourier).
|
True
|
Use real FFTs - Add an option to perform real-to-complex and complex-to-real FFTs with a kwarg, and use that to do the potentials as real arrays. Could also do dispatch on the eltype of f_real, but it's not compatible with G_to_r(f_fourier).
|
non_process
|
use real ffts add an option to perform real to complex and complex to real ffts with a kwarg and use that to do the potentials as real arrays could also do dispatch on the eltype of f real but it s not compatible with g to r f fourier
| 0
|
46,364
| 7,253,986,287
|
IssuesEvent
|
2018-02-16 09:07:25
|
pluginkollektiv/antispam-bee
|
https://api.github.com/repos/pluginkollektiv/antispam-bee
|
closed
|
Change wording for "At a glance" dashboard widget
|
bug documentation
|
> Perhaps the wording of that text should be adjusted in the “at a glance” box on the dashboard to reflect the actual status. Something like “{number} spam comments detected and deleted automatically” or something.
> The way it is now, it’s misleading and confusing.
https://wordpress.org/support/topic/list-of-blocked-comments-2/
This is a problem because the meaning of this number is switching according to the delete option:
https://github.com/pluginkollektiv/antispam-bee/wiki/en-Documentation#spam-counter-on-the-dashboard
I think the draft is much to long, but maybe there is a way to better reflect the change.
|
1.0
|
Change wording for "At a glance" dashboard widget - > Perhaps the wording of that text should be adjusted in the “at a glance” box on the dashboard to reflect the actual status. Something like “{number} spam comments detected and deleted automatically” or something.
> The way it is now, it’s misleading and confusing.
https://wordpress.org/support/topic/list-of-blocked-comments-2/
This is a problem because the meaning of this number is switching according to the delete option:
https://github.com/pluginkollektiv/antispam-bee/wiki/en-Documentation#spam-counter-on-the-dashboard
I think the draft is much to long, but maybe there is a way to better reflect the change.
|
non_process
|
change wording for at a glance dashboard widget perhaps the wording of that text should be adjusted in the “at a glance” box on the dashboard to reflect the actual status something like “ number spam comments detected and deleted automatically” or something the way it is now it’s misleading and confusing this is a problem because the meaning of this number is switching according to the delete option i think the draft is much to long but maybe there is a way to better reflect the change
| 0
|
10,313
| 13,156,849,528
|
IssuesEvent
|
2020-08-10 11:37:36
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
Shared memory manager connection timed out error. In nested multiprocess program and with dataloader num_workers > 0
|
module: dataloader module: multiprocessing triaged
|
## 🐛 Bug
I have a training program whose architecture like this:
- use ONE data but 4 different hyper-parameter, so `main()` spawns 4 process, each for one hyper parameter
- for each hyper-parameter training process, spawn one sub-process for asynchronous evaluation
- all the 8 (=4 * 2) process use the same data resource: a dict-of-SharedMemoryTensor
After started, It works as expected for a while (about 3-5 hours) and then throw `RuntimeError:Shared memory manager connection has timed out`. If set dataloader `num_workers` to 0, or do not use evaluation process, than the error disappears.
detailed error information is:
```
===========================
... (user code)...
for i, (X, y) in enumerate(dloader):
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 345, in __next__
data = self._next_data()
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 841, in _next_data
idx, data = self._get_data()
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 808, in _get_data
success, data = self._try_get_data()
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 761, in _try_get_data
data = self._data_queue.get(timeout=timeout)
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/multiprocessing/queues.py", line 116, in get
return _ForkingPickler.loads(res)
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/multiprocessing/reductions.py", line 310, in rebuild_storage_filename
storage = cls._new_shared_filename(manager, handle, size)
RuntimeError: Shared memory manager connection has timed out at /pytorch/torch/lib/libshm/core.cpp:99
```
A simplified version of my production code is below:
```python
def process_task(rank, shm_resources):
train_ds = MyCustomizedDataset(shm_resources)
train_dl = DataLoader(train_ds, batch_size=256, shuffle=True, drop_last=True, num_workers=4)
test_ds = MyCustomizedDataset(shm_resources)
test_dl = DataLoader(test_ds, batch_size=256, shuffle=True, drop_last=True, num_workers=4)
eval_process = mp.spawn(fn=train_or_evaluate_loop, args=('evaluate', test_dl), nprocs=1, join=False)
train_or_evaluate_loop(0, 'train', train_dl)
eval_process.join()
def train_or_evaluate_loop(rank, loop_name, dl):
it = iter(dl)
for i in range(n_batchs):
X, y = next(it)
if __name__ == "__main__":
shm_resources = {
'X': {
i: torch.rand(size=(1_0000, 300)) for i in range(3000)
},
'y': {
i: torch.rand(size=(1_0000,)) for i in range(3000)
}
}
mp.spawn(fn=process_task, args=(shm_resources,), nprocs=4, join=True)
```
## Environment
python collect_env.py
```
Collecting environment information...
PyTorch version: 1.5.1+cu101
Is debug build: No
CUDA used to build PyTorch: 10.1
OS: Ubuntu 18.04.4 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: version 3.17.1
Python version: 3.8
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti
GPU 4: GeForce RTX 2080 Ti
GPU 5: GeForce RTX 2080 Ti
GPU 6: GeForce RTX 2080 Ti
GPU 7: GeForce RTX 2080 Ti
GPU 8: GeForce RTX 2080 Ti
Nvidia driver version: 440.59
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5
Versions of relevant libraries:
[pip3] numpy==1.18.5
[pip3] torch==1.5.1+cu101
[pip3] torchvision==0.6.1+cu101
[conda] numpy 1.18.5 pypi_0 pypi
[conda] torch 1.5.1+cu101 pypi_0 pypi
[conda] torchvision 0.6.1+cu101 pypi_0 pypi
```
cc @SsnL @VitalyFedyunin
|
1.0
|
Shared memory manager connection timed out error. In nested multiprocess program and with dataloader num_workers > 0 - ## 🐛 Bug
I have a training program whose architecture like this:
- use ONE data but 4 different hyper-parameter, so `main()` spawns 4 process, each for one hyper parameter
- for each hyper-parameter training process, spawn one sub-process for asynchronous evaluation
- all the 8 (=4 * 2) process use the same data resource: a dict-of-SharedMemoryTensor
After started, It works as expected for a while (about 3-5 hours) and then throw `RuntimeError:Shared memory manager connection has timed out`. If set dataloader `num_workers` to 0, or do not use evaluation process, than the error disappears.
detailed error information is:
```
===========================
... (user code)...
for i, (X, y) in enumerate(dloader):
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 345, in __next__
data = self._next_data()
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 841, in _next_data
idx, data = self._get_data()
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 808, in _get_data
success, data = self._try_get_data()
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 761, in _try_get_data
data = self._data_queue.get(timeout=timeout)
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/multiprocessing/queues.py", line 116, in get
return _ForkingPickler.loads(res)
File "/home/rjia/anaconda3/envs/gpu38/lib/python3.8/site-packages/torch/multiprocessing/reductions.py", line 310, in rebuild_storage_filename
storage = cls._new_shared_filename(manager, handle, size)
RuntimeError: Shared memory manager connection has timed out at /pytorch/torch/lib/libshm/core.cpp:99
```
A simplified version of my production code is below:
```python
def process_task(rank, shm_resources):
train_ds = MyCustomizedDataset(shm_resources)
train_dl = DataLoader(train_ds, batch_size=256, shuffle=True, drop_last=True, num_workers=4)
test_ds = MyCustomizedDataset(shm_resources)
test_dl = DataLoader(test_ds, batch_size=256, shuffle=True, drop_last=True, num_workers=4)
eval_process = mp.spawn(fn=train_or_evaluate_loop, args=('evaluate', test_dl), nprocs=1, join=False)
train_or_evaluate_loop(0, 'train', train_dl)
eval_process.join()
def train_or_evaluate_loop(rank, loop_name, dl):
it = iter(dl)
for i in range(n_batchs):
X, y = next(it)
if __name__ == "__main__":
shm_resources = {
'X': {
i: torch.rand(size=(1_0000, 300)) for i in range(3000)
},
'y': {
i: torch.rand(size=(1_0000,)) for i in range(3000)
}
}
mp.spawn(fn=process_task, args=(shm_resources,), nprocs=4, join=True)
```
## Environment
python collect_env.py
```
Collecting environment information...
PyTorch version: 1.5.1+cu101
Is debug build: No
CUDA used to build PyTorch: 10.1
OS: Ubuntu 18.04.4 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: version 3.17.1
Python version: 3.8
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti
GPU 4: GeForce RTX 2080 Ti
GPU 5: GeForce RTX 2080 Ti
GPU 6: GeForce RTX 2080 Ti
GPU 7: GeForce RTX 2080 Ti
GPU 8: GeForce RTX 2080 Ti
Nvidia driver version: 440.59
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5
Versions of relevant libraries:
[pip3] numpy==1.18.5
[pip3] torch==1.5.1+cu101
[pip3] torchvision==0.6.1+cu101
[conda] numpy 1.18.5 pypi_0 pypi
[conda] torch 1.5.1+cu101 pypi_0 pypi
[conda] torchvision 0.6.1+cu101 pypi_0 pypi
```
cc @SsnL @VitalyFedyunin
|
process
|
shared memory manager connection timed out error in nested multiprocess program and with dataloader num workers 🐛 bug i have a training program whose architecture like this use one data but different hyper parameter so main spawns process each for one hyper parameter for each hyper parameter training process spawn one sub process for asynchronous evaluation all the process use the same data resource a dict of sharedmemorytensor after started it works as expected for a while about hours and then throw runtimeerror shared memory manager connection has timed out if set dataloader num workers to or do not use evaluation process than the error disappears detailed error information is user code for i x y in enumerate dloader file home rjia envs lib site packages torch utils data dataloader py line in next data self next data file home rjia envs lib site packages torch utils data dataloader py line in next data idx data self get data file home rjia envs lib site packages torch utils data dataloader py line in get data success data self try get data file home rjia envs lib site packages torch utils data dataloader py line in try get data data self data queue get timeout timeout file home rjia envs lib multiprocessing queues py line in get return forkingpickler loads res file home rjia envs lib site packages torch multiprocessing reductions py line in rebuild storage filename storage cls new shared filename manager handle size runtimeerror shared memory manager connection has timed out at pytorch torch lib libshm core cpp a simplified version of my production code is below python def process task rank shm resources train ds mycustomizeddataset shm resources train dl dataloader train ds batch size shuffle true drop last true num workers test ds mycustomizeddataset shm resources test dl dataloader test ds batch size shuffle true drop last true num workers eval process mp spawn fn train or evaluate loop args evaluate test dl nprocs join false train or evaluate loop train train dl eval process join def train or evaluate loop rank loop name dl it iter dl for i in range n batchs x y next it if name main shm resources x i torch rand size for i in range y i torch rand size for i in range mp spawn fn process task args shm resources nprocs join true environment python collect env py collecting environment information pytorch version is debug build no cuda used to build pytorch os ubuntu lts gcc version ubuntu cmake version version python version is cuda available yes cuda runtime version could not collect gpu models and configuration gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti gpu geforce rtx ti nvidia driver version cudnn version usr lib linux gnu libcudnn so versions of relevant libraries numpy torch torchvision numpy pypi pypi torch pypi pypi torchvision pypi pypi cc ssnl vitalyfedyunin
| 1
|
15,907
| 20,112,797,859
|
IssuesEvent
|
2022-02-07 16:30:33
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
closed
|
Unification: Windows testing
|
process: tests stage: work in progress type: chore
|
### What would you like?
We want to expand our testing of Windows for our unification launch to ensure things are working well for our Windows users.
### Why is this needed?
_No response_
### Other
_No response_
|
1.0
|
Unification: Windows testing - ### What would you like?
We want to expand our testing of Windows for our unification launch to ensure things are working well for our Windows users.
### Why is this needed?
_No response_
### Other
_No response_
|
process
|
unification windows testing what would you like we want to expand our testing of windows for our unification launch to ensure things are working well for our windows users why is this needed no response other no response
| 1
|
417,405
| 28,110,445,326
|
IssuesEvent
|
2023-03-31 06:41:02
|
gyulong1/ped
|
https://api.github.com/repos/gyulong1/ped
|
opened
|
Missing space in the error message for status command
|
type.DocumentationBug severity.VeryLow
|
After providing an invalid status, the error message is missing a space in "matchonly"
<!--session: 1680242296715-29bb0fea-05f1-41ae-b4d9-71039571a17e-->
<!--Version: Web v3.4.7-->
|
1.0
|
Missing space in the error message for status command - After providing an invalid status, the error message is missing a space in "matchonly"
<!--session: 1680242296715-29bb0fea-05f1-41ae-b4d9-71039571a17e-->
<!--Version: Web v3.4.7-->
|
non_process
|
missing space in the error message for status command after providing an invalid status the error message is missing a space in matchonly
| 0
|
100,270
| 8,729,229,715
|
IssuesEvent
|
2018-12-10 19:39:08
|
Microsoft/AzureStorageExplorer
|
https://api.github.com/repos/Microsoft/AzureStorageExplorer
|
closed
|
'OK' button is disabled with the default name on the New Folder dialog
|
:gear: adls gen2 :white_check_mark: merged :x: regression testing
|
**Storage Explorer Version**: 1.6.1
**Platform/OS Version**: Windows 10/ MacOS High Sierra/ Linux Ubuntu 16.04
**Architecture**: ia32
**Build Number**: 20181210.2
**Commit**: 4fed5a79
**Regression From**: Previous release 1.6.0
#### Steps to Reproduce: ####
1. Choose one ADLS Gen2 account then open one blob container.
2. Click 'New Folder' on the toolbar -> Check whether the OK is enabled or not on the New Folder dialog.
#### Expected Experience: ####
'OK' is **enabled** with the default name on the New Folder dialog.
#### Actual Experience: ####
'OK' is **disabled** with the default name on the New Folder dialog.
|
1.0
|
'OK' button is disabled with the default name on the New Folder dialog - **Storage Explorer Version**: 1.6.1
**Platform/OS Version**: Windows 10/ MacOS High Sierra/ Linux Ubuntu 16.04
**Architecture**: ia32
**Build Number**: 20181210.2
**Commit**: 4fed5a79
**Regression From**: Previous release 1.6.0
#### Steps to Reproduce: ####
1. Choose one ADLS Gen2 account then open one blob container.
2. Click 'New Folder' on the toolbar -> Check whether the OK is enabled or not on the New Folder dialog.
#### Expected Experience: ####
'OK' is **enabled** with the default name on the New Folder dialog.
#### Actual Experience: ####
'OK' is **disabled** with the default name on the New Folder dialog.
|
non_process
|
ok button is disabled with the default name on the new folder dialog storage explorer version platform os version windows macos high sierra linux ubuntu architecture build number commit regression from previous release steps to reproduce choose one adls account then open one blob container click new folder on the toolbar check whether the ok is enabled or not on the new folder dialog expected experience ok is enabled with the default name on the new folder dialog actual experience ok is disabled with the default name on the new folder dialog
| 0
|
603,034
| 18,522,735,703
|
IssuesEvent
|
2021-10-20 16:41:17
|
cu-mkp/m-k-manuscript-data
|
https://api.github.com/repos/cu-mkp/m-k-manuscript-data
|
closed
|
<del>s in TL
|
markup consistency translation low-priority
|
FRom @Pantagrueliste
Reading through TL made me realize the extent to which translated deletions can be problematic. They are translated inconsistently, many—if not most—of them do not provide much insight into the manuscript, and I’m concerned that the "noise” they produce will ultimately confuse, distract, and sometimes even mislead the reader. These translated deletions, moreover, seem to be based on the very questionable assumption that phonological, morphological and syntactical errors can be consistently translated from one language to another. How do we intend to justify this editorial choice?
As editors, our primary role is to establish a text. Yet if we transcribe and translate every single deletion into the TL, without explaining why, we seem to be evading this responsibility.
While I share the enthusiasm of highlighting deletions in the TL, I think that the way we are doing it is not satisfactory, and I’m afraid that we would need, at some point, to synthesize all the information regarding deletions, in order to keep only the ones that we editors believe to be relevant for the reader. This would probably imply the deletion of `<del>` tags in TL and the addition of editorial comments whenever necessary.
E.g., 62v partial translation with incomplete french word
>Also, to make plumb lines, which go from the top <del>to make <fr>vif</fr></del> to the bottom
|
1.0
|
<del>s in TL - FRom @Pantagrueliste
Reading through TL made me realize the extent to which translated deletions can be problematic. They are translated inconsistently, many—if not most—of them do not provide much insight into the manuscript, and I’m concerned that the "noise” they produce will ultimately confuse, distract, and sometimes even mislead the reader. These translated deletions, moreover, seem to be based on the very questionable assumption that phonological, morphological and syntactical errors can be consistently translated from one language to another. How do we intend to justify this editorial choice?
As editors, our primary role is to establish a text. Yet if we transcribe and translate every single deletion into the TL, without explaining why, we seem to be evading this responsibility.
While I share the enthusiasm of highlighting deletions in the TL, I think that the way we are doing it is not satisfactory, and I’m afraid that we would need, at some point, to synthesize all the information regarding deletions, in order to keep only the ones that we editors believe to be relevant for the reader. This would probably imply the deletion of `<del>` tags in TL and the addition of editorial comments whenever necessary.
E.g., 62v partial translation with incomplete french word
>Also, to make plumb lines, which go from the top <del>to make <fr>vif</fr></del> to the bottom
|
non_process
|
s in tl from pantagrueliste reading through tl made me realize the extent to which translated deletions can be problematic they are translated inconsistently many—if not most—of them do not provide much insight into the manuscript and i’m concerned that the noise” they produce will ultimately confuse distract and sometimes even mislead the reader these translated deletions moreover seem to be based on the very questionable assumption that phonological morphological and syntactical errors can be consistently translated from one language to another how do we intend to justify this editorial choice as editors our primary role is to establish a text yet if we transcribe and translate every single deletion into the tl without explaining why we seem to be evading this responsibility while i share the enthusiasm of highlighting deletions in the tl i think that the way we are doing it is not satisfactory and i’m afraid that we would need at some point to synthesize all the information regarding deletions in order to keep only the ones that we editors believe to be relevant for the reader this would probably imply the deletion of tags in tl and the addition of editorial comments whenever necessary e g partial translation with incomplete french word also to make plumb lines which go from the top to make vif to the bottom
| 0
|
263,553
| 28,040,504,749
|
IssuesEvent
|
2023-03-28 18:07:47
|
socialtables/react-image-fallback
|
https://api.github.com/repos/socialtables/react-image-fallback
|
closed
|
CVE-2020-7733 (High) detected in ua-parser-js-0.7.18.tgz - autoclosed
|
security vulnerability
|
## CVE-2020-7733 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ua-parser-js-0.7.18.tgz</b></p></summary>
<p>Lightweight JavaScript-based user-agent string parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.18.tgz">https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.18.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ua-parser-js/package.json</p>
<p>
Dependency Hierarchy:
- prop-types-15.6.1.tgz (Root Library)
- fbjs-0.8.16.tgz
- :x: **ua-parser-js-0.7.18.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/socialtables/react-image-fallback/commit/c7153a7f2cc175073dc8b6baf6898558c21c66a0">c7153a7f2cc175073dc8b6baf6898558c21c66a0</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>
The package ua-parser-js before 0.7.22 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex for Redmi Phones and Mi Pad Tablets UA.
<p>Publish Date: 2020-09-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7733>CVE-2020-7733</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7733">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7733</a></p>
<p>Release Date: 2020-09-16</p>
<p>Fix Resolution (ua-parser-js): 0.7.22</p>
<p>Direct dependency fix Resolution (prop-types): 15.6.2</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"prop-types","packageVersion":"15.6.1","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"prop-types:15.6.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"15.6.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7733","vulnerabilityDetails":"The package ua-parser-js before 0.7.22 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex for Redmi Phones and Mi Pad Tablets UA.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7733","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-7733 (High) detected in ua-parser-js-0.7.18.tgz - autoclosed - ## CVE-2020-7733 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ua-parser-js-0.7.18.tgz</b></p></summary>
<p>Lightweight JavaScript-based user-agent string parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.18.tgz">https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.18.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ua-parser-js/package.json</p>
<p>
Dependency Hierarchy:
- prop-types-15.6.1.tgz (Root Library)
- fbjs-0.8.16.tgz
- :x: **ua-parser-js-0.7.18.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/socialtables/react-image-fallback/commit/c7153a7f2cc175073dc8b6baf6898558c21c66a0">c7153a7f2cc175073dc8b6baf6898558c21c66a0</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>
The package ua-parser-js before 0.7.22 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex for Redmi Phones and Mi Pad Tablets UA.
<p>Publish Date: 2020-09-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7733>CVE-2020-7733</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7733">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7733</a></p>
<p>Release Date: 2020-09-16</p>
<p>Fix Resolution (ua-parser-js): 0.7.22</p>
<p>Direct dependency fix Resolution (prop-types): 15.6.2</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"prop-types","packageVersion":"15.6.1","packageFilePaths":["/package.json"],"isTransitiveDependency":false,"dependencyTree":"prop-types:15.6.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"15.6.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7733","vulnerabilityDetails":"The package ua-parser-js before 0.7.22 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex for Redmi Phones and Mi Pad Tablets UA.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7733","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_process
|
cve high detected in ua parser js tgz autoclosed cve high severity vulnerability vulnerable library ua parser js tgz lightweight javascript based user agent string parser library home page a href path to dependency file package json path to vulnerable library node modules ua parser js package json dependency hierarchy prop types tgz root library fbjs tgz x ua parser js tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package ua parser js before are vulnerable to regular expression denial of service redos via the regex for redmi phones and mi pad tablets ua 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 ua parser js direct dependency fix resolution prop types rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree prop types isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the package ua parser js before are vulnerable to regular expression denial of service redos via the regex for redmi phones and mi pad tablets ua vulnerabilityurl
| 0
|
21,105
| 28,067,698,229
|
IssuesEvent
|
2023-03-29 16:37:52
|
darktable-org/darktable
|
https://api.github.com/repos/darktable-org/darktable
|
closed
|
Diffuse: Additional sharpen presets
|
feature: enhancement scope: UI scope: image processing
|
Recently, two of my presets for the diffuse module have turned out to be relatively versatile for some real-world scenarios.
In contrast to the default lens blur presets, they are engineered more towards providing pixel-level sharpness and halo suppression, with the disadvantage of slight noise amplification.
Regarding to my personal taste, the presets yield quite naturally looking sharpness for medium lens blur as well as slightly defocused portrait shots. The latter use case has been a lifesaver for me several times ;)
Given those presets could be useful for others, too, maybe it might be considerable to ship them with DT?
[presets_sharpen.zip](https://github.com/darktable-org/darktable/files/7017022/presets_sharpen.zip)
A comparison of two 1:1 crops without (first) and with (second) the strong sharpen preset is provided below.
|
1.0
|
Diffuse: Additional sharpen presets - Recently, two of my presets for the diffuse module have turned out to be relatively versatile for some real-world scenarios.
In contrast to the default lens blur presets, they are engineered more towards providing pixel-level sharpness and halo suppression, with the disadvantage of slight noise amplification.
Regarding to my personal taste, the presets yield quite naturally looking sharpness for medium lens blur as well as slightly defocused portrait shots. The latter use case has been a lifesaver for me several times ;)
Given those presets could be useful for others, too, maybe it might be considerable to ship them with DT?
[presets_sharpen.zip](https://github.com/darktable-org/darktable/files/7017022/presets_sharpen.zip)
A comparison of two 1:1 crops without (first) and with (second) the strong sharpen preset is provided below.
|
process
|
diffuse additional sharpen presets recently two of my presets for the diffuse module have turned out to be relatively versatile for some real world scenarios in contrast to the default lens blur presets they are engineered more towards providing pixel level sharpness and halo suppression with the disadvantage of slight noise amplification regarding to my personal taste the presets yield quite naturally looking sharpness for medium lens blur as well as slightly defocused portrait shots the latter use case has been a lifesaver for me several times given those presets could be useful for others too maybe it might be considerable to ship them with dt a comparison of two crops without first and with second the strong sharpen preset is provided below
| 1
|
8,854
| 11,955,671,930
|
IssuesEvent
|
2020-04-04 06:07:35
|
kubeflow/testing
|
https://api.github.com/repos/kubeflow/testing
|
closed
|
Setup kubeflow-testing to be cluster for prow jobs - move off Kubernete's prow instance
|
area/engprod kind/process priority/p1
|
See: GoogleCloudPlatform/oss-test-infra#93
See :kubernetes/test-infra#14343
/assign @scottilee
|
1.0
|
Setup kubeflow-testing to be cluster for prow jobs - move off Kubernete's prow instance - See: GoogleCloudPlatform/oss-test-infra#93
See :kubernetes/test-infra#14343
/assign @scottilee
|
process
|
setup kubeflow testing to be cluster for prow jobs move off kubernete s prow instance see googlecloudplatform oss test infra see kubernetes test infra assign scottilee
| 1
|
810,296
| 30,235,256,427
|
IssuesEvent
|
2023-07-06 09:46:09
|
wanderer-moe/site
|
https://api.github.com/repos/wanderer-moe/site
|
opened
|
create project sekai oc generator
|
enhancement priority: medium d1
|
will be added to d1 (database) only and not as a json file on the cdn, so it'll be released on the same time as #230
|
1.0
|
create project sekai oc generator - will be added to d1 (database) only and not as a json file on the cdn, so it'll be released on the same time as #230
|
non_process
|
create project sekai oc generator will be added to database only and not as a json file on the cdn so it ll be released on the same time as
| 0
|
725,883
| 24,979,357,533
|
IssuesEvent
|
2022-11-02 10:27:12
|
frequenz-floss/frequenz-channels-python
|
https://api.github.com/repos/frequenz-floss/frequenz-channels-python
|
opened
|
Allow sending `None`
|
part:❓ priority:❓ type:enhancement
|
### What's needed?
Users should be able to send **any** value through a channel (or at least any serializable value if at some point channels can be over the wire). This includes `None`.
### Proposed solution
Allow sending `None` by raising an exception instead of returning `None` if a channel is closed.
### Use cases
_No response_
### Alternatives and workarounds
Wrapping the `None` in another type (like `(None,)`).
### Additional context
_No response_
|
1.0
|
Allow sending `None` - ### What's needed?
Users should be able to send **any** value through a channel (or at least any serializable value if at some point channels can be over the wire). This includes `None`.
### Proposed solution
Allow sending `None` by raising an exception instead of returning `None` if a channel is closed.
### Use cases
_No response_
### Alternatives and workarounds
Wrapping the `None` in another type (like `(None,)`).
### Additional context
_No response_
|
non_process
|
allow sending none what s needed users should be able to send any value through a channel or at least any serializable value if at some point channels can be over the wire this includes none proposed solution allow sending none by raising an exception instead of returning none if a channel is closed use cases no response alternatives and workarounds wrapping the none in another type like none additional context no response
| 0
|
18,879
| 24,816,323,750
|
IssuesEvent
|
2022-10-25 13:25:08
|
StormSurgeLive/asgs
|
https://api.github.com/repos/StormSurgeLive/asgs
|
opened
|
Use CF std name instead of netCDF var name in generateXDMF.f90
|
bug postprocessing
|
When writing XML for time varying output, the `Attribute` name should be the standard CF name rather than the name of the corresponding variable in the netCDF file.
|
1.0
|
Use CF std name instead of netCDF var name in generateXDMF.f90 - When writing XML for time varying output, the `Attribute` name should be the standard CF name rather than the name of the corresponding variable in the netCDF file.
|
process
|
use cf std name instead of netcdf var name in generatexdmf when writing xml for time varying output the attribute name should be the standard cf name rather than the name of the corresponding variable in the netcdf file
| 1
|
20,684
| 30,764,666,549
|
IssuesEvent
|
2023-07-30 06:11:48
|
elementor/elementor
|
https://api.github.com/repos/elementor/elementor
|
closed
|
❌ 🧩 🛟 Support Request: ELEMENTSKIT IS CONSTANTLY CREATING ISSUES
|
compatibility/3rd_party mod*
|
### Prerequisites
- [ ] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [ ] The issue still exists against the latest stable version of Elementor.
### Description
HI,
For some reason, Elementskit is giving me constant errors. I think it conflicts with Elementor. If I just deactivate and activate the plugin the problem is solved .... but it is really annoying and unprofessional looking.
<img width="640" alt="Scherm_afbeelding 2023-07-19 om 11 03 04" src="https://github.com/elementor/elementor/assets/140411289/47502898-c73b-46db-90ae-86b00cc37d91">
Could please someone help me out and is someone experiencing the same problem?
https://ubuntumuziektherapie.nl
### Steps to reproduce
install elemenstkit
### Isolating the problem
- [ ] This bug happens with only Elementor plugin active (and Elementor Pro).
- [ ] This bug happens with a Blank WordPress theme active ([Hello theme](https://wordpress.org/themes/hello-elementor/)).
- [ ] I can reproduce this bug consistently following the steps above.
### System Info
x
|
True
|
❌ 🧩 🛟 Support Request: ELEMENTSKIT IS CONSTANTLY CREATING ISSUES - ### Prerequisites
- [ ] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [ ] The issue still exists against the latest stable version of Elementor.
### Description
HI,
For some reason, Elementskit is giving me constant errors. I think it conflicts with Elementor. If I just deactivate and activate the plugin the problem is solved .... but it is really annoying and unprofessional looking.
<img width="640" alt="Scherm_afbeelding 2023-07-19 om 11 03 04" src="https://github.com/elementor/elementor/assets/140411289/47502898-c73b-46db-90ae-86b00cc37d91">
Could please someone help me out and is someone experiencing the same problem?
https://ubuntumuziektherapie.nl
### Steps to reproduce
install elemenstkit
### Isolating the problem
- [ ] This bug happens with only Elementor plugin active (and Elementor Pro).
- [ ] This bug happens with a Blank WordPress theme active ([Hello theme](https://wordpress.org/themes/hello-elementor/)).
- [ ] I can reproduce this bug consistently following the steps above.
### System Info
x
|
non_process
|
❌ 🧩 🛟 support request elementskit is constantly creating issues prerequisites i have searched for similar issues in both open and closed tickets and cannot find a duplicate the issue still exists against the latest stable version of elementor description hi for some reason elementskit is giving me constant errors i think it conflicts with elementor if i just deactivate and activate the plugin the problem is solved but it is really annoying and unprofessional looking img width alt scherm afbeelding om src could please someone help me out and is someone experiencing the same problem steps to reproduce install elemenstkit isolating the problem this bug happens with only elementor plugin active and elementor pro this bug happens with a blank wordpress theme active i can reproduce this bug consistently following the steps above system info x
| 0
|
13,197
| 15,624,222,666
|
IssuesEvent
|
2021-03-21 01:09:43
|
shirou/gopsutil
|
https://api.github.com/repos/shirou/gopsutil
|
closed
|
Freebsd(jail): process.NewProcess doesnt work if no procfs mounted
|
os:freebsd package:process
|
**Describe the bug**
Important, this is within jail. I don't have freshly installed FreeBSD to check what is situation on fresh install.
Within jails procfs is not mounted by default, but /proc exists.
Due to this, process.NewProcess(pid) doesnt work.
The issue is handling within process_posix.go
`func PidExistsWithContext(ctx context.Context, pid int32) (bool, error)`
`if _, err := os.Stat(common.HostProc()); err == nil { //Means that proc filesystem exist`
The issue is that HostProc returns /proc by default, and the directory is really there but if procfs is not in use, it is just empty directory. When stat checks for /proc it is found and presumes procfs is there.
Further down the code it checks if process is within the /proc direcectory and always fails.
`_, err := os.Stat(common.HostProc(strconv.Itoa(int(pid))))`
Even if you are having handling for systems without procfs mounted, it is never called.
**To Reproduce**
```go
_, err := process.NewProcess(int32(os.Getpid()))
```
**Expected behavior**
The check for procfs is inadequate, fast fix would be to instead rather check if /proc is empty while the ultimate solution would be to actually check if procfs is mounted. Workaround would be to mount procfs but it would be nice if this wouldnt be a requirement.
**Environment (please complete the following information):**
- [x] FreeBSD: [
FreeBSD build 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC amd64
12.2-RELEASE-p3
**Additional context**
No cross compiling.
|
1.0
|
Freebsd(jail): process.NewProcess doesnt work if no procfs mounted - **Describe the bug**
Important, this is within jail. I don't have freshly installed FreeBSD to check what is situation on fresh install.
Within jails procfs is not mounted by default, but /proc exists.
Due to this, process.NewProcess(pid) doesnt work.
The issue is handling within process_posix.go
`func PidExistsWithContext(ctx context.Context, pid int32) (bool, error)`
`if _, err := os.Stat(common.HostProc()); err == nil { //Means that proc filesystem exist`
The issue is that HostProc returns /proc by default, and the directory is really there but if procfs is not in use, it is just empty directory. When stat checks for /proc it is found and presumes procfs is there.
Further down the code it checks if process is within the /proc direcectory and always fails.
`_, err := os.Stat(common.HostProc(strconv.Itoa(int(pid))))`
Even if you are having handling for systems without procfs mounted, it is never called.
**To Reproduce**
```go
_, err := process.NewProcess(int32(os.Getpid()))
```
**Expected behavior**
The check for procfs is inadequate, fast fix would be to instead rather check if /proc is empty while the ultimate solution would be to actually check if procfs is mounted. Workaround would be to mount procfs but it would be nice if this wouldnt be a requirement.
**Environment (please complete the following information):**
- [x] FreeBSD: [
FreeBSD build 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC amd64
12.2-RELEASE-p3
**Additional context**
No cross compiling.
|
process
|
freebsd jail process newprocess doesnt work if no procfs mounted describe the bug important this is within jail i don t have freshly installed freebsd to check what is situation on fresh install within jails procfs is not mounted by default but proc exists due to this process newprocess pid doesnt work the issue is handling within process posix go func pidexistswithcontext ctx context context pid bool error if err os stat common hostproc err nil means that proc filesystem exist the issue is that hostproc returns proc by default and the directory is really there but if procfs is not in use it is just empty directory when stat checks for proc it is found and presumes procfs is there further down the code it checks if process is within the proc direcectory and always fails err os stat common hostproc strconv itoa int pid even if you are having handling for systems without procfs mounted it is never called to reproduce go err process newprocess os getpid expected behavior the check for procfs is inadequate fast fix would be to instead rather check if proc is empty while the ultimate solution would be to actually check if procfs is mounted workaround would be to mount procfs but it would be nice if this wouldnt be a requirement environment please complete the following information freebsd freebsd build release freebsd release generic release additional context no cross compiling
| 1
|
194,122
| 15,397,624,888
|
IssuesEvent
|
2021-03-03 22:27:55
|
10up/ElasticPress
|
https://api.github.com/repos/10up/ElasticPress
|
opened
|
Update *-feature WP-CLI commands documentation
|
needs documentation
|
Any of the `*-feature` commands listed [here](https://10up.github.io/ElasticPress/tutorial-wp-cli.html) accept the `--network-wide` flag. We should update the [wp-cli.md](https://github.com/10up/ElasticPress/blob/develop/docs/wp-cli.md) file to reflect that.
For quick access, the related code is in https://github.com/10up/ElasticPress/blob/develop/includes/classes/Command.php, see `list_features`, `activate_feature`, and `deactivate_feature`.
|
1.0
|
Update *-feature WP-CLI commands documentation - Any of the `*-feature` commands listed [here](https://10up.github.io/ElasticPress/tutorial-wp-cli.html) accept the `--network-wide` flag. We should update the [wp-cli.md](https://github.com/10up/ElasticPress/blob/develop/docs/wp-cli.md) file to reflect that.
For quick access, the related code is in https://github.com/10up/ElasticPress/blob/develop/includes/classes/Command.php, see `list_features`, `activate_feature`, and `deactivate_feature`.
|
non_process
|
update feature wp cli commands documentation any of the feature commands listed accept the network wide flag we should update the file to reflect that for quick access the related code is in see list features activate feature and deactivate feature
| 0
|
12,316
| 9,630,930,125
|
IssuesEvent
|
2019-05-15 13:13:43
|
dockstore/dockstore
|
https://api.github.com/repos/dockstore/dockstore
|
opened
|
Get new webservice release working on staging
|
web-service
|
Investigate what is causing the 1.7.0 versions of the webservice to not work on staging.
|
1.0
|
Get new webservice release working on staging - Investigate what is causing the 1.7.0 versions of the webservice to not work on staging.
|
non_process
|
get new webservice release working on staging investigate what is causing the versions of the webservice to not work on staging
| 0
|
17,514
| 12,404,284,441
|
IssuesEvent
|
2020-05-21 15:17:10
|
sciencehistory/scihist_digicoll
|
https://api.github.com/repos/sciencehistory/scihist_digicoll
|
opened
|
Improve our handling of ImageMagick and VIPs
|
infrastructure
|
From our team meeting, right now we rebuild IM and VIPs whenever our build scripts detect updates but building from the source can be slow and make the application update process slow down. This is an issue for rapidly deploying ansible changes to production if there happens to have been a recent change our nightly updates didn't catch due to the timing.
|
1.0
|
Improve our handling of ImageMagick and VIPs - From our team meeting, right now we rebuild IM and VIPs whenever our build scripts detect updates but building from the source can be slow and make the application update process slow down. This is an issue for rapidly deploying ansible changes to production if there happens to have been a recent change our nightly updates didn't catch due to the timing.
|
non_process
|
improve our handling of imagemagick and vips from our team meeting right now we rebuild im and vips whenever our build scripts detect updates but building from the source can be slow and make the application update process slow down this is an issue for rapidly deploying ansible changes to production if there happens to have been a recent change our nightly updates didn t catch due to the timing
| 0
|
7,782
| 10,923,805,350
|
IssuesEvent
|
2019-11-22 08:43:34
|
axa-group/Parsr
|
https://api.github.com/repos/axa-group/Parsr
|
closed
|
Font-size is always 0px on the Vue demo with Tesseract
|
bug gui processing
|
**Summary**
When sending a PDF with only images (such as a scan) and using TesseractExtractor, the font-size is always 0px so the text is invisible on the web interface.
**Steps To Reproduce**
Steps to reproduce the behavior:
1. Send a scanned document to the pipeline from the Vue Web Demo
2. Wait and have a look at the Document Viewer
**Expected behavior**
To be able to read the extracted text.
**Actual behavior**
Nothing shows because font-size is 0.
**Additional context**
I tried on the `develop` branch.
|
1.0
|
Font-size is always 0px on the Vue demo with Tesseract - **Summary**
When sending a PDF with only images (such as a scan) and using TesseractExtractor, the font-size is always 0px so the text is invisible on the web interface.
**Steps To Reproduce**
Steps to reproduce the behavior:
1. Send a scanned document to the pipeline from the Vue Web Demo
2. Wait and have a look at the Document Viewer
**Expected behavior**
To be able to read the extracted text.
**Actual behavior**
Nothing shows because font-size is 0.
**Additional context**
I tried on the `develop` branch.
|
process
|
font size is always on the vue demo with tesseract summary when sending a pdf with only images such as a scan and using tesseractextractor the font size is always so the text is invisible on the web interface steps to reproduce steps to reproduce the behavior send a scanned document to the pipeline from the vue web demo wait and have a look at the document viewer expected behavior to be able to read the extracted text actual behavior nothing shows because font size is additional context i tried on the develop branch
| 1
|
202,481
| 15,286,679,151
|
IssuesEvent
|
2021-02-23 14:57:57
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: schemachange/bulkingest failed
|
C-test-failure O-roachtest O-robot branch-release-20.1 release-blocker
|
[(roachtest).schemachange/bulkingest failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2661563&tab=buildLog) on [release-20.1@90f78268f3b5b08ba838ac3ad164821d2f5a5362](https://github.com/cockroachdb/cockroach/commits/90f78268f3b5b08ba838ac3ad164821d2f5a5362):
```
| main.(*monitor).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2606
| github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup.(*Group).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup/errgroup.go:57
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (2) 2 safe details enclosed
Wraps: (3) output in run_091905.809_n5_workload_run_bulkingest
Wraps: (4) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2661563-1612941348-106-n5cpu4:5 -- ./workload run bulkingest --duration 20m0s {pgurl:1-4} --a 100000000 --b 1 --c 1 --payload-bytes 4 returned
| stderr:
| ./workload: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory
| Error: COMMAND_PROBLEM: exit status 127
| (1) COMMAND_PROBLEM
| Wraps: (2) Node 5. Command with error:
| | ```
| | ./workload run bulkingest --duration 20m0s {pgurl:1-4} --a 100000000 --b 1 --c 1 --payload-bytes 4
| | ```
| Wraps: (3) exit status 127
| Error types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError
|
| stdout:
Wraps: (5) exit status 20
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errutil.withMessage (4) *main.withCommandDetails (5) *exec.ExitError
cluster.go:2628,schemachange.go:401,test_runner.go:749: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
| main.(*monitor).WaitE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2616
| main.(*monitor).Wait
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2624
| main.makeSchemaChangeBulkIngestTest.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/schemachange.go:401
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:749
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
| main.(*monitor).wait.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2672
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
| main.init
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2586
| runtime.doInit
| /usr/local/go/src/runtime/proc.go:5652
| runtime.main
| /usr/local/go/src/runtime/proc.go:191
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withMessage (3) *withstack.withStack (4) *errutil.withMessage (5) *withstack.withStack (6) *errors.errorString
```
<details><summary>More</summary><p>
Artifacts: [/schemachange/bulkingest](https://teamcity.cockroachdb.com/viewLog.html?buildId=2661563&tab=artifacts#/schemachange/bulkingest)
Related:
- #60244 roachtest: schemachange/bulkingest failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-60149](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-60149) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aschemachange%2Fbulkingest.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
2.0
|
roachtest: schemachange/bulkingest failed - [(roachtest).schemachange/bulkingest failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2661563&tab=buildLog) on [release-20.1@90f78268f3b5b08ba838ac3ad164821d2f5a5362](https://github.com/cockroachdb/cockroach/commits/90f78268f3b5b08ba838ac3ad164821d2f5a5362):
```
| main.(*monitor).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2606
| github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup.(*Group).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup/errgroup.go:57
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (2) 2 safe details enclosed
Wraps: (3) output in run_091905.809_n5_workload_run_bulkingest
Wraps: (4) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2661563-1612941348-106-n5cpu4:5 -- ./workload run bulkingest --duration 20m0s {pgurl:1-4} --a 100000000 --b 1 --c 1 --payload-bytes 4 returned
| stderr:
| ./workload: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory
| Error: COMMAND_PROBLEM: exit status 127
| (1) COMMAND_PROBLEM
| Wraps: (2) Node 5. Command with error:
| | ```
| | ./workload run bulkingest --duration 20m0s {pgurl:1-4} --a 100000000 --b 1 --c 1 --payload-bytes 4
| | ```
| Wraps: (3) exit status 127
| Error types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError
|
| stdout:
Wraps: (5) exit status 20
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errutil.withMessage (4) *main.withCommandDetails (5) *exec.ExitError
cluster.go:2628,schemachange.go:401,test_runner.go:749: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
| main.(*monitor).WaitE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2616
| main.(*monitor).Wait
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2624
| main.makeSchemaChangeBulkIngestTest.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/schemachange.go:401
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:749
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
| main.(*monitor).wait.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2672
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
| main.init
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2586
| runtime.doInit
| /usr/local/go/src/runtime/proc.go:5652
| runtime.main
| /usr/local/go/src/runtime/proc.go:191
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withMessage (3) *withstack.withStack (4) *errutil.withMessage (5) *withstack.withStack (6) *errors.errorString
```
<details><summary>More</summary><p>
Artifacts: [/schemachange/bulkingest](https://teamcity.cockroachdb.com/viewLog.html?buildId=2661563&tab=artifacts#/schemachange/bulkingest)
Related:
- #60244 roachtest: schemachange/bulkingest failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-60149](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-60149) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aschemachange%2Fbulkingest.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
non_process
|
roachtest schemachange bulkingest failed on main monitor go home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go github com cockroachdb cockroach vendor golang org x sync errgroup group go home agent work go src github com cockroachdb cockroach vendor golang org x sync errgroup errgroup go runtime goexit usr local go src runtime asm s wraps safe details enclosed wraps output in run workload run bulkingest wraps home agent work go src github com cockroachdb cockroach bin roachprod run teamcity workload run bulkingest duration pgurl a b c payload bytes returned stderr workload error while loading shared libraries libncurses so cannot open shared object file no such file or directory error command problem exit status command problem wraps node command with error workload run bulkingest duration pgurl a b c payload bytes wraps exit status error types errors cmd hintdetail withdetail exec exiterror stdout wraps exit status error types withstack withstack safedetails withsafedetails errutil withmessage main withcommanddetails exec exiterror cluster go schemachange go test runner go monitor failure monitor task failed t fatal was called attached stack trace main monitor waite home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main makeschemachangebulkingesttest home agent work go src github com cockroachdb cockroach pkg cmd roachtest schemachange go main testrunner runtest home agent work go src github com cockroachdb cockroach pkg cmd roachtest test runner go wraps monitor failure wraps attached stack trace main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go wraps monitor task failed wraps attached stack trace main init home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go runtime doinit usr local go src runtime proc go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps t fatal was called error types withstack withstack errutil withmessage withstack withstack errutil withmessage withstack withstack errors errorstring more artifacts related roachtest schemachange bulkingest failed powered by
| 0
|
422,751
| 12,287,479,983
|
IssuesEvent
|
2020-05-09 12:24:09
|
googleapis/elixir-google-api
|
https://api.github.com/repos/googleapis/elixir-google-api
|
opened
|
Synthesis failed for CloudScheduler
|
api: cloudscheduler autosynth failure priority: p1 type: bug
|
Hello! Autosynth couldn't regenerate CloudScheduler. :broken_heart:
Here's the output from running `synth.py`:
```
2020-05-09 05:08:03 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-09 05:08:03,029 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-cloudscheduler'
2020-05-09 05:08:04 [INFO] Running synthtool
2020-05-09 05:08:04,692 autosynth > Running synthtool
2020-05-09 05:08:04 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/cloud_scheduler/synth.metadata', 'synth.py', '--']
2020-05-09 05:08:04,692 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/cloud_scheduler/synth.metadata', 'synth.py', '--']
2020-05-09 05:08:04,902 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-cloudscheduler
nothing to commit, working tree clean
2020-05-09 05:08:05,068 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-09 05:08:05,518 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh CloudScheduler
2020-05-09 05:08:10,511 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
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 180, in __exit__
write(self.metadata_file_path)
File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/cloud_scheduler/synth.metadata'
2020-05-09 05:08:10 [ERROR] Synthesis failed
2020-05-09 05:08:10,543 autosynth > Synthesis failed
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 599, in <module>
main()
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
return _inner_main(temp_dir)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
).synthesize(base_synth_log_path)
File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, 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/cloud_scheduler/synth.metadata', 'synth.py', '--', 'CloudScheduler']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](https://sponge/11ff3741-9158-4831-8681-fff828f77e1a).
|
1.0
|
Synthesis failed for CloudScheduler - Hello! Autosynth couldn't regenerate CloudScheduler. :broken_heart:
Here's the output from running `synth.py`:
```
2020-05-09 05:08:03 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-09 05:08:03,029 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-cloudscheduler'
2020-05-09 05:08:04 [INFO] Running synthtool
2020-05-09 05:08:04,692 autosynth > Running synthtool
2020-05-09 05:08:04 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/cloud_scheduler/synth.metadata', 'synth.py', '--']
2020-05-09 05:08:04,692 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/cloud_scheduler/synth.metadata', 'synth.py', '--']
2020-05-09 05:08:04,902 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-cloudscheduler
nothing to commit, working tree clean
2020-05-09 05:08:05,068 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-09 05:08:05,518 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh CloudScheduler
2020-05-09 05:08:10,511 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
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 180, in __exit__
write(self.metadata_file_path)
File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/cloud_scheduler/synth.metadata'
2020-05-09 05:08:10 [ERROR] Synthesis failed
2020-05-09 05:08:10,543 autosynth > Synthesis failed
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 599, in <module>
main()
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
return _inner_main(temp_dir)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
).synthesize(base_synth_log_path)
File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, 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/cloud_scheduler/synth.metadata', 'synth.py', '--', 'CloudScheduler']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](https://sponge/11ff3741-9158-4831-8681-fff828f77e1a).
|
non_process
|
synthesis failed for cloudscheduler hello autosynth couldn t regenerate cloudscheduler broken heart here s the output from running synth py logs will be written to tmpfs src github synthtool logs googleapis elixir google api autosynth logs will be written to tmpfs src github synthtool logs googleapis elixir google api switched to branch autosynth cloudscheduler running synthtool autosynth running synthtool autosynth synthtool executing home kbuilder cache synthtool elixir google api synth py on branch autosynth cloudscheduler nothing to commit working tree clean synthtool cloning synthtool running docker run rm v home kbuilder cache synthtool elixir google api workspace v var run docker sock var run docker sock e user group w workspace gcr io cloud devrel public resources scripts generate client sh cloudscheduler synthtool no files in sources home kbuilder cache synthtool elixir google api clients were copied does the source contain files 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 write self metadata file path file tmpfs src github synthtool synthtool metadata py line in write with open outfile w as fh filenotfounderror no such file or directory clients cloud scheduler synth metadata synthesis failed autosynth synthesis failed 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 base synth log path 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
|
168,403
| 20,761,555,463
|
IssuesEvent
|
2022-03-15 16:35:02
|
linkerd/linkerd2
|
https://api.github.com/repos/linkerd/linkerd2
|
closed
|
linkerd-policy-controller: [RUSTSEC-2022-0013] Regexes with large repetitions on empty sub-expressions take a very long time to parse
|
area/controller rust security
|
The Rust Security Response WG was notified that the `regex` crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the `regex` crate is used to parse untrusted regexes. Other uses
of the `regex` crate are not affected by this vulnerability.
## Overview
The `regex` crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent
untrusted regexes to take an arbitrary amount of time during parsing, and it's
possible to craft regexes that bypass such mitigations. This makes it possible
to perform denial of service attacks by sending specially crafted regexes to
services accepting user-controlled, untrusted regexes.
## Affected versions
All versions of the `regex` crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from `regex` 1.5.5.
## Mitigations
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the `regex` crate.
Unfortunately there is no fixed set of problematic regexes, as there are
practically infinite regexes that could be crafted to exploit this
vulnerability. Because of this, we do not recommend denying known problematic
regexes.
## Acknowledgements
We want to thank Addison Crump for responsibly disclosing this to us according
to the [Rust security policy][1], and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini
for coordinating the disclosure and writing this advisory.
[1]: https://www.rust-lang.org/policies/security
|
True
|
linkerd-policy-controller: [RUSTSEC-2022-0013] Regexes with large repetitions on empty sub-expressions take a very long time to parse - The Rust Security Response WG was notified that the `regex` crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the `regex` crate is used to parse untrusted regexes. Other uses
of the `regex` crate are not affected by this vulnerability.
## Overview
The `regex` crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent
untrusted regexes to take an arbitrary amount of time during parsing, and it's
possible to craft regexes that bypass such mitigations. This makes it possible
to perform denial of service attacks by sending specially crafted regexes to
services accepting user-controlled, untrusted regexes.
## Affected versions
All versions of the `regex` crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from `regex` 1.5.5.
## Mitigations
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the `regex` crate.
Unfortunately there is no fixed set of problematic regexes, as there are
practically infinite regexes that could be crafted to exploit this
vulnerability. Because of this, we do not recommend denying known problematic
regexes.
## Acknowledgements
We want to thank Addison Crump for responsibly disclosing this to us according
to the [Rust security policy][1], and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini
for coordinating the disclosure and writing this advisory.
[1]: https://www.rust-lang.org/policies/security
|
non_process
|
linkerd policy controller regexes with large repetitions on empty sub expressions take a very long time to parse the rust security response wg was notified that the regex crate did not properly limit the complexity of the regular expressions regex it parses an attacker could use this security issue to perform a denial of service by sending a specially crafted regex to a service accepting untrusted regexes no known vulnerability is present when parsing untrusted input with trusted regexes this issue has been assigned cve the severity of this vulnerability is high when the regex crate is used to parse untrusted regexes other uses of the regex crate are not affected by this vulnerability overview the regex crate features built in mitigations to prevent denial of service attacks caused by untrusted regexes or untrusted input matched by trusted regexes those tunable mitigations already provide sane defaults to prevent attacks this guarantee is documented and it s considered part of the crate s api unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing and it s possible to craft regexes that bypass such mitigations this makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user controlled untrusted regexes affected versions all versions of the regex crate before or equal to are affected by this issue the fix is include starting from regex mitigations we recommend everyone accepting user controlled regexes to upgrade immediately to the latest version of the regex crate unfortunately there is no fixed set of problematic regexes as there are practically infinite regexes that could be crafted to exploit this vulnerability because of this we do not recommend denying known problematic regexes acknowledgements we want to thank addison crump for responsibly disclosing this to us according to the and for helping review the fix we also want to thank andrew gallant for developing the fix and pietro albini for coordinating the disclosure and writing this advisory
| 0
|
263,718
| 23,076,405,827
|
IssuesEvent
|
2022-07-26 00:20:03
|
ClickHouse/ClickHouse
|
https://api.github.com/repos/ClickHouse/ClickHouse
|
closed
|
heap-buffer-overflow in `avro::DataFileReaderBase::readDataBlock()`
|
testing
|
https://s3.amazonaws.com/clickhouse-test-reports/0/fccdb6583c998888a5f94240a6ba2d3e4b4f0ba0/stress_test__address__actions_.html
```
==549==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200037c8cc at pc 0x000034e6e371 bp 0x7fc5a2e97e50 sp 0x7fc5a2e97e48
READ of size 1 at 0x60200037c8cc thread T553 (QueryPipelineEx)
#0 0x34e6e370 in avro::DataFileReaderBase::readDataBlock() obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:418:18
#1 0x34e70485 in avro::DataFileReaderBase::hasMore() obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:338:9
#2 0x29db5bb9 in DB::AvroRowInputFormat::readRow(std::__1::vector<COW<DB::IColumn>::mutable_ptr<DB::IColumn>, std::__1::allocator<COW<DB::IColumn>::mutable_ptr<DB::IColumn> > >&, DB::RowReadExtension&) obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/AvroRowInputFormat.cpp:632:26
#3 0x29dfb00d in DB::IRowInputFormat::generate() obj-x86_64-linux-gnu/../src/Processors/Formats/IRowInputFormat.cpp:81:36
#4 0x29cd55af in DB::ISource::tryGenerate() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:79:18
#5 0x29cd489c in DB::ISource::work() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:53:26
#6 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#7 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#8 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#9 0x29d0d0b7 in DB::PipelineExecutor::executeStep(std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:115:5
#10 0x29d39545 in DB::PullingPipelineExecutor::pull(DB::Chunk&) obj-x86_64-linux-gnu/../src/Processors/Executors/PullingPipelineExecutor.cpp:50:20
#11 0x288c8b9c in DB::StorageFileSource::generate() obj-x86_64-linux-gnu/../src/Storages/StorageFile.cpp:473:25
#12 0x29cd55af in DB::ISource::tryGenerate() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:79:18
#13 0x29cd489c in DB::ISource::work() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:53:26
#14 0x2a341625 in DB::SourceWithProgress::work() obj-x86_64-linux-gnu/../src/Processors/Sources/SourceWithProgress.cpp:67:30
#15 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#16 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#17 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#18 0x29d0c02e in DB::PipelineExecutor::executeSingleThread(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:178:5
#19 0x29d0c02e in DB::PipelineExecutor::executeImpl(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:329:9
#20 0x29d0b2ef in DB::PipelineExecutor::execute(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:84:9
#21 0x29d36fba in DB::threadFunction(DB::PullingAsyncPipelineExecutor::Data&, std::__1::shared_ptr<DB::ThreadGroupStatus>, unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PullingAsyncPipelineExecutor.cpp:85:24
#22 0x29d36fba in DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0::operator()() const obj-x86_64-linux-gnu/../src/Processors/Executors/PullingAsyncPipelineExecutor.cpp:112:13
#23 0x29d36fba in decltype(std::__1::forward<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&>(fp)()) std::__1::__invoke_constexpr<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&) obj-x86_64-linux-gnu/../contrib/libcxx/include/type_traits:3682:1
#24 0x29d36fba in decltype(auto) std::__1::__apply_tuple_impl<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&, std::__1::__tuple_indices<>) obj-x86_64-linux-gnu/../contrib/libcxx/include/tuple:1415:1
#25 0x29d36fba in decltype(auto) std::__1::apply<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&) obj-x86_64-linux-gnu/../contrib/libcxx/include/tuple:1424:1
#26 0x29d36fba in ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()::operator()() obj-x86_64-linux-gnu/../src/Common/ThreadPool.h:188:13
#27 0x29d36fba in decltype(std::__1::forward<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(fp)()) std::__1::__invoke<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&) obj-x86_64-linux-gnu/../contrib/libcxx/include/type_traits:3676:1
#28 0x29d36fba in void std::__1::__invoke_void_return_wrapper<void>::__call<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()&>(ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()&) obj-x86_64-linux-gnu/../contrib/libcxx/include/__functional_base:348:9
#29 0x29d36fba in std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'(), void ()>::operator()() obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:1608:12
#30 0x29d36fba in void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'(), void ()> >(std::__1::__function::__policy_storage const*) obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:2089:16
#31 0xc59a966 in std::__1::__function::__policy_func<void ()>::operator()() const obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:2221:16
#32 0xc59a966 in std::__1::function<void ()>::operator()() const obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:2560:12
#33 0xc59a966 in ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:274:17
#34 0xc5a2cd6 in void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()::operator()() const obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:139:73
#35 0xc5a2cd6 in decltype(std::__1::forward<void>(fp)()) std::__1::__invoke<void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(void&&) obj-x86_64-linux-gnu/../contrib/libcxx/include/type_traits:3676:1
#36 0xc5a2cd6 in void std::__1::__thread_execute<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(std::__1::tuple<void, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>&, std::__1::__tuple_indices<>) obj-x86_64-linux-gnu/../contrib/libcxx/include/thread:280:5
#37 0xc5a2cd6 in void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()> >(void*) obj-x86_64-linux-gnu/../contrib/libcxx/include/thread:291:5
#38 0x7fc802f74608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
#39 0x7fc802e9b292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
0x60200037c8cc is located 4 bytes to the left of 8-byte region [0x60200037c8d0,0x60200037c8d8)
allocated by thread T553 (QueryPipelineEx) here:
#0 0xc47babd in operator new(unsigned long) (/usr/bin/clickhouse+0xc47babd)
#1 0x34e74e28 in void* std::__1::__libcpp_operator_new<unsigned long>(unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/new:235:10
#2 0x34e74e28 in std::__1::__libcpp_allocate(unsigned long, unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/new:261:10
#3 0x34e74e28 in std::__1::allocator<char>::allocate(unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/memory:840:38
#4 0x34e74e28 in std::__1::allocator_traits<std::__1::allocator<char> >::allocate(std::__1::allocator<char>&, unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/__memory/allocator_traits.h:468:21
#5 0x34e74e28 in std::__1::__split_buffer<char, std::__1::allocator<char>&>::__split_buffer(unsigned long, unsigned long, std::__1::allocator<char>&) obj-x86_64-linux-gnu/../contrib/libcxx/include/__split_buffer:314:29
#6 0x34e74e28 in std::__1::enable_if<(__is_cpp17_forward_iterator<unsigned char const*>::value) && (is_constructible<char, std::__1::iterator_traits<unsigned char const*>::reference>::value), std::__1::__wrap_iter<char*> >::type std::__1::vector<char, std::__1::allocator<char> >::insert<unsigned char const*>(std::__1::__wrap_iter<char const*>, unsigned char const*, unsigned char const*) obj-x86_64-linux-gnu/../contrib/libcxx/include/vector:2010:57
#7 0x34e6ddc2 in avro::DataFileReaderBase::readDataBlock() obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:415:25
#8 0x29dfa98b in DB::IRowInputFormat::generate() obj-x86_64-linux-gnu/../src/Processors/Formats/IRowInputFormat.cpp:58:9
#9 0x29cd55af in DB::ISource::tryGenerate() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:79:18
#10 0x29cd489c in DB::ISource::work() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:53:26
#11 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#12 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#13 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#14 0x29d0d0b7 in DB::PipelineExecutor::executeStep(std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:115:5
#15 0x29d39545 in DB::PullingPipelineExecutor::pull(DB::Chunk&) obj-x86_64-linux-gnu/../src/Processors/Executors/PullingPipelineExecutor.cpp:50:20
Thread T553 (QueryPipelineEx) created by T447 (TCPHandler) here:
#0 0xc43439c in pthread_create (/usr/bin/clickhouse+0xc43439c)
#1 0xc5a1cb6 in std::__1::__libcpp_thread_create(unsigned long*, void* (*)(void*), void*) obj-x86_64-linux-gnu/../contrib/libcxx/include/__threading_support:509:10
#2 0xc5a1cb6 in std::__1::thread::thread<void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'(), void>(void&&) obj-x86_64-linux-gnu/../contrib/libcxx/include/thread:307:16
#3 0xc597279 in void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:139:35
#4 0xc5a5745 in ThreadPoolImpl<std::__1::thread>::scheduleOrThrow(std::__1::function<void ()>, int, unsigned long) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:171:5
#5 0xc5a5745 in ThreadFromGlobalPool::ThreadFromGlobalPool<void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(void&&) obj-x86_64-linux-gnu/../src/Common/ThreadPool.h:169:38
#6 0xc59c5ff in void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:139:35
#7 0xc59bc95 in ThreadPoolImpl<ThreadFromGlobalPool>::scheduleOrThrowOnError(std::__1::function<void ()>, int) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:159:5
#8 0x29f6384a in DB::ParallelFormattingOutputFormat::scheduleFormatterThreadForUnitWithNumber(unsigned long, unsigned long) obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/ParallelFormattingOutputFormat.h:251:14
#9 0x29f5ffc8 in DB::ParallelFormattingOutputFormat::addChunk(DB::Chunk, DB::ParallelFormattingOutputFormat::ProcessingUnitType, bool) obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/ParallelFormattingOutputFormat.cpp:66:9
#10 0x29f5f410 in DB::ParallelFormattingOutputFormat::finalizeImpl() obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/ParallelFormattingOutputFormat.cpp:13:9
#11 0x29d4fe37 in DB::IOutputFormat::finalize() obj-x86_64-linux-gnu/../src/Processors/Formats/IOutputFormat.cpp:125:5
#12 0x29d4fe37 in DB::IOutputFormat::work() obj-x86_64-linux-gnu/../src/Processors/Formats/IOutputFormat.cpp:75:9
#13 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#14 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#15 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#16 0x29d0c02e in DB::PipelineExecutor::executeSingleThread(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:178:5
#17 0x29d0c02e in DB::PipelineExecutor::executeImpl(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:329:9
#18 0x29d0b2ef in DB::PipelineExecutor::execute(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:84:9
#19 0x29d08680 in DB::CompletedPipelineExecutor::execute() obj-x86_64-linux-gnu/../src/Processors/Executors/CompletedPipelineExecutor.cpp:101:18
#20 0x28054573 in DB::executeQuery(DB::ReadBuffer&, DB::WriteBuffer&, bool, std::__1::shared_ptr<DB::Context>, std::__1::function<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)>, std::__1::optional<DB::FormatSettings> const&) obj-x86_64-linux-gnu/../src/Interpreters/executeQuery.cpp:1126:22
#21 0x29b20fa6 in DB::HTTPHandler::processQuery(DB::HTTPServerRequest&, DB::HTMLForm&, DB::HTTPServerResponse&, DB::HTTPHandler::Output&, std::__1::optional<DB::CurrentThread::QueryScope>&) obj-x86_64-linux-gnu/../src/Server/HTTPHandler.cpp:790:5
#22 0x29b2e491 in DB::HTTPHandler::handleRequest(DB::HTTPServerRequest&, DB::HTTPServerResponse&) obj-x86_64-linux-gnu/../src/Server/HTTPHandler.cpp:928:9
#23 0x29c47a54 in DB::HTTPServerConnection::run() obj-x86_64-linux-gnu/../src/Server/HTTP/HTTPServerConnection.cpp:65:34
#24 0x30873dce in Poco::Net::TCPServerConnection::start() obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServerConnection.cpp:43:3
#25 0x30874b40 in Poco::Net::TCPServerDispatcher::run() obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServerDispatcher.cpp:115:20
#26 0x30d57265 in Poco::PooledThread::run() obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:199:14
#27 0x30d50519 in Poco::ThreadImpl::runnableEntry(void*) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:345:27
#28 0x7fc802f74608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
Thread T447 (TCPHandler) created by T243 here:
#0 0xc43439c in pthread_create (/usr/bin/clickhouse+0xc43439c)
#1 0x30d4f7c9 in Poco::ThreadImpl::startImpl(Poco::SharedPtr<Poco::Runnable, Poco::ReferenceCounter, Poco::ReleasePolicy<Poco::Runnable> >) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:202:6
#2 0x30d5285d in Poco::Thread::start(Poco::Runnable&) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread.cpp:128:2
#3 0x30d5b359 in Poco::PooledThread::start() obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:85:10
#4 0x30d5b359 in Poco::ThreadPool::getThread() obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:461:14
#5 0x30d5ba36 in Poco::ThreadPool::startWithPriority(Poco::Thread::Priority, Poco::Runnable&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:365:2
#6 0x30875727 in Poco::Net::TCPServerDispatcher::enqueue(Poco::Net::StreamSocket const&) obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServerDispatcher.cpp:152:17
#7 0x30873600 in Poco::Net::TCPServer::run() obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServer.cpp:148:21
#8 0x30d50519 in Poco::ThreadImpl::runnableEntry(void*) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:345:27
#9 0x7fc802f74608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
Thread T243 created by T0 here:
#0 0xc43439c in pthread_create (/usr/bin/clickhouse+0xc43439c)
#1 0x30d4f7c9 in Poco::ThreadImpl::startImpl(Poco::SharedPtr<Poco::Runnable, Poco::ReferenceCounter, Poco::ReleasePolicy<Poco::Runnable> >) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:202:6
#2 0x30d5285d in Poco::Thread::start(Poco::Runnable&) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread.cpp:128:2
#3 0xc4a9a3c in DB::ProtocolServerAdapter::start() obj-x86_64-linux-gnu/../src/Server/ProtocolServerAdapter.h:29:26
#4 0xc4a9a3c in DB::Server::main(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) obj-x86_64-linux-gnu/../programs/server/Server.cpp:1443:24
#5 0x308a7d1a in Poco::Util::Application::run() obj-x86_64-linux-gnu/../contrib/poco/Util/src/Application.cpp:334:8
#6 0xc48a398 in DB::Server::run() obj-x86_64-linux-gnu/../programs/server/Server.cpp:447:25
#7 0x308ed39d in Poco::Util::ServerApplication::run(int, char**) obj-x86_64-linux-gnu/../contrib/poco/Util/src/ServerApplication.cpp:611:9
#8 0xc483afd in mainEntryClickHouseServer(int, char**) obj-x86_64-linux-gnu/../programs/server/Server.cpp:188:20
#9 0xc47f688 in main obj-x86_64-linux-gnu/../programs/main.cpp:378:12
#10 0x7fc802da00b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
SUMMARY: AddressSanitizer: heap-buffer-overflow obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:418:18 in avro::DataFileReaderBase::readDataBlock()
Shadow bytes around the buggy address:
0x0c04800678c0: fa fa fa fa fa fa fd fa fa fa fd fd fa fa fa fa
0x0c04800678d0: fa fa fd fd fa fa fd fd fa fa 02 fa fa fa fa fa
0x0c04800678e0: fa fa fd fd fa fa fa fa fa fa fa fa fa fa fa fa
0x0c04800678f0: fa fa fd fd fa fa fa fa fa fa 00 00 fa fa 00 00
0x0c0480067900: fa fa fd fd fa fa fa fa fa fa fd fa fa fa fa fa
=>0x0c0480067910: fa fa 00 00 fa fa fa fa fa[fa]fc fa fa fa fd fd
0x0c0480067920: fa fa fa fa fa fa fd fd fa fa fd fd fa fa fd fd
0x0c0480067930: fa fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa
0x0c0480067940: fa fa fd fd fa fa fa fa fa fa fa fa fa fa fd fd
0x0c0480067950: fa fa fd fa fa fa fa fa fa fa fa fa fa fa fd fd
0x0c0480067960: fa fa fa fa fa fa fd fa fa fa fd fa fa fa fd fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==549==ABORTING
```
|
1.0
|
heap-buffer-overflow in `avro::DataFileReaderBase::readDataBlock()` - https://s3.amazonaws.com/clickhouse-test-reports/0/fccdb6583c998888a5f94240a6ba2d3e4b4f0ba0/stress_test__address__actions_.html
```
==549==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200037c8cc at pc 0x000034e6e371 bp 0x7fc5a2e97e50 sp 0x7fc5a2e97e48
READ of size 1 at 0x60200037c8cc thread T553 (QueryPipelineEx)
#0 0x34e6e370 in avro::DataFileReaderBase::readDataBlock() obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:418:18
#1 0x34e70485 in avro::DataFileReaderBase::hasMore() obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:338:9
#2 0x29db5bb9 in DB::AvroRowInputFormat::readRow(std::__1::vector<COW<DB::IColumn>::mutable_ptr<DB::IColumn>, std::__1::allocator<COW<DB::IColumn>::mutable_ptr<DB::IColumn> > >&, DB::RowReadExtension&) obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/AvroRowInputFormat.cpp:632:26
#3 0x29dfb00d in DB::IRowInputFormat::generate() obj-x86_64-linux-gnu/../src/Processors/Formats/IRowInputFormat.cpp:81:36
#4 0x29cd55af in DB::ISource::tryGenerate() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:79:18
#5 0x29cd489c in DB::ISource::work() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:53:26
#6 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#7 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#8 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#9 0x29d0d0b7 in DB::PipelineExecutor::executeStep(std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:115:5
#10 0x29d39545 in DB::PullingPipelineExecutor::pull(DB::Chunk&) obj-x86_64-linux-gnu/../src/Processors/Executors/PullingPipelineExecutor.cpp:50:20
#11 0x288c8b9c in DB::StorageFileSource::generate() obj-x86_64-linux-gnu/../src/Storages/StorageFile.cpp:473:25
#12 0x29cd55af in DB::ISource::tryGenerate() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:79:18
#13 0x29cd489c in DB::ISource::work() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:53:26
#14 0x2a341625 in DB::SourceWithProgress::work() obj-x86_64-linux-gnu/../src/Processors/Sources/SourceWithProgress.cpp:67:30
#15 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#16 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#17 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#18 0x29d0c02e in DB::PipelineExecutor::executeSingleThread(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:178:5
#19 0x29d0c02e in DB::PipelineExecutor::executeImpl(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:329:9
#20 0x29d0b2ef in DB::PipelineExecutor::execute(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:84:9
#21 0x29d36fba in DB::threadFunction(DB::PullingAsyncPipelineExecutor::Data&, std::__1::shared_ptr<DB::ThreadGroupStatus>, unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PullingAsyncPipelineExecutor.cpp:85:24
#22 0x29d36fba in DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0::operator()() const obj-x86_64-linux-gnu/../src/Processors/Executors/PullingAsyncPipelineExecutor.cpp:112:13
#23 0x29d36fba in decltype(std::__1::forward<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&>(fp)()) std::__1::__invoke_constexpr<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&) obj-x86_64-linux-gnu/../contrib/libcxx/include/type_traits:3682:1
#24 0x29d36fba in decltype(auto) std::__1::__apply_tuple_impl<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&, std::__1::__tuple_indices<>) obj-x86_64-linux-gnu/../contrib/libcxx/include/tuple:1415:1
#25 0x29d36fba in decltype(auto) std::__1::apply<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&, std::__1::tuple<>&) obj-x86_64-linux-gnu/../contrib/libcxx/include/tuple:1424:1
#26 0x29d36fba in ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()::operator()() obj-x86_64-linux-gnu/../src/Common/ThreadPool.h:188:13
#27 0x29d36fba in decltype(std::__1::forward<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(fp)()) std::__1::__invoke<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()&>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&) obj-x86_64-linux-gnu/../contrib/libcxx/include/type_traits:3676:1
#28 0x29d36fba in void std::__1::__invoke_void_return_wrapper<void>::__call<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()&>(ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'()&) obj-x86_64-linux-gnu/../contrib/libcxx/include/__functional_base:348:9
#29 0x29d36fba in std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'(), void ()>::operator()() obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:1608:12
#30 0x29d36fba in void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0>(DB::PullingAsyncPipelineExecutor::pull(DB::Chunk&, unsigned long)::$_0&&)::'lambda'(), void ()> >(std::__1::__function::__policy_storage const*) obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:2089:16
#31 0xc59a966 in std::__1::__function::__policy_func<void ()>::operator()() const obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:2221:16
#32 0xc59a966 in std::__1::function<void ()>::operator()() const obj-x86_64-linux-gnu/../contrib/libcxx/include/functional:2560:12
#33 0xc59a966 in ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:274:17
#34 0xc5a2cd6 in void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()::operator()() const obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:139:73
#35 0xc5a2cd6 in decltype(std::__1::forward<void>(fp)()) std::__1::__invoke<void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(void&&) obj-x86_64-linux-gnu/../contrib/libcxx/include/type_traits:3676:1
#36 0xc5a2cd6 in void std::__1::__thread_execute<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(std::__1::tuple<void, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>&, std::__1::__tuple_indices<>) obj-x86_64-linux-gnu/../contrib/libcxx/include/thread:280:5
#37 0xc5a2cd6 in void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()> >(void*) obj-x86_64-linux-gnu/../contrib/libcxx/include/thread:291:5
#38 0x7fc802f74608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
#39 0x7fc802e9b292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
0x60200037c8cc is located 4 bytes to the left of 8-byte region [0x60200037c8d0,0x60200037c8d8)
allocated by thread T553 (QueryPipelineEx) here:
#0 0xc47babd in operator new(unsigned long) (/usr/bin/clickhouse+0xc47babd)
#1 0x34e74e28 in void* std::__1::__libcpp_operator_new<unsigned long>(unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/new:235:10
#2 0x34e74e28 in std::__1::__libcpp_allocate(unsigned long, unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/new:261:10
#3 0x34e74e28 in std::__1::allocator<char>::allocate(unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/memory:840:38
#4 0x34e74e28 in std::__1::allocator_traits<std::__1::allocator<char> >::allocate(std::__1::allocator<char>&, unsigned long) obj-x86_64-linux-gnu/../contrib/libcxx/include/__memory/allocator_traits.h:468:21
#5 0x34e74e28 in std::__1::__split_buffer<char, std::__1::allocator<char>&>::__split_buffer(unsigned long, unsigned long, std::__1::allocator<char>&) obj-x86_64-linux-gnu/../contrib/libcxx/include/__split_buffer:314:29
#6 0x34e74e28 in std::__1::enable_if<(__is_cpp17_forward_iterator<unsigned char const*>::value) && (is_constructible<char, std::__1::iterator_traits<unsigned char const*>::reference>::value), std::__1::__wrap_iter<char*> >::type std::__1::vector<char, std::__1::allocator<char> >::insert<unsigned char const*>(std::__1::__wrap_iter<char const*>, unsigned char const*, unsigned char const*) obj-x86_64-linux-gnu/../contrib/libcxx/include/vector:2010:57
#7 0x34e6ddc2 in avro::DataFileReaderBase::readDataBlock() obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:415:25
#8 0x29dfa98b in DB::IRowInputFormat::generate() obj-x86_64-linux-gnu/../src/Processors/Formats/IRowInputFormat.cpp:58:9
#9 0x29cd55af in DB::ISource::tryGenerate() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:79:18
#10 0x29cd489c in DB::ISource::work() obj-x86_64-linux-gnu/../src/Processors/ISource.cpp:53:26
#11 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#12 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#13 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#14 0x29d0d0b7 in DB::PipelineExecutor::executeStep(std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:115:5
#15 0x29d39545 in DB::PullingPipelineExecutor::pull(DB::Chunk&) obj-x86_64-linux-gnu/../src/Processors/Executors/PullingPipelineExecutor.cpp:50:20
Thread T553 (QueryPipelineEx) created by T447 (TCPHandler) here:
#0 0xc43439c in pthread_create (/usr/bin/clickhouse+0xc43439c)
#1 0xc5a1cb6 in std::__1::__libcpp_thread_create(unsigned long*, void* (*)(void*), void*) obj-x86_64-linux-gnu/../contrib/libcxx/include/__threading_support:509:10
#2 0xc5a1cb6 in std::__1::thread::thread<void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'(), void>(void&&) obj-x86_64-linux-gnu/../contrib/libcxx/include/thread:307:16
#3 0xc597279 in void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:139:35
#4 0xc5a5745 in ThreadPoolImpl<std::__1::thread>::scheduleOrThrow(std::__1::function<void ()>, int, unsigned long) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:171:5
#5 0xc5a5745 in ThreadFromGlobalPool::ThreadFromGlobalPool<void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(void&&) obj-x86_64-linux-gnu/../src/Common/ThreadPool.h:169:38
#6 0xc59c5ff in void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:139:35
#7 0xc59bc95 in ThreadPoolImpl<ThreadFromGlobalPool>::scheduleOrThrowOnError(std::__1::function<void ()>, int) obj-x86_64-linux-gnu/../src/Common/ThreadPool.cpp:159:5
#8 0x29f6384a in DB::ParallelFormattingOutputFormat::scheduleFormatterThreadForUnitWithNumber(unsigned long, unsigned long) obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/ParallelFormattingOutputFormat.h:251:14
#9 0x29f5ffc8 in DB::ParallelFormattingOutputFormat::addChunk(DB::Chunk, DB::ParallelFormattingOutputFormat::ProcessingUnitType, bool) obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/ParallelFormattingOutputFormat.cpp:66:9
#10 0x29f5f410 in DB::ParallelFormattingOutputFormat::finalizeImpl() obj-x86_64-linux-gnu/../src/Processors/Formats/Impl/ParallelFormattingOutputFormat.cpp:13:9
#11 0x29d4fe37 in DB::IOutputFormat::finalize() obj-x86_64-linux-gnu/../src/Processors/Formats/IOutputFormat.cpp:125:5
#12 0x29d4fe37 in DB::IOutputFormat::work() obj-x86_64-linux-gnu/../src/Processors/Formats/IOutputFormat.cpp:75:9
#13 0x29d2d625 in DB::executeJob(DB::IProcessor*) obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:45:20
#14 0x29d2d625 in DB::ExecutionThreadContext::executeTask() obj-x86_64-linux-gnu/../src/Processors/Executors/ExecutionThreadContext.cpp:63:9
#15 0x29d0db06 in DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:213:26
#16 0x29d0c02e in DB::PipelineExecutor::executeSingleThread(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:178:5
#17 0x29d0c02e in DB::PipelineExecutor::executeImpl(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:329:9
#18 0x29d0b2ef in DB::PipelineExecutor::execute(unsigned long) obj-x86_64-linux-gnu/../src/Processors/Executors/PipelineExecutor.cpp:84:9
#19 0x29d08680 in DB::CompletedPipelineExecutor::execute() obj-x86_64-linux-gnu/../src/Processors/Executors/CompletedPipelineExecutor.cpp:101:18
#20 0x28054573 in DB::executeQuery(DB::ReadBuffer&, DB::WriteBuffer&, bool, std::__1::shared_ptr<DB::Context>, std::__1::function<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)>, std::__1::optional<DB::FormatSettings> const&) obj-x86_64-linux-gnu/../src/Interpreters/executeQuery.cpp:1126:22
#21 0x29b20fa6 in DB::HTTPHandler::processQuery(DB::HTTPServerRequest&, DB::HTMLForm&, DB::HTTPServerResponse&, DB::HTTPHandler::Output&, std::__1::optional<DB::CurrentThread::QueryScope>&) obj-x86_64-linux-gnu/../src/Server/HTTPHandler.cpp:790:5
#22 0x29b2e491 in DB::HTTPHandler::handleRequest(DB::HTTPServerRequest&, DB::HTTPServerResponse&) obj-x86_64-linux-gnu/../src/Server/HTTPHandler.cpp:928:9
#23 0x29c47a54 in DB::HTTPServerConnection::run() obj-x86_64-linux-gnu/../src/Server/HTTP/HTTPServerConnection.cpp:65:34
#24 0x30873dce in Poco::Net::TCPServerConnection::start() obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServerConnection.cpp:43:3
#25 0x30874b40 in Poco::Net::TCPServerDispatcher::run() obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServerDispatcher.cpp:115:20
#26 0x30d57265 in Poco::PooledThread::run() obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:199:14
#27 0x30d50519 in Poco::ThreadImpl::runnableEntry(void*) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:345:27
#28 0x7fc802f74608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
Thread T447 (TCPHandler) created by T243 here:
#0 0xc43439c in pthread_create (/usr/bin/clickhouse+0xc43439c)
#1 0x30d4f7c9 in Poco::ThreadImpl::startImpl(Poco::SharedPtr<Poco::Runnable, Poco::ReferenceCounter, Poco::ReleasePolicy<Poco::Runnable> >) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:202:6
#2 0x30d5285d in Poco::Thread::start(Poco::Runnable&) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread.cpp:128:2
#3 0x30d5b359 in Poco::PooledThread::start() obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:85:10
#4 0x30d5b359 in Poco::ThreadPool::getThread() obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:461:14
#5 0x30d5ba36 in Poco::ThreadPool::startWithPriority(Poco::Thread::Priority, Poco::Runnable&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/ThreadPool.cpp:365:2
#6 0x30875727 in Poco::Net::TCPServerDispatcher::enqueue(Poco::Net::StreamSocket const&) obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServerDispatcher.cpp:152:17
#7 0x30873600 in Poco::Net::TCPServer::run() obj-x86_64-linux-gnu/../contrib/poco/Net/src/TCPServer.cpp:148:21
#8 0x30d50519 in Poco::ThreadImpl::runnableEntry(void*) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:345:27
#9 0x7fc802f74608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
Thread T243 created by T0 here:
#0 0xc43439c in pthread_create (/usr/bin/clickhouse+0xc43439c)
#1 0x30d4f7c9 in Poco::ThreadImpl::startImpl(Poco::SharedPtr<Poco::Runnable, Poco::ReferenceCounter, Poco::ReleasePolicy<Poco::Runnable> >) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread_POSIX.cpp:202:6
#2 0x30d5285d in Poco::Thread::start(Poco::Runnable&) obj-x86_64-linux-gnu/../contrib/poco/Foundation/src/Thread.cpp:128:2
#3 0xc4a9a3c in DB::ProtocolServerAdapter::start() obj-x86_64-linux-gnu/../src/Server/ProtocolServerAdapter.h:29:26
#4 0xc4a9a3c in DB::Server::main(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) obj-x86_64-linux-gnu/../programs/server/Server.cpp:1443:24
#5 0x308a7d1a in Poco::Util::Application::run() obj-x86_64-linux-gnu/../contrib/poco/Util/src/Application.cpp:334:8
#6 0xc48a398 in DB::Server::run() obj-x86_64-linux-gnu/../programs/server/Server.cpp:447:25
#7 0x308ed39d in Poco::Util::ServerApplication::run(int, char**) obj-x86_64-linux-gnu/../contrib/poco/Util/src/ServerApplication.cpp:611:9
#8 0xc483afd in mainEntryClickHouseServer(int, char**) obj-x86_64-linux-gnu/../programs/server/Server.cpp:188:20
#9 0xc47f688 in main obj-x86_64-linux-gnu/../programs/main.cpp:378:12
#10 0x7fc802da00b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
SUMMARY: AddressSanitizer: heap-buffer-overflow obj-x86_64-linux-gnu/../contrib/avro/lang/c++/impl/DataFile.cc:418:18 in avro::DataFileReaderBase::readDataBlock()
Shadow bytes around the buggy address:
0x0c04800678c0: fa fa fa fa fa fa fd fa fa fa fd fd fa fa fa fa
0x0c04800678d0: fa fa fd fd fa fa fd fd fa fa 02 fa fa fa fa fa
0x0c04800678e0: fa fa fd fd fa fa fa fa fa fa fa fa fa fa fa fa
0x0c04800678f0: fa fa fd fd fa fa fa fa fa fa 00 00 fa fa 00 00
0x0c0480067900: fa fa fd fd fa fa fa fa fa fa fd fa fa fa fa fa
=>0x0c0480067910: fa fa 00 00 fa fa fa fa fa[fa]fc fa fa fa fd fd
0x0c0480067920: fa fa fa fa fa fa fd fd fa fa fd fd fa fa fd fd
0x0c0480067930: fa fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa
0x0c0480067940: fa fa fd fd fa fa fa fa fa fa fa fa fa fa fd fd
0x0c0480067950: fa fa fd fa fa fa fa fa fa fa fa fa fa fa fd fd
0x0c0480067960: fa fa fa fa fa fa fd fa fa fa fd fa fa fa fd fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==549==ABORTING
```
|
non_process
|
heap buffer overflow in avro datafilereaderbase readdatablock error addresssanitizer heap buffer overflow on address at pc bp sp read of size at thread querypipelineex in avro datafilereaderbase readdatablock obj linux gnu contrib avro lang c impl datafile cc in avro datafilereaderbase hasmore obj linux gnu contrib avro lang c impl datafile cc in db avrorowinputformat readrow std vector mutable ptr std allocator mutable ptr db rowreadextension obj linux gnu src processors formats impl avrorowinputformat cpp in db irowinputformat generate obj linux gnu src processors formats irowinputformat cpp in db isource trygenerate obj linux gnu src processors isource cpp in db isource work obj linux gnu src processors isource cpp in db executejob db iprocessor obj linux gnu src processors executors executionthreadcontext cpp in db executionthreadcontext executetask obj linux gnu src processors executors executionthreadcontext cpp in db pipelineexecutor executestepimpl unsigned long std atomic obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor executestep std atomic obj linux gnu src processors executors pipelineexecutor cpp in db pullingpipelineexecutor pull db chunk obj linux gnu src processors executors pullingpipelineexecutor cpp in db storagefilesource generate obj linux gnu src storages storagefile cpp in db isource trygenerate obj linux gnu src processors isource cpp in db isource work obj linux gnu src processors isource cpp in db sourcewithprogress work obj linux gnu src processors sources sourcewithprogress cpp in db executejob db iprocessor obj linux gnu src processors executors executionthreadcontext cpp in db executionthreadcontext executetask obj linux gnu src processors executors executionthreadcontext cpp in db pipelineexecutor executestepimpl unsigned long std atomic obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor executesinglethread unsigned long obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor executeimpl unsigned long obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor execute unsigned long obj linux gnu src processors executors pipelineexecutor cpp in db threadfunction db pullingasyncpipelineexecutor data std shared ptr unsigned long obj linux gnu src processors executors pullingasyncpipelineexecutor cpp in db pullingasyncpipelineexecutor pull db chunk unsigned long operator const obj linux gnu src processors executors pullingasyncpipelineexecutor cpp in decltype std forward fp std invoke constexpr db pullingasyncpipelineexecutor pull db chunk unsigned long obj linux gnu contrib libcxx include type traits in decltype auto std apply tuple impl db pullingasyncpipelineexecutor pull db chunk unsigned long std tuple std tuple indices obj linux gnu contrib libcxx include tuple in decltype auto std apply db pullingasyncpipelineexecutor pull db chunk unsigned long std tuple obj linux gnu contrib libcxx include tuple in threadfromglobalpool threadfromglobalpool db pullingasyncpipelineexecutor pull db chunk unsigned long lambda operator obj linux gnu src common threadpool h in decltype std forward fp std invoke db pullingasyncpipelineexecutor pull db chunk unsigned long lambda db pullingasyncpipelineexecutor pull db chunk unsigned long obj linux gnu contrib libcxx include type traits in void std invoke void return wrapper call db pullingasyncpipelineexecutor pull db chunk unsigned long lambda threadfromglobalpool threadfromglobalpool db pullingasyncpipelineexecutor pull db chunk unsigned long lambda obj linux gnu contrib libcxx include functional base in std function default alloc func db pullingasyncpipelineexecutor pull db chunk unsigned long lambda void operator obj linux gnu contrib libcxx include functional in void std function policy invoker call impl db pullingasyncpipelineexecutor pull db chunk unsigned long lambda void std function policy storage const obj linux gnu contrib libcxx include functional in std function policy func operator const obj linux gnu contrib libcxx include functional in std function operator const obj linux gnu contrib libcxx include functional in threadpoolimpl worker std list iterator obj linux gnu src common threadpool cpp in void threadpoolimpl scheduleimpl std function int std optional operator const obj linux gnu src common threadpool cpp in decltype std forward fp std invoke scheduleimpl std function int std optional void obj linux gnu contrib libcxx include type traits in void std thread execute void threadpoolimpl scheduleimpl std function int std optional std tuple scheduleimpl std function int std optional std tuple indices obj linux gnu contrib libcxx include thread in void std thread proxy void threadpoolimpl scheduleimpl std function int std optional void obj linux gnu contrib libcxx include thread in start thread lib linux gnu libpthread so in clone lib linux gnu libc so is located bytes to the left of byte region allocated by thread querypipelineex here in operator new unsigned long usr bin clickhouse in void std libcpp operator new unsigned long obj linux gnu contrib libcxx include new in std libcpp allocate unsigned long unsigned long obj linux gnu contrib libcxx include new in std allocator allocate unsigned long obj linux gnu contrib libcxx include memory in std allocator traits allocate std allocator unsigned long obj linux gnu contrib libcxx include memory allocator traits h in std split buffer split buffer unsigned long unsigned long std allocator obj linux gnu contrib libcxx include split buffer in std enable if value is constructible reference value std wrap iter type std vector insert std wrap iter unsigned char const unsigned char const obj linux gnu contrib libcxx include vector in avro datafilereaderbase readdatablock obj linux gnu contrib avro lang c impl datafile cc in db irowinputformat generate obj linux gnu src processors formats irowinputformat cpp in db isource trygenerate obj linux gnu src processors isource cpp in db isource work obj linux gnu src processors isource cpp in db executejob db iprocessor obj linux gnu src processors executors executionthreadcontext cpp in db executionthreadcontext executetask obj linux gnu src processors executors executionthreadcontext cpp in db pipelineexecutor executestepimpl unsigned long std atomic obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor executestep std atomic obj linux gnu src processors executors pipelineexecutor cpp in db pullingpipelineexecutor pull db chunk obj linux gnu src processors executors pullingpipelineexecutor cpp thread querypipelineex created by tcphandler here in pthread create usr bin clickhouse in std libcpp thread create unsigned long void void void obj linux gnu contrib libcxx include threading support in std thread thread scheduleimpl std function int std optional void void obj linux gnu contrib libcxx include thread in void threadpoolimpl scheduleimpl std function int std optional obj linux gnu src common threadpool cpp in threadpoolimpl scheduleorthrow std function int unsigned long obj linux gnu src common threadpool cpp in threadfromglobalpool threadfromglobalpool scheduleimpl std function int std optional void obj linux gnu src common threadpool h in void threadpoolimpl scheduleimpl std function int std optional obj linux gnu src common threadpool cpp in threadpoolimpl scheduleorthrowonerror std function int obj linux gnu src common threadpool cpp in db parallelformattingoutputformat scheduleformatterthreadforunitwithnumber unsigned long unsigned long obj linux gnu src processors formats impl parallelformattingoutputformat h in db parallelformattingoutputformat addchunk db chunk db parallelformattingoutputformat processingunittype bool obj linux gnu src processors formats impl parallelformattingoutputformat cpp in db parallelformattingoutputformat finalizeimpl obj linux gnu src processors formats impl parallelformattingoutputformat cpp in db ioutputformat finalize obj linux gnu src processors formats ioutputformat cpp in db ioutputformat work obj linux gnu src processors formats ioutputformat cpp in db executejob db iprocessor obj linux gnu src processors executors executionthreadcontext cpp in db executionthreadcontext executetask obj linux gnu src processors executors executionthreadcontext cpp in db pipelineexecutor executestepimpl unsigned long std atomic obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor executesinglethread unsigned long obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor executeimpl unsigned long obj linux gnu src processors executors pipelineexecutor cpp in db pipelineexecutor execute unsigned long obj linux gnu src processors executors pipelineexecutor cpp in db completedpipelineexecutor execute obj linux gnu src processors executors completedpipelineexecutor cpp in db executequery db readbuffer db writebuffer bool std shared ptr std function std allocator const std basic string std allocator const std basic string std allocator const std basic string std allocator const std optional const obj linux gnu src interpreters executequery cpp in db httphandler processquery db httpserverrequest db htmlform db httpserverresponse db httphandler output std optional obj linux gnu src server httphandler cpp in db httphandler handlerequest db httpserverrequest db httpserverresponse obj linux gnu src server httphandler cpp in db httpserverconnection run obj linux gnu src server http httpserverconnection cpp in poco net tcpserverconnection start obj linux gnu contrib poco net src tcpserverconnection cpp in poco net tcpserverdispatcher run obj linux gnu contrib poco net src tcpserverdispatcher cpp in poco pooledthread run obj linux gnu contrib poco foundation src threadpool cpp in poco threadimpl runnableentry void obj linux gnu contrib poco foundation src thread posix cpp in start thread lib linux gnu libpthread so thread tcphandler created by here in pthread create usr bin clickhouse in poco threadimpl startimpl poco sharedptr obj linux gnu contrib poco foundation src thread posix cpp in poco thread start poco runnable obj linux gnu contrib poco foundation src thread cpp in poco pooledthread start obj linux gnu contrib poco foundation src threadpool cpp in poco threadpool getthread obj linux gnu contrib poco foundation src threadpool cpp in poco threadpool startwithpriority poco thread priority poco runnable std basic string std allocator const obj linux gnu contrib poco foundation src threadpool cpp in poco net tcpserverdispatcher enqueue poco net streamsocket const obj linux gnu contrib poco net src tcpserverdispatcher cpp in poco net tcpserver run obj linux gnu contrib poco net src tcpserver cpp in poco threadimpl runnableentry void obj linux gnu contrib poco foundation src thread posix cpp in start thread lib linux gnu libpthread so thread created by here in pthread create usr bin clickhouse in poco threadimpl startimpl poco sharedptr obj linux gnu contrib poco foundation src thread posix cpp in poco thread start poco runnable obj linux gnu contrib poco foundation src thread cpp in db protocolserveradapter start obj linux gnu src server protocolserveradapter h in db server main std vector std allocator std allocator std allocator const obj linux gnu programs server server cpp in poco util application run obj linux gnu contrib poco util src application cpp in db server run obj linux gnu programs server server cpp in poco util serverapplication run int char obj linux gnu contrib poco util src serverapplication cpp in mainentryclickhouseserver int char obj linux gnu programs server server cpp in main obj linux gnu programs main cpp in libc start main lib linux gnu libc so summary addresssanitizer heap buffer overflow obj linux gnu contrib avro lang c impl datafile cc in avro datafilereaderbase readdatablock shadow bytes around the buggy address fa fa fa fa fa fa fd fa fa fa fd fd fa fa fa fa fa fa fd fd fa fa fd fd fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa fa fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa fa fa fd fa fa fa fa fa fa fa fa fa fa fa fa fc fa fa fa fd fd fa fa fa fa fa fa fd fd fa fa fd fd fa fa fd fd fa fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa fa fa fd fd fa fa fa fa fa fa fa fa fa fa fd fd fa fa fd fa fa fa fa fa fa fa fa fa fa fa fd fd fa fa fa fa fa fa fd fa fa fa fd fa fa fa fd fa shadow byte legend one shadow byte represents application bytes addressable partially addressable heap left redzone fa freed heap region fd stack left redzone stack mid redzone stack right redzone stack after return stack use after scope global redzone global init order poisoned by user container overflow fc array cookie ac intra object redzone bb asan internal fe left alloca redzone ca right alloca redzone cb aborting
| 0
|
100,613
| 16,490,043,530
|
IssuesEvent
|
2021-05-25 01:27:57
|
heholek/sheets-api
|
https://api.github.com/repos/heholek/sheets-api
|
opened
|
CVE-2021-23383 (High) detected in handlebars-4.1.2.tgz
|
security vulnerability
|
## CVE-2021-23383 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.1.2.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz</a></p>
<p>Path to dependency file: sheets-api/step07/package.json</p>
<p>Path to vulnerable library: sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- express-handlebars-3.1.0.tgz (Root Library)
- :x: **handlebars-4.1.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383>CVE-2021-23383</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: handlebars - v4.7.7</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-23383 (High) detected in handlebars-4.1.2.tgz - ## CVE-2021-23383 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.1.2.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz</a></p>
<p>Path to dependency file: sheets-api/step07/package.json</p>
<p>Path to vulnerable library: sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json,sheets-api/step10/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- express-handlebars-3.1.0.tgz (Root Library)
- :x: **handlebars-4.1.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383>CVE-2021-23383</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: handlebars - v4.7.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in handlebars tgz cve high severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file sheets api package json path to vulnerable library sheets api node modules handlebars package json sheets api node modules handlebars package json sheets api node modules handlebars package json sheets api node modules handlebars package json sheets api node modules handlebars package json sheets api node modules handlebars package json sheets api node modules handlebars package json dependency hierarchy express handlebars tgz root library x handlebars tgz vulnerable library vulnerability details the package handlebars before are vulnerable to prototype pollution when selecting certain compiling options to compile templates coming from an untrusted source 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 handlebars step up your open source security game with whitesource
| 0
|
2,756
| 5,681,068,673
|
IssuesEvent
|
2017-04-13 04:28:36
|
inasafe/inasafe-realtime
|
https://api.github.com/repos/inasafe/inasafe-realtime
|
closed
|
Ash Realtime: add the KRB data as an overlay on the impact report
|
feature request ready realtime processor
|
Problem
Friends from PVMBG have requested that realtime ash reports include the KRB pyroclastic boundaries as context data
Expected Behaviour
The boundaries will be shown as lines over the ash model.
the lines will be coloured but no fill
Proposed Solution
The map should show the official data from PVMBG
@willi09 will share the KRB data and volcano point data when it is ready.
@ivan will add the data to the realtime data share and the map can be updated
cc
@lucernae @timlinux
This is not a blocker for the release of ash realtime
See original ticket at https://github.com/inasafe/inasafe/issues/3337 for further discussion.
|
1.0
|
Ash Realtime: add the KRB data as an overlay on the impact report - Problem
Friends from PVMBG have requested that realtime ash reports include the KRB pyroclastic boundaries as context data
Expected Behaviour
The boundaries will be shown as lines over the ash model.
the lines will be coloured but no fill
Proposed Solution
The map should show the official data from PVMBG
@willi09 will share the KRB data and volcano point data when it is ready.
@ivan will add the data to the realtime data share and the map can be updated
cc
@lucernae @timlinux
This is not a blocker for the release of ash realtime
See original ticket at https://github.com/inasafe/inasafe/issues/3337 for further discussion.
|
process
|
ash realtime add the krb data as an overlay on the impact report problem friends from pvmbg have requested that realtime ash reports include the krb pyroclastic boundaries as context data expected behaviour the boundaries will be shown as lines over the ash model the lines will be coloured but no fill proposed solution the map should show the official data from pvmbg will share the krb data and volcano point data when it is ready ivan will add the data to the realtime data share and the map can be updated cc lucernae timlinux this is not a blocker for the release of ash realtime see original ticket at for further discussion
| 1
|
1,379
| 3,945,840,857
|
IssuesEvent
|
2016-04-28 00:09:00
|
PlagueHO/LabBuilder
|
https://api.github.com/repos/PlagueHO/LabBuilder
|
closed
|
Split LabBuilder.psm1 into smaller Lib files
|
enhancement In Process
|
The LabBuilder.psm1 file is getting too large. It needs to be split into smaller Lib files.
|
1.0
|
Split LabBuilder.psm1 into smaller Lib files - The LabBuilder.psm1 file is getting too large. It needs to be split into smaller Lib files.
|
process
|
split labbuilder into smaller lib files the labbuilder file is getting too large it needs to be split into smaller lib files
| 1
|
5,855
| 8,679,602,701
|
IssuesEvent
|
2018-12-01 00:54:50
|
hackcambridge/hack-cambridge-website
|
https://api.github.com/repos/hackcambridge/hack-cambridge-website
|
opened
|
Modify frontend to hc-scripts to compile the scripts first
|
Epic: Dev process Type: Enhancement
|
That way we don't run an out of date version of the scripts.
|
1.0
|
Modify frontend to hc-scripts to compile the scripts first - That way we don't run an out of date version of the scripts.
|
process
|
modify frontend to hc scripts to compile the scripts first that way we don t run an out of date version of the scripts
| 1
|
191,162
| 22,215,658,263
|
IssuesEvent
|
2022-06-08 01:10:11
|
AlexRogalskiy/javascript-tools
|
https://api.github.com/repos/AlexRogalskiy/javascript-tools
|
closed
|
WS-2021-0154 (Medium) detected in glob-parent-5.1.1.tgz - autoclosed
|
security vulnerability
|
## WS-2021-0154 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: javascript-tools/package.json</p>
<p>Path to vulnerable library: javascript-tools/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- github-7.2.0.tgz (Root Library)
- globby-11.0.2.tgz
- fast-glob-3.2.5.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/javascript-tools/commit/a7c3aca6d1322622cb3c58274af611de788606d7">a7c3aca6d1322622cb3c58274af611de788606d7</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) vulnerability was found in glob-parent before 5.1.2.
<p>Publish Date: 2021-01-27
<p>URL: <a href=https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366>WS-2021-0154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/gulpjs/glob-parent/releases/tag/v5.1.2">https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2</a></p>
<p>Release Date: 2021-01-27</p>
<p>Fix Resolution: glob-parent - 5.1.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
|
WS-2021-0154 (Medium) detected in glob-parent-5.1.1.tgz - autoclosed - ## WS-2021-0154 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: javascript-tools/package.json</p>
<p>Path to vulnerable library: javascript-tools/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- github-7.2.0.tgz (Root Library)
- globby-11.0.2.tgz
- fast-glob-3.2.5.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/javascript-tools/commit/a7c3aca6d1322622cb3c58274af611de788606d7">a7c3aca6d1322622cb3c58274af611de788606d7</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) vulnerability was found in glob-parent before 5.1.2.
<p>Publish Date: 2021-01-27
<p>URL: <a href=https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366>WS-2021-0154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/gulpjs/glob-parent/releases/tag/v5.1.2">https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2</a></p>
<p>Release Date: 2021-01-27</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
ws medium detected in glob parent tgz autoclosed ws medium severity vulnerability vulnerable library glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file javascript tools package json path to vulnerable library javascript tools node modules glob parent package json dependency hierarchy github tgz root library globby tgz fast glob tgz x glob parent tgz vulnerable library found in head commit a href vulnerability details regular expression denial of service redos vulnerability was found in glob parent 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 none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution glob parent step up your open source security game with whitesource
| 0
|
5,507
| 8,376,873,167
|
IssuesEvent
|
2018-10-05 21:28:57
|
dotnet/corefx
|
https://api.github.com/repos/dotnet/corefx
|
closed
|
Test GetProcesses_InvalidMachineName_ThrowsInvalidOperationException crashes uap test run
|
area-System.Diagnostics.Process os-windows-uwp test bug test-run-uwp-coreclr
|
The InvalidOperationException thrown at test method GetProcesses_InvalidMachineName_ThrowsInvalidOperationException is currently crashing the UAP app when running the F5 tests. I did not dig deep to find out why this is, but I'm creating this issue to track the fix in order to be able to unblock the maestro auto update PRs.
cc: @stephentoub
|
1.0
|
Test GetProcesses_InvalidMachineName_ThrowsInvalidOperationException crashes uap test run - The InvalidOperationException thrown at test method GetProcesses_InvalidMachineName_ThrowsInvalidOperationException is currently crashing the UAP app when running the F5 tests. I did not dig deep to find out why this is, but I'm creating this issue to track the fix in order to be able to unblock the maestro auto update PRs.
cc: @stephentoub
|
process
|
test getprocesses invalidmachinename throwsinvalidoperationexception crashes uap test run the invalidoperationexception thrown at test method getprocesses invalidmachinename throwsinvalidoperationexception is currently crashing the uap app when running the tests i did not dig deep to find out why this is but i m creating this issue to track the fix in order to be able to unblock the maestro auto update prs cc stephentoub
| 1
|
19,775
| 26,150,881,786
|
IssuesEvent
|
2022-12-30 13:24:46
|
prisma/prisma
|
https://api.github.com/repos/prisma/prisma
|
opened
|
Error: called `Option::unwrap()` on a `None` value
|
bug/1-unconfirmed kind/bug process/candidate topic: error reporting team/schema
|
<!-- If required, please update the title to be clear and descriptive -->
Command: `prisma db pull`
Version: `4.8.0`
Binary Version: `d6e67a83f971b175a593ccc12e15c4a757f93ffe`
Report: https://prisma-errors.netlify.app/report/14484
OS: `x64 linux 5.15.0-56-generic`
JS Stacktrace:
```
Error: [introspection-engine/connectors/sql-introspection-connector/src/pair/default.rs:76:22] called `Option::unwrap()` on a `None` value
```
Rust Stacktrace:
```
0: user_facing_errors::panic_hook::set_panic_hook::{{closure}}
1: std::panicking::rust_panic_with_hook
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:702:17
2: std::panicking::begin_panic_handler::{{closure}}
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:586:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:138:18
4: rust_begin_unwind
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:584:5
5: core::panicking::panic_fmt
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:142:14
6: core::panicking::panic
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:48:5
7: sql_introspection_connector::rendering::models::render_model
8: sql_introspection_connector::datamodel_calculator::calculate
9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
11: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
12: <futures_util::future::future::Then<Fut1,Fut2,F> as core::future::future::Future>::poll
13: tokio::runtime::task::core::CoreStage<T>::poll
14: tokio::runtime::task::raw::poll
15: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
16: tokio::runtime::task::raw::poll
17: tokio::runtime::task::UnownedTask<S>::run
18: std::sys_common::backtrace::__rust_begin_short_backtrace
19: core::ops::function::FnOnce::call_once{{vtable.shim}}
20: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/alloc/src/boxed.rs:1935:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/alloc/src/boxed.rs:1935:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys/unix/thread.rs:108:17
21: start_thread
at ./nptl/./nptl/pthread_create.c:442:8
22: clone3
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
```
|
1.0
|
Error: called `Option::unwrap()` on a `None` value - <!-- If required, please update the title to be clear and descriptive -->
Command: `prisma db pull`
Version: `4.8.0`
Binary Version: `d6e67a83f971b175a593ccc12e15c4a757f93ffe`
Report: https://prisma-errors.netlify.app/report/14484
OS: `x64 linux 5.15.0-56-generic`
JS Stacktrace:
```
Error: [introspection-engine/connectors/sql-introspection-connector/src/pair/default.rs:76:22] called `Option::unwrap()` on a `None` value
```
Rust Stacktrace:
```
0: user_facing_errors::panic_hook::set_panic_hook::{{closure}}
1: std::panicking::rust_panic_with_hook
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:702:17
2: std::panicking::begin_panic_handler::{{closure}}
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:586:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:138:18
4: rust_begin_unwind
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:584:5
5: core::panicking::panic_fmt
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:142:14
6: core::panicking::panic
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:48:5
7: sql_introspection_connector::rendering::models::render_model
8: sql_introspection_connector::datamodel_calculator::calculate
9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
11: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
12: <futures_util::future::future::Then<Fut1,Fut2,F> as core::future::future::Future>::poll
13: tokio::runtime::task::core::CoreStage<T>::poll
14: tokio::runtime::task::raw::poll
15: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
16: tokio::runtime::task::raw::poll
17: tokio::runtime::task::UnownedTask<S>::run
18: std::sys_common::backtrace::__rust_begin_short_backtrace
19: core::ops::function::FnOnce::call_once{{vtable.shim}}
20: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/alloc/src/boxed.rs:1935:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/alloc/src/boxed.rs:1935:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys/unix/thread.rs:108:17
21: start_thread
at ./nptl/./nptl/pthread_create.c:442:8
22: clone3
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
```
|
process
|
error called option unwrap on a none value command prisma db pull version binary version report os linux generic js stacktrace error called option unwrap on a none value rust stacktrace user facing errors panic hook set panic hook closure std panicking rust panic with hook at rustc library std src panicking rs std panicking begin panic handler closure at rustc library std src panicking rs std sys common backtrace rust end short backtrace at rustc library std src sys common backtrace rs rust begin unwind at rustc library std src panicking rs core panicking panic fmt at rustc library core src panicking rs core panicking panic at rustc library core src panicking rs sql introspection connector rendering models render model sql introspection connector datamodel calculator calculate as core future future future poll as core future future future poll as core future future future poll as core future future future poll tokio runtime task core corestage poll tokio runtime task raw poll tokio runtime scheduler multi thread worker context run task tokio runtime task raw poll tokio runtime task unownedtask run std sys common backtrace rust begin short backtrace core ops function fnonce call once vtable shim as core ops function fnonce call once at rustc library alloc src boxed rs as core ops function fnonce call once at rustc library alloc src boxed rs std sys unix thread thread new thread start at rustc library std src sys unix thread rs start thread at nptl nptl pthread create c at misc sysdeps unix sysv linux s
| 1
|
4,674
| 7,517,256,363
|
IssuesEvent
|
2018-04-12 02:31:16
|
UnbFeelings/unb-feelings-GQA
|
https://api.github.com/repos/UnbFeelings/unb-feelings-GQA
|
closed
|
Definir técnicas para cada objeto de auditoria
|
document process wiki
|
Definir quais vão ser as técnicas utilizadas para cada objeto de auditoria existente. Estas técnicas podem ser checklists, entrevistas, ou alguma forma de verificação de maneira que, com elas, seja possível produzir os documentos que irão compor o feedback da auditoria.
[Atividade no processo](https://github.com/UnbFeelings/unb-feelings-GQA/wiki/Fluxo-de-Trabalho#15-definir-t%C3%A9cnicas-para-cada-objeto-de-auditoria).
|
1.0
|
Definir técnicas para cada objeto de auditoria - Definir quais vão ser as técnicas utilizadas para cada objeto de auditoria existente. Estas técnicas podem ser checklists, entrevistas, ou alguma forma de verificação de maneira que, com elas, seja possível produzir os documentos que irão compor o feedback da auditoria.
[Atividade no processo](https://github.com/UnbFeelings/unb-feelings-GQA/wiki/Fluxo-de-Trabalho#15-definir-t%C3%A9cnicas-para-cada-objeto-de-auditoria).
|
process
|
definir técnicas para cada objeto de auditoria definir quais vão ser as técnicas utilizadas para cada objeto de auditoria existente estas técnicas podem ser checklists entrevistas ou alguma forma de verificação de maneira que com elas seja possível produzir os documentos que irão compor o feedback da auditoria
| 1
|
21,803
| 30,316,175,549
|
IssuesEvent
|
2023-07-10 15:43:05
|
tdwg/dwc
|
https://api.github.com/repos/tdwg/dwc
|
closed
|
Change term - superfamily
|
Term - change Class - Taxon normative Process - complete
|
## Term change
* Submitter: John Wieczorek
* Efficacy Justification (why is this change necessary?): Erratum
* Demand Justification (if the change is semantic in nature, name at least two organizations that independently need this term): Erratum
* Stability Justification (what concerns are there that this might affect existing implementations?): Erratum
* Implications for dwciri: namespace (does this change affect a dwciri term version)?: None
Current Term definition: https://dwc.tdwg.org/list/#dwc_superfamily
Proposed attributes of the new term version (Please put actual changes to be implemented in **bold** and ~strikethrough~):
* Term name (in lowerCamelCase for properties, UpperCamelCase for classes): superfamily
* Term label (English, not normative): Superfamily
* Organized in Class (e.g., Occurrence, Event, Location, Taxon): Taxon
* Definition of the term (normative): The full scientific name of the **super**family in which the dwc:Taxon is classified.
* Usage comments (recommendations regarding content, etc., not normative): A taxonomic category subordinate to an order and superior to a family. According to ICZN article 29.2, the suffix -oidea is used for a superfamily name.
* Examples (not normative): `Achatinoidea`, `Cerithioidea`, `Helicoidea`, `Hypsibioidea`, `Valvatoidea`, `Zonitoidea`
* Refines (identifier of the broader term this term refines; normative): None
* Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): ScientificNameIdentified/HigherTaxon/HigherTaxonRank (enumeration value: superfamilia)
|
1.0
|
Change term - superfamily - ## Term change
* Submitter: John Wieczorek
* Efficacy Justification (why is this change necessary?): Erratum
* Demand Justification (if the change is semantic in nature, name at least two organizations that independently need this term): Erratum
* Stability Justification (what concerns are there that this might affect existing implementations?): Erratum
* Implications for dwciri: namespace (does this change affect a dwciri term version)?: None
Current Term definition: https://dwc.tdwg.org/list/#dwc_superfamily
Proposed attributes of the new term version (Please put actual changes to be implemented in **bold** and ~strikethrough~):
* Term name (in lowerCamelCase for properties, UpperCamelCase for classes): superfamily
* Term label (English, not normative): Superfamily
* Organized in Class (e.g., Occurrence, Event, Location, Taxon): Taxon
* Definition of the term (normative): The full scientific name of the **super**family in which the dwc:Taxon is classified.
* Usage comments (recommendations regarding content, etc., not normative): A taxonomic category subordinate to an order and superior to a family. According to ICZN article 29.2, the suffix -oidea is used for a superfamily name.
* Examples (not normative): `Achatinoidea`, `Cerithioidea`, `Helicoidea`, `Hypsibioidea`, `Valvatoidea`, `Zonitoidea`
* Refines (identifier of the broader term this term refines; normative): None
* Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): ScientificNameIdentified/HigherTaxon/HigherTaxonRank (enumeration value: superfamilia)
|
process
|
change term superfamily term change submitter john wieczorek efficacy justification why is this change necessary erratum demand justification if the change is semantic in nature name at least two organizations that independently need this term erratum stability justification what concerns are there that this might affect existing implementations erratum implications for dwciri namespace does this change affect a dwciri term version none current term definition proposed attributes of the new term version please put actual changes to be implemented in bold and strikethrough term name in lowercamelcase for properties uppercamelcase for classes superfamily term label english not normative superfamily organized in class e g occurrence event location taxon taxon definition of the term normative the full scientific name of the super family in which the dwc taxon is classified usage comments recommendations regarding content etc not normative a taxonomic category subordinate to an order and superior to a family according to iczn article the suffix oidea is used for a superfamily name examples not normative achatinoidea cerithioidea helicoidea hypsibioidea valvatoidea zonitoidea refines identifier of the broader term this term refines normative none replaces identifier of the existing term that would be deprecated and replaced by this term normative abcd xpath of the equivalent term in abcd or efg not normative scientificnameidentified highertaxon highertaxonrank enumeration value superfamilia
| 1
|
16,139
| 20,403,666,329
|
IssuesEvent
|
2022-02-23 00:57:28
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
opened
|
DISABLED test_first_argument_index (__main__.SpawnTest)
|
module: multiprocessing triaged module: flaky-tests skipped
|
Platforms: linux
This test was disabled because it is failing in CI. See [recent examples](http://torch-ci.com/failure/test_first_argument_index%2C%20SpawnTest) and the most recent [workflow logs](https://github.com/pytorch/pytorch/actions/runs/1884385804).
Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 red and 3 green.
|
1.0
|
DISABLED test_first_argument_index (__main__.SpawnTest) - Platforms: linux
This test was disabled because it is failing in CI. See [recent examples](http://torch-ci.com/failure/test_first_argument_index%2C%20SpawnTest) and the most recent [workflow logs](https://github.com/pytorch/pytorch/actions/runs/1884385804).
Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 red and 3 green.
|
process
|
disabled test first argument index main spawntest platforms linux this test was disabled because it is failing in ci see and the most recent over the past hours it has been determined flaky in workflow s with red and green
| 1
|
266,245
| 23,226,664,646
|
IssuesEvent
|
2022-08-03 01:24:20
|
MPMG-DCC-UFMG/F01
|
https://api.github.com/repos/MPMG-DCC-UFMG/F01
|
closed
|
Teste de generalizacao para a tag Servidores - Relatório mensal da despesa com pessoal - Novo Cruzeiro
|
generalization test development template-Síntese tecnologia informatica subtag-Relatórios Despesas com Pessoal tag-Servidores
|
DoD: Realizar o teste de Generalização do validador da tag Servidores - Relatório mensal da despesa com pessoal para o Município de Novo Cruzeiro.
|
1.0
|
Teste de generalizacao para a tag Servidores - Relatório mensal da despesa com pessoal - Novo Cruzeiro - DoD: Realizar o teste de Generalização do validador da tag Servidores - Relatório mensal da despesa com pessoal para o Município de Novo Cruzeiro.
|
non_process
|
teste de generalizacao para a tag servidores relatório mensal da despesa com pessoal novo cruzeiro dod realizar o teste de generalização do validador da tag servidores relatório mensal da despesa com pessoal para o município de novo cruzeiro
| 0
|
5,541
| 8,392,427,600
|
IssuesEvent
|
2018-10-09 17:36:00
|
googleapis/google-cloud-python
|
https://api.github.com/repos/googleapis/google-cloud-python
|
closed
|
Logging: 'test_list_entry_with_unregistered' systest flakes with '429 ResourceExhausted`
|
api: logging flaky testing type: process
|
See: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7594
```python
________________ TestLogging.test_list_entry_with_unregistered _________________
self = <test_system.TestLogging testMethod=test_list_entry_with_unregistered>
def test_list_entry_with_unregistered(self):
from google.protobuf import any_pb2
from google.protobuf import descriptor_pool
from google.cloud.logging import entries
pool = descriptor_pool.Default()
type_name = 'google.cloud.audit.AuditLog'
# Make sure the descriptor is not known in the registry.
with self.assertRaises(KeyError):
pool.FindMessageTypeByName(type_name)
type_url = 'type.googleapis.com/' + type_name
filter_ = self.TYPE_FILTER.format(type_url)
entry_iter = iter(
Config.CLIENT.list_entries(page_size=1, filter_=filter_))
> protobuf_entry = next(entry_iter)
tests/system/test_system.py:135:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:199: in _items_iter
for page in self._page_iter(increment=False):
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:230: in _page_iter
page = self._next_page()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:512: in _next_page
response = self._method(self._request)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/gapic_v1/method.py:139: in __call__
return wrapped_func(*args, **kwargs)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:260: in retry_wrapped_func
on_error=on_error,
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:177: in retry_target
return target()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/timeout.py:206: in func_with_timeout
return func(*args, **kwargs)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/grpc_helpers.py:61: in error_remapped_callable
six.raise_from(exceptions.from_grpc_error(exc), exc)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = ResourceExhausted("Insufficient tokens for quota 'logging.googleapis.com/read_...ervice 'logging.googleapis.com' for consumer 'project_number:1065521786570'.",)
from_value = <_Rendezvous of RPC that terminated with:
status = StatusCode.RESOURCE_EXHAUS...ogleapis.com' for consumer 'project_number:1065521786570'.","grpc_status":8}"
>
def raise_from(value, from_value):
> raise value
E ResourceExhausted: 429 Insufficient tokens for quota 'logging.googleapis.com/read_requests' and limit 'ReadRequestsPerMinutePerProject' of service 'logging.googleapis.com' for consumer 'project_number:1065521786570'.
../.nox/sys-2-7/lib/python2.7/site-packages/six.py:737: ResourceExhausted
```
|
1.0
|
Logging: 'test_list_entry_with_unregistered' systest flakes with '429 ResourceExhausted` - See: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7594
```python
________________ TestLogging.test_list_entry_with_unregistered _________________
self = <test_system.TestLogging testMethod=test_list_entry_with_unregistered>
def test_list_entry_with_unregistered(self):
from google.protobuf import any_pb2
from google.protobuf import descriptor_pool
from google.cloud.logging import entries
pool = descriptor_pool.Default()
type_name = 'google.cloud.audit.AuditLog'
# Make sure the descriptor is not known in the registry.
with self.assertRaises(KeyError):
pool.FindMessageTypeByName(type_name)
type_url = 'type.googleapis.com/' + type_name
filter_ = self.TYPE_FILTER.format(type_url)
entry_iter = iter(
Config.CLIENT.list_entries(page_size=1, filter_=filter_))
> protobuf_entry = next(entry_iter)
tests/system/test_system.py:135:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:199: in _items_iter
for page in self._page_iter(increment=False):
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:230: in _page_iter
page = self._next_page()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:512: in _next_page
response = self._method(self._request)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/gapic_v1/method.py:139: in __call__
return wrapped_func(*args, **kwargs)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:260: in retry_wrapped_func
on_error=on_error,
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:177: in retry_target
return target()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/timeout.py:206: in func_with_timeout
return func(*args, **kwargs)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/grpc_helpers.py:61: in error_remapped_callable
six.raise_from(exceptions.from_grpc_error(exc), exc)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = ResourceExhausted("Insufficient tokens for quota 'logging.googleapis.com/read_...ervice 'logging.googleapis.com' for consumer 'project_number:1065521786570'.",)
from_value = <_Rendezvous of RPC that terminated with:
status = StatusCode.RESOURCE_EXHAUS...ogleapis.com' for consumer 'project_number:1065521786570'.","grpc_status":8}"
>
def raise_from(value, from_value):
> raise value
E ResourceExhausted: 429 Insufficient tokens for quota 'logging.googleapis.com/read_requests' and limit 'ReadRequestsPerMinutePerProject' of service 'logging.googleapis.com' for consumer 'project_number:1065521786570'.
../.nox/sys-2-7/lib/python2.7/site-packages/six.py:737: ResourceExhausted
```
|
process
|
logging test list entry with unregistered systest flakes with resourceexhausted see python testlogging test list entry with unregistered self def test list entry with unregistered self from google protobuf import any from google protobuf import descriptor pool from google cloud logging import entries pool descriptor pool default type name google cloud audit auditlog make sure the descriptor is not known in the registry with self assertraises keyerror pool findmessagetypebyname type name type url type googleapis com type name filter self type filter format type url entry iter iter config client list entries page size filter filter protobuf entry next entry iter tests system test system py nox sys lib site packages google api core page iterator py in items iter for page in self page iter increment false nox sys lib site packages google api core page iterator py in page iter page self next page nox sys lib site packages google api core page iterator py in next page response self method self request nox sys lib site packages google api core gapic method py in call return wrapped func args kwargs nox sys lib site packages google api core retry py in retry wrapped func on error on error nox sys lib site packages google api core retry py in retry target return target nox sys lib site packages google api core timeout py in func with timeout return func args kwargs nox sys lib site packages google api core grpc helpers py in error remapped callable six raise from exceptions from grpc error exc exc value resourceexhausted insufficient tokens for quota logging googleapis com read ervice logging googleapis com for consumer project number from value rendezvous of rpc that terminated with status statuscode resource exhaus ogleapis com for consumer project number grpc status def raise from value from value raise value e resourceexhausted insufficient tokens for quota logging googleapis com read requests and limit readrequestsperminuteperproject of service logging googleapis com for consumer project number nox sys lib site packages six py resourceexhausted
| 1
|
646,080
| 21,036,691,823
|
IssuesEvent
|
2022-03-31 08:31:17
|
zephyrproject-rtos/zephyr
|
https://api.github.com/repos/zephyrproject-rtos/zephyr
|
closed
|
drivers: can: z_vrfy_can_recover() does not compile
|
bug priority: medium area: CAN has-pr
|
**Describe the bug**
The following code has clearly never been tested. Notice the call to `z_impl_can_recover()`.
```
static inline int z_vrfy_can_recover(const struct device *dev,
k_timeout_t timeout)
{
Z_OOPS(Z_SYSCALL_OBJ(dev, K_OBJ_DRIVER_CAN));
return z_impl_can_recover(dev, k_timeout_t timeout);
}
#include <syscalls/can_recover_mrsh.c>
```
**To Reproduce**
Steps to reproduce the behavior:
1. Set `CONFIG_USERSPACE=y`, `CONFIG_CAN=y`, and `CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=n`.
2. Compile any of the CAN samples or tests
3. See error
**Expected behavior**
The code should compile.
**Impact**
Unable to use `CONFIG_USERSPACE=y`, `CONFIG_CAN=y`, and `CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=n` combination.
**Environment (please complete the following information):**
- OS: Ubuntu Linux 20.04 LTS
- Toolchain: Zephyr SDK v0.14.0
- Commit SHA: 50cc558924d1a6cdaed2a0fc9efd9979aafa0417
|
1.0
|
drivers: can: z_vrfy_can_recover() does not compile - **Describe the bug**
The following code has clearly never been tested. Notice the call to `z_impl_can_recover()`.
```
static inline int z_vrfy_can_recover(const struct device *dev,
k_timeout_t timeout)
{
Z_OOPS(Z_SYSCALL_OBJ(dev, K_OBJ_DRIVER_CAN));
return z_impl_can_recover(dev, k_timeout_t timeout);
}
#include <syscalls/can_recover_mrsh.c>
```
**To Reproduce**
Steps to reproduce the behavior:
1. Set `CONFIG_USERSPACE=y`, `CONFIG_CAN=y`, and `CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=n`.
2. Compile any of the CAN samples or tests
3. See error
**Expected behavior**
The code should compile.
**Impact**
Unable to use `CONFIG_USERSPACE=y`, `CONFIG_CAN=y`, and `CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=n` combination.
**Environment (please complete the following information):**
- OS: Ubuntu Linux 20.04 LTS
- Toolchain: Zephyr SDK v0.14.0
- Commit SHA: 50cc558924d1a6cdaed2a0fc9efd9979aafa0417
|
non_process
|
drivers can z vrfy can recover does not compile describe the bug the following code has clearly never been tested notice the call to z impl can recover static inline int z vrfy can recover const struct device dev k timeout t timeout z oops z syscall obj dev k obj driver can return z impl can recover dev k timeout t timeout include to reproduce steps to reproduce the behavior set config userspace y config can y and config can auto bus off recovery n compile any of the can samples or tests see error expected behavior the code should compile impact unable to use config userspace y config can y and config can auto bus off recovery n combination environment please complete the following information os ubuntu linux lts toolchain zephyr sdk commit sha
| 0
|
809,930
| 30,217,724,849
|
IssuesEvent
|
2023-07-05 16:47:44
|
calcom/cal.com
|
https://api.github.com/repos/calcom/cal.com
|
closed
|
[CAL-1617] Bookings rejected on a date overridden day.
|
🐛 bug High priority bookings
|
Created via Threads. See full discussion: [https://threads.com/34469350238](https://threads.com/34469350238)
<sub>From [SyncLinear.com](https://synclinear.com) | [CAL-1617](https://linear.app/calcom/issue/CAL-1617/bookings-rejected-on-a-date-overridden-day)</sub>
|
1.0
|
[CAL-1617] Bookings rejected on a date overridden day. - Created via Threads. See full discussion: [https://threads.com/34469350238](https://threads.com/34469350238)
<sub>From [SyncLinear.com](https://synclinear.com) | [CAL-1617](https://linear.app/calcom/issue/CAL-1617/bookings-rejected-on-a-date-overridden-day)</sub>
|
non_process
|
bookings rejected on a date overridden day created via threads see full discussion from
| 0
|
16,188
| 20,626,710,801
|
IssuesEvent
|
2022-03-07 23:36:08
|
GSA/EDX
|
https://api.github.com/repos/GSA/EDX
|
closed
|
Website Eval Protocol
|
process collaboration
|
## Summary
Develop a protocol for website reviews
## Additional context and links
[Proposal](https://docs.google.com/document/d/1zro0ewvgOElrm21JMQWBFqc3_H13X9brlIDkw_oFAXQ/edit#) (work in progress)
[Working folder for website evals](https://drive.google.com/drive/folders/1aRvGDHqbdDWQ8X7zfIYMNM5f0Okwog4r)
[Sprint plan](https://app.asana.com/0/1201500521890223/timeline)
## Checklist - Process Tasks
- [x] Complete first draft
- [x] Review draft w/the team and incorporate feedback
- [x] Identify a site to test out the protocol
- [x] Conduct the test and tweak the process as needed
- [x] Identify exactly which ~80 sites we'll review in 2022
- [x] Determine the schedule for individual site reviews
- [x] Reach out to site owners 2-3 weeks beforehand, to introduce the project and schedule the review
- [x] Pull data and create the site info report for each site that is reviewed
## Checklist - Comms
Develop templates for:
- [x] Intro email (to introduce the review process and schedule the interview)
- [x] Report on findings (to send after the interview) - [Website Evaluation Findings and Action Items](https://docs.google.com/document/d/1IFkJT_yYSd2Nwmjf-7PK7P96dE6hbyqisH4NuAH3nkU/edit#)
- [x] Followup email back to website manager/team (to check in on progress)
|
1.0
|
Website Eval Protocol - ## Summary
Develop a protocol for website reviews
## Additional context and links
[Proposal](https://docs.google.com/document/d/1zro0ewvgOElrm21JMQWBFqc3_H13X9brlIDkw_oFAXQ/edit#) (work in progress)
[Working folder for website evals](https://drive.google.com/drive/folders/1aRvGDHqbdDWQ8X7zfIYMNM5f0Okwog4r)
[Sprint plan](https://app.asana.com/0/1201500521890223/timeline)
## Checklist - Process Tasks
- [x] Complete first draft
- [x] Review draft w/the team and incorporate feedback
- [x] Identify a site to test out the protocol
- [x] Conduct the test and tweak the process as needed
- [x] Identify exactly which ~80 sites we'll review in 2022
- [x] Determine the schedule for individual site reviews
- [x] Reach out to site owners 2-3 weeks beforehand, to introduce the project and schedule the review
- [x] Pull data and create the site info report for each site that is reviewed
## Checklist - Comms
Develop templates for:
- [x] Intro email (to introduce the review process and schedule the interview)
- [x] Report on findings (to send after the interview) - [Website Evaluation Findings and Action Items](https://docs.google.com/document/d/1IFkJT_yYSd2Nwmjf-7PK7P96dE6hbyqisH4NuAH3nkU/edit#)
- [x] Followup email back to website manager/team (to check in on progress)
|
process
|
website eval protocol summary develop a protocol for website reviews additional context and links work in progress checklist process tasks complete first draft review draft w the team and incorporate feedback identify a site to test out the protocol conduct the test and tweak the process as needed identify exactly which sites we ll review in determine the schedule for individual site reviews reach out to site owners weeks beforehand to introduce the project and schedule the review pull data and create the site info report for each site that is reviewed checklist comms develop templates for intro email to introduce the review process and schedule the interview report on findings to send after the interview followup email back to website manager team to check in on progress
| 1
|
22,695
| 32,006,314,233
|
IssuesEvent
|
2023-09-21 15:02:20
|
haddocking/haddock3
|
https://api.github.com/repos/haddocking/haddock3
|
closed
|
remove traceback for analysis runs
|
bug analysis/postprocessing
|
traceback should not be run on workflows containing only analysis modules (such as https://github.com/haddocking/haddock3/blob/main/examples/analysis/topoaa-caprieval-test.cfg)
|
1.0
|
remove traceback for analysis runs - traceback should not be run on workflows containing only analysis modules (such as https://github.com/haddocking/haddock3/blob/main/examples/analysis/topoaa-caprieval-test.cfg)
|
process
|
remove traceback for analysis runs traceback should not be run on workflows containing only analysis modules such as
| 1
|
728,537
| 25,083,482,780
|
IssuesEvent
|
2022-11-07 21:27:47
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
Add Question search in Dashboard editor does not return question with exact name match
|
Type:Bug Priority:P1 Reporting/Dashboards .Correctness Organization/Saved Questions Organization/Search .Regression
|
**Describe the bug**
When using the search function to add a question to a dashboard, the question whose name exactly matches my search phrase does not show up in the result list. The question does show up, however, in the global search.
**Logs**
<details><summary>The web console doesn't show anything particularly notable, but here it is.</summary>
```
i18n.js:49 Setting moment.js start of week for Locale en to sunday
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: ThemeProvider
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
scheduleUpdateOnFiber @ react-dom.development.js:21188
updateContainer @ react-dom.development.js:24373
(anonymous) @ react-dom.development.js:24758
unbatchedUpdates @ react-dom.development.js:21903
legacyRenderSubtreeIntoContainer @ react-dom.development.js:24757
render @ react-dom.development.js:24840
_init @ app.js:76
(anonymous) @ app.js:118
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: DragDropContextProvider, ThemeProvider
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
scheduleUpdateOnFiber @ react-dom.development.js:21188
updateContainer @ react-dom.development.js:24373
(anonymous) @ react-dom.development.js:24758
unbatchedUpdates @ react-dom.development.js:21903
legacyRenderSubtreeIntoContainer @ react-dom.development.js:24757
render @ react-dom.development.js:24840
_init @ app.js:76
(anonymous) @ app.js:118
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Box, Dashboardstyled__DashboardLoadingAndErrorWrapper, Flex, Icon, Icon__IconWrapper, Link, MetabaseIsSetup(Connect(UserIsAuthenticated(Component))), SearchBarstyled__SearchInput, SearchBarstyled__SearchWrapper, UndoListing__UndoList, UserIsAuthenticated(Component)
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
(anonymous) @ Router.js:109
(anonymous) @ createTransitionManager.js:228
(anonymous) @ createTransitionManager.js:83
done @ AsyncUtils.js:74
(anonymous) @ AsyncUtils.js:80
getComponentsForRoute @ getComponents.js:6
(anonymous) @ getComponents.js:30
(anonymous) @ AsyncUtils.js:79
mapAsync @ AsyncUtils.js:78
getComponents @ getComponents.js:29
finishEnterHooks @ createTransitionManager.js:77
next @ AsyncUtils.js:47
(anonymous) @ TransitionUtils.js:88
wrappedNext @ TransitionUtils.js:110
_callee$ @ routes.jsx:166
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ utils.js:127
_next @ utils.js:127
Show 8 more frames
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Box, Dashboardstyled__DashboardLoadingAndErrorWrapper, Flex, Icon, Icon__IconWrapper, Link, MetabaseIsSetup(Connect(UserIsAuthenticated(Component))), SearchBarstyled__SearchInput, SearchBarstyled__SearchWrapper, UndoListing__UndoList, UserIsAuthenticated(Component)
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
(anonymous) @ Router.js:109
(anonymous) @ createTransitionManager.js:228
(anonymous) @ createTransitionManager.js:83
done @ AsyncUtils.js:74
(anonymous) @ AsyncUtils.js:80
getComponentsForRoute @ getComponents.js:6
(anonymous) @ getComponents.js:30
(anonymous) @ AsyncUtils.js:79
mapAsync @ AsyncUtils.js:78
getComponents @ getComponents.js:29
finishEnterHooks @ createTransitionManager.js:77
next @ AsyncUtils.js:47
(anonymous) @ TransitionUtils.js:88
wrappedNext @ TransitionUtils.js:110
_callee$ @ routes.jsx:166
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ utils.js:127
_next @ utils.js:127
Show 8 more frames
metadata.js:18 DEPRECATED: metabase/redux/metadata addFields
deprecated @ metadata.js:18
addFields @ metadata.js:124
_callee6$ @ actions.js:707
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ index.js:20
_next @ index.js:20
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Button, Buttonstyled__TextButton, DashboardHeaderstyled__DashboardHeaderButton, Dashboardstyled__CardsContainer, Dashboardstyled__DashboardBody, Dashboardstyled__DashboardStyled, Dashboardstyled__HeaderContainer, Dashboardstyled__ParametersAndCardsContainer, FullWidthContainer, TransitionGroup
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Button, Buttonstyled__TextButton, DashboardHeaderstyled__DashboardHeaderButton, Dashboardstyled__CardsContainer, Dashboardstyled__DashboardBody, Dashboardstyled__DashboardStyled, Dashboardstyled__HeaderContainer, Dashboardstyled__ParametersAndCardsContainer, FullWidthContainer, TransitionGroup
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
checkPropTypes.js:20 Warning: Failed prop type: minWidth larger than item width/maxWidth
in GridItem (created by ReactGridLayout)
in ReactGridLayout (created by ResponsiveReactGridLayout)
in ResponsiveReactGridLayout (created by GridLayout)
in GridLayout (created by DashboardGrid)
in div (created by DashboardGrid)
in DashboardGrid (created by ExplicitSize[DashboardGrid])
in ExplicitSize[DashboardGrid] (created by LoadingAndErrorWrapper)
in div (created by FullWidthContainer)
in FullWidthContainer (created by Dashboardstyled__CardsContainer)
in Dashboardstyled__CardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__ParametersAndCardsContainer)
in Dashboardstyled__ParametersAndCardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
printWarning @ checkPropTypes.js:20
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1714
createElementWithValidation @ react.development.js:1813
processGridItem @ ReactGridLayout.js:649
(anonymous) @ ReactGridLayout.js:714
mapSingleChildIntoContext @ react.development.js:1149
traverseAllChildrenImpl @ react.development.js:1007
traverseAllChildrenImpl @ react.development.js:1023
traverseAllChildren @ react.development.js:1092
mapIntoWithKeyPrefixInternal @ react.development.js:1174
mapChildren @ react.development.js:1198
render @ ReactGridLayout.js:713
finishClassComponent @ react-dom.development.js:17160
updateClassComponent @ react-dom.development.js:17110
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 13 more frames
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: ChartCaptionstyled__ChartCaptionRoot, LegendActionsstyled__LegendActionsRoot, LegendCaptionstyled__LegendCaptionRoot, LegendCaptionstyled__LegendLabel
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: ChartCaptionstyled__ChartCaptionRoot, LegendActionsstyled__LegendActionsRoot, LegendCaptionstyled__LegendCaptionRoot, LegendCaptionstyled__LegendLabel
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
react-dom.development.js:88 Warning: React does not recognize the `hasMargin` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hasmargin` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in svg (created by BaseIcon)
in BaseIcon (created by Icon)
in Icon (created by Tooltipify[Icon])
in Tooltipify[Icon] (created by Badgestyled__BadgeIcon)
in Badgestyled__BadgeIcon (created by Badge)
in a (created by Link)
in Link (created by BaseLink)
in BaseLink (created by Link)
in Link (created by RawMaybeLink)
in RawMaybeLink (created by Badgestyled__MaybeLink)
in Badgestyled__MaybeLink (created by Badge)
in Badge (created by CollectionBadge)
in CollectionBadge (created by EntityObjectLoader)
in EntityObjectLoader (created by Connect(EntityObjectLoader))
in Connect(EntityObjectLoader) (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType)
in Unknown (created by Header)
in div (created by Clean.div)
in Clean.div (created by Flex)
in Flex (created by Header)
in div (created by Clean.div)
in Clean.div (created by Box)
in Box (created by Header)
in div (created by Header)
in div (created by Header)
in Header (created by DashboardHeader)
in DashboardHeader (created by LoadingAndErrorWrapper)
in header (created by Dashboardstyled__HeaderContainer)
in Dashboardstyled__HeaderContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
printWarning @ react-dom.development.js:88
react-dom.development.js:88 Warning: React does not recognize the `activeColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `activecolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in a (created by Link)
in Link (created by BaseLink)
in BaseLink (created by Link)
in Link (created by RawMaybeLink)
in RawMaybeLink (created by Badgestyled__MaybeLink)
in Badgestyled__MaybeLink (created by Badge)
in Badge (created by CollectionBadge)
in CollectionBadge (created by EntityObjectLoader)
in EntityObjectLoader (created by Connect(EntityObjectLoader))
in Connect(EntityObjectLoader) (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType)
in Unknown (created by Header)
in div (created by Clean.div)
in Clean.div (created by Flex)
in Flex (created by Header)
in div (created by Clean.div)
in Clean.div (created by Box)
in Box (created by Header)
in div (created by Header)
in div (created by Header)
in Header (created by DashboardHeader)
in DashboardHeader (created by LoadingAndErrorWrapper)
in header (created by Dashboardstyled__HeaderContainer)
in Dashboardstyled__HeaderContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
printWarning @ react-dom.development.js:88
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Badgestyled__BadgeIcon, Badgestyled__MaybeLink
printWarning @ react-dom.development.js:88
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Badgestyled__BadgeIcon, Badgestyled__MaybeLink
printWarning @ react-dom.development.js:88
VM2823 react_devtools_backend.js:2540 Warning: Failed prop type: Invalid prop `target` supplied to `Popover`.
in Popover (created by TooltipPopover)
in TooltipPopover
in TooltipPopover (created by Tooltip)
in Tooltip (created by DashboardHeader)
in span (created by Header)
in span (created by Header)
in div (created by Header)
in div (created by Header)
in div (created by Header)
in Header (created by DashboardHeader)
in DashboardHeader (created by LoadingAndErrorWrapper)
in header (created by Dashboardstyled__HeaderContainer)
in Dashboardstyled__HeaderContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
VM2823 react_devtools_backend.js:2540 Warning: React does not recognize the `maxHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in span (created by TooltipPopover)
in div
in span
overrideMethod @ VM2823 react_devtools_backend.js:2540
VM2823 react_devtools_backend.js:2540 Warning: Each child in a list should have a unique "key" prop.
Check the render method of `DashCardActionButtons`. See https://fb.me/react-warning-keys for more information.
in ChartSettingsButton (created by DashCardActionButtons)
in DashCardActionButtons (created by DashCard)
in div (created by DashCard__DashboardCardActionsPanel)
in DashCard__DashboardCardActionsPanel (created by DashCard)
in div (created by DashCard)
in DashCard (created by GridLayout)
in div (created by GridItem)
in Resizable (created by GridItem)
in DraggableCore (created by GridItem)
in GridItem (created by ReactGridLayout)
in div (created by ReactGridLayout)
in ReactGridLayout (created by ResponsiveReactGridLayout)
in ResponsiveReactGridLayout (created by GridLayout)
in GridLayout (created by DashboardGrid)
in div (created by DashboardGrid)
in DashboardGrid (created by ExplicitSize[DashboardGrid])
in ExplicitSize[DashboardGrid] (created by LoadingAndErrorWrapper)
in div (created by FullWidthContainer)
in FullWidthContainer (created by Dashboardstyled__CardsContainer)
in Dashboardstyled__CardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__ParametersAndCardsContainer)
in Dashboardstyled__ParametersAndCardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react.development.js:315
error @ react.development.js:287
validateExplicitKey @ react.development.js:1630
validateChildKeys @ react.development.js:1656
createElementWithValidation @ react.development.js:1806
DashCardActionButtons @ DashCard.jsx:366
renderWithHooks @ react-dom.development.js:14803
mountIndeterminateComponent @ react-dom.development.js:17482
beginWork @ react-dom.development.js:18596
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: DashCard__DashboardCardActionsPanel
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: DashCard__DashboardCardActionsPanel
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: Failed prop type: Invalid prop `collectionId` of type `number` supplied to `QuestionList`, expected `string`.
in QuestionList (created by QuestionPicker)
in QuestionPicker (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by EntityListLoader)
in EntityListLoader (created by Connect(EntityListLoader))
in Connect(EntityListLoader) (created by _class2)
in _class2 (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType) (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by AddCardSidebar)
in div (created by Sidebar)
in aside (created by Sidebar)
in Sidebar (created by AddCardSidebar)
in AddCardSidebar (created by DashboardSidebars)
in DashboardSidebars (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ checkPropTypes.js:20
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1714
createElementWithValidation @ react.development.js:1813
QuestionPicker @ QuestionPicker.jsx:105
renderWithHooks @ react-dom.development.js:14803
mountIndeterminateComponent @ react-dom.development.js:17482
beginWork @ react-dom.development.js:18596
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionPickerstyled__BreadcrumbsWrapper, QuestionPickerstyled__SearchInput, TextInputstyled__IconWrapper, TextInputstyled__Input, TextInputstyled__TextInputRoot
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionPickerstyled__BreadcrumbsWrapper, QuestionPickerstyled__SearchInput, TextInputstyled__IconWrapper, TextInputstyled__Input, TextInputstyled__TextInputRoot
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: Failed prop type: Invalid prop `id` of type `number` supplied to `SelectListItem`, expected `string`.
in SelectListItem (created by QuestionListstyled__QuestionListItem)
in QuestionListstyled__QuestionListItem (created by LoadingAndErrorWrapper)
in ul (created by SelectList)
in SelectList (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by EntityListLoader)
in EntityListLoader (created by Connect(EntityListLoader))
in Connect(EntityListLoader) (created by _class2)
in _class2 (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType) (created by search.ListLoader)
in search.ListLoader (created by QuestionList)
in QuestionList (created by QuestionPicker)
in div (created by Clean.div)
in Clean.div (created by Box)
in Box (created by QuestionPicker)
in QuestionPicker (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by EntityListLoader)
in EntityListLoader (created by Connect(EntityListLoader))
in Connect(EntityListLoader) (created by _class2)
in _class2 (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType) (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by AddCardSidebar)
in div (created by Sidebar)
in aside (created by Sidebar)
in Sidebar (created by AddCardSidebar)
in AddCardSidebar (created by DashboardSidebars)
in DashboardSidebars (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ checkPropTypes.js:20
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1714
createElementWithValidation @ react.development.js:1813
render @ styled-components.browser.es.js:1791
finishClassComponent @ react-dom.development.js:17160
updateClassComponent @ react-dom.development.js:17110
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
(anonymous) @ redux.js:241
setTimeout (async)
_callee4$ @ redux.js:241
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Promise.then (async)
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:229
(anonymous) @ redux.js:298
_callee3$ @ redux.js:200
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:200
(anonymous) @ store.js:23
(anonymous) @ bindActionCreators.js:3
_callee$ @ EntityListLoader.jsx:141
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ EntityLink.jsx:31
_next @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityListLoader.jsx:140
UNSAFE_componentWillMount @ EntityListLoader.jsx:160
callComponentWillMount @ react-dom.development.js:12953
mountClassInstance @ react-dom.development.js:13048
updateClassComponent @ react-dom.development.js:17101
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
Show 43 more frames
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionListstyled__QuestionListItem, SelectListItemstyled__ItemIcon, SelectListItemstyled__ItemRoot, SelectListItemstyled__ItemTitle, Text
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
(anonymous) @ redux.js:241
setTimeout (async)
_callee4$ @ redux.js:241
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Promise.then (async)
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:229
(anonymous) @ redux.js:298
_callee3$ @ redux.js:200
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:200
(anonymous) @ store.js:23
(anonymous) @ bindActionCreators.js:3
_callee$ @ EntityListLoader.jsx:141
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ EntityLink.jsx:31
_next @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityListLoader.jsx:140
UNSAFE_componentWillMount @ EntityListLoader.jsx:160
callComponentWillMount @ react-dom.development.js:12953
mountClassInstance @ react-dom.development.js:13048
updateClassComponent @ react-dom.development.js:17101
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
Show 43 more frames
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionListstyled__QuestionListItem, SelectListItemstyled__ItemIcon, SelectListItemstyled__ItemRoot, SelectListItemstyled__ItemTitle, Text
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
(anonymous) @ redux.js:241
setTimeout (async)
_callee4$ @ redux.js:241
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Promise.then (async)
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:229
(anonymous) @ redux.js:298
_callee3$ @ redux.js:200
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:200
(anonymous) @ store.js:23
(anonymous) @ bindActionCreators.js:3
_callee$ @ EntityListLoader.jsx:141
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ EntityLink.jsx:31
_next @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityListLoader.jsx:140
UNSAFE_componentWillMount @ EntityListLoader.jsx:160
callComponentWillMount @ react-dom.development.js:12953
mountClassInstance @ react-dom.development.js:13048
updateClassComponent @ react-dom.development.js:17101
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
Show 43 more frames
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: TextInputstyled__ClearButton
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
flushPendingDiscreteUpdates @ react-dom.development.js:21847
flushDiscreteUpdates @ react-dom.development.js:21827
finishEventHandler @ react-dom.development.js:764
batchedEventUpdates @ react-dom.development.js:798
dispatchEventForLegacyPluginEventSystem @ react-dom.development.js:3568
attemptToDispatchEvent @ react-dom.development.js:4267
dispatchEvent @ react-dom.development.js:4189
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
discreteUpdates$1 @ react-dom.development.js:21887
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: TextInputstyled__ClearButton
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
flushPendingDiscreteUpdates @ react-dom.development.js:21847
flushDiscreteUpdates @ react-dom.development.js:21827
finishEventHandler @ react-dom.development.js:764
batchedEventUpdates @ react-dom.development.js:798
dispatchEventForLegacyPluginEventSystem @ react-dom.development.js:3568
attemptToDispatchEvent @ react-dom.development.js:4267
dispatchEvent @ react-dom.development.js:4189
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
discreteUpdates$1 @ react-dom.development.js:21887
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
```
</details>
I couldn't find anything relevant in the server logs.
**To Reproduce**
1. Edit a dashboard
2. Click `Add question`
3. Search for a question title that you know exists
4. It does not show up in results
5. Try searching the same phrase in global search
6. Question shows up at top of search results, click to open it
Most of this video is just the loading time during the search. You can feel free to skip around - there isn't anything very exciting.
https://user-images.githubusercontent.com/29556484/146084497-1315ef9d-6da6-488d-b032-efc642b7c256.mp4
**Expected behavior**
This question should show up at the top of the search list for Add Question just as it does for Global Search. If not the top, it should be somewhere on the list.
**Information about your Metabase Installation:**
```
{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.13+8",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "11.0.13",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.13+8",
"os.name": "Linux",
"os.version": "4.14.186-146.268.amzn2.x86_64",
"user.language": "en",
"user.timezone": "GMT"
},
"metabase-info": {
"databases": [
"redshift",
"postgres",
"snowflake",
"h2",
"sparksql"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "11.12"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.23"
}
},
"run-mode": "prod",
"version": {
"date": "2021-12-10",
"tag": "v0.41.5-SNAPSHOT",
"branch": "convoy-release-0.41.4",
"hash": "7cf979c"
},
"settings": {
"report-timezone": "UTC"
}
}
}
```
**Severity**
This is low priority. Users are working around this by using `Add to dashboard` directly from the question.
|
1.0
|
Add Question search in Dashboard editor does not return question with exact name match - **Describe the bug**
When using the search function to add a question to a dashboard, the question whose name exactly matches my search phrase does not show up in the result list. The question does show up, however, in the global search.
**Logs**
<details><summary>The web console doesn't show anything particularly notable, but here it is.</summary>
```
i18n.js:49 Setting moment.js start of week for Locale en to sunday
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: ThemeProvider
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
scheduleUpdateOnFiber @ react-dom.development.js:21188
updateContainer @ react-dom.development.js:24373
(anonymous) @ react-dom.development.js:24758
unbatchedUpdates @ react-dom.development.js:21903
legacyRenderSubtreeIntoContainer @ react-dom.development.js:24757
render @ react-dom.development.js:24840
_init @ app.js:76
(anonymous) @ app.js:118
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: DragDropContextProvider, ThemeProvider
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
scheduleUpdateOnFiber @ react-dom.development.js:21188
updateContainer @ react-dom.development.js:24373
(anonymous) @ react-dom.development.js:24758
unbatchedUpdates @ react-dom.development.js:21903
legacyRenderSubtreeIntoContainer @ react-dom.development.js:24757
render @ react-dom.development.js:24840
_init @ app.js:76
(anonymous) @ app.js:118
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Box, Dashboardstyled__DashboardLoadingAndErrorWrapper, Flex, Icon, Icon__IconWrapper, Link, MetabaseIsSetup(Connect(UserIsAuthenticated(Component))), SearchBarstyled__SearchInput, SearchBarstyled__SearchWrapper, UndoListing__UndoList, UserIsAuthenticated(Component)
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
(anonymous) @ Router.js:109
(anonymous) @ createTransitionManager.js:228
(anonymous) @ createTransitionManager.js:83
done @ AsyncUtils.js:74
(anonymous) @ AsyncUtils.js:80
getComponentsForRoute @ getComponents.js:6
(anonymous) @ getComponents.js:30
(anonymous) @ AsyncUtils.js:79
mapAsync @ AsyncUtils.js:78
getComponents @ getComponents.js:29
finishEnterHooks @ createTransitionManager.js:77
next @ AsyncUtils.js:47
(anonymous) @ TransitionUtils.js:88
wrappedNext @ TransitionUtils.js:110
_callee$ @ routes.jsx:166
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ utils.js:127
_next @ utils.js:127
Show 8 more frames
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Box, Dashboardstyled__DashboardLoadingAndErrorWrapper, Flex, Icon, Icon__IconWrapper, Link, MetabaseIsSetup(Connect(UserIsAuthenticated(Component))), SearchBarstyled__SearchInput, SearchBarstyled__SearchWrapper, UndoListing__UndoList, UserIsAuthenticated(Component)
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
(anonymous) @ Router.js:109
(anonymous) @ createTransitionManager.js:228
(anonymous) @ createTransitionManager.js:83
done @ AsyncUtils.js:74
(anonymous) @ AsyncUtils.js:80
getComponentsForRoute @ getComponents.js:6
(anonymous) @ getComponents.js:30
(anonymous) @ AsyncUtils.js:79
mapAsync @ AsyncUtils.js:78
getComponents @ getComponents.js:29
finishEnterHooks @ createTransitionManager.js:77
next @ AsyncUtils.js:47
(anonymous) @ TransitionUtils.js:88
wrappedNext @ TransitionUtils.js:110
_callee$ @ routes.jsx:166
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ utils.js:127
_next @ utils.js:127
Show 8 more frames
metadata.js:18 DEPRECATED: metabase/redux/metadata addFields
deprecated @ metadata.js:18
addFields @ metadata.js:124
_callee6$ @ actions.js:707
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ index.js:20
_next @ index.js:20
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Button, Buttonstyled__TextButton, DashboardHeaderstyled__DashboardHeaderButton, Dashboardstyled__CardsContainer, Dashboardstyled__DashboardBody, Dashboardstyled__DashboardStyled, Dashboardstyled__HeaderContainer, Dashboardstyled__ParametersAndCardsContainer, FullWidthContainer, TransitionGroup
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Button, Buttonstyled__TextButton, DashboardHeaderstyled__DashboardHeaderButton, Dashboardstyled__CardsContainer, Dashboardstyled__DashboardBody, Dashboardstyled__DashboardStyled, Dashboardstyled__HeaderContainer, Dashboardstyled__ParametersAndCardsContainer, FullWidthContainer, TransitionGroup
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
checkPropTypes.js:20 Warning: Failed prop type: minWidth larger than item width/maxWidth
in GridItem (created by ReactGridLayout)
in ReactGridLayout (created by ResponsiveReactGridLayout)
in ResponsiveReactGridLayout (created by GridLayout)
in GridLayout (created by DashboardGrid)
in div (created by DashboardGrid)
in DashboardGrid (created by ExplicitSize[DashboardGrid])
in ExplicitSize[DashboardGrid] (created by LoadingAndErrorWrapper)
in div (created by FullWidthContainer)
in FullWidthContainer (created by Dashboardstyled__CardsContainer)
in Dashboardstyled__CardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__ParametersAndCardsContainer)
in Dashboardstyled__ParametersAndCardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
printWarning @ checkPropTypes.js:20
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1714
createElementWithValidation @ react.development.js:1813
processGridItem @ ReactGridLayout.js:649
(anonymous) @ ReactGridLayout.js:714
mapSingleChildIntoContext @ react.development.js:1149
traverseAllChildrenImpl @ react.development.js:1007
traverseAllChildrenImpl @ react.development.js:1023
traverseAllChildren @ react.development.js:1092
mapIntoWithKeyPrefixInternal @ react.development.js:1174
mapChildren @ react.development.js:1198
render @ ReactGridLayout.js:713
finishClassComponent @ react-dom.development.js:17160
updateClassComponent @ react-dom.development.js:17110
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 13 more frames
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: ChartCaptionstyled__ChartCaptionRoot, LegendActionsstyled__LegendActionsRoot, LegendCaptionstyled__LegendCaptionRoot, LegendCaptionstyled__LegendLabel
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: ChartCaptionstyled__ChartCaptionRoot, LegendActionsstyled__LegendActionsRoot, LegendCaptionstyled__LegendCaptionRoot, LegendCaptionstyled__LegendLabel
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
_callee3$ @ redux.js:204
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Show 3 more frames
react-dom.development.js:88 Warning: React does not recognize the `hasMargin` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hasmargin` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in svg (created by BaseIcon)
in BaseIcon (created by Icon)
in Icon (created by Tooltipify[Icon])
in Tooltipify[Icon] (created by Badgestyled__BadgeIcon)
in Badgestyled__BadgeIcon (created by Badge)
in a (created by Link)
in Link (created by BaseLink)
in BaseLink (created by Link)
in Link (created by RawMaybeLink)
in RawMaybeLink (created by Badgestyled__MaybeLink)
in Badgestyled__MaybeLink (created by Badge)
in Badge (created by CollectionBadge)
in CollectionBadge (created by EntityObjectLoader)
in EntityObjectLoader (created by Connect(EntityObjectLoader))
in Connect(EntityObjectLoader) (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType)
in Unknown (created by Header)
in div (created by Clean.div)
in Clean.div (created by Flex)
in Flex (created by Header)
in div (created by Clean.div)
in Clean.div (created by Box)
in Box (created by Header)
in div (created by Header)
in div (created by Header)
in Header (created by DashboardHeader)
in DashboardHeader (created by LoadingAndErrorWrapper)
in header (created by Dashboardstyled__HeaderContainer)
in Dashboardstyled__HeaderContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
printWarning @ react-dom.development.js:88
react-dom.development.js:88 Warning: React does not recognize the `activeColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `activecolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in a (created by Link)
in Link (created by BaseLink)
in BaseLink (created by Link)
in Link (created by RawMaybeLink)
in RawMaybeLink (created by Badgestyled__MaybeLink)
in Badgestyled__MaybeLink (created by Badge)
in Badge (created by CollectionBadge)
in CollectionBadge (created by EntityObjectLoader)
in EntityObjectLoader (created by Connect(EntityObjectLoader))
in Connect(EntityObjectLoader) (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType)
in Unknown (created by Header)
in div (created by Clean.div)
in Clean.div (created by Flex)
in Flex (created by Header)
in div (created by Clean.div)
in Clean.div (created by Box)
in Box (created by Header)
in div (created by Header)
in div (created by Header)
in Header (created by DashboardHeader)
in DashboardHeader (created by LoadingAndErrorWrapper)
in header (created by Dashboardstyled__HeaderContainer)
in Dashboardstyled__HeaderContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
printWarning @ react-dom.development.js:88
react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Badgestyled__BadgeIcon, Badgestyled__MaybeLink
printWarning @ react-dom.development.js:88
react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: Badgestyled__BadgeIcon, Badgestyled__MaybeLink
printWarning @ react-dom.development.js:88
VM2823 react_devtools_backend.js:2540 Warning: Failed prop type: Invalid prop `target` supplied to `Popover`.
in Popover (created by TooltipPopover)
in TooltipPopover
in TooltipPopover (created by Tooltip)
in Tooltip (created by DashboardHeader)
in span (created by Header)
in span (created by Header)
in div (created by Header)
in div (created by Header)
in div (created by Header)
in Header (created by DashboardHeader)
in DashboardHeader (created by LoadingAndErrorWrapper)
in header (created by Dashboardstyled__HeaderContainer)
in Dashboardstyled__HeaderContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
VM2823 react_devtools_backend.js:2540 Warning: React does not recognize the `maxHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in span (created by TooltipPopover)
in div
in span
overrideMethod @ VM2823 react_devtools_backend.js:2540
VM2823 react_devtools_backend.js:2540 Warning: Each child in a list should have a unique "key" prop.
Check the render method of `DashCardActionButtons`. See https://fb.me/react-warning-keys for more information.
in ChartSettingsButton (created by DashCardActionButtons)
in DashCardActionButtons (created by DashCard)
in div (created by DashCard__DashboardCardActionsPanel)
in DashCard__DashboardCardActionsPanel (created by DashCard)
in div (created by DashCard)
in DashCard (created by GridLayout)
in div (created by GridItem)
in Resizable (created by GridItem)
in DraggableCore (created by GridItem)
in GridItem (created by ReactGridLayout)
in div (created by ReactGridLayout)
in ReactGridLayout (created by ResponsiveReactGridLayout)
in ResponsiveReactGridLayout (created by GridLayout)
in GridLayout (created by DashboardGrid)
in div (created by DashboardGrid)
in DashboardGrid (created by ExplicitSize[DashboardGrid])
in ExplicitSize[DashboardGrid] (created by LoadingAndErrorWrapper)
in div (created by FullWidthContainer)
in FullWidthContainer (created by Dashboardstyled__CardsContainer)
in Dashboardstyled__CardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__ParametersAndCardsContainer)
in Dashboardstyled__ParametersAndCardsContainer (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react.development.js:315
error @ react.development.js:287
validateExplicitKey @ react.development.js:1630
validateChildKeys @ react.development.js:1656
createElementWithValidation @ react.development.js:1806
DashCardActionButtons @ DashCard.jsx:366
renderWithHooks @ react-dom.development.js:14803
mountIndeterminateComponent @ react-dom.development.js:17482
beginWork @ react-dom.development.js:18596
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: DashCard__DashboardCardActionsPanel
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: DashCard__DashboardCardActionsPanel
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: Failed prop type: Invalid prop `collectionId` of type `number` supplied to `QuestionList`, expected `string`.
in QuestionList (created by QuestionPicker)
in QuestionPicker (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by EntityListLoader)
in EntityListLoader (created by Connect(EntityListLoader))
in Connect(EntityListLoader) (created by _class2)
in _class2 (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType) (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by AddCardSidebar)
in div (created by Sidebar)
in aside (created by Sidebar)
in Sidebar (created by AddCardSidebar)
in AddCardSidebar (created by DashboardSidebars)
in DashboardSidebars (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ checkPropTypes.js:20
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1714
createElementWithValidation @ react.development.js:1813
QuestionPicker @ QuestionPicker.jsx:105
renderWithHooks @ react-dom.development.js:14803
mountIndeterminateComponent @ react-dom.development.js:17482
beginWork @ react-dom.development.js:18596
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionPickerstyled__BreadcrumbsWrapper, QuestionPickerstyled__SearchInput, TextInputstyled__IconWrapper, TextInputstyled__Input, TextInputstyled__TextInputRoot
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionPickerstyled__BreadcrumbsWrapper, QuestionPickerstyled__SearchInput, TextInputstyled__IconWrapper, TextInputstyled__Input, TextInputstyled__TextInputRoot
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: Failed prop type: Invalid prop `id` of type `number` supplied to `SelectListItem`, expected `string`.
in SelectListItem (created by QuestionListstyled__QuestionListItem)
in QuestionListstyled__QuestionListItem (created by LoadingAndErrorWrapper)
in ul (created by SelectList)
in SelectList (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by EntityListLoader)
in EntityListLoader (created by Connect(EntityListLoader))
in Connect(EntityListLoader) (created by _class2)
in _class2 (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType) (created by search.ListLoader)
in search.ListLoader (created by QuestionList)
in QuestionList (created by QuestionPicker)
in div (created by Clean.div)
in Clean.div (created by Box)
in Box (created by QuestionPicker)
in QuestionPicker (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by EntityListLoader)
in EntityListLoader (created by Connect(EntityListLoader))
in Connect(EntityListLoader) (created by _class2)
in _class2 (created by EntityType)
in EntityType (created by Connect(EntityType))
in Connect(EntityType) (created by Connect(QuestionPicker))
in Connect(QuestionPicker) (created by AddCardSidebar)
in div (created by Sidebar)
in aside (created by Sidebar)
in Sidebar (created by AddCardSidebar)
in AddCardSidebar (created by DashboardSidebars)
in DashboardSidebars (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardBody)
in Dashboardstyled__DashboardBody (created by LoadingAndErrorWrapper)
in div (created by Dashboardstyled__DashboardStyled)
in Dashboardstyled__DashboardStyled (created by LoadingAndErrorWrapper)
in div (created by LoadingAndErrorWrapper)
in LoadingAndErrorWrapper (created by Dashboardstyled__DashboardLoadingAndErrorWrapper)
in Dashboardstyled__DashboardLoadingAndErrorWrapper (created by Dashboard)
in Dashboard (created by DashboardControls[Dashboard])
in DashboardControls[Dashboard] (created by Connect(DashboardControls[Dashboard]))
in Connect(DashboardControls[Dashboard]) (created by DashboardApp)
in div (created by DashboardApp)
in DashboardApp
in Unknown (created by Title[])
in Title[] (created by Title[Title[]])
in Title[Title[]] (created by FitViewport)
in FitViewport (created by Connect(FitViewport))
in Connect(FitViewport) (created by Title[Connect(FitViewport)])
in Title[Connect(FitViewport)] (created by RouterContext)
in Unknown (created by UserIsAuthenticated(Component))
in UserIsAuthenticated(Component) (created by Connect(UserIsAuthenticated(Component)))
in Connect(UserIsAuthenticated(Component)) (created by MetabaseIsSetup(Connect(UserIsAuthenticated(Component))))
in MetabaseIsSetup(Connect(UserIsAuthenticated(Component))) (created by Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))))
in Connect(MetabaseIsSetup(Connect(UserIsAuthenticated(Component)))) (created by RouterContext)
in div (created by App)
in ScrollToTop (created by withRouter(ScrollToTop))
in withRouter(ScrollToTop) (created by App)
in App (created by Connect(App))
in Connect(App) (created by Title[Connect(App)])
in Title[Connect(App)] (created by RouterContext)
in RouterContext (created by Router)
in Router
in ThemeProvider
in DragDropContextProvider
in Provider
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ checkPropTypes.js:20
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1714
createElementWithValidation @ react.development.js:1813
render @ styled-components.browser.es.js:1791
finishClassComponent @ react-dom.development.js:17160
updateClassComponent @ react-dom.development.js:17110
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
(anonymous) @ redux.js:241
setTimeout (async)
_callee4$ @ redux.js:241
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Promise.then (async)
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:229
(anonymous) @ redux.js:298
_callee3$ @ redux.js:200
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:200
(anonymous) @ store.js:23
(anonymous) @ bindActionCreators.js:3
_callee$ @ EntityListLoader.jsx:141
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ EntityLink.jsx:31
_next @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityListLoader.jsx:140
UNSAFE_componentWillMount @ EntityListLoader.jsx:160
callComponentWillMount @ react-dom.development.js:12953
mountClassInstance @ react-dom.development.js:13048
updateClassComponent @ react-dom.development.js:17101
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
Show 43 more frames
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionListstyled__QuestionListItem, SelectListItemstyled__ItemIcon, SelectListItemstyled__ItemRoot, SelectListItemstyled__ItemTitle, Text
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
(anonymous) @ redux.js:241
setTimeout (async)
_callee4$ @ redux.js:241
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Promise.then (async)
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:229
(anonymous) @ redux.js:298
_callee3$ @ redux.js:200
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:200
(anonymous) @ store.js:23
(anonymous) @ bindActionCreators.js:3
_callee$ @ EntityListLoader.jsx:141
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ EntityLink.jsx:31
_next @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityListLoader.jsx:140
UNSAFE_componentWillMount @ EntityListLoader.jsx:160
callComponentWillMount @ react-dom.development.js:12953
mountClassInstance @ react-dom.development.js:13048
updateClassComponent @ react-dom.development.js:17101
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
Show 43 more frames
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: QuestionListstyled__QuestionListItem, SelectListItemstyled__ItemIcon, SelectListItemstyled__ItemRoot, SelectListItemstyled__ItemTitle, Text
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
scheduleUpdateOnFiber @ react-dom.development.js:21199
enqueueSetState @ react-dom.development.js:12639
push.../../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:471
onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
notifyNestedSubs @ Subscription.js:62
onStateChange @ connectAdvanced.js:204
dispatch @ createStore.js:173
(anonymous) @ middleware.js:22
(anonymous) @ index.js:28
(anonymous) @ store.js:25
dispatch @ applyMiddleware.js:35
(anonymous) @ redux.js:241
setTimeout (async)
_callee4$ @ redux.js:241
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
Promise.then (async)
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:229
(anonymous) @ redux.js:298
_callee3$ @ redux.js:200
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ query_time.js:284
_next @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ query_time.js:284
(anonymous) @ redux.js:200
(anonymous) @ store.js:23
(anonymous) @ bindActionCreators.js:3
_callee$ @ EntityListLoader.jsx:141
tryCatch @ runtime.js:63
invoke @ runtime.js:293
(anonymous) @ runtime.js:118
asyncGeneratorStep @ EntityLink.jsx:31
_next @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityLink.jsx:31
(anonymous) @ EntityListLoader.jsx:140
UNSAFE_componentWillMount @ EntityListLoader.jsx:160
callComponentWillMount @ react-dom.development.js:12953
mountClassInstance @ react-dom.development.js:13048
updateClassComponent @ react-dom.development.js:17101
beginWork @ react-dom.development.js:18620
beginWork$1 @ react-dom.development.js:23179
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
discreteUpdates$1 @ react-dom.development.js:21893
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
Show 43 more frames
VM2823 react_devtools_backend.js:2540 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: TextInputstyled__ClearButton
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11371
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
flushPendingDiscreteUpdates @ react-dom.development.js:21847
flushDiscreteUpdates @ react-dom.development.js:21827
finishEventHandler @ react-dom.development.js:764
batchedEventUpdates @ react-dom.development.js:798
dispatchEventForLegacyPluginEventSystem @ react-dom.development.js:3568
attemptToDispatchEvent @ react-dom.development.js:4267
dispatchEvent @ react-dom.development.js:4189
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
discreteUpdates$1 @ react-dom.development.js:21887
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
VM2823 react_devtools_backend.js:2540 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
Please update the following components: TextInputstyled__ClearButton
overrideMethod @ VM2823 react_devtools_backend.js:2540
printWarning @ react-dom.development.js:88
warn @ react-dom.development.js:51
push.../../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11377
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23112
commitRootImpl @ react-dom.development.js:22396
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
flushPendingDiscreteUpdates @ react-dom.development.js:21847
flushDiscreteUpdates @ react-dom.development.js:21827
finishEventHandler @ react-dom.development.js:764
batchedEventUpdates @ react-dom.development.js:798
dispatchEventForLegacyPluginEventSystem @ react-dom.development.js:3568
attemptToDispatchEvent @ react-dom.development.js:4267
dispatchEvent @ react-dom.development.js:4189
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
discreteUpdates$1 @ react-dom.development.js:21887
discreteUpdates @ react-dom.development.js:806
dispatchDiscreteEvent @ react-dom.development.js:4168
```
</details>
I couldn't find anything relevant in the server logs.
**To Reproduce**
1. Edit a dashboard
2. Click `Add question`
3. Search for a question title that you know exists
4. It does not show up in results
5. Try searching the same phrase in global search
6. Question shows up at top of search results, click to open it
Most of this video is just the loading time during the search. You can feel free to skip around - there isn't anything very exciting.
https://user-images.githubusercontent.com/29556484/146084497-1315ef9d-6da6-488d-b032-efc642b7c256.mp4
**Expected behavior**
This question should show up at the top of the search list for Add Question just as it does for Global Search. If not the top, it should be somewhere on the list.
**Information about your Metabase Installation:**
```
{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.13+8",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "11.0.13",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.13+8",
"os.name": "Linux",
"os.version": "4.14.186-146.268.amzn2.x86_64",
"user.language": "en",
"user.timezone": "GMT"
},
"metabase-info": {
"databases": [
"redshift",
"postgres",
"snowflake",
"h2",
"sparksql"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "11.12"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.23"
}
},
"run-mode": "prod",
"version": {
"date": "2021-12-10",
"tag": "v0.41.5-SNAPSHOT",
"branch": "convoy-release-0.41.4",
"hash": "7cf979c"
},
"settings": {
"report-timezone": "UTC"
}
}
}
```
**Severity**
This is low priority. Users are working around this by using `Add to dashboard` directly from the question.
|
non_process
|
add question search in dashboard editor does not return question with exact name match describe the bug when using the search function to add a question to a dashboard the question whose name exactly matches my search phrase does not show up in the result list the question does show up however in the global search logs the web console doesn t show anything particularly notable but here it is js setting moment js start of week for locale en to sunday react dom development js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components themeprovider printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js scheduleupdateonfiber react dom development js updatecontainer react dom development js anonymous react dom development js unbatchedupdates react dom development js legacyrendersubtreeintocontainer react dom development js render react dom development js init app js anonymous app js react dom development js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components dragdropcontextprovider themeprovider printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js scheduleupdateonfiber react dom development js updatecontainer react dom development js anonymous react dom development js unbatchedupdates react dom development js legacyrendersubtreeintocontainer react dom development js render react dom development js init app js anonymous app js react dom development js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components box dashboardstyled dashboardloadinganderrorwrapper flex icon icon iconwrapper link metabaseissetup connect userisauthenticated component searchbarstyled searchinput searchbarstyled searchwrapper undolisting undolist userisauthenticated component printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js anonymous router js anonymous createtransitionmanager js anonymous createtransitionmanager js done asyncutils js anonymous asyncutils js getcomponentsforroute getcomponents js anonymous getcomponents js anonymous asyncutils js mapasync asyncutils js getcomponents getcomponents js finishenterhooks createtransitionmanager js next asyncutils js anonymous transitionutils js wrappednext transitionutils js callee routes jsx trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep utils js next utils js show more frames react dom development js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components box dashboardstyled dashboardloadinganderrorwrapper flex icon icon iconwrapper link metabaseissetup connect userisauthenticated component searchbarstyled searchinput searchbarstyled searchwrapper undolisting undolist userisauthenticated component printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js anonymous router js anonymous createtransitionmanager js anonymous createtransitionmanager js done asyncutils js anonymous asyncutils js getcomponentsforroute getcomponents js anonymous getcomponents js anonymous asyncutils js mapasync asyncutils js getcomponents getcomponents js finishenterhooks createtransitionmanager js next asyncutils js anonymous transitionutils js wrappednext transitionutils js callee routes jsx trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep utils js next utils js show more frames metadata js deprecated metabase redux metadata addfields deprecated metadata js addfields metadata js actions js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep index js next index js react dom development js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components button buttonstyled textbutton dashboardheaderstyled dashboardheaderbutton dashboardstyled cardscontainer dashboardstyled dashboardbody dashboardstyled dashboardstyled dashboardstyled headercontainer dashboardstyled parametersandcardscontainer fullwidthcontainer transitiongroup printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js show more frames react dom development js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components button buttonstyled textbutton dashboardheaderstyled dashboardheaderbutton dashboardstyled cardscontainer dashboardstyled dashboardbody dashboardstyled dashboardstyled dashboardstyled headercontainer dashboardstyled parametersandcardscontainer fullwidthcontainer transitiongroup printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js show more frames checkproptypes js warning failed prop type minwidth larger than item width maxwidth in griditem created by reactgridlayout in reactgridlayout created by responsivereactgridlayout in responsivereactgridlayout created by gridlayout in gridlayout created by dashboardgrid in div created by dashboardgrid in dashboardgrid created by explicitsize in explicitsize created by loadinganderrorwrapper in div created by fullwidthcontainer in fullwidthcontainer created by dashboardstyled cardscontainer in dashboardstyled cardscontainer created by loadinganderrorwrapper in div created by dashboardstyled parametersandcardscontainer in dashboardstyled parametersandcardscontainer created by loadinganderrorwrapper in div created by dashboardstyled dashboardbody in dashboardstyled dashboardbody created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider printwarning checkproptypes js checkproptypes checkproptypes js validateproptypes react development js createelementwithvalidation react development js processgriditem reactgridlayout js anonymous reactgridlayout js mapsinglechildintocontext react development js traverseallchildrenimpl react development js traverseallchildrenimpl react development js traverseallchildren react development js mapintowithkeyprefixinternal react development js mapchildren react development js render reactgridlayout js finishclasscomponent react dom development js updateclasscomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js show more frames react dom development js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components chartcaptionstyled chartcaptionroot legendactionsstyled legendactionsroot legendcaptionstyled legendcaptionroot legendcaptionstyled legendlabel printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js show more frames react dom development js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components chartcaptionstyled chartcaptionroot legendactionsstyled legendactionsroot legendcaptionstyled legendcaptionroot legendcaptionstyled legendlabel printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js show more frames react dom development js warning react does not recognize the hasmargin prop on a dom element if you intentionally want it to appear in the dom as a custom attribute spell it as lowercase hasmargin instead if you accidentally passed it from a parent component remove it from the dom element in svg created by baseicon in baseicon created by icon in icon created by tooltipify in tooltipify created by badgestyled badgeicon in badgestyled badgeicon created by badge in a created by link in link created by baselink in baselink created by link in link created by rawmaybelink in rawmaybelink created by badgestyled maybelink in badgestyled maybelink created by badge in badge created by collectionbadge in collectionbadge created by entityobjectloader in entityobjectloader created by connect entityobjectloader in connect entityobjectloader created by entitytype in entitytype created by connect entitytype in connect entitytype in unknown created by header in div created by clean div in clean div created by flex in flex created by header in div created by clean div in clean div created by box in box created by header in div created by header in div created by header in header created by dashboardheader in dashboardheader created by loadinganderrorwrapper in header created by dashboardstyled headercontainer in dashboardstyled headercontainer created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider printwarning react dom development js react dom development js warning react does not recognize the activecolor prop on a dom element if you intentionally want it to appear in the dom as a custom attribute spell it as lowercase activecolor instead if you accidentally passed it from a parent component remove it from the dom element in a created by link in link created by baselink in baselink created by link in link created by rawmaybelink in rawmaybelink created by badgestyled maybelink in badgestyled maybelink created by badge in badge created by collectionbadge in collectionbadge created by entityobjectloader in entityobjectloader created by connect entityobjectloader in connect entityobjectloader created by entitytype in entitytype created by connect entitytype in connect entitytype in unknown created by header in div created by clean div in clean div created by flex in flex created by header in div created by clean div in clean div created by box in box created by header in div created by header in div created by header in header created by dashboardheader in dashboardheader created by loadinganderrorwrapper in header created by dashboardstyled headercontainer in dashboardstyled headercontainer created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider printwarning react dom development js react dom development js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components badgestyled badgeicon badgestyled maybelink printwarning react dom development js react dom development js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components badgestyled badgeicon badgestyled maybelink printwarning react dom development js react devtools backend js warning failed prop type invalid prop target supplied to popover in popover created by tooltippopover in tooltippopover in tooltippopover created by tooltip in tooltip created by dashboardheader in span created by header in span created by header in div created by header in div created by header in div created by header in header created by dashboardheader in dashboardheader created by loadinganderrorwrapper in header created by dashboardstyled headercontainer in dashboardstyled headercontainer created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider overridemethod react devtools backend js react devtools backend js warning react does not recognize the maxheight prop on a dom element if you intentionally want it to appear in the dom as a custom attribute spell it as lowercase maxheight instead if you accidentally passed it from a parent component remove it from the dom element in span created by tooltippopover in div in span overridemethod react devtools backend js react devtools backend js warning each child in a list should have a unique key prop check the render method of dashcardactionbuttons see for more information in chartsettingsbutton created by dashcardactionbuttons in dashcardactionbuttons created by dashcard in div created by dashcard dashboardcardactionspanel in dashcard dashboardcardactionspanel created by dashcard in div created by dashcard in dashcard created by gridlayout in div created by griditem in resizable created by griditem in draggablecore created by griditem in griditem created by reactgridlayout in div created by reactgridlayout in reactgridlayout created by responsivereactgridlayout in responsivereactgridlayout created by gridlayout in gridlayout created by dashboardgrid in div created by dashboardgrid in dashboardgrid created by explicitsize in explicitsize created by loadinganderrorwrapper in div created by fullwidthcontainer in fullwidthcontainer created by dashboardstyled cardscontainer in dashboardstyled cardscontainer created by loadinganderrorwrapper in div created by dashboardstyled parametersandcardscontainer in dashboardstyled parametersandcardscontainer created by loadinganderrorwrapper in div created by dashboardstyled dashboardbody in dashboardstyled dashboardbody created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider overridemethod react devtools backend js printwarning react development js error react development js validateexplicitkey react development js validatechildkeys react development js createelementwithvalidation react development js dashcardactionbuttons dashcard jsx renderwithhooks react dom development js mountindeterminatecomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components dashcard dashboardcardactionspanel overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components dashcard dashboardcardactionspanel overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning failed prop type invalid prop collectionid of type number supplied to questionlist expected string in questionlist created by questionpicker in questionpicker created by connect questionpicker in connect questionpicker created by entitylistloader in entitylistloader created by connect entitylistloader in connect entitylistloader created by in created by entitytype in entitytype created by connect entitytype in connect entitytype created by connect questionpicker in connect questionpicker created by addcardsidebar in div created by sidebar in aside created by sidebar in sidebar created by addcardsidebar in addcardsidebar created by dashboardsidebars in dashboardsidebars created by loadinganderrorwrapper in div created by dashboardstyled dashboardbody in dashboardstyled dashboardbody created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider overridemethod react devtools backend js printwarning checkproptypes js checkproptypes checkproptypes js validateproptypes react development js createelementwithvalidation react development js questionpicker questionpicker jsx renderwithhooks react dom development js mountindeterminatecomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components questionpickerstyled breadcrumbswrapper questionpickerstyled searchinput textinputstyled iconwrapper textinputstyled input textinputstyled textinputroot overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components questionpickerstyled breadcrumbswrapper questionpickerstyled searchinput textinputstyled iconwrapper textinputstyled input textinputstyled textinputroot overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning failed prop type invalid prop id of type number supplied to selectlistitem expected string in selectlistitem created by questionliststyled questionlistitem in questionliststyled questionlistitem created by loadinganderrorwrapper in ul created by selectlist in selectlist created by loadinganderrorwrapper in loadinganderrorwrapper created by entitylistloader in entitylistloader created by connect entitylistloader in connect entitylistloader created by in created by entitytype in entitytype created by connect entitytype in connect entitytype created by search listloader in search listloader created by questionlist in questionlist created by questionpicker in div created by clean div in clean div created by box in box created by questionpicker in questionpicker created by connect questionpicker in connect questionpicker created by entitylistloader in entitylistloader created by connect entitylistloader in connect entitylistloader created by in created by entitytype in entitytype created by connect entitytype in connect entitytype created by connect questionpicker in connect questionpicker created by addcardsidebar in div created by sidebar in aside created by sidebar in sidebar created by addcardsidebar in addcardsidebar created by dashboardsidebars in dashboardsidebars created by loadinganderrorwrapper in div created by dashboardstyled dashboardbody in dashboardstyled dashboardbody created by loadinganderrorwrapper in div created by dashboardstyled dashboardstyled in dashboardstyled dashboardstyled created by loadinganderrorwrapper in div created by loadinganderrorwrapper in loadinganderrorwrapper created by dashboardstyled dashboardloadinganderrorwrapper in dashboardstyled dashboardloadinganderrorwrapper created by dashboard in dashboard created by dashboardcontrols in dashboardcontrols created by connect dashboardcontrols in connect dashboardcontrols created by dashboardapp in div created by dashboardapp in dashboardapp in unknown created by title in title created by title in title created by fitviewport in fitviewport created by connect fitviewport in connect fitviewport created by title in title created by routercontext in unknown created by userisauthenticated component in userisauthenticated component created by connect userisauthenticated component in connect userisauthenticated component created by metabaseissetup connect userisauthenticated component in metabaseissetup connect userisauthenticated component created by connect metabaseissetup connect userisauthenticated component in connect metabaseissetup connect userisauthenticated component created by routercontext in div created by app in scrolltotop created by withrouter scrolltotop in withrouter scrolltotop created by app in app created by connect app in connect app created by title in title created by routercontext in routercontext created by router in router in themeprovider in dragdropcontextprovider in provider overridemethod react devtools backend js printwarning checkproptypes js checkproptypes checkproptypes js validateproptypes react development js createelementwithvalidation react development js render styled components browser es js finishclasscomponent react dom development js updateclasscomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js anonymous redux js settimeout async redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js promise then async asyncgeneratorstep query time js next query time js anonymous query time js anonymous query time js anonymous redux js anonymous redux js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js anonymous query time js anonymous query time js anonymous redux js anonymous store js anonymous bindactioncreators js callee entitylistloader jsx trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep entitylink jsx next entitylink jsx anonymous entitylink jsx anonymous entitylink jsx anonymous entitylistloader jsx unsafe componentwillmount entitylistloader jsx callcomponentwillmount react dom development js mountclassinstance react dom development js updateclasscomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js show more frames react devtools backend js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components questionliststyled questionlistitem selectlistitemstyled itemicon selectlistitemstyled itemroot selectlistitemstyled itemtitle text overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js anonymous redux js settimeout async redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js promise then async asyncgeneratorstep query time js next query time js anonymous query time js anonymous query time js anonymous redux js anonymous redux js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js anonymous query time js anonymous query time js anonymous redux js anonymous store js anonymous bindactioncreators js callee entitylistloader jsx trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep entitylink jsx next entitylink jsx anonymous entitylink jsx anonymous entitylink jsx anonymous entitylistloader jsx unsafe componentwillmount entitylistloader jsx callcomponentwillmount react dom development js mountclassinstance react dom development js updateclasscomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js show more frames react devtools backend js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components questionliststyled questionlistitem selectlistitemstyled itemicon selectlistitemstyled itemroot selectlistitemstyled itemtitle text overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js scheduleupdateonfiber react dom development js enqueuesetstate react dom development js push node modules react cjs react development js component setstate react development js onstatechange connectadvanced js notify subscription js notifynestedsubs subscription js onstatechange connectadvanced js dispatch createstore js anonymous middleware js anonymous index js anonymous store js dispatch applymiddleware js anonymous redux js settimeout async redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js promise then async asyncgeneratorstep query time js next query time js anonymous query time js anonymous query time js anonymous redux js anonymous redux js redux js trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep query time js next query time js anonymous query time js anonymous query time js anonymous redux js anonymous store js anonymous bindactioncreators js callee entitylistloader jsx trycatch runtime js invoke runtime js anonymous runtime js asyncgeneratorstep entitylink jsx next entitylink jsx anonymous entitylink jsx anonymous entitylink jsx anonymous entitylistloader jsx unsafe componentwillmount entitylistloader jsx callcomponentwillmount react dom development js mountclassinstance react dom development js updateclasscomponent react dom development js beginwork react dom development js beginwork react dom development js performunitofwork react dom development js workloopsync react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js show more frames react devtools backend js warning componentwillmount has been renamed and is not recommended for use see for details move code with side effects to componentdidmount and set initial state in the constructor rename componentwillmount to unsafe componentwillmount to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components textinputstyled clearbutton overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js flushpendingdiscreteupdates react dom development js flushdiscreteupdates react dom development js finisheventhandler react dom development js batchedeventupdates react dom development js dispatcheventforlegacyplugineventsystem react dom development js attempttodispatchevent react dom development js dispatchevent react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js react devtools backend js warning componentwillreceiveprops has been renamed and is not recommended for use see for details move data fetching code or side effects to componentdidupdate if you re updating state whenever props change refactor your code to use memoization techniques or move it to static getderivedstatefromprops learn more at rename componentwillreceiveprops to unsafe componentwillreceiveprops to suppress this warning in non strict mode in react x only the unsafe name will work to rename all deprecated lifecycles to their new names you can run npx react codemod rename unsafe lifecycles in your project source folder please update the following components textinputstyled clearbutton overridemethod react devtools backend js printwarning react dom development js warn react dom development js push node modules react dom cjs react dom development js reactstrictmodewarnings flushpendingunsafelifecyclewarnings react dom development js flushrenderphasestrictmodewarningsindev react dom development js commitrootimpl react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js commitroot react dom development js finishsyncrender react dom development js performsyncworkonroot react dom development js anonymous react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js flushsynccallbackqueueimpl react dom development js flushsynccallbackqueue react dom development js flushpendingdiscreteupdates react dom development js flushdiscreteupdates react dom development js finisheventhandler react dom development js batchedeventupdates react dom development js dispatcheventforlegacyplugineventsystem react dom development js attempttodispatchevent react dom development js dispatchevent react dom development js unstable runwithpriority scheduler development js runwithpriority react dom development js discreteupdates react dom development js discreteupdates react dom development js dispatchdiscreteevent react dom development js i couldn t find anything relevant in the server logs to reproduce edit a dashboard click add question search for a question title that you know exists it does not show up in results try searching the same phrase in global search question shows up at top of search results click to open it most of this video is just the loading time during the search you can feel free to skip around there isn t anything very exciting expected behavior this question should show up at the top of the search list for add question just as it does for global search if not the top it should be somewhere on the list information about your metabase installation browser info language en us platform macintel useragent mozilla macintosh intel mac os x applewebkit khtml like gecko chrome safari vendor google inc system info file encoding utf java runtime name openjdk runtime environment java runtime version java vendor eclipse adoptium java vendor url java version java vm name openjdk bit server vm java vm version os name linux os version user language en user timezone gmt metabase info databases redshift postgres snowflake sparksql hosting env unknown application database postgres application database details database name postgresql version jdbc driver name postgresql jdbc driver version run mode prod version date tag snapshot branch convoy release hash settings report timezone utc severity this is low priority users are working around this by using add to dashboard directly from the question
| 0
|
70,563
| 7,191,161,190
|
IssuesEvent
|
2018-02-02 19:55:14
|
rust-lang/rust
|
https://api.github.com/repos/rust-lang/rust
|
closed
|
Error compiling problem case #4 from nll-rfc
|
A-NLL C-bug E-mentor E-needstest WG-compiler-nll
|
UPDATE: This example works now, but needs someone to add a test. See [mentoring instructions](https://github.com/rust-lang/rust/issues/46361#issuecomment-357991656) below.
---
I'm trying to compile some examples using nonlexical lifetimes. To do so, I'm compiling rustc using the `master` branch, and the `-Z nll` compiler option.
```
rustc 1.24.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.24.0-dev
LLVM version: 4.0
```
By compiling "Problem case 4: mutating &mut references" from [nll-rfc](https://github.com/nikomatsakis/nll-rfc/blob/master/0000-nonlexical-lifetimes.md), I get some errors.
<details>
<summary>Program</summary>
```rust
struct List<T> {
value: T,
next: Option<Box<List<T>>>,
}
fn to_refs<T>(mut list: &mut List<T>) -> Vec<&mut T> {
let mut result = vec![];
loop {
result.push(&mut list.value);
if let Some(n) = list.next.as_mut() {
list = &mut n;
} else {
return result;
}
}
}
fn main() {
println!("Hello World!");
}
```
</details>
<details>
<summary>Output of `rustc -g -Zverbose -Znll nll-problem-case-4.rs`:</summary>
```
error[E0597]: `n` does not live long enough
--> nll-problem-case-4.rs:11:25
|
11 | list = &mut n;
| ^ does not live long enough
...
14 | }
| - borrowed value only lives until here
|
note: borrowed value must be valid for the anonymous lifetime #1 defined on the function body at 6:1...
--> nll-problem-case-4.rs:6:1
|
6 | / fn to_refs<T>(mut list: &mut List<T>) -> Vec<&mut T> {
7 | | let mut result = vec![];
8 | | loop {
9 | | result.push(&mut list.value);
... |
15 | | }
16 | | }
| |_^
error[E0499]: cannot borrow `list.value` as mutable more than once at a time
--> nll-problem-case-4.rs:9:26
|
9 | result.push(&mut list.value);
| ^^^^^^^^^^ mutable borrow starts here in previous iteration of loop
...
16 | }
| - mutable borrow ends here
error[E0499]: cannot borrow `list.next` as mutable more than once at a time
--> nll-problem-case-4.rs:10:26
|
10 | if let Some(n) = list.next.as_mut() {
| ^^^^^^^^^ mutable borrow starts here in previous iteration of loop
...
16 | }
| - mutable borrow ends here
error[E0506]: cannot assign to `list` because it is borrowed
--> nll-problem-case-4.rs:11:13
|
9 | result.push(&mut list.value);
| ---------- borrow of `list` occurs here
10 | if let Some(n) = list.next.as_mut() {
11 | list = &mut n;
| ^^^^^^^^^^^^^ assignment to borrowed `list` occurs here
error: aborting due to 4 previous errors
```
</details>
<br/>
My questions are:
- Am I enabling correctly the experimental nll? What confuses me is that I compiled `rustc` with `./configure --enable-debug --enable-debuginfo`, but I still don't see the `debug!("mir_borrowck done");` message from the compiler.
- Is "problem case 4" supposed to compile without errors in the future, when nll will be stable?
|
1.0
|
Error compiling problem case #4 from nll-rfc - UPDATE: This example works now, but needs someone to add a test. See [mentoring instructions](https://github.com/rust-lang/rust/issues/46361#issuecomment-357991656) below.
---
I'm trying to compile some examples using nonlexical lifetimes. To do so, I'm compiling rustc using the `master` branch, and the `-Z nll` compiler option.
```
rustc 1.24.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.24.0-dev
LLVM version: 4.0
```
By compiling "Problem case 4: mutating &mut references" from [nll-rfc](https://github.com/nikomatsakis/nll-rfc/blob/master/0000-nonlexical-lifetimes.md), I get some errors.
<details>
<summary>Program</summary>
```rust
struct List<T> {
value: T,
next: Option<Box<List<T>>>,
}
fn to_refs<T>(mut list: &mut List<T>) -> Vec<&mut T> {
let mut result = vec![];
loop {
result.push(&mut list.value);
if let Some(n) = list.next.as_mut() {
list = &mut n;
} else {
return result;
}
}
}
fn main() {
println!("Hello World!");
}
```
</details>
<details>
<summary>Output of `rustc -g -Zverbose -Znll nll-problem-case-4.rs`:</summary>
```
error[E0597]: `n` does not live long enough
--> nll-problem-case-4.rs:11:25
|
11 | list = &mut n;
| ^ does not live long enough
...
14 | }
| - borrowed value only lives until here
|
note: borrowed value must be valid for the anonymous lifetime #1 defined on the function body at 6:1...
--> nll-problem-case-4.rs:6:1
|
6 | / fn to_refs<T>(mut list: &mut List<T>) -> Vec<&mut T> {
7 | | let mut result = vec![];
8 | | loop {
9 | | result.push(&mut list.value);
... |
15 | | }
16 | | }
| |_^
error[E0499]: cannot borrow `list.value` as mutable more than once at a time
--> nll-problem-case-4.rs:9:26
|
9 | result.push(&mut list.value);
| ^^^^^^^^^^ mutable borrow starts here in previous iteration of loop
...
16 | }
| - mutable borrow ends here
error[E0499]: cannot borrow `list.next` as mutable more than once at a time
--> nll-problem-case-4.rs:10:26
|
10 | if let Some(n) = list.next.as_mut() {
| ^^^^^^^^^ mutable borrow starts here in previous iteration of loop
...
16 | }
| - mutable borrow ends here
error[E0506]: cannot assign to `list` because it is borrowed
--> nll-problem-case-4.rs:11:13
|
9 | result.push(&mut list.value);
| ---------- borrow of `list` occurs here
10 | if let Some(n) = list.next.as_mut() {
11 | list = &mut n;
| ^^^^^^^^^^^^^ assignment to borrowed `list` occurs here
error: aborting due to 4 previous errors
```
</details>
<br/>
My questions are:
- Am I enabling correctly the experimental nll? What confuses me is that I compiled `rustc` with `./configure --enable-debug --enable-debuginfo`, but I still don't see the `debug!("mir_borrowck done");` message from the compiler.
- Is "problem case 4" supposed to compile without errors in the future, when nll will be stable?
|
non_process
|
error compiling problem case from nll rfc update this example works now but needs someone to add a test see below i m trying to compile some examples using nonlexical lifetimes to do so i m compiling rustc using the master branch and the z nll compiler option rustc dev binary rustc commit hash unknown commit date unknown host unknown linux gnu release dev llvm version by compiling problem case mutating mut references from i get some errors program rust struct list value t next option fn to refs mut list mut list vec let mut result vec loop result push mut list value if let some n list next as mut list mut n else return result fn main println hello world output of rustc g zverbose znll nll problem case rs error n does not live long enough nll problem case rs list mut n does not live long enough borrowed value only lives until here note borrowed value must be valid for the anonymous lifetime defined on the function body at nll problem case rs fn to refs mut list mut list vec let mut result vec loop result push mut list value error cannot borrow list value as mutable more than once at a time nll problem case rs result push mut list value mutable borrow starts here in previous iteration of loop mutable borrow ends here error cannot borrow list next as mutable more than once at a time nll problem case rs if let some n list next as mut mutable borrow starts here in previous iteration of loop mutable borrow ends here error cannot assign to list because it is borrowed nll problem case rs result push mut list value borrow of list occurs here if let some n list next as mut list mut n assignment to borrowed list occurs here error aborting due to previous errors my questions are am i enabling correctly the experimental nll what confuses me is that i compiled rustc with configure enable debug enable debuginfo but i still don t see the debug mir borrowck done message from the compiler is problem case supposed to compile without errors in the future when nll will be stable
| 0
|
11,923
| 14,703,540,936
|
IssuesEvent
|
2021-01-04 15:11:31
|
timberio/vector
|
https://api.github.com/repos/timberio/vector
|
closed
|
Add multiline highlight for 0.12
|
domain: processing domain: releasing domain: remap transform: reduce type: task
|
I'm deferring this highlight for 0.12 since it is dependent on the Remap Language. We'll need an announcement and docs for the Remap language that we can refer to:
```
---
last_modified_on: "2020-10-27"
$schema: ".schema.json"
title: "Robust Multi-line Merging"
description: "Merging split logs with ease."
author_github: "https://github.com/binarylogic"
pr_numbers: [1314]
release: "0.11.0"
hide_on_release_notes: false
tags: ["type: announcement", "domain: processing"]
---
Vector collects logs and sends them somewhere. What's the big deal?
Let me tell you about multi-line logs. These seemlingly innocent logs contain
new-line characters, and when fed through a medium that uses new-line characters
as delimiters (such as files), it splits them into many different logs. This
obviously is not desirable, and engineers need a way to piece their logs back
together.
Sadly, this problem has plagued tools like Vector for many years. There always
seems to be an edge-case that requires additional processing steps to resolve.
Sometimes the simplest problems are the hardest!
## The multi-line war is over!
We believe we've landed on an elegant and robust solution that can handle any
multi-line scenario thrown at it (knock on wood). There are two big improvements
with Vector's new multi-line solution that set it apart:
1. Vector's [`reduce` transform][reduce_transform] is able to reduce logs at the
_transform-level_. This means you get the full power of Vector's processing
tools to pre-process data before merging it. For example, decoding JSON.
2. The `starts_when` and `ends_when` options leverage Timber's new Remap
Language 👀. This is a new purpose-built language...
```
|
1.0
|
Add multiline highlight for 0.12 - I'm deferring this highlight for 0.12 since it is dependent on the Remap Language. We'll need an announcement and docs for the Remap language that we can refer to:
```
---
last_modified_on: "2020-10-27"
$schema: ".schema.json"
title: "Robust Multi-line Merging"
description: "Merging split logs with ease."
author_github: "https://github.com/binarylogic"
pr_numbers: [1314]
release: "0.11.0"
hide_on_release_notes: false
tags: ["type: announcement", "domain: processing"]
---
Vector collects logs and sends them somewhere. What's the big deal?
Let me tell you about multi-line logs. These seemlingly innocent logs contain
new-line characters, and when fed through a medium that uses new-line characters
as delimiters (such as files), it splits them into many different logs. This
obviously is not desirable, and engineers need a way to piece their logs back
together.
Sadly, this problem has plagued tools like Vector for many years. There always
seems to be an edge-case that requires additional processing steps to resolve.
Sometimes the simplest problems are the hardest!
## The multi-line war is over!
We believe we've landed on an elegant and robust solution that can handle any
multi-line scenario thrown at it (knock on wood). There are two big improvements
with Vector's new multi-line solution that set it apart:
1. Vector's [`reduce` transform][reduce_transform] is able to reduce logs at the
_transform-level_. This means you get the full power of Vector's processing
tools to pre-process data before merging it. For example, decoding JSON.
2. The `starts_when` and `ends_when` options leverage Timber's new Remap
Language 👀. This is a new purpose-built language...
```
|
process
|
add multiline highlight for i m deferring this highlight for since it is dependent on the remap language we ll need an announcement and docs for the remap language that we can refer to last modified on schema schema json title robust multi line merging description merging split logs with ease author github pr numbers release hide on release notes false tags vector collects logs and sends them somewhere what s the big deal let me tell you about multi line logs these seemlingly innocent logs contain new line characters and when fed through a medium that uses new line characters as delimiters such as files it splits them into many different logs this obviously is not desirable and engineers need a way to piece their logs back together sadly this problem has plagued tools like vector for many years there always seems to be an edge case that requires additional processing steps to resolve sometimes the simplest problems are the hardest the multi line war is over we believe we ve landed on an elegant and robust solution that can handle any multi line scenario thrown at it knock on wood there are two big improvements with vector s new multi line solution that set it apart vector s is able to reduce logs at the transform level this means you get the full power of vector s processing tools to pre process data before merging it for example decoding json the starts when and ends when options leverage timber s new remap language 👀 this is a new purpose built language
| 1
|
5,227
| 8,029,716,204
|
IssuesEvent
|
2018-07-27 16:59:31
|
GoogleCloudPlatform/google-cloud-python
|
https://api.github.com/repos/GoogleCloudPlatform/google-cloud-python
|
closed
|
BigQuery: `fetch_single_page` systest returns 500 response
|
api: bigquery flaky testing type: process
|
See: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7040
```python
____________ TestBigQuery.test_insert_rows_nested_nested_dictionary ____________
self = <tests.system.TestBigQuery testMethod=test_insert_rows_nested_nested_dictionary>
def test_insert_rows_nested_nested_dictionary(self):
# See #2951
SF = bigquery.SchemaField
schema = [
SF('string_col', 'STRING', mode='NULLABLE'),
SF('record_col', 'RECORD', mode='NULLABLE', fields=[
SF('nested_string', 'STRING', mode='NULLABLE'),
SF('nested_repeated', 'INTEGER', mode='REPEATED'),
SF('nested_record', 'RECORD', mode='NULLABLE', fields=[
SF('nested_nested_string', 'STRING', mode='NULLABLE'),
]),
]),
]
record = {
'nested_string': 'another string value',
'nested_repeated': [0, 1, 2],
'nested_record': {'nested_nested_string': 'some deep insight'},
}
to_insert = [
{'string_col': 'Some value', 'record_col': record}
]
table_id = 'test_table'
dataset = self.temp_dataset(_make_dataset_id('issue_2951'))
table_arg = Table(dataset.table(table_id), schema=schema)
table = retry_403(Config.CLIENT.create_table)(table_arg)
self.to_delete.insert(0, table)
Config.CLIENT.insert_rows(table, to_insert)
retry = RetryResult(_has_rows, max_tries=8)
> rows = retry(self._fetch_single_page)(table)
tests/system.py:1585:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../.nox/sys-2-7/lib/python2.7/site-packages/test_utils/retry.py:144: in wrapped_function
result = to_wrap(*args, **kwargs)
tests/system.py:386: in _fetch_single_page
page = six.next(iterator.pages)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:230: in _page_iter
page = self._next_page()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:349: in _next_page
response = self._get_next_page_response()
google/cloud/bigquery/table.py:1114: in _get_next_page_response
query_params=params)
google/cloud/bigquery/client.py:315: in _call_api
return call()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:260: in retry_wrapped_func
on_error=on_error,
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:177: in retry_target
return target()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.cloud.bigquery._http.Connection object at 0x7fc7cd371790>
method = 'GET'
path = '/projects/precise-truck-742/datasets/issue_2951_7040_1530308905/tables/test_table/data'
query_params = {}, data = None, content_type = None, headers = None
api_base_url = None, api_version = None, expect_json = True
_target_object = None
def api_request(self, method, path, query_params=None,
data=None, content_type=None, headers=None,
api_base_url=None, api_version=None,
expect_json=True, _target_object=None):
"""Make a request over the HTTP transport to the API.
You shouldn't need to use this method, but if you plan to
interact with the API using these primitives, this is the
correct one to use.
:type method: str
:param method: The HTTP method name (ie, ``GET``, ``POST``, etc).
Required.
:type path: str
:param path: The path to the resource (ie, ``'/b/bucket-name'``).
Required.
:type query_params: dict or list
:param query_params: A dictionary of keys and values (or list of
key-value pairs) to insert into the query
string of the URL.
:type data: str
:param data: The data to send as the body of the request. Default is
the empty string.
:type content_type: str
:param content_type: The proper MIME type of the data provided. Default
is None.
:type headers: dict
:param headers: extra HTTP headers to be sent with the request.
:type api_base_url: str
:param api_base_url: The base URL for the API endpoint.
Typically you won't have to provide this.
Default is the standard API base URL.
:type api_version: str
:param api_version: The version of the API to call. Typically
you shouldn't provide this and instead use
the default for the library. Default is the
latest API version supported by
google-cloud-python.
:type expect_json: bool
:param expect_json: If True, this method will try to parse the
response as JSON and raise an exception if
that cannot be done. Default is True.
:type _target_object: :class:`object`
:param _target_object:
(Optional) Protected argument to be used by library callers. This
can allow custom behavior, for example, to defer an HTTP request
and complete initialization of the object at a later time.
:raises ~google.cloud.exceptions.GoogleCloudError: if the response code
is not 200 OK.
:raises ValueError: if the response content type is not JSON.
:rtype: dict or str
:returns: The API response payload, either as a raw string or
a dictionary if the response is valid JSON.
"""
url = self.build_api_url(path=path, query_params=query_params,
api_base_url=api_base_url,
api_version=api_version)
# Making the executive decision that any dictionary
# data will be sent properly as JSON.
if data and isinstance(data, dict):
data = json.dumps(data)
content_type = 'application/json'
response = self._make_request(
method=method, url=url, data=data, content_type=content_type,
headers=headers, target_object=_target_object)
if not 200 <= response.status_code < 300:
> raise exceptions.from_http_response(response)
E InternalServerError: 500 GET https://www.googleapis.com/bigquery/v2/projects/precise-truck-742/datasets/issue_2951_7040_1530308905/tables/test_table/data: An internal error occurred and the request could not be completed.
../.nox/sys-2-7/lib/python2.7/site-packages/google/cloud/_http.py:293: InternalServerError
```
|
1.0
|
BigQuery: `fetch_single_page` systest returns 500 response - See: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7040
```python
____________ TestBigQuery.test_insert_rows_nested_nested_dictionary ____________
self = <tests.system.TestBigQuery testMethod=test_insert_rows_nested_nested_dictionary>
def test_insert_rows_nested_nested_dictionary(self):
# See #2951
SF = bigquery.SchemaField
schema = [
SF('string_col', 'STRING', mode='NULLABLE'),
SF('record_col', 'RECORD', mode='NULLABLE', fields=[
SF('nested_string', 'STRING', mode='NULLABLE'),
SF('nested_repeated', 'INTEGER', mode='REPEATED'),
SF('nested_record', 'RECORD', mode='NULLABLE', fields=[
SF('nested_nested_string', 'STRING', mode='NULLABLE'),
]),
]),
]
record = {
'nested_string': 'another string value',
'nested_repeated': [0, 1, 2],
'nested_record': {'nested_nested_string': 'some deep insight'},
}
to_insert = [
{'string_col': 'Some value', 'record_col': record}
]
table_id = 'test_table'
dataset = self.temp_dataset(_make_dataset_id('issue_2951'))
table_arg = Table(dataset.table(table_id), schema=schema)
table = retry_403(Config.CLIENT.create_table)(table_arg)
self.to_delete.insert(0, table)
Config.CLIENT.insert_rows(table, to_insert)
retry = RetryResult(_has_rows, max_tries=8)
> rows = retry(self._fetch_single_page)(table)
tests/system.py:1585:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../.nox/sys-2-7/lib/python2.7/site-packages/test_utils/retry.py:144: in wrapped_function
result = to_wrap(*args, **kwargs)
tests/system.py:386: in _fetch_single_page
page = six.next(iterator.pages)
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:230: in _page_iter
page = self._next_page()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/page_iterator.py:349: in _next_page
response = self._get_next_page_response()
google/cloud/bigquery/table.py:1114: in _get_next_page_response
query_params=params)
google/cloud/bigquery/client.py:315: in _call_api
return call()
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:260: in retry_wrapped_func
on_error=on_error,
../.nox/sys-2-7/lib/python2.7/site-packages/google/api_core/retry.py:177: in retry_target
return target()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.cloud.bigquery._http.Connection object at 0x7fc7cd371790>
method = 'GET'
path = '/projects/precise-truck-742/datasets/issue_2951_7040_1530308905/tables/test_table/data'
query_params = {}, data = None, content_type = None, headers = None
api_base_url = None, api_version = None, expect_json = True
_target_object = None
def api_request(self, method, path, query_params=None,
data=None, content_type=None, headers=None,
api_base_url=None, api_version=None,
expect_json=True, _target_object=None):
"""Make a request over the HTTP transport to the API.
You shouldn't need to use this method, but if you plan to
interact with the API using these primitives, this is the
correct one to use.
:type method: str
:param method: The HTTP method name (ie, ``GET``, ``POST``, etc).
Required.
:type path: str
:param path: The path to the resource (ie, ``'/b/bucket-name'``).
Required.
:type query_params: dict or list
:param query_params: A dictionary of keys and values (or list of
key-value pairs) to insert into the query
string of the URL.
:type data: str
:param data: The data to send as the body of the request. Default is
the empty string.
:type content_type: str
:param content_type: The proper MIME type of the data provided. Default
is None.
:type headers: dict
:param headers: extra HTTP headers to be sent with the request.
:type api_base_url: str
:param api_base_url: The base URL for the API endpoint.
Typically you won't have to provide this.
Default is the standard API base URL.
:type api_version: str
:param api_version: The version of the API to call. Typically
you shouldn't provide this and instead use
the default for the library. Default is the
latest API version supported by
google-cloud-python.
:type expect_json: bool
:param expect_json: If True, this method will try to parse the
response as JSON and raise an exception if
that cannot be done. Default is True.
:type _target_object: :class:`object`
:param _target_object:
(Optional) Protected argument to be used by library callers. This
can allow custom behavior, for example, to defer an HTTP request
and complete initialization of the object at a later time.
:raises ~google.cloud.exceptions.GoogleCloudError: if the response code
is not 200 OK.
:raises ValueError: if the response content type is not JSON.
:rtype: dict or str
:returns: The API response payload, either as a raw string or
a dictionary if the response is valid JSON.
"""
url = self.build_api_url(path=path, query_params=query_params,
api_base_url=api_base_url,
api_version=api_version)
# Making the executive decision that any dictionary
# data will be sent properly as JSON.
if data and isinstance(data, dict):
data = json.dumps(data)
content_type = 'application/json'
response = self._make_request(
method=method, url=url, data=data, content_type=content_type,
headers=headers, target_object=_target_object)
if not 200 <= response.status_code < 300:
> raise exceptions.from_http_response(response)
E InternalServerError: 500 GET https://www.googleapis.com/bigquery/v2/projects/precise-truck-742/datasets/issue_2951_7040_1530308905/tables/test_table/data: An internal error occurred and the request could not be completed.
../.nox/sys-2-7/lib/python2.7/site-packages/google/cloud/_http.py:293: InternalServerError
```
|
process
|
bigquery fetch single page systest returns response see python testbigquery test insert rows nested nested dictionary self def test insert rows nested nested dictionary self see sf bigquery schemafield schema sf string col string mode nullable sf record col record mode nullable fields sf nested string string mode nullable sf nested repeated integer mode repeated sf nested record record mode nullable fields sf nested nested string string mode nullable record nested string another string value nested repeated nested record nested nested string some deep insight to insert string col some value record col record table id test table dataset self temp dataset make dataset id issue table arg table dataset table table id schema schema table retry config client create table table arg self to delete insert table config client insert rows table to insert retry retryresult has rows max tries rows retry self fetch single page table tests system py nox sys lib site packages test utils retry py in wrapped function result to wrap args kwargs tests system py in fetch single page page six next iterator pages nox sys lib site packages google api core page iterator py in page iter page self next page nox sys lib site packages google api core page iterator py in next page response self get next page response google cloud bigquery table py in get next page response query params params google cloud bigquery client py in call api return call nox sys lib site packages google api core retry py in retry wrapped func on error on error nox sys lib site packages google api core retry py in retry target return target self method get path projects precise truck datasets issue tables test table data query params data none content type none headers none api base url none api version none expect json true target object none def api request self method path query params none data none content type none headers none api base url none api version none expect json true target object none make a request over the http transport to the api you shouldn t need to use this method but if you plan to interact with the api using these primitives this is the correct one to use type method str param method the http method name ie get post etc required type path str param path the path to the resource ie b bucket name required type query params dict or list param query params a dictionary of keys and values or list of key value pairs to insert into the query string of the url type data str param data the data to send as the body of the request default is the empty string type content type str param content type the proper mime type of the data provided default is none type headers dict param headers extra http headers to be sent with the request type api base url str param api base url the base url for the api endpoint typically you won t have to provide this default is the standard api base url type api version str param api version the version of the api to call typically you shouldn t provide this and instead use the default for the library default is the latest api version supported by google cloud python type expect json bool param expect json if true this method will try to parse the response as json and raise an exception if that cannot be done default is true type target object class object param target object optional protected argument to be used by library callers this can allow custom behavior for example to defer an http request and complete initialization of the object at a later time raises google cloud exceptions googleclouderror if the response code is not ok raises valueerror if the response content type is not json rtype dict or str returns the api response payload either as a raw string or a dictionary if the response is valid json url self build api url path path query params query params api base url api base url api version api version making the executive decision that any dictionary data will be sent properly as json if data and isinstance data dict data json dumps data content type application json response self make request method method url url data data content type content type headers headers target object target object if not response status code raise exceptions from http response response e internalservererror get an internal error occurred and the request could not be completed nox sys lib site packages google cloud http py internalservererror
| 1
|
387
| 2,831,696,366
|
IssuesEvent
|
2015-05-24 21:12:54
|
everypolitician/everypolitician-data
|
https://api.github.com/repos/everypolitician/everypolitician-data
|
closed
|
Angola
|
4 - To Process
|
http://www.parlamento.ao/web/guest/deputados-e-grupos-parlamentares/deputados/lista#http://www.parlamento.ao/glue/AN_Navigation.jsp?
Scraping the site itself is easy (and there doesn't appear to be any extra information on the Person page that's not on the List page) — but the next/prev links are JS driven, so we'll probably need to use Morph's [Phantom.js support](https://www.openaustraliafoundation.org.au/2015/03/17/scraping-javascript-sites-with-morph-io/)
<!---
@huboard:{"custom_state":"blocked"}
-->
|
1.0
|
Angola - http://www.parlamento.ao/web/guest/deputados-e-grupos-parlamentares/deputados/lista#http://www.parlamento.ao/glue/AN_Navigation.jsp?
Scraping the site itself is easy (and there doesn't appear to be any extra information on the Person page that's not on the List page) — but the next/prev links are JS driven, so we'll probably need to use Morph's [Phantom.js support](https://www.openaustraliafoundation.org.au/2015/03/17/scraping-javascript-sites-with-morph-io/)
<!---
@huboard:{"custom_state":"blocked"}
-->
|
process
|
angola scraping the site itself is easy and there doesn t appear to be any extra information on the person page that s not on the list page — but the next prev links are js driven so we ll probably need to use morph s huboard custom state blocked
| 1
|
18,880
| 24,818,184,948
|
IssuesEvent
|
2022-10-25 14:33:37
|
zephyrproject-rtos/zephyr
|
https://api.github.com/repos/zephyrproject-rtos/zephyr
|
opened
|
Documentation vs Regulations/Guidelines
|
Process
|
Guidelines and "regulations" in the project need to be treated differently from basic subsystem or feature documentation.
One subsystem should not put in place guidelines that go beyond recommendations and guidelines for using the subsystem itself. Any cross subsystem and project level guidelines need to be discussed by the wider community and agreed upon in exising forums before they become guidelines that every contributor need to follow. Similarily, visionary and design goals maintained as part of the documentation of a subsystem or documentation should not become de facto guidelines based on the fact they exist in the documentation.
|
1.0
|
Documentation vs Regulations/Guidelines - Guidelines and "regulations" in the project need to be treated differently from basic subsystem or feature documentation.
One subsystem should not put in place guidelines that go beyond recommendations and guidelines for using the subsystem itself. Any cross subsystem and project level guidelines need to be discussed by the wider community and agreed upon in exising forums before they become guidelines that every contributor need to follow. Similarily, visionary and design goals maintained as part of the documentation of a subsystem or documentation should not become de facto guidelines based on the fact they exist in the documentation.
|
process
|
documentation vs regulations guidelines guidelines and regulations in the project need to be treated differently from basic subsystem or feature documentation one subsystem should not put in place guidelines that go beyond recommendations and guidelines for using the subsystem itself any cross subsystem and project level guidelines need to be discussed by the wider community and agreed upon in exising forums before they become guidelines that every contributor need to follow similarily visionary and design goals maintained as part of the documentation of a subsystem or documentation should not become de facto guidelines based on the fact they exist in the documentation
| 1
|
11,365
| 14,175,804,994
|
IssuesEvent
|
2020-11-12 22:15:18
|
MicrosoftDocs/azure-devops-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-devops-docs
|
closed
|
Update documentation for Pipelines Resource tag filters
|
Pri2 devops-cicd-process/tech devops/prod doc-enhancement
|
As per the latest sprint release notes here -
https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-171-update#tag-filter-support-for-pipeline-resources
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
* Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
* Content: [Resources - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#resources-pipelines)
* Content Source: [docs/pipelines/process/resources.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/resources.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
1.0
|
Update documentation for Pipelines Resource tag filters -
As per the latest sprint release notes here -
https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-171-update#tag-filter-support-for-pipeline-resources
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
* Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
* Content: [Resources - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#resources-pipelines)
* Content Source: [docs/pipelines/process/resources.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/resources.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
process
|
update documentation for pipelines resource tag filters as per the latest sprint release notes here document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product devops technology devops cicd process github login juliakm microsoft alias jukullam
| 1
|
2,214
| 5,051,508,288
|
IssuesEvent
|
2016-12-20 22:06:20
|
cfpb/design-manual
|
https://api.github.com/repos/cfpb/design-manual
|
closed
|
structure and IA for manual
|
1 - Working process and planning UI
|
I think there are some closed issues that we should reference for background
|
1.0
|
structure and IA for manual - I think there are some closed issues that we should reference for background
|
process
|
structure and ia for manual i think there are some closed issues that we should reference for background
| 1
|
12,151
| 14,741,415,928
|
IssuesEvent
|
2021-01-07 10:35:14
|
kdjstudios/SABillingGitlab
|
https://api.github.com/repos/kdjstudios/SABillingGitlab
|
closed
|
SA Billing - SA Hosted - Invalid Late Fees
|
anc-process anp-not prioritized ant-bug
|
In GitLab by @kdjstudios on Jan 17, 2019, 16:16
**Submitted by:** "Michelle McKee" <michelle.mckee@answernet.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/2019-01-15-14898/conversation
**Server:** Internal
**Client/Site:** SA Hosted
**Account:** NA
**Issue:**
I have already addressed and corrected this error.
|
1.0
|
SA Billing - SA Hosted - Invalid Late Fees - In GitLab by @kdjstudios on Jan 17, 2019, 16:16
**Submitted by:** "Michelle McKee" <michelle.mckee@answernet.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/2019-01-15-14898/conversation
**Server:** Internal
**Client/Site:** SA Hosted
**Account:** NA
**Issue:**
I have already addressed and corrected this error.
|
process
|
sa billing sa hosted invalid late fees in gitlab by kdjstudios on jan submitted by michelle mckee helpdesk server internal client site sa hosted account na issue i have already addressed and corrected this error
| 1
|
442,432
| 30,835,183,043
|
IssuesEvent
|
2023-08-02 06:47:38
|
refinedev/refine
|
https://api.github.com/repos/refinedev/refine
|
closed
|
[DOC] missing closing tag on line 660
|
documentation
|
### Documentation issue
https://refine.dev/docs/api-reference/antd/components/antd-auth-page/#rememberme
The section of loginLink did not display correctly
### Describe the thing to improve
Missing closing tag ::: on line 660 of the markdown, which causes the loginLink did not display properly.
### Describe the solution (optional)
Should be a quick fix by adding the ::: closing tag to line 660
https://github.com/refinedev/refine/blob/next/documentation/docs/api-reference/antd/components/auth-page.md?plain=1
|
1.0
|
[DOC] missing closing tag on line 660 - ### Documentation issue
https://refine.dev/docs/api-reference/antd/components/antd-auth-page/#rememberme
The section of loginLink did not display correctly
### Describe the thing to improve
Missing closing tag ::: on line 660 of the markdown, which causes the loginLink did not display properly.
### Describe the solution (optional)
Should be a quick fix by adding the ::: closing tag to line 660
https://github.com/refinedev/refine/blob/next/documentation/docs/api-reference/antd/components/auth-page.md?plain=1
|
non_process
|
missing closing tag on line documentation issue the section of loginlink did not display correctly describe the thing to improve missing closing tag on line of the markdown which causes the loginlink did not display properly describe the solution optional should be a quick fix by adding the closing tag to line
| 0
|
19,600
| 11,254,330,878
|
IssuesEvent
|
2020-01-11 22:47:14
|
trilinos/Trilinos
|
https://api.github.com/repos/trilinos/Trilinos
|
closed
|
TpetraCore_MultiVector_UnitTests_MPI_4 and TpetraCore_gemm_m_eq_<X>_MPI_1 tests in build Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug failing starting 2019-12-07
|
ATDM Sev: Blocker PA: Data Services client: ATDM impacting: tests pkg: KokkosKernels pkg: Tpetra type: bug
|
CC: @trilinos/tpetra, @kddevin (Trilinos Data Services Product Lead), @bartlettroscoe, @fryeguy52, @seheracer
<Checklist>
<???: Add label "client: ATDM">
<???: Add label "ATDM Sev: Blocker" (by default but could be other "ATDM Sev: XXX")>
<???: Add label "type: bug"?>
<???: Add label for affected packages (e.g. "pkg: MueLu", "pkg: Tpetra", "pkg: Kokkos", etc.)>
<???: Add label "PA: ???Project Area???" (e.g. "PA: Linear Solvers", "PA: Data Services")>
<???: Add milestone "Initial cleanup of new ATDM ..." or "Keep promoted ATDM ...">
<???: Once GitHub Issue is created, add entries for tests to TrilinosATDMStatus/*.csv files>
## Next Action Status
<status-and-or-first-action>
## Description
As shown in [this query](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&begin=2019-11-11&end=2019-12-10&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=block&field3count=2&field3field1=testname&field3compare1=61&field3value1=TpetraCore_MultiVector_UnitTests_MPI_4&field3field2=testname&field3compare2=65&field3value2=TpetraCore_gemm_m_eq_) the tests:
* `TpetraCore_gemm_m_eq_1_MPI_1`
* `TpetraCore_gemm_m_eq_2_MPI_1`
* `TpetraCore_gemm_m_eq_5_MPI_1`
* `TpetraCore_gemm_m_eq_13_MPI_1`
* `TpetraCore_MultiVector_UnitTests_MPI_4`
are failing in build:
* `Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug`
starting 2019-12-07.
As shown in [this query](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&begin=2019-11-11&end=2019-12-10&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=testname&compare3=65&value3=TpetraCore_gemm_m_eq_&field4=testoutput&compare4=97&value4=FAILED.*%20Blas_std_complex0double0_Gemm_UnitTest), the tests `TpetraCore_gemm_m_eq_<X>_MPI_1` are all failing the unit test `Blas_std_complex0double0_Gemm_UnitTest` showing error output like:
```
...
trans_A: C
trans_B: N
A_norm: 1.15513
B_norm: 0.355242
C_norm: 1.13028
bound: 1.77636e-15
false = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/Blas/gemm.cpp:306
Comparing KokkosBlas::gemm against Teuchos::BLAS::GEMM: Max error 0.699682 > error bound 1.77636e-15
false = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/Blas/gemm.cpp:333
Comparing KokkosBlas::Default::gemm against Teuchos::BLAS::GEMM: Max error 0.699682 > error bound 1.77636e-15
At least one test FAILED; abandoning the others.
At least one test FAILED; abandoning the others.
At least one test FAILED; abandoning the others.
[FAILED] (2.47 sec) Blas_std_complex0double0_Gemm_UnitTest
```
As shown in [this query](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&begin=2019-11-11&end=2019-12-10&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=testname&compare3=61&value3=TpetraCore_MultiVector_UnitTests_MPI_4&field4=testoutput&compare4=97&value4=FAILED.*MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest), the test `TpetraCore_MultiVector_UnitTests_MPI_4` is failing the unit test `MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest` showing oputput like:
```
88. MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest ...
Test: MultiVector, Multiply
Comparing tmpView(0,9) == check3 ... passed
Comparing tmpView(0,4) == check2 ... passed
Comparing tmpView(0,4) == check2 ... passed
Comparing tmpView(0,9) == check3 ... passed
gblSuccess == 1 = 1 == true : passed
Comparing tmpView == sdmView ... passed
gblSuccess == 1 = 1 == true : passed
Comparing tmpView == sdmView ... passed
gblSuccess == 1 = 1 == true : passed
Comparing tmpView == sdmView ...
Error, relErr(tmpView[0],sdmView[0]) = relErr((1.3406,0.995454),(2.15303,0)) = 0.596788 <= tol = 2.22045e-14: failed!
Error, relErr(tmpView[1],sdmView[1]) = relErr((-0.767759,0.205214),(-0.0764208,-0.51095)) = 1.25254 <= tol = 2.22045e-14: failed!
Error, relErr(tmpView[2],sdmView[2]) = relErr((-0.767759,0.205214),(-0.0764208,0.51095)) = 0.951195 <= tol = 2.22045e-14: failed!
Error, relErr(tmpView[3],sdmView[3]) = relErr((-0.18601,0.101217),(0.738326,0)) = 1.25942 <= tol = 2.22045e-14: failed!
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:815
Comparing tmpView == sdmView ... passed
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:828
Comparing tmpView == check(0,tmpView.size()) ... passed
Comparing tmpView == check(0,tmpView.size()) ... passed
Comparing tmpView == check(0,tmpView.size()) ... passed
Comparing tmpView == check(0,tmpView.size()) ... passed
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:861
Comparing tmpView == check2 ... passed
Comparing tmpView == check3 ... passed
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:888
[FAILED] (0.0303 sec) MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest
Location: /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:707
```
The new commits that were pulled on the testing day 2019-12-07 as shown [here](https://testing-dev.sandia.gov/cdash/viewNotes.php?buildid=5069857#!#note6). Looking over that set of commits, the commits most likely to have triggered this failuire are:
```
d3a22b1: Add beta=0 case and allow number of teams smaller than 32 to resolve NaN and diff issues in some Teko and ShyLu tests.
Author: Seher Acer <sacer@sandia.gov>
Date: Wed Dec 4 21:10:29 2019 -0700
M packages/kokkos-kernels/src/impl/tpls/KokkosBlas3_gemm_tpl_spec_decl.hpp
e5f7c38: KokkosKernels: Optimized GEMM (over CUBLAS GEMM) for A^TB with tall and skinny matrices on CUDA.
Author: Seher Acer <sacer@sandia.gov>
Date: Tue Nov 5 19:47:58 2019 -0700
M packages/kokkos-kernels/src/impl/tpls/KokkosBlas3_gemm_tpl_spec_decl.hpp
```
pulled in from PR #6226 by @seheracer.
## Current Status on CDash
* [`TpetraCore_MultiVector_UnitTests_MPI_4` and `TpetraCore_gemm_m_eq_<X>_MPI_1` tests in build Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug for current testing day](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=block&field3count=2&field3field1=testname&field3compare1=61&field3value1=TpetraCore_MultiVector_UnitTests_MPI_4&field3field2=testname&field3compare2=65&field3value2=TpetraCore_gemm_m_eq_)
## Steps to Reproduce
One should be able to reproduce this failure on a CEE LAN `ascicgpu<NUM>` 'sems-rhel7' as described in:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md
More specifically, the commands given for the system CEE LAN `ascicgpu<NUM>` 'sems-rhel7' are provided at:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md#sems-rhel7-environment
The exact commands to reproduce this issue should be:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh \
Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_TpetraCore=ON \
$TRILINOS_DIR
$ make NP=16
$ ctest -j4
```
|
1.0
|
TpetraCore_MultiVector_UnitTests_MPI_4 and TpetraCore_gemm_m_eq_<X>_MPI_1 tests in build Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug failing starting 2019-12-07 - CC: @trilinos/tpetra, @kddevin (Trilinos Data Services Product Lead), @bartlettroscoe, @fryeguy52, @seheracer
<Checklist>
<???: Add label "client: ATDM">
<???: Add label "ATDM Sev: Blocker" (by default but could be other "ATDM Sev: XXX")>
<???: Add label "type: bug"?>
<???: Add label for affected packages (e.g. "pkg: MueLu", "pkg: Tpetra", "pkg: Kokkos", etc.)>
<???: Add label "PA: ???Project Area???" (e.g. "PA: Linear Solvers", "PA: Data Services")>
<???: Add milestone "Initial cleanup of new ATDM ..." or "Keep promoted ATDM ...">
<???: Once GitHub Issue is created, add entries for tests to TrilinosATDMStatus/*.csv files>
## Next Action Status
<status-and-or-first-action>
## Description
As shown in [this query](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&begin=2019-11-11&end=2019-12-10&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=block&field3count=2&field3field1=testname&field3compare1=61&field3value1=TpetraCore_MultiVector_UnitTests_MPI_4&field3field2=testname&field3compare2=65&field3value2=TpetraCore_gemm_m_eq_) the tests:
* `TpetraCore_gemm_m_eq_1_MPI_1`
* `TpetraCore_gemm_m_eq_2_MPI_1`
* `TpetraCore_gemm_m_eq_5_MPI_1`
* `TpetraCore_gemm_m_eq_13_MPI_1`
* `TpetraCore_MultiVector_UnitTests_MPI_4`
are failing in build:
* `Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug`
starting 2019-12-07.
As shown in [this query](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&begin=2019-11-11&end=2019-12-10&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=testname&compare3=65&value3=TpetraCore_gemm_m_eq_&field4=testoutput&compare4=97&value4=FAILED.*%20Blas_std_complex0double0_Gemm_UnitTest), the tests `TpetraCore_gemm_m_eq_<X>_MPI_1` are all failing the unit test `Blas_std_complex0double0_Gemm_UnitTest` showing error output like:
```
...
trans_A: C
trans_B: N
A_norm: 1.15513
B_norm: 0.355242
C_norm: 1.13028
bound: 1.77636e-15
false = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/Blas/gemm.cpp:306
Comparing KokkosBlas::gemm against Teuchos::BLAS::GEMM: Max error 0.699682 > error bound 1.77636e-15
false = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/Blas/gemm.cpp:333
Comparing KokkosBlas::Default::gemm against Teuchos::BLAS::GEMM: Max error 0.699682 > error bound 1.77636e-15
At least one test FAILED; abandoning the others.
At least one test FAILED; abandoning the others.
At least one test FAILED; abandoning the others.
[FAILED] (2.47 sec) Blas_std_complex0double0_Gemm_UnitTest
```
As shown in [this query](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&begin=2019-11-11&end=2019-12-10&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=testname&compare3=61&value3=TpetraCore_MultiVector_UnitTests_MPI_4&field4=testoutput&compare4=97&value4=FAILED.*MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest), the test `TpetraCore_MultiVector_UnitTests_MPI_4` is failing the unit test `MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest` showing oputput like:
```
88. MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest ...
Test: MultiVector, Multiply
Comparing tmpView(0,9) == check3 ... passed
Comparing tmpView(0,4) == check2 ... passed
Comparing tmpView(0,4) == check2 ... passed
Comparing tmpView(0,9) == check3 ... passed
gblSuccess == 1 = 1 == true : passed
Comparing tmpView == sdmView ... passed
gblSuccess == 1 = 1 == true : passed
Comparing tmpView == sdmView ... passed
gblSuccess == 1 = 1 == true : passed
Comparing tmpView == sdmView ...
Error, relErr(tmpView[0],sdmView[0]) = relErr((1.3406,0.995454),(2.15303,0)) = 0.596788 <= tol = 2.22045e-14: failed!
Error, relErr(tmpView[1],sdmView[1]) = relErr((-0.767759,0.205214),(-0.0764208,-0.51095)) = 1.25254 <= tol = 2.22045e-14: failed!
Error, relErr(tmpView[2],sdmView[2]) = relErr((-0.767759,0.205214),(-0.0764208,0.51095)) = 0.951195 <= tol = 2.22045e-14: failed!
Error, relErr(tmpView[3],sdmView[3]) = relErr((-0.18601,0.101217),(0.738326,0)) = 1.25942 <= tol = 2.22045e-14: failed!
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:815
Comparing tmpView == sdmView ... passed
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:828
Comparing tmpView == check(0,tmpView.size()) ... passed
Comparing tmpView == check(0,tmpView.size()) ... passed
Comparing tmpView == check(0,tmpView.size()) ... passed
Comparing tmpView == check(0,tmpView.size()) ... passed
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:861
Comparing tmpView == check2 ... passed
Comparing tmpView == check3 ... passed
gblSuccess == 1 = 0 == true : FAILED ==> /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:888
[FAILED] (0.0303 sec) MultiVector_int_longlong_std_complex0double0_Kokkos_Compat_KokkosCudaWrapperNode_Multiply_UnitTest
Location: /scratch/jenkins/ascicgpu14/workspace/Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug/SRC_AND_BUILD/Trilinos/packages/tpetra/core/test/MultiVector/MultiVector_UnitTests.cpp:707
```
The new commits that were pulled on the testing day 2019-12-07 as shown [here](https://testing-dev.sandia.gov/cdash/viewNotes.php?buildid=5069857#!#note6). Looking over that set of commits, the commits most likely to have triggered this failuire are:
```
d3a22b1: Add beta=0 case and allow number of teams smaller than 32 to resolve NaN and diff issues in some Teko and ShyLu tests.
Author: Seher Acer <sacer@sandia.gov>
Date: Wed Dec 4 21:10:29 2019 -0700
M packages/kokkos-kernels/src/impl/tpls/KokkosBlas3_gemm_tpl_spec_decl.hpp
e5f7c38: KokkosKernels: Optimized GEMM (over CUBLAS GEMM) for A^TB with tall and skinny matrices on CUDA.
Author: Seher Acer <sacer@sandia.gov>
Date: Tue Nov 5 19:47:58 2019 -0700
M packages/kokkos-kernels/src/impl/tpls/KokkosBlas3_gemm_tpl_spec_decl.hpp
```
pulled in from PR #6226 by @seheracer.
## Current Status on CDash
* [`TpetraCore_MultiVector_UnitTests_MPI_4` and `TpetraCore_gemm_m_eq_<X>_MPI_1` tests in build Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug for current testing day](https://testing-dev.sandia.gov/cdash/queryTests.php?project=Trilinos&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug&field2=site&compare2=61&value2=sems-rhel7&field3=block&field3count=2&field3field1=testname&field3compare1=61&field3value1=TpetraCore_MultiVector_UnitTests_MPI_4&field3field2=testname&field3compare2=65&field3value2=TpetraCore_gemm_m_eq_)
## Steps to Reproduce
One should be able to reproduce this failure on a CEE LAN `ascicgpu<NUM>` 'sems-rhel7' as described in:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md
More specifically, the commands given for the system CEE LAN `ascicgpu<NUM>` 'sems-rhel7' are provided at:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md#sems-rhel7-environment
The exact commands to reproduce this issue should be:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh \
Trilinos-atdm-sems-rhel7-cuda-9.2-Volta70-complex-shared-release-debug
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_TpetraCore=ON \
$TRILINOS_DIR
$ make NP=16
$ ctest -j4
```
|
non_process
|
tpetracore multivector unittests mpi and tpetracore gemm m eq mpi tests in build trilinos atdm sems cuda complex shared release debug failing starting cc trilinos tpetra kddevin trilinos data services product lead bartlettroscoe seheracer next action status description as shown in the tests tpetracore gemm m eq mpi tpetracore gemm m eq mpi tpetracore gemm m eq mpi tpetracore gemm m eq mpi tpetracore multivector unittests mpi are failing in build trilinos atdm sems cuda complex shared release debug starting as shown in the tests tpetracore gemm m eq mpi are all failing the unit test blas std gemm unittest showing error output like trans a c trans b n a norm b norm c norm bound false true failed scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test blas gemm cpp comparing kokkosblas gemm against teuchos blas gemm max error error bound false true failed scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test blas gemm cpp comparing kokkosblas default gemm against teuchos blas gemm max error error bound at least one test failed abandoning the others at least one test failed abandoning the others at least one test failed abandoning the others sec blas std gemm unittest as shown in the test tpetracore multivector unittests mpi is failing the unit test multivector int longlong std kokkos compat kokkoscudawrappernode multiply unittest showing oputput like multivector int longlong std kokkos compat kokkoscudawrappernode multiply unittest test multivector multiply comparing tmpview passed comparing tmpview passed comparing tmpview passed comparing tmpview passed gblsuccess true passed comparing tmpview sdmview passed gblsuccess true passed comparing tmpview sdmview passed gblsuccess true passed comparing tmpview sdmview error relerr tmpview sdmview relerr tol failed error relerr tmpview sdmview relerr tol failed error relerr tmpview sdmview relerr tol failed error relerr tmpview sdmview relerr tol failed gblsuccess true failed scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test multivector multivector unittests cpp comparing tmpview sdmview passed gblsuccess true failed scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test multivector multivector unittests cpp comparing tmpview check tmpview size passed comparing tmpview check tmpview size passed comparing tmpview check tmpview size passed comparing tmpview check tmpview size passed gblsuccess true failed scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test multivector multivector unittests cpp comparing tmpview passed comparing tmpview passed gblsuccess true failed scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test multivector multivector unittests cpp sec multivector int longlong std kokkos compat kokkoscudawrappernode multiply unittest location scratch jenkins workspace trilinos atdm sems cuda complex shared release debug src and build trilinos packages tpetra core test multivector multivector unittests cpp the new commits that were pulled on the testing day as shown looking over that set of commits the commits most likely to have triggered this failuire are add beta case and allow number of teams smaller than to resolve nan and diff issues in some teko and shylu tests author seher acer date wed dec m packages kokkos kernels src impl tpls gemm tpl spec decl hpp kokkoskernels optimized gemm over cublas gemm for a tb with tall and skinny matrices on cuda author seher acer date tue nov m packages kokkos kernels src impl tpls gemm tpl spec decl hpp pulled in from pr by seheracer current status on cdash steps to reproduce one should be able to reproduce this failure on a cee lan ascicgpu sems as described in more specifically the commands given for the system cee lan ascicgpu sems are provided at the exact commands to reproduce this issue should be cd source trilinos dir cmake std atdm load env sh trilinos atdm sems cuda complex shared release debug cmake gninja dtrilinos configure options file string cmake std atdm atdmdevenv cmake dtrilinos enable tests on dtrilinos enable tpetracore on trilinos dir make np ctest
| 0
|
8,959
| 12,068,353,876
|
IssuesEvent
|
2020-04-16 14:39:32
|
Inria-Visages/BIDS-prov
|
https://api.github.com/repos/Inria-Visages/BIDS-prov
|
closed
|
Create an issue template that we will use to propose updates on the spec [2h]
|
Spec update process
|
Choose one feature that is not currently in the spec and use it as an example to create an issue template for proposal of updates on the spec.
This issue template will include the following: "Minimal example before/after", "rationale" and probably more.
Look at examples of issues in the https://github.com/bids-standard/bids-specification/ to see if there is a common structure / existing issue templates?
Deliverable: a markdown file (in the current repo) as Github issue template.
|
1.0
|
Create an issue template that we will use to propose updates on the spec [2h] - Choose one feature that is not currently in the spec and use it as an example to create an issue template for proposal of updates on the spec.
This issue template will include the following: "Minimal example before/after", "rationale" and probably more.
Look at examples of issues in the https://github.com/bids-standard/bids-specification/ to see if there is a common structure / existing issue templates?
Deliverable: a markdown file (in the current repo) as Github issue template.
|
process
|
create an issue template that we will use to propose updates on the spec choose one feature that is not currently in the spec and use it as an example to create an issue template for proposal of updates on the spec this issue template will include the following minimal example before after rationale and probably more look at examples of issues in the to see if there is a common structure existing issue templates deliverable a markdown file in the current repo as github issue template
| 1
|
125,549
| 10,346,058,921
|
IssuesEvent
|
2019-09-04 14:36:33
|
rancher/rancher
|
https://api.github.com/repos/rancher/rancher
|
closed
|
No way to add taints to nodes
|
[zube]: To Test area/node-template area/rke internal kind/feature team/cn
|
Background:
There doesn't seem to be any way to add taints in Rancher or RKE at the moment.
Ideally, we should be allowed to define this in the node template.
If someone wants to create dedicated load balancer (e.g ingress controllers) nodes, then we can't mark those nodes with taints and use tolerations for specific workloads.
This becomes a pain because you have to do this afterwards with `kubectl`, but you needlessly need to change taints to NoExecute to evict some containers that have been scheduled automatically to the nodes, where it should have been prevented at creation time.
Expected:
- [x] Support taints for node pool
- [x] Support taints for node template
- [x] Support taints for node
- [x] Support taints when adding custom node
- [x] Show taints in node list
- [x] Support adding tolerations when enable istio and monitoring for workloads
|
1.0
|
No way to add taints to nodes - Background:
There doesn't seem to be any way to add taints in Rancher or RKE at the moment.
Ideally, we should be allowed to define this in the node template.
If someone wants to create dedicated load balancer (e.g ingress controllers) nodes, then we can't mark those nodes with taints and use tolerations for specific workloads.
This becomes a pain because you have to do this afterwards with `kubectl`, but you needlessly need to change taints to NoExecute to evict some containers that have been scheduled automatically to the nodes, where it should have been prevented at creation time.
Expected:
- [x] Support taints for node pool
- [x] Support taints for node template
- [x] Support taints for node
- [x] Support taints when adding custom node
- [x] Show taints in node list
- [x] Support adding tolerations when enable istio and monitoring for workloads
|
non_process
|
no way to add taints to nodes background there doesn t seem to be any way to add taints in rancher or rke at the moment ideally we should be allowed to define this in the node template if someone wants to create dedicated load balancer e g ingress controllers nodes then we can t mark those nodes with taints and use tolerations for specific workloads this becomes a pain because you have to do this afterwards with kubectl but you needlessly need to change taints to noexecute to evict some containers that have been scheduled automatically to the nodes where it should have been prevented at creation time expected support taints for node pool support taints for node template support taints for node support taints when adding custom node show taints in node list support adding tolerations when enable istio and monitoring for workloads
| 0
|
8,860
| 27,172,339,624
|
IssuesEvent
|
2023-02-17 20:41:31
|
OneDrive/onedrive-api-docs
|
https://api.github.com/repos/OneDrive/onedrive-api-docs
|
closed
|
429 - throttledRequest errors using /createLink endpoint after creating just a few links
|
Needs: Investigation automation:Closed
|
#### Category
- [x] Question
- [x] Documentation issue
- [ ] Bug
#### Observed Behavior
Since a while, I am getting `429 - throttledRequest` errors when creating a few read-only shared links via the `/drives/{driveId}/items/{itemId}/createLink` endpoint. It seems to be specific for _OneDrive Personal_ accounts.
```
{
"type": "view",
"scope": "anonymous"
}
```
Here is the specific response I get
```
{
"headers": {
"retry-after": "3360",
},
"error": {
"code": "accessDenied",
"message": "Too Many Requests",
"innerError": {
"code": "throttledRequest",
"date": "2021-02-11T09:36:01",
"request-id": "a28f6f2b-b233-47a1-85dd-111da0293500",
"client-request-id": "a28f6f2b-b233-47a1-85dd-111da0293500"
}
}
}
```
Generally speaking that shouldn't be an issue, however:
- I get this error if I create only 10 links in ~5 minutes time. Even if no API calls were made that day at all /for this user.
- The error is also thrown if a sharing link already exists for the file.
- The Retry-After period is set to ~ 1 hour, which makes it practically impossible to use the backoff mechanism that is implemented to prevent throttling.
Also:
- I haven't observed this issue until a few weeks ago
- I can only reproduce this for OneDrive Personal accounts.
- All other other endpoints are not throttled. So other API requests are successful when the `/createLink` request is still being throttled.
#### Steps to Reproduce
Create multiple (>10) shared read-only links via the API on a OneDrive Personal account.
#### Question
Is this behavior expected and has the throttling threshold indeed been decreased? Or is this a bug in the API itself which has been introduced?
If the limit is indeed this low, it would be a good idea to mention this in the documentation as it limits the use of this specific endpoint.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues
|
1.0
|
429 - throttledRequest errors using /createLink endpoint after creating just a few links - #### Category
- [x] Question
- [x] Documentation issue
- [ ] Bug
#### Observed Behavior
Since a while, I am getting `429 - throttledRequest` errors when creating a few read-only shared links via the `/drives/{driveId}/items/{itemId}/createLink` endpoint. It seems to be specific for _OneDrive Personal_ accounts.
```
{
"type": "view",
"scope": "anonymous"
}
```
Here is the specific response I get
```
{
"headers": {
"retry-after": "3360",
},
"error": {
"code": "accessDenied",
"message": "Too Many Requests",
"innerError": {
"code": "throttledRequest",
"date": "2021-02-11T09:36:01",
"request-id": "a28f6f2b-b233-47a1-85dd-111da0293500",
"client-request-id": "a28f6f2b-b233-47a1-85dd-111da0293500"
}
}
}
```
Generally speaking that shouldn't be an issue, however:
- I get this error if I create only 10 links in ~5 minutes time. Even if no API calls were made that day at all /for this user.
- The error is also thrown if a sharing link already exists for the file.
- The Retry-After period is set to ~ 1 hour, which makes it practically impossible to use the backoff mechanism that is implemented to prevent throttling.
Also:
- I haven't observed this issue until a few weeks ago
- I can only reproduce this for OneDrive Personal accounts.
- All other other endpoints are not throttled. So other API requests are successful when the `/createLink` request is still being throttled.
#### Steps to Reproduce
Create multiple (>10) shared read-only links via the API on a OneDrive Personal account.
#### Question
Is this behavior expected and has the throttling threshold indeed been decreased? Or is this a bug in the API itself which has been introduced?
If the limit is indeed this low, it would be a good idea to mention this in the documentation as it limits the use of this specific endpoint.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues
|
non_process
|
throttledrequest errors using createlink endpoint after creating just a few links category question documentation issue bug observed behavior since a while i am getting throttledrequest errors when creating a few read only shared links via the drives driveid items itemid createlink endpoint it seems to be specific for onedrive personal accounts type view scope anonymous here is the specific response i get headers retry after error code accessdenied message too many requests innererror code throttledrequest date request id client request id generally speaking that shouldn t be an issue however i get this error if i create only links in minutes time even if no api calls were made that day at all for this user the error is also thrown if a sharing link already exists for the file the retry after period is set to hour which makes it practically impossible to use the backoff mechanism that is implemented to prevent throttling also i haven t observed this issue until a few weeks ago i can only reproduce this for onedrive personal accounts all other other endpoints are not throttled so other api requests are successful when the createlink request is still being throttled steps to reproduce create multiple shared read only links via the api on a onedrive personal account question is this behavior expected and has the throttling threshold indeed been decreased or is this a bug in the api itself which has been introduced if the limit is indeed this low it would be a good idea to mention this in the documentation as it limits the use of this specific endpoint
| 0
|
82,559
| 15,646,596,807
|
IssuesEvent
|
2021-03-23 01:17:33
|
fbennets/HU-grade-crawler
|
https://api.github.com/repos/fbennets/HU-grade-crawler
|
opened
|
CVE-2020-27783 (Medium) detected in lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl
|
security vulnerability
|
## CVE-2020-27783 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>Powerful and Pythonic XML processing library combining libxml2/libxslt with the ElementTree API.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/03/06/eb9f000882f671a2d494342c1fe93b1c8b18fb04420bb611aeaa3298ef17/lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/03/06/eb9f000882f671a2d494342c1fe93b1c8b18fb04420bb611aeaa3298ef17/lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: HU-grade-crawler/requirements.txt</p>
<p>Path to vulnerable library: HU-grade-crawler/requirements.txt</p>
<p>
Dependency Hierarchy:
- MechanicalSoup-0.12.0-py2.py3-none-any.whl (Root Library)
- :x: **lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote attacker could exploit this flaw to run arbitrary HTML/JS code.
<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27783>CVE-2020-27783</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1901633">https://bugzilla.redhat.com/show_bug.cgi?id=1901633</a></p>
<p>Release Date: 2020-10-27</p>
<p>Fix Resolution: 4.6.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-27783 (Medium) detected in lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2020-27783 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>Powerful and Pythonic XML processing library combining libxml2/libxslt with the ElementTree API.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/03/06/eb9f000882f671a2d494342c1fe93b1c8b18fb04420bb611aeaa3298ef17/lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/03/06/eb9f000882f671a2d494342c1fe93b1c8b18fb04420bb611aeaa3298ef17/lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: HU-grade-crawler/requirements.txt</p>
<p>Path to vulnerable library: HU-grade-crawler/requirements.txt</p>
<p>
Dependency Hierarchy:
- MechanicalSoup-0.12.0-py2.py3-none-any.whl (Root Library)
- :x: **lxml-4.5.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote attacker could exploit this flaw to run arbitrary HTML/JS code.
<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27783>CVE-2020-27783</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1901633">https://bugzilla.redhat.com/show_bug.cgi?id=1901633</a></p>
<p>Release Date: 2020-10-27</p>
<p>Fix Resolution: 4.6.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in lxml whl cve medium severity vulnerability vulnerable library lxml whl powerful and pythonic xml processing library combining libxslt with the elementtree api library home page a href path to dependency file hu grade crawler requirements txt path to vulnerable library hu grade crawler requirements txt dependency hierarchy mechanicalsoup none any whl root library x lxml whl vulnerable library vulnerability details a xss vulnerability was discovered in python lxml s clean module the module s parser didn t properly imitate browsers which caused different behaviors between the sanitizer and the user s page a remote attacker could exploit this flaw to run arbitrary html js code publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
342,431
| 24,742,203,647
|
IssuesEvent
|
2022-10-21 06:36:54
|
actualbudget/docs
|
https://api.github.com/repos/actualbudget/docs
|
closed
|
🗄️ [Documentation] - How to manage credit cards
|
documentation complete
|
### Description
Detail a workflow and thought process of using credit cards with Actual.
1. Paying the card
2. Adding debt to the credit card to balance the budget in a month of over spending.
3. Adding transactions against a credit card.
edit: I know this is covered briefly in the FAQ, but I think it's a budgeting topic that deserves some in depth explanation.
### Category
Budgeting
|
1.0
|
🗄️ [Documentation] - How to manage credit cards - ### Description
Detail a workflow and thought process of using credit cards with Actual.
1. Paying the card
2. Adding debt to the credit card to balance the budget in a month of over spending.
3. Adding transactions against a credit card.
edit: I know this is covered briefly in the FAQ, but I think it's a budgeting topic that deserves some in depth explanation.
### Category
Budgeting
|
non_process
|
🗄️ how to manage credit cards description detail a workflow and thought process of using credit cards with actual paying the card adding debt to the credit card to balance the budget in a month of over spending adding transactions against a credit card edit i know this is covered briefly in the faq but i think it s a budgeting topic that deserves some in depth explanation category budgeting
| 0
|
15,541
| 19,703,300,414
|
IssuesEvent
|
2022-01-12 18:54:34
|
googleapis/sloth
|
https://api.github.com/repos/googleapis/sloth
|
opened
|
Your .repo-metadata.json file has a problem 🤒
|
type: process repo-metadata: lint
|
You have a problem with your .repo-metadata.json file:
Result of scan 📈:
* must have required property 'library_type' in .repo-metadata.json
* must have required property 'release_level' in .repo-metadata.json
☝️ Once you correct these problems, you can close this issue.
Reach out to **go/github-automation** if you have any questions.
|
1.0
|
Your .repo-metadata.json file has a problem 🤒 - You have a problem with your .repo-metadata.json file:
Result of scan 📈:
* must have required property 'library_type' in .repo-metadata.json
* must have required property 'release_level' in .repo-metadata.json
☝️ Once you correct these problems, you can close this issue.
Reach out to **go/github-automation** if you have any questions.
|
process
|
your repo metadata json file has a problem 🤒 you have a problem with your repo metadata json file result of scan 📈 must have required property library type in repo metadata json must have required property release level in repo metadata json ☝️ once you correct these problems you can close this issue reach out to go github automation if you have any questions
| 1
|
657,351
| 21,791,029,659
|
IssuesEvent
|
2022-05-14 22:42:24
|
lockc-project/lockc
|
https://api.github.com/repos/lockc-project/lockc
|
closed
|
[EPIC] Migrate from libbpf-rs to aya-rs
|
enhancement priority/high
|
Aya allows to write BPF programs in Rust which is natively compiled by Rust compiler.
https://github.com/aya-rs/aya
# TODO
## Upstream
- [x] aya-rs/aya/issues/9
- [x] aya-rs/aya-log/issues/4
- [x] aya-rs/aya/issues/128
## Downstream
First steps, which can be done now:
- [x] #135
- [ ] #136
- [ ] #137
Items blocked by upstream:
- [ ] #138
- [ ] #139
|
1.0
|
[EPIC] Migrate from libbpf-rs to aya-rs - Aya allows to write BPF programs in Rust which is natively compiled by Rust compiler.
https://github.com/aya-rs/aya
# TODO
## Upstream
- [x] aya-rs/aya/issues/9
- [x] aya-rs/aya-log/issues/4
- [x] aya-rs/aya/issues/128
## Downstream
First steps, which can be done now:
- [x] #135
- [ ] #136
- [ ] #137
Items blocked by upstream:
- [ ] #138
- [ ] #139
|
non_process
|
migrate from libbpf rs to aya rs aya allows to write bpf programs in rust which is natively compiled by rust compiler todo upstream aya rs aya issues aya rs aya log issues aya rs aya issues downstream first steps which can be done now items blocked by upstream
| 0
|
13,998
| 9,124,507,462
|
IssuesEvent
|
2019-02-24 04:03:28
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Allow Access to Azure Services
|
cxp product-question security/svc triaged
|
The documentation says: "A Web App can be mapped to a private IP in a VNet/subnet. Even if service endpoints are turned ON from the given VNet/subnet, connections from the Web App to the server will have an Azure public IP source, not a VNet/subnet source. To enable connectivity from a Web App to a server that has VNet firewall rules, you must Allow Azure services to access server on the server.".
But my question is: Could we use the outbound IP address of the App Service Plan to set up our firewall rules on the Azure SQL Database? We would like to disable the option "Allow Access to Azure Services", so we want to add the Outbound IP Address of our App Services Plan to allow access from our App Services to our Azure SQL Database. Is it a good way to improve the security to restrict the access to our Azure SQL Databases?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 500a2c86-b9f9-1e9a-1c22-3579450ba95b
* Version Independent ID: ce872fbb-7707-5ff3-e1f9-aa8c170553cc
* Content: [Securing PaaS Databases in Azure](https://docs.microsoft.com/en-us/azure/security/security-paas-applications-using-sql)
* Content Source: [articles/security/security-paas-applications-using-sql.md](https://github.com/Microsoft/azure-docs/blob/master/articles/security/security-paas-applications-using-sql.md)
* Service: **security**
* GitHub Login: @techlake
* Microsoft Alias: **terrylan**
|
True
|
Allow Access to Azure Services - The documentation says: "A Web App can be mapped to a private IP in a VNet/subnet. Even if service endpoints are turned ON from the given VNet/subnet, connections from the Web App to the server will have an Azure public IP source, not a VNet/subnet source. To enable connectivity from a Web App to a server that has VNet firewall rules, you must Allow Azure services to access server on the server.".
But my question is: Could we use the outbound IP address of the App Service Plan to set up our firewall rules on the Azure SQL Database? We would like to disable the option "Allow Access to Azure Services", so we want to add the Outbound IP Address of our App Services Plan to allow access from our App Services to our Azure SQL Database. Is it a good way to improve the security to restrict the access to our Azure SQL Databases?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 500a2c86-b9f9-1e9a-1c22-3579450ba95b
* Version Independent ID: ce872fbb-7707-5ff3-e1f9-aa8c170553cc
* Content: [Securing PaaS Databases in Azure](https://docs.microsoft.com/en-us/azure/security/security-paas-applications-using-sql)
* Content Source: [articles/security/security-paas-applications-using-sql.md](https://github.com/Microsoft/azure-docs/blob/master/articles/security/security-paas-applications-using-sql.md)
* Service: **security**
* GitHub Login: @techlake
* Microsoft Alias: **terrylan**
|
non_process
|
allow access to azure services the documentation says a web app can be mapped to a private ip in a vnet subnet even if service endpoints are turned on from the given vnet subnet connections from the web app to the server will have an azure public ip source not a vnet subnet source to enable connectivity from a web app to a server that has vnet firewall rules you must allow azure services to access server on the server but my question is could we use the outbound ip address of the app service plan to set up our firewall rules on the azure sql database we would like to disable the option allow access to azure services so we want to add the outbound ip address of our app services plan to allow access from our app services to our azure sql database is it a good way to improve the security to restrict the access to our azure sql databases 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 security github login techlake microsoft alias terrylan
| 0
|
4,976
| 7,807,886,294
|
IssuesEvent
|
2018-06-11 18:21:12
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Azure Site Recorvery : Replication Error
|
cxp in-process product-question site-recovery/svc triaged
|
Getting the following error below when trying to enable azure site recovery on my VM. How can I fix this?
ERROR (1):
Virtual machine's OS disk is encrypted and no target keyvault information passed. ( ERROR CODE : 150175)
Possible causes: Disk encryption information like, secret identifier and its target KeyVault resource id are missing.
Recommended actions: Resolve the issue and retry the operation. If the problem persists, contact support.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: c714cc40-47f5-fb3c-51e0-f504c38ec937
* Version Independent ID: 15da2499-61eb-ec11-53be-7d006cdd4b38
* Content: [Set up disaster recovery for Azure VMs to a secondary Azure region with Azure Site Recovery](https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication#enable-replication)
* Content Source: [articles/site-recovery/azure-to-azure-tutorial-enable-replication.md](https://github.com/Microsoft/azure-docs/blob/master/articles/site-recovery/azure-to-azure-tutorial-enable-replication.md)
* Service: **site-recovery**
* GitHub Login: @rayne-wiselman
* Microsoft Alias: **raynew**
|
1.0
|
Azure Site Recorvery : Replication Error - Getting the following error below when trying to enable azure site recovery on my VM. How can I fix this?
ERROR (1):
Virtual machine's OS disk is encrypted and no target keyvault information passed. ( ERROR CODE : 150175)
Possible causes: Disk encryption information like, secret identifier and its target KeyVault resource id are missing.
Recommended actions: Resolve the issue and retry the operation. If the problem persists, contact support.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: c714cc40-47f5-fb3c-51e0-f504c38ec937
* Version Independent ID: 15da2499-61eb-ec11-53be-7d006cdd4b38
* Content: [Set up disaster recovery for Azure VMs to a secondary Azure region with Azure Site Recovery](https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication#enable-replication)
* Content Source: [articles/site-recovery/azure-to-azure-tutorial-enable-replication.md](https://github.com/Microsoft/azure-docs/blob/master/articles/site-recovery/azure-to-azure-tutorial-enable-replication.md)
* Service: **site-recovery**
* GitHub Login: @rayne-wiselman
* Microsoft Alias: **raynew**
|
process
|
azure site recorvery replication error getting the following error below when trying to enable azure site recovery on my vm how can i fix this error virtual machine s os disk is encrypted and no target keyvault information passed error code possible causes disk encryption information like secret identifier and its target keyvault resource id are missing recommended actions resolve the issue and retry the operation if the problem persists contact support 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 site recovery github login rayne wiselman microsoft alias raynew
| 1
|
13,480
| 16,011,518,322
|
IssuesEvent
|
2021-04-20 11:12:50
|
e4exp/paper_manager_abstract
|
https://api.github.com/repos/e4exp/paper_manager_abstract
|
opened
|
An Adversarially-Learned Turing Test for Dialog Generation Models
|
2021 Adversarial Attack Adversarial Training Evaluation Natural Language Processing
|
- https://arxiv.org/abs/2104.08231
- 2021
より優れた自動対話評価指標の設計は、会話AIの評価研究を加速させる可能性を秘めています。
しかし、既存の学習可能な対話評価モデルは、一般的に純粋な教師ありきで学習された分類器に限られており、敵対的な攻撃（例えば、無意味な回答が高い分類スコアを享受すること）による大きなリスクを抱えています。
このリスクを軽減するために、我々は、機械で生成された応答と人間が書いた応答を識別する頑健なモデルATT（Adversarial Turing Test）を学習するための敵対的学習アプローチを提案する。
これまでの摂動に基づく手法とは異なり、我々の識別器は、強化学習を用いて制限のない多様な敵対的な例を反復的に生成することで学習される。
この制限のない敵対的な学習アプローチの主な利点は、反復的な攻撃と防御のゲームにおいて識別器のロバスト性を向上させることです。
我々の識別器は、DialoGPTやGPT-3などの強力な攻撃者に対して高い精度を示す。
|
1.0
|
An Adversarially-Learned Turing Test for Dialog Generation Models - - https://arxiv.org/abs/2104.08231
- 2021
より優れた自動対話評価指標の設計は、会話AIの評価研究を加速させる可能性を秘めています。
しかし、既存の学習可能な対話評価モデルは、一般的に純粋な教師ありきで学習された分類器に限られており、敵対的な攻撃（例えば、無意味な回答が高い分類スコアを享受すること）による大きなリスクを抱えています。
このリスクを軽減するために、我々は、機械で生成された応答と人間が書いた応答を識別する頑健なモデルATT（Adversarial Turing Test）を学習するための敵対的学習アプローチを提案する。
これまでの摂動に基づく手法とは異なり、我々の識別器は、強化学習を用いて制限のない多様な敵対的な例を反復的に生成することで学習される。
この制限のない敵対的な学習アプローチの主な利点は、反復的な攻撃と防御のゲームにおいて識別器のロバスト性を向上させることです。
我々の識別器は、DialoGPTやGPT-3などの強力な攻撃者に対して高い精度を示す。
|
process
|
an adversarially learned turing test for dialog generation models より優れた自動対話評価指標の設計は、会話aiの評価研究を加速させる可能性を秘めています。 しかし、既存の学習可能な対話評価モデルは、一般的に純粋な教師ありきで学習された分類器に限られており、敵対的な攻撃（例えば、無意味な回答が高い分類スコアを享受すること）による大きなリスクを抱えています。 このリスクを軽減するために、我々は、機械で生成された応答と人間が書いた応答を識別する頑健なモデルatt（adversarial turing test）を学習するための敵対的学習アプローチを提案する。 これまでの摂動に基づく手法とは異なり、我々の識別器は、強化学習を用いて制限のない多様な敵対的な例を反復的に生成することで学習される。 この制限のない敵対的な学習アプローチの主な利点は、反復的な攻撃と防御のゲームにおいて識別器のロバスト性を向上させることです。 我々の識別器は、dialogptやgpt 。
| 1
|
4,095
| 7,045,915,322
|
IssuesEvent
|
2018-01-02 02:33:37
|
inasafe/inasafe
|
https://api.github.com/repos/inasafe/inasafe
|
closed
|
Smoothed MMI and contours should be produced as pre-processor step
|
Impact function Preprocessing
|
### Problem
We should automatically generate the smoothed MMI grid and contours during IF run and then make this available as 'future products' so that they can be used in the multi-exposure dialog.
|
1.0
|
Smoothed MMI and contours should be produced as pre-processor step - ### Problem
We should automatically generate the smoothed MMI grid and contours during IF run and then make this available as 'future products' so that they can be used in the multi-exposure dialog.
|
process
|
smoothed mmi and contours should be produced as pre processor step problem we should automatically generate the smoothed mmi grid and contours during if run and then make this available as future products so that they can be used in the multi exposure dialog
| 1
|
17,769
| 23,698,683,445
|
IssuesEvent
|
2022-08-29 16:50:54
|
cloudfoundry/korifi
|
https://api.github.com/repos/cloudfoundry/korifi
|
opened
|
[Feature]: Developer can push apps using the top-level `command` field in the manifest
|
Top-level process config
|
### Blockers/Dependencies
_No response_
### Background
**As a** developer
**I want** top-level process configuration in manifests to be supported
**So that** I can use shortcut `cf push` flags like `-c`, `-i`, `-m` etc.
### Acceptance Criteria
**GIVEN** I have the sources of an application (e.g. `tests/smoke/assets/test-node-app`)
**WHEN I** push it with the following command:
```sh
cf push test -c "sleep 999"
```
**THEN I** see the push succeeds with an output similar to this:
```
name: test
requested state: started
routes: test.vcap.me
last uploaded: Mon 29 Aug 16:28:36 UTC 2022
stack: cflinuxfs3
buildpacks:
name version detect output buildpack name
nodejs_buildpack 1.7.61 nodejs nodejs
type: web
sidecars:
instances: 1/1
memory usage: 256M
start command: sleep 999
state since cpu memory disk details
#0 running 2022-08-29T16:28:54Z 1.6% 42.3M of 256M 115.7M of 1G
```
### Dev Notes
The CLI will use the top-level `command` field on app objects for this, but [only if](https://github.com/cloudfoundry/cli/blob/68d897a19792bdffe20c39589148216b23c950d1/actor/v7pushaction/handle_start_command_override.go#L14-L20) there's no `manifest.yml`, or if `manifest.yml` doesn't already have a `web` process definition.
|
1.0
|
[Feature]: Developer can push apps using the top-level `command` field in the manifest - ### Blockers/Dependencies
_No response_
### Background
**As a** developer
**I want** top-level process configuration in manifests to be supported
**So that** I can use shortcut `cf push` flags like `-c`, `-i`, `-m` etc.
### Acceptance Criteria
**GIVEN** I have the sources of an application (e.g. `tests/smoke/assets/test-node-app`)
**WHEN I** push it with the following command:
```sh
cf push test -c "sleep 999"
```
**THEN I** see the push succeeds with an output similar to this:
```
name: test
requested state: started
routes: test.vcap.me
last uploaded: Mon 29 Aug 16:28:36 UTC 2022
stack: cflinuxfs3
buildpacks:
name version detect output buildpack name
nodejs_buildpack 1.7.61 nodejs nodejs
type: web
sidecars:
instances: 1/1
memory usage: 256M
start command: sleep 999
state since cpu memory disk details
#0 running 2022-08-29T16:28:54Z 1.6% 42.3M of 256M 115.7M of 1G
```
### Dev Notes
The CLI will use the top-level `command` field on app objects for this, but [only if](https://github.com/cloudfoundry/cli/blob/68d897a19792bdffe20c39589148216b23c950d1/actor/v7pushaction/handle_start_command_override.go#L14-L20) there's no `manifest.yml`, or if `manifest.yml` doesn't already have a `web` process definition.
|
process
|
developer can push apps using the top level command field in the manifest blockers dependencies no response background as a developer i want top level process configuration in manifests to be supported so that i can use shortcut cf push flags like c i m etc acceptance criteria given i have the sources of an application e g tests smoke assets test node app when i push it with the following command sh cf push test c sleep then i see the push succeeds with an output similar to this name test requested state started routes test vcap me last uploaded mon aug utc stack buildpacks name version detect output buildpack name nodejs buildpack nodejs nodejs type web sidecars instances memory usage start command sleep state since cpu memory disk details running of of dev notes the cli will use the top level command field on app objects for this but there s no manifest yml or if manifest yml doesn t already have a web process definition
| 1
|
15,492
| 19,703,225,240
|
IssuesEvent
|
2022-01-12 18:49:32
|
googleapis/common-protos-ruby
|
https://api.github.com/repos/googleapis/common-protos-ruby
|
opened
|
Your .repo-metadata.json files have a problem 🤒
|
type: process repo-metadata: lint
|
You have a problem with your .repo-metadata.json files:
Result of scan 📈:
* must have required property 'release_level' in google-cloud-common/.repo-metadata.json
* must have required property 'client_documentation' in google-cloud-common/.repo-metadata.json
* must have required property 'release_level' in googleapis-common-protos-types/.repo-metadata.json
* must have required property 'client_documentation' in googleapis-common-protos-types/.repo-metadata.json
* must have required property 'release_level' in googleapis-common-protos/.repo-metadata.json
* must have required property 'client_documentation' in googleapis-common-protos/.repo-metadata.json
* must have required property 'release_level' in grpc-google-iam-v1/.repo-metadata.json
* must have required property 'client_documentation' in grpc-google-iam-v1/.repo-metadata.json
☝️ Once you correct these problems, you can close this issue.
Reach out to **go/github-automation** if you have any questions.
|
1.0
|
Your .repo-metadata.json files have a problem 🤒 - You have a problem with your .repo-metadata.json files:
Result of scan 📈:
* must have required property 'release_level' in google-cloud-common/.repo-metadata.json
* must have required property 'client_documentation' in google-cloud-common/.repo-metadata.json
* must have required property 'release_level' in googleapis-common-protos-types/.repo-metadata.json
* must have required property 'client_documentation' in googleapis-common-protos-types/.repo-metadata.json
* must have required property 'release_level' in googleapis-common-protos/.repo-metadata.json
* must have required property 'client_documentation' in googleapis-common-protos/.repo-metadata.json
* must have required property 'release_level' in grpc-google-iam-v1/.repo-metadata.json
* must have required property 'client_documentation' in grpc-google-iam-v1/.repo-metadata.json
☝️ Once you correct these problems, you can close this issue.
Reach out to **go/github-automation** if you have any questions.
|
process
|
your repo metadata json files have a problem 🤒 you have a problem with your repo metadata json files result of scan 📈 must have required property release level in google cloud common repo metadata json must have required property client documentation in google cloud common repo metadata json must have required property release level in googleapis common protos types repo metadata json must have required property client documentation in googleapis common protos types repo metadata json must have required property release level in googleapis common protos repo metadata json must have required property client documentation in googleapis common protos repo metadata json must have required property release level in grpc google iam repo metadata json must have required property client documentation in grpc google iam repo metadata json ☝️ once you correct these problems you can close this issue reach out to go github automation if you have any questions
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.