Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 4
112
| repo_url
stringlengths 33
141
| action
stringclasses 3
values | title
stringlengths 1
1.02k
| labels
stringlengths 4
1.54k
| body
stringlengths 1
262k
| index
stringclasses 17
values | text_combine
stringlengths 95
262k
| label
stringclasses 2
values | text
stringlengths 96
252k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
156,779
| 5,989,092,559
|
IssuesEvent
|
2017-06-02 07:33:29
|
universAAL/ui
|
https://api.github.com/repos/universAAL/ui
|
closed
|
Message dialog callback after clicking Delete btn not called
|
bug imported priority 3
|
_Originally Opened: Ioannis Moulos (2012-05-23 11:47:43_)
_Originally Closed: 2012-05-24 15:13:43_
Using bus.ui/1.1.0 and dm.mobile/1.1.0
Message dialog callback after clicking Delete btn not called.
public void dialogAborted(String dialogID) {
System.out.println("-----DIALOG ABORTED--------");
//THIS IS NOT SHOWN WHEN I CLICK DELETE ON THE MESSAGE DIALOG
}
private Form initMainDialog() {
Form f = Form.newMessage("MPLA MPLA"," message");
return f;
}
void startMainDialog() {
if (mainDialog == null)
mainDialog = initMainDialog();
UIRequest out = new UIRequest(new Resource(), mainDialog,
LevelRating.middle, Locale.ENGLISH, PrivacyLevel.insensible);
sendUIRequest(out);
}
--
From: _this issue has been automatically imported from our old issue tracker_
|
1.0
|
Message dialog callback after clicking Delete btn not called - _Originally Opened: Ioannis Moulos (2012-05-23 11:47:43_)
_Originally Closed: 2012-05-24 15:13:43_
Using bus.ui/1.1.0 and dm.mobile/1.1.0
Message dialog callback after clicking Delete btn not called.
public void dialogAborted(String dialogID) {
System.out.println("-----DIALOG ABORTED--------");
//THIS IS NOT SHOWN WHEN I CLICK DELETE ON THE MESSAGE DIALOG
}
private Form initMainDialog() {
Form f = Form.newMessage("MPLA MPLA"," message");
return f;
}
void startMainDialog() {
if (mainDialog == null)
mainDialog = initMainDialog();
UIRequest out = new UIRequest(new Resource(), mainDialog,
LevelRating.middle, Locale.ENGLISH, PrivacyLevel.insensible);
sendUIRequest(out);
}
--
From: _this issue has been automatically imported from our old issue tracker_
|
non_test
|
message dialog callback after clicking delete btn not called originally opened ioannis moulos originally closed using bus ui and dm mobile message dialog callback after clicking delete btn not called public void dialogaborted string dialogid system out println quot dialog aborted quot this is not shown when i click delete on the message dialog private form initmaindialog form f form newmessage quot mpla mpla quot quot message quot return f void startmaindialog if maindialog null maindialog initmaindialog uirequest out new uirequest new resource maindialog levelrating middle locale english privacylevel insensible senduirequest out from this issue has been automatically imported from our old issue tracker
| 0
|
232,775
| 7,675,153,037
|
IssuesEvent
|
2018-05-15 07:44:20
|
Intelehealth/intelehealth-openmrs-module
|
https://api.github.com/repos/Intelehealth/intelehealth-openmrs-module
|
closed
|
Allergy UI links to the clinician facing patient dashboard
|
enhancement priority:medium
|
IH patient dashboard > Allergy fragment links to clinician facing patient dashboard.
|
1.0
|
Allergy UI links to the clinician facing patient dashboard - IH patient dashboard > Allergy fragment links to clinician facing patient dashboard.
|
non_test
|
allergy ui links to the clinician facing patient dashboard ih patient dashboard allergy fragment links to clinician facing patient dashboard
| 0
|
77,227
| 26,862,937,732
|
IssuesEvent
|
2023-02-03 20:12:56
|
department-of-veterans-affairs/va.gov-cms
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms
|
closed
|
Lovell editors can not select a System when creating VAMC System Health Service
|
Defect Needs refining
|
## Describe the defect
When creating or editing a VAMC System Health Service, Lovell editors have no options in the VAMC System dropdown. Because of that, they can not create the service.
## To Reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
## AC / Expected behavior
An editor of a given system, including Lovell, should be able to create or edit a VAMC System Health Service, including choosing the appropriate VAMC System from the VAMC System dropdown.
## QA Steps
### As a Lovell Editor
- Create a "VAMC System Health Service"
- Edit a "VAMC System Health Service"
### As a Non-Lovell Editor
- Create a "VAMC System Health Service"
- Edit a "VAMC System Health Service"
## Screenshots
If applicable, add screenshots to help explain your problem.
## Additional context
Add any other context about the problem here. Reach out to the Product Managers to determine if it should be escalated as critical (prevents users from accomplishing their work with no known workaround and needs to be addressed within 2 business days).
## Desktop (please complete the following information if relevant, or delete)
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
## Labels
(You can delete this section once it's complete)
- [x] Issue type (red) (defaults to "Defect")
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [x] CMS workstream (orange) (not needed for bug tickets)
- [ ] CMS-supported product (black)
### Team
Please check the team(s) that will do this work.
- [ ] `CMS Team`
- [ ] `Public Websites`
- [ ] `Facilities`
- [ ] `User support`
|
1.0
|
Lovell editors can not select a System when creating VAMC System Health Service - ## Describe the defect
When creating or editing a VAMC System Health Service, Lovell editors have no options in the VAMC System dropdown. Because of that, they can not create the service.
## To Reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
## AC / Expected behavior
An editor of a given system, including Lovell, should be able to create or edit a VAMC System Health Service, including choosing the appropriate VAMC System from the VAMC System dropdown.
## QA Steps
### As a Lovell Editor
- Create a "VAMC System Health Service"
- Edit a "VAMC System Health Service"
### As a Non-Lovell Editor
- Create a "VAMC System Health Service"
- Edit a "VAMC System Health Service"
## Screenshots
If applicable, add screenshots to help explain your problem.
## Additional context
Add any other context about the problem here. Reach out to the Product Managers to determine if it should be escalated as critical (prevents users from accomplishing their work with no known workaround and needs to be addressed within 2 business days).
## Desktop (please complete the following information if relevant, or delete)
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
## Labels
(You can delete this section once it's complete)
- [x] Issue type (red) (defaults to "Defect")
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [x] CMS workstream (orange) (not needed for bug tickets)
- [ ] CMS-supported product (black)
### Team
Please check the team(s) that will do this work.
- [ ] `CMS Team`
- [ ] `Public Websites`
- [ ] `Facilities`
- [ ] `User support`
|
non_test
|
lovell editors can not select a system when creating vamc system health service describe the defect when creating or editing a vamc system health service lovell editors have no options in the vamc system dropdown because of that they can not create the service to reproduce steps to reproduce the behavior go to click on scroll down to see error ac expected behavior an editor of a given system including lovell should be able to create or edit a vamc system health service including choosing the appropriate vamc system from the vamc system dropdown qa steps as a lovell editor create a vamc system health service edit a vamc system health service as a non lovell editor create a vamc system health service edit a vamc system health service screenshots if applicable add screenshots to help explain your problem additional context add any other context about the problem here reach out to the product managers to determine if it should be escalated as critical prevents users from accomplishing their work with no known workaround and needs to be addressed within business days desktop please complete the following information if relevant or delete os browser version labels you can delete this section once it s complete issue type red defaults to defect cms subsystem green cms practice area blue cms workstream orange not needed for bug tickets cms supported product black team please check the team s that will do this work cms team public websites facilities user support
| 0
|
123,076
| 4,856,839,146
|
IssuesEvent
|
2016-11-12 08:34:54
|
Samulus/uap
|
https://api.github.com/repos/Samulus/uap
|
closed
|
Modify src/taglist.py to use relative filepaths instead of absolute paths
|
med priority
|
It's a security problem and it's extraneous information that doesn't need to be sent to the client every time they request more data (wastes space).
|
1.0
|
Modify src/taglist.py to use relative filepaths instead of absolute paths - It's a security problem and it's extraneous information that doesn't need to be sent to the client every time they request more data (wastes space).
|
non_test
|
modify src taglist py to use relative filepaths instead of absolute paths it s a security problem and it s extraneous information that doesn t need to be sent to the client every time they request more data wastes space
| 0
|
59,954
| 17,023,298,366
|
IssuesEvent
|
2021-07-03 01:18:01
|
tomhughes/trac-tickets
|
https://api.github.com/repos/tomhughes/trac-tickets
|
closed
|
Compile error
|
Component: merkaartor Priority: major Resolution: fixed Type: defect
|
**[Submitted to the original trac issue database at 7.08pm, Saturday, 20th September 2008]**
Last week Merkaartor compiled correctly. But after an svn update I get this:
In file included from Map/RoadManipulations.cpp:11:
./PropertiesDock.h:12:42: error: Utils/ShortcutOverrideFilter.h: No such file or directory
In file included from Map/RoadManipulations.cpp:11:
./PropertiesDock.h:80: error: ISO C++ forbids declaration of ShortcutOverrideFilter with no type
./PropertiesDock.h:80: error: expected ; before * token
make: *** [tmp/obj_release/RoadManipulations.o] Error 1
I'm compiling with g++ (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8), qt-4.4.1-2.fc9.x86_64 on a Fedora Linux system. svn revision #10803
A make clean; make does not help either.
|
1.0
|
Compile error - **[Submitted to the original trac issue database at 7.08pm, Saturday, 20th September 2008]**
Last week Merkaartor compiled correctly. But after an svn update I get this:
In file included from Map/RoadManipulations.cpp:11:
./PropertiesDock.h:12:42: error: Utils/ShortcutOverrideFilter.h: No such file or directory
In file included from Map/RoadManipulations.cpp:11:
./PropertiesDock.h:80: error: ISO C++ forbids declaration of ShortcutOverrideFilter with no type
./PropertiesDock.h:80: error: expected ; before * token
make: *** [tmp/obj_release/RoadManipulations.o] Error 1
I'm compiling with g++ (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8), qt-4.4.1-2.fc9.x86_64 on a Fedora Linux system. svn revision #10803
A make clean; make does not help either.
|
non_test
|
compile error last week merkaartor compiled correctly but after an svn update i get this in file included from map roadmanipulations cpp propertiesdock h error utils shortcutoverridefilter h no such file or directory in file included from map roadmanipulations cpp propertiesdock h error iso c forbids declaration of shortcutoverridefilter with no type propertiesdock h error expected before token make error i m compiling with g gcc red hat qt on a fedora linux system svn revision a make clean make does not help either
| 0
|
579,397
| 17,190,702,548
|
IssuesEvent
|
2021-07-16 10:29:34
|
schemathesis/schemathesis
|
https://api.github.com/repos/schemathesis/schemathesis
|
closed
|
[FEATURE] Check non-string keys when links are looked up
|
Difficulty: Easy Priority: High Type: Enhancement
|
**Is your feature request related to a problem? Please describe.**
If the schema is loaded from a YAML file, then sometimes response statuses are not quoted and parsed as integers. In this case, Open API Links may not be found, as only stringified statuses are checked.
|
1.0
|
[FEATURE] Check non-string keys when links are looked up - **Is your feature request related to a problem? Please describe.**
If the schema is loaded from a YAML file, then sometimes response statuses are not quoted and parsed as integers. In this case, Open API Links may not be found, as only stringified statuses are checked.
|
non_test
|
check non string keys when links are looked up is your feature request related to a problem please describe if the schema is loaded from a yaml file then sometimes response statuses are not quoted and parsed as integers in this case open api links may not be found as only stringified statuses are checked
| 0
|
362,559
| 25,381,429,007
|
IssuesEvent
|
2022-11-21 17:52:32
|
dagger/dagger
|
https://api.github.com/repos/dagger/dagger
|
closed
|
docs.dagger.io/install sends to deprecated 0.2 docs
|
area/documentation
|
## Problem
When navigating to [https://docs.dagger.io/install](https://docs.dagger.io/install) I see the old 0.2 install docs, without context making that clear. There are 2 problems here:
* The URL doesn't have an ID so it implies that it's "mutable" and kept up-to-date
* Lack of context makes the confusion worse
## Solution
Reclaim "intuitive" URLs such as `/install` to always serve up-to-date contents; and/or add a banner on out-of-date content so that it's clear to the user.
|
1.0
|
docs.dagger.io/install sends to deprecated 0.2 docs - ## Problem
When navigating to [https://docs.dagger.io/install](https://docs.dagger.io/install) I see the old 0.2 install docs, without context making that clear. There are 2 problems here:
* The URL doesn't have an ID so it implies that it's "mutable" and kept up-to-date
* Lack of context makes the confusion worse
## Solution
Reclaim "intuitive" URLs such as `/install` to always serve up-to-date contents; and/or add a banner on out-of-date content so that it's clear to the user.
|
non_test
|
docs dagger io install sends to deprecated docs problem when navigating to i see the old install docs without context making that clear there are problems here the url doesn t have an id so it implies that it s mutable and kept up to date lack of context makes the confusion worse solution reclaim intuitive urls such as install to always serve up to date contents and or add a banner on out of date content so that it s clear to the user
| 0
|
826,893
| 31,717,006,094
|
IssuesEvent
|
2023-09-10 01:06:18
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
closed
|
Vertical tab drag and drop support for links
|
priority/P5 OS/Desktop feature/vertical-tabs
|
<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
yes i have searched for similar issues.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
ok!
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. hold a link
2. drag and try to drop link on vertical tab
## Actual result:
<!--Please add screenshots if needed-->
## Expected result:
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
very often // always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Desktop
Release Notes v1.57.62 (Sep 6, 2023)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
yes
- Can you reproduce this issue with the current release?
-yes
- Can you reproduce this issue with the beta channel?
yes
- Can you reproduce this issue with the nightly channel?
yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields?
- no
- Does the issue resolve itself when disabling Brave Rewards?
- no
- Is the issue reproducible on the latest version of Chrome?
no
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
The brave browser does not support drag and drop functionality on vertical tabs. However, Brave do have drag and drop support on horizontal tabs, which you can use to easily move links around.
If you would like to request drag and drop support for vertical tabs,
I am using garuda linux nightly build brave but vertical tabs drag and drop link doesn`t support on other build too .
```[tasklist]
### Tasks
```
|
1.0
|
Vertical tab drag and drop support for links - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
yes i have searched for similar issues.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
ok!
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. hold a link
2. drag and try to drop link on vertical tab
## Actual result:
<!--Please add screenshots if needed-->
## Expected result:
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
very often // always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Desktop
Release Notes v1.57.62 (Sep 6, 2023)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
yes
- Can you reproduce this issue with the current release?
-yes
- Can you reproduce this issue with the beta channel?
yes
- Can you reproduce this issue with the nightly channel?
yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields?
- no
- Does the issue resolve itself when disabling Brave Rewards?
- no
- Is the issue reproducible on the latest version of Chrome?
no
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
The brave browser does not support drag and drop functionality on vertical tabs. However, Brave do have drag and drop support on horizontal tabs, which you can use to easily move links around.
If you would like to request drag and drop support for vertical tabs,
I am using garuda linux nightly build brave but vertical tabs drag and drop link doesn`t support on other build too .
```[tasklist]
### Tasks
```
|
non_test
|
vertical tab drag and drop support for links have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue yes i have searched for similar issues please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description ok steps to reproduce hold a link drag and try to drop link on vertical tab actual result expected result reproduces how often very often always brave version brave version info desktop release notes sep version channel information yes can you reproduce this issue with the current release yes can you reproduce this issue with the beta channel yes can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields no does the issue resolve itself when disabling brave rewards no is the issue reproducible on the latest version of chrome no miscellaneous information the brave browser does not support drag and drop functionality on vertical tabs however brave do have drag and drop support on horizontal tabs which you can use to easily move links around if you would like to request drag and drop support for vertical tabs i am using garuda linux nightly build brave but vertical tabs drag and drop link doesn t support on other build too tasks
| 0
|
195,369
| 15,527,685,418
|
IssuesEvent
|
2021-03-13 07:18:40
|
SunnieShine/Sudoku
|
https://api.github.com/repos/SunnieShine/Sudoku
|
closed
|
Add more comments on step searchers
|
author TODOs documentation
|
I found that the logic for some step searchers are too difficult to understand and analyze. I'll append more comments on it to enhance the code readability.
|
1.0
|
Add more comments on step searchers - I found that the logic for some step searchers are too difficult to understand and analyze. I'll append more comments on it to enhance the code readability.
|
non_test
|
add more comments on step searchers i found that the logic for some step searchers are too difficult to understand and analyze i ll append more comments on it to enhance the code readability
| 0
|
341,533
| 30,591,103,664
|
IssuesEvent
|
2023-07-21 17:07:56
|
microsoft/vscode-python
|
https://api.github.com/repos/microsoft/vscode-python
|
opened
|
Skip test display correctly in test explorer
|
bug area-testing needs PR
|
given a file called skip_test_file_node.py that has raise SkipTest(".....") this should appear in the sidebar with no children. The bug is that currently it shows a "unittest" node that gives "loader" and other incorrect nodes below it.
<img width="555" alt="image" src="https://github.com/microsoft/vscode-python/assets/26030610/24f48265-b0ce-416e-a76d-d0d084800c8e">
This is wrong, thought I fixed it with but it is still persisting. https://github.com/microsoft/vscode-python/pull/21665
|
1.0
|
Skip test display correctly in test explorer - given a file called skip_test_file_node.py that has raise SkipTest(".....") this should appear in the sidebar with no children. The bug is that currently it shows a "unittest" node that gives "loader" and other incorrect nodes below it.
<img width="555" alt="image" src="https://github.com/microsoft/vscode-python/assets/26030610/24f48265-b0ce-416e-a76d-d0d084800c8e">
This is wrong, thought I fixed it with but it is still persisting. https://github.com/microsoft/vscode-python/pull/21665
|
test
|
skip test display correctly in test explorer given a file called skip test file node py that has raise skiptest this should appear in the sidebar with no children the bug is that currently it shows a unittest node that gives loader and other incorrect nodes below it img width alt image src this is wrong thought i fixed it with but it is still persisting
| 1
|
28,871
| 5,543,713,749
|
IssuesEvent
|
2017-03-22 17:30:47
|
fossasia/susper.com
|
https://api.github.com/repos/fossasia/susper.com
|
closed
|
About Page link not working
|
bug documentation enhancement
|
Clicking on About page gives a 404 Page not found error.
This bug was fixed earlier, but has funnily enough risen again. We can redirect the user to yacysearch about page, but from what we decided earlier, I think a new About page needs to be added for susper.
|
1.0
|
About Page link not working - Clicking on About page gives a 404 Page not found error.
This bug was fixed earlier, but has funnily enough risen again. We can redirect the user to yacysearch about page, but from what we decided earlier, I think a new About page needs to be added for susper.
|
non_test
|
about page link not working clicking on about page gives a page not found error this bug was fixed earlier but has funnily enough risen again we can redirect the user to yacysearch about page but from what we decided earlier i think a new about page needs to be added for susper
| 0
|
225,771
| 17,893,619,726
|
IssuesEvent
|
2021-09-08 05:01:47
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
[CI] LegacyGeoShapeIT testBulk failing
|
:Analytics/Geo >test-failure Team:Analytics
|
**Build scan:**
https://gradle-enterprise.elastic.co/s/6ld2i2ojixqfy/tests/:server:internalClusterTest/org.elasticsearch.search.geo.LegacyGeoShapeIT/testBulk
**Reproduction line:**
`./gradlew ':server:internalClusterTest' --tests "org.elasticsearch.search.geo.LegacyGeoShapeIT.testBulk" -Dtests.seed=AE5B9DCA21C1837A -Dtests.locale=hu -Dtests.timezone=NET -Druntime.java=11`
**Applicable branches:**
master
**Reproduces locally?:**
Yes
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.search.geo.LegacyGeoShapeIT&tests.test=testBulk
**Failure excerpt:**
```
org.elasticsearch.index.mapper.MapperParsingException: Failed to parse mapping: using deprecated parameters [strategy] in mapper [location] of type [geo_shape] is no longer allowed
at __randomizedtesting.SeedInfo.seed([AE5B9DCA21C1837A:F7EFCB215FA875D3]:0)
at org.elasticsearch.index.mapper.MapperService.parseMapping(MapperService.java:297)
at org.elasticsearch.index.mapper.MapperService.mergeAndApplyMappings(MapperService.java:275)
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:259)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.updateIndexMappingsAndBuildSortOrder(MetadataCreateIndexService.java:1006)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.lambda$applyCreateIndexWithTemporaryService$2(MetadataCreateIndexService.java:413)
at org.elasticsearch.indices.IndicesService.withTempIndexService(IndicesService.java:636)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexWithTemporaryService(MetadataCreateIndexService.java:411)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequestWithV1Templates(MetadataCreateIndexService.java:488)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:374)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:381)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService$1.execute(MetadataCreateIndexService.java:298)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:48)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:745)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:361)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:224)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:161)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:139)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:177)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:678)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:259)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:222)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalArgumentException: using deprecated parameters [strategy] in mapper [location] of type [geo_shape] is no longer allowed
at org.elasticsearch.index.mapper.GeoShapeFieldMapper.lambda$static$0(GeoShapeFieldMapper.java:157)
at org.elasticsearch.index.mapper.ObjectMapper$TypeParser.parseProperties(ObjectMapper.java:203)
at org.elasticsearch.index.mapper.ObjectMapper$TypeParser.parseObjectOrDocumentTypeProperties(ObjectMapper.java:153)
at org.elasticsearch.index.mapper.RootObjectMapper$TypeParser.parse(RootObjectMapper.java:149)
at org.elasticsearch.index.mapper.MappingParser.parse(MappingParser.java:98)
at org.elasticsearch.index.mapper.MappingParser.parse(MappingParser.java:92)
at org.elasticsearch.index.mapper.MapperService.parseMapping(MapperService.java:295)
at org.elasticsearch.index.mapper.MapperService.mergeAndApplyMappings(MapperService.java:275)
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:259)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.updateIndexMappingsAndBuildSortOrder(MetadataCreateIndexService.java:1006)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.lambda$applyCreateIndexWithTemporaryService$2(MetadataCreateIndexService.java:413)
at org.elasticsearch.indices.IndicesService.withTempIndexService(IndicesService.java:636)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexWithTemporaryService(MetadataCreateIndexService.java:411)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequestWithV1Templates(MetadataCreateIndexService.java:488)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:374)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:381)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService$1.execute(MetadataCreateIndexService.java:298)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:48)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:745)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:361)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:224)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:161)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:139)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:177)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:678)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:259)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:222)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:834)
```
|
1.0
|
[CI] LegacyGeoShapeIT testBulk failing - **Build scan:**
https://gradle-enterprise.elastic.co/s/6ld2i2ojixqfy/tests/:server:internalClusterTest/org.elasticsearch.search.geo.LegacyGeoShapeIT/testBulk
**Reproduction line:**
`./gradlew ':server:internalClusterTest' --tests "org.elasticsearch.search.geo.LegacyGeoShapeIT.testBulk" -Dtests.seed=AE5B9DCA21C1837A -Dtests.locale=hu -Dtests.timezone=NET -Druntime.java=11`
**Applicable branches:**
master
**Reproduces locally?:**
Yes
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.search.geo.LegacyGeoShapeIT&tests.test=testBulk
**Failure excerpt:**
```
org.elasticsearch.index.mapper.MapperParsingException: Failed to parse mapping: using deprecated parameters [strategy] in mapper [location] of type [geo_shape] is no longer allowed
at __randomizedtesting.SeedInfo.seed([AE5B9DCA21C1837A:F7EFCB215FA875D3]:0)
at org.elasticsearch.index.mapper.MapperService.parseMapping(MapperService.java:297)
at org.elasticsearch.index.mapper.MapperService.mergeAndApplyMappings(MapperService.java:275)
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:259)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.updateIndexMappingsAndBuildSortOrder(MetadataCreateIndexService.java:1006)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.lambda$applyCreateIndexWithTemporaryService$2(MetadataCreateIndexService.java:413)
at org.elasticsearch.indices.IndicesService.withTempIndexService(IndicesService.java:636)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexWithTemporaryService(MetadataCreateIndexService.java:411)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequestWithV1Templates(MetadataCreateIndexService.java:488)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:374)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:381)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService$1.execute(MetadataCreateIndexService.java:298)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:48)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:745)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:361)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:224)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:161)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:139)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:177)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:678)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:259)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:222)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalArgumentException: using deprecated parameters [strategy] in mapper [location] of type [geo_shape] is no longer allowed
at org.elasticsearch.index.mapper.GeoShapeFieldMapper.lambda$static$0(GeoShapeFieldMapper.java:157)
at org.elasticsearch.index.mapper.ObjectMapper$TypeParser.parseProperties(ObjectMapper.java:203)
at org.elasticsearch.index.mapper.ObjectMapper$TypeParser.parseObjectOrDocumentTypeProperties(ObjectMapper.java:153)
at org.elasticsearch.index.mapper.RootObjectMapper$TypeParser.parse(RootObjectMapper.java:149)
at org.elasticsearch.index.mapper.MappingParser.parse(MappingParser.java:98)
at org.elasticsearch.index.mapper.MappingParser.parse(MappingParser.java:92)
at org.elasticsearch.index.mapper.MapperService.parseMapping(MapperService.java:295)
at org.elasticsearch.index.mapper.MapperService.mergeAndApplyMappings(MapperService.java:275)
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:259)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.updateIndexMappingsAndBuildSortOrder(MetadataCreateIndexService.java:1006)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.lambda$applyCreateIndexWithTemporaryService$2(MetadataCreateIndexService.java:413)
at org.elasticsearch.indices.IndicesService.withTempIndexService(IndicesService.java:636)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexWithTemporaryService(MetadataCreateIndexService.java:411)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequestWithV1Templates(MetadataCreateIndexService.java:488)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:374)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.applyCreateIndexRequest(MetadataCreateIndexService.java:381)
at org.elasticsearch.cluster.metadata.MetadataCreateIndexService$1.execute(MetadataCreateIndexService.java:298)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:48)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:745)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:361)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:224)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:161)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:139)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:177)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:678)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:259)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:222)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:834)
```
|
test
|
legacygeoshapeit testbulk failing build scan reproduction line gradlew server internalclustertest tests org elasticsearch search geo legacygeoshapeit testbulk dtests seed dtests locale hu dtests timezone net druntime java applicable branches master reproduces locally yes failure history failure excerpt org elasticsearch index mapper mapperparsingexception failed to parse mapping using deprecated parameters in mapper of type is no longer allowed at randomizedtesting seedinfo seed at org elasticsearch index mapper mapperservice parsemapping mapperservice java at org elasticsearch index mapper mapperservice mergeandapplymappings mapperservice java at org elasticsearch index mapper mapperservice merge mapperservice java at org elasticsearch cluster metadata metadatacreateindexservice updateindexmappingsandbuildsortorder metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice lambda applycreateindexwithtemporaryservice metadatacreateindexservice java at org elasticsearch indices indicesservice withtempindexservice indicesservice java at org elasticsearch cluster metadata metadatacreateindexservice applycreateindexwithtemporaryservice metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice applycreateindexrequest metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice applycreateindexrequest metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice execute metadatacreateindexservice java at org elasticsearch cluster clusterstateupdatetask execute clusterstateupdatetask java at org elasticsearch cluster service masterservice executetasks masterservice java at org elasticsearch cluster service masterservice calculatetaskoutputs masterservice java at org elasticsearch cluster service masterservice runtasks masterservice java at org elasticsearch cluster service masterservice batcher run masterservice java at org elasticsearch cluster service taskbatcher runifnotprocessed taskbatcher java at org elasticsearch cluster service taskbatcher batchedtask run taskbatcher java at org elasticsearch common util concurrent threadcontext contextpreservingrunnable run threadcontext java at org elasticsearch common util concurrent prioritizedesthreadpoolexecutor tiebreakingprioritizedrunnable runandclean prioritizedesthreadpoolexecutor java at org elasticsearch common util concurrent prioritizedesthreadpoolexecutor tiebreakingprioritizedrunnable run prioritizedesthreadpoolexecutor java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java caused by java lang illegalargumentexception using deprecated parameters in mapper of type is no longer allowed at org elasticsearch index mapper geoshapefieldmapper lambda static geoshapefieldmapper java at org elasticsearch index mapper objectmapper typeparser parseproperties objectmapper java at org elasticsearch index mapper objectmapper typeparser parseobjectordocumenttypeproperties objectmapper java at org elasticsearch index mapper rootobjectmapper typeparser parse rootobjectmapper java at org elasticsearch index mapper mappingparser parse mappingparser java at org elasticsearch index mapper mappingparser parse mappingparser java at org elasticsearch index mapper mapperservice parsemapping mapperservice java at org elasticsearch index mapper mapperservice mergeandapplymappings mapperservice java at org elasticsearch index mapper mapperservice merge mapperservice java at org elasticsearch cluster metadata metadatacreateindexservice updateindexmappingsandbuildsortorder metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice lambda applycreateindexwithtemporaryservice metadatacreateindexservice java at org elasticsearch indices indicesservice withtempindexservice indicesservice java at org elasticsearch cluster metadata metadatacreateindexservice applycreateindexwithtemporaryservice metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice applycreateindexrequest metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice applycreateindexrequest metadatacreateindexservice java at org elasticsearch cluster metadata metadatacreateindexservice execute metadatacreateindexservice java at org elasticsearch cluster clusterstateupdatetask execute clusterstateupdatetask java at org elasticsearch cluster service masterservice executetasks masterservice java at org elasticsearch cluster service masterservice calculatetaskoutputs masterservice java at org elasticsearch cluster service masterservice runtasks masterservice java at org elasticsearch cluster service masterservice batcher run masterservice java at org elasticsearch cluster service taskbatcher runifnotprocessed taskbatcher java at org elasticsearch cluster service taskbatcher batchedtask run taskbatcher java at org elasticsearch common util concurrent threadcontext contextpreservingrunnable run threadcontext java at org elasticsearch common util concurrent prioritizedesthreadpoolexecutor tiebreakingprioritizedrunnable runandclean prioritizedesthreadpoolexecutor java at org elasticsearch common util concurrent prioritizedesthreadpoolexecutor tiebreakingprioritizedrunnable run prioritizedesthreadpoolexecutor java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java
| 1
|
323,441
| 9,854,785,772
|
IssuesEvent
|
2019-06-19 17:43:27
|
bit-bots/bitbots_vision
|
https://api.github.com/repos/bit-bots/bitbots_vision
|
closed
|
Arguments for basler/logitech camera
|
high priority
|
Add arguments like `basler:=true` and `logitech:=true` to the vision launch file
|
1.0
|
Arguments for basler/logitech camera - Add arguments like `basler:=true` and `logitech:=true` to the vision launch file
|
non_test
|
arguments for basler logitech camera add arguments like basler true and logitech true to the vision launch file
| 0
|
44,523
| 5,843,024,103
|
IssuesEvent
|
2017-05-10 08:04:53
|
JoshuaBThompson/JEM
|
https://api.github.com/repos/JoshuaBThompson/JEM
|
opened
|
Design: Finish schematic and layout
|
design electrical
|
For JEM-1 finish the schematic and layout based on electrical requirements.
**JEM-1 Electronics Block Diagram**
|
1.0
|
Design: Finish schematic and layout - For JEM-1 finish the schematic and layout based on electrical requirements.
**JEM-1 Electronics Block Diagram**
|
non_test
|
design finish schematic and layout for jem finish the schematic and layout based on electrical requirements jem electronics block diagram
| 0
|
6,094
| 2,610,220,939
|
IssuesEvent
|
2015-02-26 19:10:08
|
chrsmith/somefinders
|
https://api.github.com/repos/chrsmith/somefinders
|
opened
|
opngl32 dll
|
auto-migrated Priority-Medium Type-Defect
|
```
'''Георгий Якушев'''
День добрый никак не могу найти .opngl32 dll. где
то видел уже
'''Арий Романов'''
Качай тут http://bit.ly/17vpfRU
'''Боеслав Бирюков'''
Просит ввести номер мобилы!Не опасно ли это?
'''Виктор Иванов'''
Неа все ок у меня ничего не списало
'''Владлен Бирюков'''
Не это не влияет на баланс
Информация о файле: opngl32 dll
Загружен: В этом месяце
Скачан раз: 1400
Рейтинг: 375
Средняя скорость скачивания: 294
Похожих файлов: 30
```
-----
Original issue reported on code.google.com by `kondense...@gmail.com` on 17 Dec 2013 at 8:50
|
1.0
|
opngl32 dll - ```
'''Георгий Якушев'''
День добрый никак не могу найти .opngl32 dll. где
то видел уже
'''Арий Романов'''
Качай тут http://bit.ly/17vpfRU
'''Боеслав Бирюков'''
Просит ввести номер мобилы!Не опасно ли это?
'''Виктор Иванов'''
Неа все ок у меня ничего не списало
'''Владлен Бирюков'''
Не это не влияет на баланс
Информация о файле: opngl32 dll
Загружен: В этом месяце
Скачан раз: 1400
Рейтинг: 375
Средняя скорость скачивания: 294
Похожих файлов: 30
```
-----
Original issue reported on code.google.com by `kondense...@gmail.com` on 17 Dec 2013 at 8:50
|
non_test
|
dll георгий якушев день добрый никак не могу найти dll где то видел уже арий романов качай тут боеслав бирюков просит ввести номер мобилы не опасно ли это виктор иванов неа все ок у меня ничего не списало владлен бирюков не это не влияет на баланс информация о файле dll загружен в этом месяце скачан раз рейтинг средняя скорость скачивания похожих файлов original issue reported on code google com by kondense gmail com on dec at
| 0
|
205,262
| 15,602,850,129
|
IssuesEvent
|
2021-03-19 00:40:51
|
MinaProtocol/mina
|
https://api.github.com/repos/MinaProtocol/mina
|
closed
|
Kademlia-half of net DHT changes
|
consider-for-closing planning-for-testnet
|
Should we choose to stick with the Haskell kademlia implementation. Address all the TODOs in Main.hs
|
1.0
|
Kademlia-half of net DHT changes - Should we choose to stick with the Haskell kademlia implementation. Address all the TODOs in Main.hs
|
test
|
kademlia half of net dht changes should we choose to stick with the haskell kademlia implementation address all the todos in main hs
| 1
|
342,426
| 30,621,693,373
|
IssuesEvent
|
2023-07-24 08:42:53
|
unifyai/ivy
|
https://api.github.com/repos/unifyai/ivy
|
closed
|
Fix jax_numpy_searching_sorting.test_jax_sort_complex
|
JAX Frontend Sub Task Failing Test
|
| | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|
1.0
|
Fix jax_numpy_searching_sorting.test_jax_sort_complex - | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5548508539/jobs/10131563553"><img src=https://img.shields.io/badge/-success-success></a>
|
test
|
fix jax numpy searching sorting test jax sort complex numpy a href src jax a href src tensorflow a href src torch a href src paddle a href src
| 1
|
268,909
| 23,403,764,041
|
IssuesEvent
|
2022-08-12 10:39:18
|
wazuh/wazuh-qa
|
https://api.github.com/repos/wazuh/wazuh-qa
|
closed
|
QA testing - Avoid errno value in unit tests
|
team/qa subteam/qa-storm type/qa-testing target/4.3.7
|
| Target version | Related issue | Related PR |
|--------------------|--------------------|-----------------|
| 4.3.7 | https://github.com/wazuh/wazuh/issues/14502 | https://github.com/wazuh/wazuh/pull/14518 |
<!-- Important: No section may be left blank. If not, delete it directly (in principle only Steps to reproduce could be left blank in case of not proceeding, although there are always exceptions). -->
## Description
This PR aims to fix a set of failure results reported by the unit tests.
## Proposed checks
- [x] Check that Jenkins ran the unit tests for PR https://github.com/wazuh/wazuh/pull/14518 successfully:
<!-- Indicate through a list of checkboxes the suggested checks to be carried out by the QA tester -->
- [x] Run CMocka unit tests for server.
- [x] Run CMocka unit tests for the UNIX agent.
- [x] Run CMocka unit tests for the Windows agent.
## Steps to reproduce
The problem appeared intermitently.
## Expected results
Tests must pass.
|
1.0
|
QA testing - Avoid errno value in unit tests - | Target version | Related issue | Related PR |
|--------------------|--------------------|-----------------|
| 4.3.7 | https://github.com/wazuh/wazuh/issues/14502 | https://github.com/wazuh/wazuh/pull/14518 |
<!-- Important: No section may be left blank. If not, delete it directly (in principle only Steps to reproduce could be left blank in case of not proceeding, although there are always exceptions). -->
## Description
This PR aims to fix a set of failure results reported by the unit tests.
## Proposed checks
- [x] Check that Jenkins ran the unit tests for PR https://github.com/wazuh/wazuh/pull/14518 successfully:
<!-- Indicate through a list of checkboxes the suggested checks to be carried out by the QA tester -->
- [x] Run CMocka unit tests for server.
- [x] Run CMocka unit tests for the UNIX agent.
- [x] Run CMocka unit tests for the Windows agent.
## Steps to reproduce
The problem appeared intermitently.
## Expected results
Tests must pass.
|
test
|
qa testing avoid errno value in unit tests target version related issue related pr description this pr aims to fix a set of failure results reported by the unit tests proposed checks check that jenkins ran the unit tests for pr successfully run cmocka unit tests for server run cmocka unit tests for the unix agent run cmocka unit tests for the windows agent steps to reproduce the problem appeared intermitently expected results tests must pass
| 1
|
57,501
| 7,064,060,578
|
IssuesEvent
|
2018-01-06 01:38:06
|
Microsoft/TypeScript
|
https://api.github.com/repos/Microsoft/TypeScript
|
closed
|
Definite assignment for exhaustive switch statements.
|
Design Limitation
|
Consider the following code
```ts
function test4(value: 1 | 2) {
let x: string;
switch (value) {
case 1: x = "one"; break;
case 2: x = "two"; break;
}
return x; //There is no path through the switch so x is alwayes assigned here.
}
```
**Expected behavior:**
The code should type check under --strict
**Actual behavior:**
Definite assignment does not realize that the switch is exhaustive and that all paths assign to x, so we get an error.
Checked with 2143a3f439aea887b2078e21e7585e4fa712f5fa
|
1.0
|
Definite assignment for exhaustive switch statements. - Consider the following code
```ts
function test4(value: 1 | 2) {
let x: string;
switch (value) {
case 1: x = "one"; break;
case 2: x = "two"; break;
}
return x; //There is no path through the switch so x is alwayes assigned here.
}
```
**Expected behavior:**
The code should type check under --strict
**Actual behavior:**
Definite assignment does not realize that the switch is exhaustive and that all paths assign to x, so we get an error.
Checked with 2143a3f439aea887b2078e21e7585e4fa712f5fa
|
non_test
|
definite assignment for exhaustive switch statements consider the following code ts function value let x string switch value case x one break case x two break return x there is no path through the switch so x is alwayes assigned here expected behavior the code should type check under strict actual behavior definite assignment does not realize that the switch is exhaustive and that all paths assign to x so we get an error checked with
| 0
|
2,703
| 2,532,561,475
|
IssuesEvent
|
2015-01-23 16:53:31
|
Esri/geoform-template-js
|
https://api.github.com/repos/Esri/geoform-template-js
|
closed
|
Viewer About text
|
bug high priority
|
The about text should pull from the webmap description, not have text in the NLS file
|
1.0
|
Viewer About text - The about text should pull from the webmap description, not have text in the NLS file
|
non_test
|
viewer about text the about text should pull from the webmap description not have text in the nls file
| 0
|
346,737
| 31,019,214,253
|
IssuesEvent
|
2023-08-10 02:54:13
|
wazuh/wazuh-qa
|
https://api.github.com/repos/wazuh/wazuh-qa
|
closed
|
Update test_agent_database_version test
|
level/task type/test
|
| Target version | Related issue | Related PR/dev branch |
|--------------------|--------------------|-----------------|
| 4.7 | https://github.com/wazuh/wazuh/issues/5443 | https://github.com/wazuh/wazuh/pull/17982 |
<!-- Important: No section may be left blank. If not, delete it directly (in principle only "Configurations" and "Considerations" could be left blank in case of not proceeding). -->
## Description
<!-- Description that puts into context and shows the QA tester the changes that have been implemented and have to be tested. -->
We need to update the Wazuh db test due to a schema upgrade to version 12
|
1.0
|
Update test_agent_database_version test - | Target version | Related issue | Related PR/dev branch |
|--------------------|--------------------|-----------------|
| 4.7 | https://github.com/wazuh/wazuh/issues/5443 | https://github.com/wazuh/wazuh/pull/17982 |
<!-- Important: No section may be left blank. If not, delete it directly (in principle only "Configurations" and "Considerations" could be left blank in case of not proceeding). -->
## Description
<!-- Description that puts into context and shows the QA tester the changes that have been implemented and have to be tested. -->
We need to update the Wazuh db test due to a schema upgrade to version 12
|
test
|
update test agent database version test target version related issue related pr dev branch description we need to update the wazuh db test due to a schema upgrade to version
| 1
|
59,209
| 6,635,962,341
|
IssuesEvent
|
2017-09-26 01:58:15
|
ngageoint/hootenanny
|
https://api.github.com/repos/ngageoint/hootenanny
|
opened
|
Successful Jenkins builds hiding errors
|
Category: Core Category: Test Priority: Low Status: In Progress Type: Bug
|
Just saw a Jenkins build that was successful that had the following at the bottom of console output. It needs to be fixed by updating the `HootApiDbWriter::finalizePartial()` function.
```
terminateHandler caught unhandled exception. what(): Tried to commit but weren't in a transaction. You may need to set hootapi.db.writer.create.user=true.
stack trace:
hoot::SignalCatcher::terminateHandler() +0x84
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5e6d6
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5d799
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gxx_personality_v0()+0x52a
/lib/x86_64-linux-gnu/libgcc_s.so.1 : ()+0xffd3
/lib/x86_64-linux-gnu/libgcc_s.so.1 : _Unwind_Resume()+0x57
hoot::HootApiDbWriter::~HootApiDbWriter() +0x273
hoot::DeleteMapCmd::runSimple(QStringList) +0x274
hoot::BaseCommand::run(char**, int) +0x18e
/home/vagrant/hoot/bin/hoot.bin : main()+0x28d
/lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xf5
/home/vagrant/hoot/bin/hoot.bin() [0x404514]
Error: signal 6:
stack trace:
hoot::SignalCatcher::default_handler(int) +0x2d
/lib/x86_64-linux-gnu/libc.so.6 : ()+0x36cb0
/lib/x86_64-linux-gnu/libc.so.6 : gsignal()+0x37
/lib/x86_64-linux-gnu/libc.so.6 : abort()+0x148
hoot::SignalCatcher::terminateHandler() +0x91
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5e6d6
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5d799
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gxx_personality_v0()+0x52a
/lib/x86_64-linux-gnu/libgcc_s.so.1 : ()+0xffd3
/lib/x86_64-linux-gnu/libgcc_s.so.1 : _Unwind_Resume()+0x57
hoot::HootApiDbWriter::~HootApiDbWriter() +0x273
hoot::DeleteMapCmd::runSimple(QStringList) +0x274
hoot::BaseCommand::run(char**, int) +0x18e
/home/vagrant/hoot/bin/hoot.bin : main()+0x28d
/lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xf5
/home/vagrant/hoot/bin/hoot.bin() [0x404514]
```
|
1.0
|
Successful Jenkins builds hiding errors - Just saw a Jenkins build that was successful that had the following at the bottom of console output. It needs to be fixed by updating the `HootApiDbWriter::finalizePartial()` function.
```
terminateHandler caught unhandled exception. what(): Tried to commit but weren't in a transaction. You may need to set hootapi.db.writer.create.user=true.
stack trace:
hoot::SignalCatcher::terminateHandler() +0x84
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5e6d6
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5d799
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gxx_personality_v0()+0x52a
/lib/x86_64-linux-gnu/libgcc_s.so.1 : ()+0xffd3
/lib/x86_64-linux-gnu/libgcc_s.so.1 : _Unwind_Resume()+0x57
hoot::HootApiDbWriter::~HootApiDbWriter() +0x273
hoot::DeleteMapCmd::runSimple(QStringList) +0x274
hoot::BaseCommand::run(char**, int) +0x18e
/home/vagrant/hoot/bin/hoot.bin : main()+0x28d
/lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xf5
/home/vagrant/hoot/bin/hoot.bin() [0x404514]
Error: signal 6:
stack trace:
hoot::SignalCatcher::default_handler(int) +0x2d
/lib/x86_64-linux-gnu/libc.so.6 : ()+0x36cb0
/lib/x86_64-linux-gnu/libc.so.6 : gsignal()+0x37
/lib/x86_64-linux-gnu/libc.so.6 : abort()+0x148
hoot::SignalCatcher::terminateHandler() +0x91
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5e6d6
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x5d799
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gxx_personality_v0()+0x52a
/lib/x86_64-linux-gnu/libgcc_s.so.1 : ()+0xffd3
/lib/x86_64-linux-gnu/libgcc_s.so.1 : _Unwind_Resume()+0x57
hoot::HootApiDbWriter::~HootApiDbWriter() +0x273
hoot::DeleteMapCmd::runSimple(QStringList) +0x274
hoot::BaseCommand::run(char**, int) +0x18e
/home/vagrant/hoot/bin/hoot.bin : main()+0x28d
/lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xf5
/home/vagrant/hoot/bin/hoot.bin() [0x404514]
```
|
test
|
successful jenkins builds hiding errors just saw a jenkins build that was successful that had the following at the bottom of console output it needs to be fixed by updating the hootapidbwriter finalizepartial function terminatehandler caught unhandled exception what tried to commit but weren t in a transaction you may need to set hootapi db writer create user true stack trace hoot signalcatcher terminatehandler usr lib linux gnu libstdc so usr lib linux gnu libstdc so usr lib linux gnu libstdc so gxx personality lib linux gnu libgcc s so lib linux gnu libgcc s so unwind resume hoot hootapidbwriter hootapidbwriter hoot deletemapcmd runsimple qstringlist hoot basecommand run char int home vagrant hoot bin hoot bin main lib linux gnu libc so libc start main home vagrant hoot bin hoot bin error signal stack trace hoot signalcatcher default handler int lib linux gnu libc so lib linux gnu libc so gsignal lib linux gnu libc so abort hoot signalcatcher terminatehandler usr lib linux gnu libstdc so usr lib linux gnu libstdc so usr lib linux gnu libstdc so gxx personality lib linux gnu libgcc s so lib linux gnu libgcc s so unwind resume hoot hootapidbwriter hootapidbwriter hoot deletemapcmd runsimple qstringlist hoot basecommand run char int home vagrant hoot bin hoot bin main lib linux gnu libc so libc start main home vagrant hoot bin hoot bin
| 1
|
100,140
| 21,177,326,881
|
IssuesEvent
|
2022-04-08 02:21:12
|
ASE-Projekte-WS-2021/ase-ws-21-konferenzassistent
|
https://api.github.com/repos/ASE-Projekte-WS-2021/ase-ws-21-konferenzassistent
|
closed
|
Klasse "Meetings" obsolet
|
code quality
|
Durch Tobias Implementation der Room Datenbanken haben wir im Endeffekt die gleiche Klasse zwei Mal:
https://github.com/ASE-Projekte-WS-2021/ase-ws-21-konferenzassistent/blob/dev/app/src/main/java/com/example/myapplication/Meeting.java
https://github.com/ASE-Projekte-WS-2021/ase-ws-21-konferenzassistent/blob/dev/app/src/main/java/com/example/myapplication/data/MeetingData.java
Theoretisch könnten wir eigentlich dann Codeblöcke wie diesen im `HomeFragment.java`...
```
meetingsList = new ArrayList<>();
List<MeetingParticipantPair> d = database.meetingWithParticipantDao().getMeetings();
d.forEach(data ->{
meetingsList.add(new Meeting(
"" +data.getMeeting().getID(),
data.getMeeting().getStartDate(),
data.getMeeting().getEndDate(),
data.getMeeting().getLocation(),
data.getMeeting().getTitle(),
"" + data.getMeeting().getDuration(),
"" +data.getParticipants().size()));
});
```
... einfach hiermit ersetzen können:
```
meetingsList = database.meetingDao().getAll();
```
Müssten halt gucken, so überall die `Meetings` Klasse bzw. erzeugte Instanzen zum Einsatz kommen.
Spontan erkenne ich nur, dass man eine Lösung für die Teilnehmeranzahl bräuchte.
|
1.0
|
Klasse "Meetings" obsolet - Durch Tobias Implementation der Room Datenbanken haben wir im Endeffekt die gleiche Klasse zwei Mal:
https://github.com/ASE-Projekte-WS-2021/ase-ws-21-konferenzassistent/blob/dev/app/src/main/java/com/example/myapplication/Meeting.java
https://github.com/ASE-Projekte-WS-2021/ase-ws-21-konferenzassistent/blob/dev/app/src/main/java/com/example/myapplication/data/MeetingData.java
Theoretisch könnten wir eigentlich dann Codeblöcke wie diesen im `HomeFragment.java`...
```
meetingsList = new ArrayList<>();
List<MeetingParticipantPair> d = database.meetingWithParticipantDao().getMeetings();
d.forEach(data ->{
meetingsList.add(new Meeting(
"" +data.getMeeting().getID(),
data.getMeeting().getStartDate(),
data.getMeeting().getEndDate(),
data.getMeeting().getLocation(),
data.getMeeting().getTitle(),
"" + data.getMeeting().getDuration(),
"" +data.getParticipants().size()));
});
```
... einfach hiermit ersetzen können:
```
meetingsList = database.meetingDao().getAll();
```
Müssten halt gucken, so überall die `Meetings` Klasse bzw. erzeugte Instanzen zum Einsatz kommen.
Spontan erkenne ich nur, dass man eine Lösung für die Teilnehmeranzahl bräuchte.
|
non_test
|
klasse meetings obsolet durch tobias implementation der room datenbanken haben wir im endeffekt die gleiche klasse zwei mal theoretisch könnten wir eigentlich dann codeblöcke wie diesen im homefragment java meetingslist new arraylist list d database meetingwithparticipantdao getmeetings d foreach data meetingslist add new meeting data getmeeting getid data getmeeting getstartdate data getmeeting getenddate data getmeeting getlocation data getmeeting gettitle data getmeeting getduration data getparticipants size einfach hiermit ersetzen können meetingslist database meetingdao getall müssten halt gucken so überall die meetings klasse bzw erzeugte instanzen zum einsatz kommen spontan erkenne ich nur dass man eine lösung für die teilnehmeranzahl bräuchte
| 0
|
137,045
| 11,097,159,738
|
IssuesEvent
|
2019-12-16 12:47:11
|
elastic/ml-cpp
|
https://api.github.com/repos/elastic/ml-cpp
|
opened
|
Test executable crashes when run under `Valgrind`
|
:ml >non-issue >test test-failure v7.6.0 v8.0.0
|
Output from `Valgrind` regarding the illegal instruction that led to the crash.
```
2019-12-13 13:57:59,742307 UTC [4656] DEBUG CTestObserver.cc@23 +-----------------------------------------------------+
2019-12-13 13:57:59,742946 UTC [4656] DEBUG CTestObserver.cc@24 | CJsonOutputStreamWrapperTest/testConcurrentWrites |
2019-12-13 13:57:59,743548 UTC [4656] DEBUG CTestObserver.cc@25 +-----------------------------------------------------+
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x63 0x0 0x10 0x83 0xF9
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F3A
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==4656== valgrind: Unrecognised instruction at address 0x23dd20.
==4656== Your program just tried to execute an instruction that Valgrind
==4656== did not recognise. There are two possible reasons for this.
==4656== 1. Your program has a bug and erroneously jumped to a non-code
==4656== location. If you are running Memcheck and you just saw a
==4656== warning about a bad jump, it's probably your program's fault.
==4656== 2. The instruction is legitimate but Valgrind doesn't handle it,
==4656== i.e. it's Valgrind's fault. If you think this is the case or
==4656== you are not sure, please let us know and we'll try to fix it.
==4656== Either way, Valgrind will now raise a SIGILL signal which will
==4656== probably kill your program.
si_signo 4, si_code: 1, si_errno: 0, address: 0x23dd20, library: ./ml_test, base: 0x108000, normalized address: 0x135d20
make[3]: *** [memcheck] Illegal instruction
make[3]: Leaving directory `/home/eds/src/ml-cpp/lib/core/unittest'
/home/eds/src/ml-cpp/lib/core make test FAILURE!!!
make[2]: *** [memcheck] Error 1
make[2]: Leaving directory `/home/eds/src/ml-cpp/lib/core'
make[1]: *** [memcheck] Error 1
make[1]: Leaving directory `/home/eds/src/ml-cpp/lib'
make: *** [memcheck] Error 1
real 64m10.560s
user 63m40.264s
sys 0m19.411s
```
|
2.0
|
Test executable crashes when run under `Valgrind` -
Output from `Valgrind` regarding the illegal instruction that led to the crash.
```
2019-12-13 13:57:59,742307 UTC [4656] DEBUG CTestObserver.cc@23 +-----------------------------------------------------+
2019-12-13 13:57:59,742946 UTC [4656] DEBUG CTestObserver.cc@24 | CJsonOutputStreamWrapperTest/testConcurrentWrites |
2019-12-13 13:57:59,743548 UTC [4656] DEBUG CTestObserver.cc@25 +-----------------------------------------------------+
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x63 0x0 0x10 0x83 0xF9
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F3A
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==4656== valgrind: Unrecognised instruction at address 0x23dd20.
==4656== Your program just tried to execute an instruction that Valgrind
==4656== did not recognise. There are two possible reasons for this.
==4656== 1. Your program has a bug and erroneously jumped to a non-code
==4656== location. If you are running Memcheck and you just saw a
==4656== warning about a bad jump, it's probably your program's fault.
==4656== 2. The instruction is legitimate but Valgrind doesn't handle it,
==4656== i.e. it's Valgrind's fault. If you think this is the case or
==4656== you are not sure, please let us know and we'll try to fix it.
==4656== Either way, Valgrind will now raise a SIGILL signal which will
==4656== probably kill your program.
si_signo 4, si_code: 1, si_errno: 0, address: 0x23dd20, library: ./ml_test, base: 0x108000, normalized address: 0x135d20
make[3]: *** [memcheck] Illegal instruction
make[3]: Leaving directory `/home/eds/src/ml-cpp/lib/core/unittest'
/home/eds/src/ml-cpp/lib/core make test FAILURE!!!
make[2]: *** [memcheck] Error 1
make[2]: Leaving directory `/home/eds/src/ml-cpp/lib/core'
make[1]: *** [memcheck] Error 1
make[1]: Leaving directory `/home/eds/src/ml-cpp/lib'
make: *** [memcheck] Error 1
real 64m10.560s
user 63m40.264s
sys 0m19.411s
```
|
test
|
test executable crashes when run under valgrind output from valgrind regarding the illegal instruction that led to the crash utc debug ctestobserver cc utc debug ctestobserver cc cjsonoutputstreamwrappertest testconcurrentwrites utc debug ctestobserver cc vex ir unhandled instruction bytes vex ir rex rex w rex r rex x rex b vex ir vex vex l vex nvvvv esc vex ir pfx pfx pfx valgrind unrecognised instruction at address your program just tried to execute an instruction that valgrind did not recognise there are two possible reasons for this your program has a bug and erroneously jumped to a non code location if you are running memcheck and you just saw a warning about a bad jump it s probably your program s fault the instruction is legitimate but valgrind doesn t handle it i e it s valgrind s fault if you think this is the case or you are not sure please let us know and we ll try to fix it either way valgrind will now raise a sigill signal which will probably kill your program si signo si code si errno address library ml test base normalized address make illegal instruction make leaving directory home eds src ml cpp lib core unittest home eds src ml cpp lib core make test failure make error make leaving directory home eds src ml cpp lib core make error make leaving directory home eds src ml cpp lib make error real user sys
| 1
|
26,049
| 19,595,913,156
|
IssuesEvent
|
2022-01-05 17:49:22
|
testomatio/app
|
https://api.github.com/repos/testomatio/app
|
closed
|
Self-hosted option
|
feature onboarding infrastructure
|
**[Self-hosted option #4](https://testomat.nolt.io/4)** by Mykhailo Poliarush <hr/> We need to meet security so we need testomat.io as self-hosted option
|
1.0
|
Self-hosted option - **[Self-hosted option #4](https://testomat.nolt.io/4)** by Mykhailo Poliarush <hr/> We need to meet security so we need testomat.io as self-hosted option
|
non_test
|
self hosted option by mykhailo poliarush we need to meet security so we need testomat io as self hosted option
| 0
|
52,273
| 7,756,678,191
|
IssuesEvent
|
2018-05-31 14:17:04
|
tsdservices/Gravity
|
https://api.github.com/repos/tsdservices/Gravity
|
opened
|
Create Roadmap
|
documentation
|
Detail which features are solid and have test coverage and where we want to head next.
|
1.0
|
Create Roadmap - Detail which features are solid and have test coverage and where we want to head next.
|
non_test
|
create roadmap detail which features are solid and have test coverage and where we want to head next
| 0
|
85,502
| 7,974,469,121
|
IssuesEvent
|
2018-07-17 05:43:04
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
testBuilderUsesDefaultSSLContext fails due to a wrong exception message
|
:Security/Network >test-failure jvm bug
|
This test failed today of the above test while running on java11, which may be relevant:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java11,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/168/console
```
16:26:03 FAILURE 0.58s J2 | RestClientBuilderIntegTests.testBuilderUsesDefaultSSLContext <<< FAILURES!
16:26:03 > Throwable #1: java.lang.AssertionError:
16:26:03 > Expected: a string containing "General SSLEngine problem"
16:26:03 > but: was "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"
16:26:03 > at __randomizedtesting.SeedInfo.seed([40A8A6346B9B56FA:78D0B8F8B871D88F]:0)
16:26:03 > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
16:26:03 > at org.elasticsearch.client.RestClientBuilderIntegTests.testBuilderUsesDefaultSSLContext(RestClientBuilderIntegTests.java:82)
16:26:03 > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
16:26:03 > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
16:26:03 > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
16:26:03 > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
16:26:03 > at java.base/java.lang.Thread.run(Thread.java:834)
```
|
1.0
|
testBuilderUsesDefaultSSLContext fails due to a wrong exception message - This test failed today of the above test while running on java11, which may be relevant:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java11,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/168/console
```
16:26:03 FAILURE 0.58s J2 | RestClientBuilderIntegTests.testBuilderUsesDefaultSSLContext <<< FAILURES!
16:26:03 > Throwable #1: java.lang.AssertionError:
16:26:03 > Expected: a string containing "General SSLEngine problem"
16:26:03 > but: was "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"
16:26:03 > at __randomizedtesting.SeedInfo.seed([40A8A6346B9B56FA:78D0B8F8B871D88F]:0)
16:26:03 > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
16:26:03 > at org.elasticsearch.client.RestClientBuilderIntegTests.testBuilderUsesDefaultSSLContext(RestClientBuilderIntegTests.java:82)
16:26:03 > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
16:26:03 > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
16:26:03 > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
16:26:03 > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
16:26:03 > at java.base/java.lang.Thread.run(Thread.java:834)
```
|
test
|
testbuilderusesdefaultsslcontext fails due to a wrong exception message this test failed today of the above test while running on which may be relevant failure restclientbuilderintegtests testbuilderusesdefaultsslcontext failures throwable java lang assertionerror expected a string containing general sslengine problem but was pkix path building failed sun security provider certpath suncertpathbuilderexception unable to find valid certification path to requested target at randomizedtesting seedinfo seed at org hamcrest matcherassert assertthat matcherassert java at org elasticsearch client restclientbuilderintegtests testbuilderusesdefaultsslcontext restclientbuilderintegtests java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at java base java lang thread run thread java
| 1
|
67,915
| 7,078,541,759
|
IssuesEvent
|
2018-01-10 04:37:24
|
learn-co-curriculum/javascript-intro-to-looping
|
https://api.github.com/repos/learn-co-curriculum/javascript-intro-to-looping
|
closed
|
#BacktoCode "Start a new streak tomorrow."
|
test
|
I received an email saying I missed today but I have been on since 6 PM PST coding. I was on yesterday around the same time and it counted. I have not missed a day since I began last week.
<img width="1035" alt="bootcampprepstreak" src="https://user-images.githubusercontent.com/16076097/34755965-764135c6-f57c-11e7-9677-a7c097cea702.png">
|
1.0
|
#BacktoCode "Start a new streak tomorrow." - I received an email saying I missed today but I have been on since 6 PM PST coding. I was on yesterday around the same time and it counted. I have not missed a day since I began last week.
<img width="1035" alt="bootcampprepstreak" src="https://user-images.githubusercontent.com/16076097/34755965-764135c6-f57c-11e7-9677-a7c097cea702.png">
|
test
|
backtocode start a new streak tomorrow i received an email saying i missed today but i have been on since pm pst coding i was on yesterday around the same time and it counted i have not missed a day since i began last week img width alt bootcampprepstreak src
| 1
|
129,336
| 10,570,554,196
|
IssuesEvent
|
2019-10-07 03:07:22
|
Ilysen/SLIssueTracker
|
https://api.github.com/repos/Ilysen/SLIssueTracker
|
closed
|
Example security vulnerability issue
|
$30 Bug Critical Priority Possibly Fixed - Test Reproducible
|
### Description
A clear and concise description of the bug. Be as specific as you can.
### Discovery
* **Testers:**
* **Time (include time zone - estimates are fine):**
### Game Version
Replace this section with the game version, if applicable.
### To Reproduce
If this issue can be consistently reproduced, describe how to cause the issue.
### Expected Behavior
If applicable, what is expected to happen?
### Media
Post any screenshots or video clips here.
|
1.0
|
Example security vulnerability issue - ### Description
A clear and concise description of the bug. Be as specific as you can.
### Discovery
* **Testers:**
* **Time (include time zone - estimates are fine):**
### Game Version
Replace this section with the game version, if applicable.
### To Reproduce
If this issue can be consistently reproduced, describe how to cause the issue.
### Expected Behavior
If applicable, what is expected to happen?
### Media
Post any screenshots or video clips here.
|
test
|
example security vulnerability issue description a clear and concise description of the bug be as specific as you can discovery testers time include time zone estimates are fine game version replace this section with the game version if applicable to reproduce if this issue can be consistently reproduced describe how to cause the issue expected behavior if applicable what is expected to happen media post any screenshots or video clips here
| 1
|
193,203
| 14,643,376,107
|
IssuesEvent
|
2020-12-25 16:07:59
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
uzyexe/cli: helpers_test.go; 8 LoC
|
fresh test tiny
|
Found a possible issue in [uzyexe/cli](https://www.github.com/uzyexe/cli) at [helpers_test.go](https://github.com/uzyexe/cli/blob/ae899f9445048a6d83dfc420ff9586bb88f4c03b/helpers_test.go#L223-L230)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to res is reassigned at line 225
[Click here to see the code in its original context.](https://github.com/uzyexe/cli/blob/ae899f9445048a6d83dfc420ff9586bb88f4c03b/helpers_test.go#L223-L230)
<details>
<summary>Click here to show the 8 line(s) of Go which triggered the analyzer.</summary>
```go
for _, res := range responses {
if r.URL.Path == res.path && r.Method == res.method {
response = &res
body = res.body
contentType = res.contentType
break
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: ae899f9445048a6d83dfc420ff9586bb88f4c03b
|
1.0
|
uzyexe/cli: helpers_test.go; 8 LoC -
Found a possible issue in [uzyexe/cli](https://www.github.com/uzyexe/cli) at [helpers_test.go](https://github.com/uzyexe/cli/blob/ae899f9445048a6d83dfc420ff9586bb88f4c03b/helpers_test.go#L223-L230)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to res is reassigned at line 225
[Click here to see the code in its original context.](https://github.com/uzyexe/cli/blob/ae899f9445048a6d83dfc420ff9586bb88f4c03b/helpers_test.go#L223-L230)
<details>
<summary>Click here to show the 8 line(s) of Go which triggered the analyzer.</summary>
```go
for _, res := range responses {
if r.URL.Path == res.path && r.Method == res.method {
response = &res
body = res.body
contentType = res.contentType
break
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: ae899f9445048a6d83dfc420ff9586bb88f4c03b
|
test
|
uzyexe cli helpers test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to res is reassigned at line click here to show the line s of go which triggered the analyzer go for res range responses if r url path res path r method res method response res body res body contenttype res contenttype break leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
317,406
| 27,235,686,872
|
IssuesEvent
|
2023-02-21 16:09:35
|
zeitgeistpm/ui
|
https://api.github.com/repos/zeitgeistpm/ui
|
closed
|
Remove cypress e2e test files
|
test
|
Move current e2e tests implemented in cypress to playwright (if possible) and remove cypress files, tests and configuration, afterwards.
|
1.0
|
Remove cypress e2e test files - Move current e2e tests implemented in cypress to playwright (if possible) and remove cypress files, tests and configuration, afterwards.
|
test
|
remove cypress test files move current tests implemented in cypress to playwright if possible and remove cypress files tests and configuration afterwards
| 1
|
324,983
| 27,836,983,470
|
IssuesEvent
|
2023-03-20 10:09:03
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
`search/380_sort_segments_on_timestamp` test from `RcsCcsCommonYamlTestSuiteIT ` fails on `main`
|
:Search/Search >test-failure Team:Search
|
### CI Link
https://gradle-enterprise.elastic.co/s/qiwxbw5bm67tg
### Repro line
```
REPRODUCE WITH: ./gradlew ':qa:ccs-common-rest:yamlRestTest' --tests "org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT.test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping}" \ -Dtests.seed=86C57DA037724F15 \ -Dtests.locale=en-CA \ -Dtests.timezone=Asia/Macau \ -Druntime.java=19
REPRODUCE WITH: ./gradlew ':qa:ccs-common-rest:yamlRestTest' --tests "org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT.test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping}" \ -Dtests.seed=86C57DA037724F15 \ -Dtests.locale=en-CA \ -Dtests.timezone=Asia/Macau \ -Druntime.java=19
```
### Does it reproduce?
Yes
### Applicable branches
main
### Failure history
_No response_
### Failure excerpt
```
09:22:48 REPRODUCE WITH: ./gradlew ':qa:ccs-common-rest:yamlRestTest' --tests "org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT.test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping}" -Dtests.seed=86C57DA037724F15 -Dtests.locale=en-CA -Dtests.timezone=Asia/Macau -Druntime.java=19
09:22:48
09:22:48 org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT > test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping} FAILED
09:22:48 java.lang.AssertionError: Failure at [search/380_sort_segments_on_timestamp:46]: Expected a list containing
09:22:48 0: expected "2021-08-02" but was "2021-08-01"
09:22:48 at __randomizedtesting.SeedInfo.seed([86C57DA037724F15:E91427A998E22ED]:0)
09:22:48 at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:547)
09:22:48 at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.test(ESClientYamlSuiteTestCase.java:499)
09:22:48 at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
09:22:48 at java.base/java.lang.reflect.Method.invoke(Method.java:578)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:48)
09:22:48 at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
09:22:48 at org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
09:22:48 at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
09:22:48 at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
09:22:48 at org.elasticsearch.test.cluster.local.LocalElasticsearchCluster$1.evaluate(LocalElasticsearchCluster.java:39)
09:22:48 at org.elasticsearch.test.cluster.local.LocalElasticsearchCluster$1.evaluate(LocalElasticsearchCluster.java:39)
09:22:48 at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
09:22:48 at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
09:22:48 at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
09:22:48 at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
09:22:48 at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
09:22:48 at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
09:22:48 at org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:850)
09:22:48 at java.base/java.lang.Thread.run(Thread.java:1589)
09:22:48
09:22:48 Caused by:
09:22:48 java.lang.AssertionError: Expected a list containing
09:22:48 0: expected "2021-08-02" but was "2021-08-01"
09:22:48 at org.elasticsearch.test.MapMatcher.assertMap(MapMatcher.java:82)
09:22:48 at org.elasticsearch.test.MapMatcher.assertMap(MapMatcher.java:65)
09:22:48 at org.elasticsearch.test.rest.yaml.section.MatchAssertion.doAssert(MatchAssertion.java:97)
09:22:48 at org.elasticsearch.test.rest.yaml.section.Assertion.execute(Assertion.java:65)
09:22:48 at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:527)
09:22:48 ... 39 more
09:22:49
```
|
1.0
|
`search/380_sort_segments_on_timestamp` test from `RcsCcsCommonYamlTestSuiteIT ` fails on `main` - ### CI Link
https://gradle-enterprise.elastic.co/s/qiwxbw5bm67tg
### Repro line
```
REPRODUCE WITH: ./gradlew ':qa:ccs-common-rest:yamlRestTest' --tests "org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT.test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping}" \ -Dtests.seed=86C57DA037724F15 \ -Dtests.locale=en-CA \ -Dtests.timezone=Asia/Macau \ -Druntime.java=19
REPRODUCE WITH: ./gradlew ':qa:ccs-common-rest:yamlRestTest' --tests "org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT.test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping}" \ -Dtests.seed=86C57DA037724F15 \ -Dtests.locale=en-CA \ -Dtests.timezone=Asia/Macau \ -Druntime.java=19
```
### Does it reproduce?
Yes
### Applicable branches
main
### Failure history
_No response_
### Failure excerpt
```
09:22:48 REPRODUCE WITH: ./gradlew ':qa:ccs-common-rest:yamlRestTest' --tests "org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT.test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping}" -Dtests.seed=86C57DA037724F15 -Dtests.locale=en-CA -Dtests.timezone=Asia/Macau -Druntime.java=19
09:22:48
09:22:48 org.elasticsearch.test.rest.yaml.RcsCcsCommonYamlTestSuiteIT > test {p0=search/380_sort_segments_on_timestamp/Test that index segments are sorted on timestamp field if @timestamp field is defined in mapping} FAILED
09:22:48 java.lang.AssertionError: Failure at [search/380_sort_segments_on_timestamp:46]: Expected a list containing
09:22:48 0: expected "2021-08-02" but was "2021-08-01"
09:22:48 at __randomizedtesting.SeedInfo.seed([86C57DA037724F15:E91427A998E22ED]:0)
09:22:48 at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:547)
09:22:48 at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.test(ESClientYamlSuiteTestCase.java:499)
09:22:48 at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
09:22:48 at java.base/java.lang.reflect.Method.invoke(Method.java:578)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:48)
09:22:48 at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
09:22:48 at org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
09:22:48 at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
09:22:48 at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
09:22:48 at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
09:22:48 at org.elasticsearch.test.cluster.local.LocalElasticsearchCluster$1.evaluate(LocalElasticsearchCluster.java:39)
09:22:48 at org.elasticsearch.test.cluster.local.LocalElasticsearchCluster$1.evaluate(LocalElasticsearchCluster.java:39)
09:22:48 at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
09:22:48 at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
09:22:48 at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
09:22:48 at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
09:22:48 at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
09:22:48 at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
09:22:48 at org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
09:22:48 at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
09:22:48 at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:850)
09:22:48 at java.base/java.lang.Thread.run(Thread.java:1589)
09:22:48
09:22:48 Caused by:
09:22:48 java.lang.AssertionError: Expected a list containing
09:22:48 0: expected "2021-08-02" but was "2021-08-01"
09:22:48 at org.elasticsearch.test.MapMatcher.assertMap(MapMatcher.java:82)
09:22:48 at org.elasticsearch.test.MapMatcher.assertMap(MapMatcher.java:65)
09:22:48 at org.elasticsearch.test.rest.yaml.section.MatchAssertion.doAssert(MatchAssertion.java:97)
09:22:48 at org.elasticsearch.test.rest.yaml.section.Assertion.execute(Assertion.java:65)
09:22:48 at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:527)
09:22:48 ... 39 more
09:22:49
```
|
test
|
search sort segments on timestamp test from rcsccscommonyamltestsuiteit fails on main ci link repro line reproduce with gradlew qa ccs common rest yamlresttest tests org elasticsearch test rest yaml rcsccscommonyamltestsuiteit test search sort segments on timestamp test that index segments are sorted on timestamp field if timestamp field is defined in mapping dtests seed dtests locale en ca dtests timezone asia macau druntime java reproduce with gradlew qa ccs common rest yamlresttest tests org elasticsearch test rest yaml rcsccscommonyamltestsuiteit test search sort segments on timestamp test that index segments are sorted on timestamp field if timestamp field is defined in mapping dtests seed dtests locale en ca dtests timezone asia macau druntime java does it reproduce yes applicable branches main failure history no response failure excerpt reproduce with gradlew qa ccs common rest yamlresttest tests org elasticsearch test rest yaml rcsccscommonyamltestsuiteit test search sort segments on timestamp test that index segments are sorted on timestamp field if timestamp field is defined in mapping dtests seed dtests locale en ca dtests timezone asia macau druntime java org elasticsearch test rest yaml rcsccscommonyamltestsuiteit test search sort segments on timestamp test that index segments are sorted on timestamp field if timestamp field is defined in mapping failed java lang assertionerror failure at expected a list containing expected but was at randomizedtesting seedinfo seed at org elasticsearch test rest yaml esclientyamlsuitetestcase executesection esclientyamlsuitetestcase java at org elasticsearch test rest yaml esclientyamlsuitetestcase test esclientyamlsuitetestcase java at java base jdk internal reflect directmethodhandleaccessor invoke directmethodhandleaccessor java at java base java lang reflect method invoke method java at com carrotsearch randomizedtesting randomizedrunner invoke randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene tests util testrulesetupteardownchained evaluate testrulesetupteardownchained java at org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene tests util testrulethreadandtestname evaluate testrulethreadandtestname java at org apache lucene tests util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene tests util testrulemarkfailure evaluate testrulemarkfailure java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol forktimeoutingtask threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol evaluate threadleakcontrol java at com carrotsearch randomizedtesting randomizedrunner runsingletest randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at org elasticsearch test cluster local localelasticsearchcluster evaluate localelasticsearchcluster java at org elasticsearch test cluster local localelasticsearchcluster evaluate localelasticsearchcluster java at org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene tests util testrulestoreclassname evaluate testrulestoreclassname java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene tests util testruleassertionsrequired evaluate testruleassertionsrequired java at org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene tests util testrulemarkfailure evaluate testrulemarkfailure java at org apache lucene tests util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene tests util testruleignoretestsuites evaluate testruleignoretestsuites java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol lambda forktimeoutingtask threadleakcontrol java at java base java lang thread run thread java caused by java lang assertionerror expected a list containing expected but was at org elasticsearch test mapmatcher assertmap mapmatcher java at org elasticsearch test mapmatcher assertmap mapmatcher java at org elasticsearch test rest yaml section matchassertion doassert matchassertion java at org elasticsearch test rest yaml section assertion execute assertion java at org elasticsearch test rest yaml esclientyamlsuitetestcase executesection esclientyamlsuitetestcase java more
| 1
|
85,861
| 10,688,391,431
|
IssuesEvent
|
2019-10-22 18:08:01
|
iterative/dvc.org
|
https://api.github.com/repos/iterative/dvc.org
|
opened
|
engine: create title entry in CONTENTS nac (right side bar)
|
design docs engine enhancement good first issue
|
Often there's a long intro in our docs before getting to the first H2 header (example below) but the CONTENTS navigation element in the right side bar does not list the document's H1 title, so it's not possible to scroll to the very top from there, which I think would be a logical feature.
> https://dvc.org/doc/tutorials/versioning
|
1.0
|
engine: create title entry in CONTENTS nac (right side bar) - Often there's a long intro in our docs before getting to the first H2 header (example below) but the CONTENTS navigation element in the right side bar does not list the document's H1 title, so it's not possible to scroll to the very top from there, which I think would be a logical feature.
> https://dvc.org/doc/tutorials/versioning
|
non_test
|
engine create title entry in contents nac right side bar often there s a long intro in our docs before getting to the first header example below but the contents navigation element in the right side bar does not list the document s title so it s not possible to scroll to the very top from there which i think would be a logical feature
| 0
|
646,665
| 21,055,493,684
|
IssuesEvent
|
2022-04-01 02:29:33
|
Gilded-Games/The-Aether
|
https://api.github.com/repos/Gilded-Games/The-Aether
|
closed
|
Enhancement: Aerwhale (polishing)
|
priority/medium status/in-progress type/enhancement feat/entity
|
- [x] Aerwhale flying movement is jittery. Look at the fix that was applied to Zephyrs for this.
- [x] Aerwhales spin a lot and their rotation often doesn't correlate with their direction.
- [x] Aerwhales rotate too fast,
- [x] Aerwhales can go really high into the sky. Maybe they should have some minimum and maximum height range they stay between.
|
1.0
|
Enhancement: Aerwhale (polishing) - - [x] Aerwhale flying movement is jittery. Look at the fix that was applied to Zephyrs for this.
- [x] Aerwhales spin a lot and their rotation often doesn't correlate with their direction.
- [x] Aerwhales rotate too fast,
- [x] Aerwhales can go really high into the sky. Maybe they should have some minimum and maximum height range they stay between.
|
non_test
|
enhancement aerwhale polishing aerwhale flying movement is jittery look at the fix that was applied to zephyrs for this aerwhales spin a lot and their rotation often doesn t correlate with their direction aerwhales rotate too fast aerwhales can go really high into the sky maybe they should have some minimum and maximum height range they stay between
| 0
|
558,313
| 16,529,320,927
|
IssuesEvent
|
2021-05-27 02:19:43
|
kobotoolbox/kpi
|
https://api.github.com/repos/kobotoolbox/kpi
|
closed
|
Self-service sync_kobocat_xforms
|
API enhancement has PR high priority
|
Extend #3002 so that people can synchronize their own forms. We used to offer this in a hacky way:
https://github.com/kobotoolbox/kpi/commit/b8351171428bd7a048c6334c68b0064167cf7845#diff-1483cb549cd31083151fa35593cfd9cd1d460bcca38c32a0049ac004d4459f1eL20
We need back-end support for this as well as some minimal UI component to invoke it. I'm unsure whether the UI component will be in KPI or KoBoCAT, but probably KoBoCAT given that we'll be [showing a notice](https://github.com/kobotoolbox/kobocat/issues/700) there?
|
1.0
|
Self-service sync_kobocat_xforms - Extend #3002 so that people can synchronize their own forms. We used to offer this in a hacky way:
https://github.com/kobotoolbox/kpi/commit/b8351171428bd7a048c6334c68b0064167cf7845#diff-1483cb549cd31083151fa35593cfd9cd1d460bcca38c32a0049ac004d4459f1eL20
We need back-end support for this as well as some minimal UI component to invoke it. I'm unsure whether the UI component will be in KPI or KoBoCAT, but probably KoBoCAT given that we'll be [showing a notice](https://github.com/kobotoolbox/kobocat/issues/700) there?
|
non_test
|
self service sync kobocat xforms extend so that people can synchronize their own forms we used to offer this in a hacky way we need back end support for this as well as some minimal ui component to invoke it i m unsure whether the ui component will be in kpi or kobocat but probably kobocat given that we ll be there
| 0
|
49,836
| 13,466,404,729
|
IssuesEvent
|
2020-09-09 22:52:02
|
wrbejar/JavaVulnerableLab
|
https://api.github.com/repos/wrbejar/JavaVulnerableLab
|
opened
|
CVE-2019-2692 (Medium) detected in mysql-connector-java-5.1.26.jar
|
security vulnerability
|
## CVE-2019-2692 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.26.jar</b></p></summary>
<p>MySQL JDBC Type 4 driver</p>
<p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p>
<p>Path to vulnerable library: _depth_0/JavaVulnerableLab/bin/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,_depth_0/JavaVulnerableLab/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,_depth_0/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,_depth_0/JavaVulnerableLab/bin/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,/JavaVulnerableLab/bin/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar</p>
<p>
Dependency Hierarchy:
- :x: **mysql-connector-java-5.1.26.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/wrbejar/JavaVulnerableLab/commit/8057b7b52ad296d310023091d3a946d7d12e2fd7">8057b7b52ad296d310023091d3a946d7d12e2fd7</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>
Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
<p>Publish Date: 2019-04-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-2692>CVE-2019-2692</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: High
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-jcq3-cprp-m333">https://github.com/advisories/GHSA-jcq3-cprp-m333</a></p>
<p>Release Date: 2019-04-23</p>
<p>Fix Resolution: mysql:mysql-connector-java:8.0.16</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"mysql","packageName":"mysql-connector-java","packageVersion":"5.1.26","isTransitiveDependency":false,"dependencyTree":"mysql:mysql-connector-java:5.1.26","isMinimumFixVersionAvailable":true,"minimumFixVersion":"mysql:mysql-connector-java:8.0.16"}],"vulnerabilityIdentifier":"CVE-2019-2692","vulnerabilityDetails":"Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-2692","cvss3Severity":"medium","cvss3Score":"6.3","cvss3Metrics":{"A":"High","AC":"High","PR":"High","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2019-2692 (Medium) detected in mysql-connector-java-5.1.26.jar - ## CVE-2019-2692 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.26.jar</b></p></summary>
<p>MySQL JDBC Type 4 driver</p>
<p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p>
<p>Path to vulnerable library: _depth_0/JavaVulnerableLab/bin/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,_depth_0/JavaVulnerableLab/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,_depth_0/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,_depth_0/JavaVulnerableLab/bin/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,/JavaVulnerableLab/bin/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar</p>
<p>
Dependency Hierarchy:
- :x: **mysql-connector-java-5.1.26.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/wrbejar/JavaVulnerableLab/commit/8057b7b52ad296d310023091d3a946d7d12e2fd7">8057b7b52ad296d310023091d3a946d7d12e2fd7</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>
Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
<p>Publish Date: 2019-04-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-2692>CVE-2019-2692</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: High
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-jcq3-cprp-m333">https://github.com/advisories/GHSA-jcq3-cprp-m333</a></p>
<p>Release Date: 2019-04-23</p>
<p>Fix Resolution: mysql:mysql-connector-java:8.0.16</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"mysql","packageName":"mysql-connector-java","packageVersion":"5.1.26","isTransitiveDependency":false,"dependencyTree":"mysql:mysql-connector-java:5.1.26","isMinimumFixVersionAvailable":true,"minimumFixVersion":"mysql:mysql-connector-java:8.0.16"}],"vulnerabilityIdentifier":"CVE-2019-2692","vulnerabilityDetails":"Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-2692","cvss3Severity":"medium","cvss3Score":"6.3","cvss3Metrics":{"A":"High","AC":"High","PR":"High","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve medium detected in mysql connector java jar cve medium severity vulnerability vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to vulnerable library depth javavulnerablelab bin target javavulnerablelab web inf lib mysql connector java jar canner repository mysql mysql connector java mysql connector java jar depth javavulnerablelab target javavulnerablelab meta inf maven org cysecurity javavulnerablelab target javavulnerablelab web inf lib mysql connector java jar depth javavulnerablelab target javavulnerablelab web inf lib mysql connector java jar depth javavulnerablelab bin target javavulnerablelab meta inf maven org cysecurity javavulnerablelab target javavulnerablelab web inf lib mysql connector java jar canner repository mysql mysql connector java mysql connector java jar canner repository mysql mysql connector java mysql connector java jar javavulnerablelab bin target javavulnerablelab web inf lib mysql connector java jar javavulnerablelab target javavulnerablelab web inf lib mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in head commit a href vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and prior difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where mysql connectors executes to compromise mysql connectors successful attacks require human interaction from a person other than the attacker successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av l ac h pr h ui r s u c h i h a h publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required high user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution mysql mysql connector java rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and prior difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where mysql connectors executes to compromise mysql connectors successful attacks require human interaction from a person other than the attacker successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av l ac h pr h ui r s u c h i h a h vulnerabilityurl
| 0
|
367,633
| 10,860,133,710
|
IssuesEvent
|
2019-11-14 08:21:56
|
openmsupply/mobile
|
https://api.github.com/repos/openmsupply/mobile
|
closed
|
Dependency upgrades November 2019
|
Docs: not needed Effort: small Feature Priority: high
|
## Is your feature request related to a problem? Please describe.
Monthly dependency upgrade
## Describe the solution you'd like
- Mainly looking to upgrade `react-navigation`. It was left out of last months as there were other major ones and didn't want to do too many at once. All of the navigators have been ripped out of the main package and are their individual packages now - i.e. stack/switch/tabs. Not a biggy as they've made them backwards compatible I believe, but a couple of code changes, I believe
- Haven't seen any other major releases
## Describe alternatives you've considered
Getting behind in upgrades
## Additional context
N/A
|
1.0
|
Dependency upgrades November 2019 - ## Is your feature request related to a problem? Please describe.
Monthly dependency upgrade
## Describe the solution you'd like
- Mainly looking to upgrade `react-navigation`. It was left out of last months as there were other major ones and didn't want to do too many at once. All of the navigators have been ripped out of the main package and are their individual packages now - i.e. stack/switch/tabs. Not a biggy as they've made them backwards compatible I believe, but a couple of code changes, I believe
- Haven't seen any other major releases
## Describe alternatives you've considered
Getting behind in upgrades
## Additional context
N/A
|
non_test
|
dependency upgrades november is your feature request related to a problem please describe monthly dependency upgrade describe the solution you d like mainly looking to upgrade react navigation it was left out of last months as there were other major ones and didn t want to do too many at once all of the navigators have been ripped out of the main package and are their individual packages now i e stack switch tabs not a biggy as they ve made them backwards compatible i believe but a couple of code changes i believe haven t seen any other major releases describe alternatives you ve considered getting behind in upgrades additional context n a
| 0
|
164,167
| 12,792,362,952
|
IssuesEvent
|
2020-07-02 01:11:04
|
microsoft/azure-tools-for-java
|
https://api.github.com/repos/microsoft/azure-tools-for-java
|
closed
|
[IntelliJ][SpringCloud]Deploy Azure Spring Cloud App dialog default value is apply
|
IntelliJ Internal Test P3 bug springcloud transfter
|
## Environment:
OS: Mac & Win
Plugins Version: Azure java toolkit for IntelliJ: 3.34.0
IDE Version: IU19.2.4 - jre11 & IC19.2.4 - jre8
## Repro steps:
1. Git clone: spring-petclinic
2. Add spring cloud dependency
3. Deploy apps from current project
## Result:
|
1.0
|
[IntelliJ][SpringCloud]Deploy Azure Spring Cloud App dialog default value is apply - ## Environment:
OS: Mac & Win
Plugins Version: Azure java toolkit for IntelliJ: 3.34.0
IDE Version: IU19.2.4 - jre11 & IC19.2.4 - jre8
## Repro steps:
1. Git clone: spring-petclinic
2. Add spring cloud dependency
3. Deploy apps from current project
## Result:
|
test
|
deploy azure spring cloud app dialog default value is apply environment os mac win plugins version azure java toolkit for intellij ide version repro steps git clone spring petclinic add spring cloud dependency deploy apps from current project result
| 1
|
144,417
| 22,345,654,768
|
IssuesEvent
|
2022-06-15 07:33:25
|
btcpayserver/btcpayserver
|
https://api.github.com/repos/btcpayserver/btcpayserver
|
closed
|
Add `store's default currency` to the dashboard wallet balance
|
UI / UX Design
|
User should be able to toggle between a store default currency and a BTC balance on the dashboard.
Not sure how we could make `toggle` action obvious, or should it be side by side. I think most wallets have toggle, so should be fine as long as it's clear a user can click. The conversion logic should already exist in the `Wallet` > `Send` tab where a BTC amount is converted to store's default currency.
This should address most concerns in https://github.com/btcpayserver/btcpayserver/discussions/3637
|
1.0
|
Add `store's default currency` to the dashboard wallet balance - User should be able to toggle between a store default currency and a BTC balance on the dashboard.
Not sure how we could make `toggle` action obvious, or should it be side by side. I think most wallets have toggle, so should be fine as long as it's clear a user can click. The conversion logic should already exist in the `Wallet` > `Send` tab where a BTC amount is converted to store's default currency.
This should address most concerns in https://github.com/btcpayserver/btcpayserver/discussions/3637
|
non_test
|
add store s default currency to the dashboard wallet balance user should be able to toggle between a store default currency and a btc balance on the dashboard not sure how we could make toggle action obvious or should it be side by side i think most wallets have toggle so should be fine as long as it s clear a user can click the conversion logic should already exist in the wallet send tab where a btc amount is converted to store s default currency this should address most concerns in
| 0
|
238,987
| 19,802,936,702
|
IssuesEvent
|
2022-01-19 01:13:26
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
opened
|
Upgrade from Chromium 97.0.4692.71 to Chromium 97.0.4692.100(?).
|
QA/Yes release-notes/include QA/Test-Plan-Specified OS/Android Chromium/upgrade minor OS/Desktop
|
Minor Chromium bump.
https://chromium.googlesource.com/chromium/src/+log/97.0.4692.71..97.0.4692.100?pretty=fuller&n=10000
QA tests:
Check branding items
Check for version bump
Additional checks:
No specific code changes in Brave (only line number changes in patches).
|
1.0
|
Upgrade from Chromium 97.0.4692.71 to Chromium 97.0.4692.100(?). - Minor Chromium bump.
https://chromium.googlesource.com/chromium/src/+log/97.0.4692.71..97.0.4692.100?pretty=fuller&n=10000
QA tests:
Check branding items
Check for version bump
Additional checks:
No specific code changes in Brave (only line number changes in patches).
|
test
|
upgrade from chromium to chromium minor chromium bump qa tests check branding items check for version bump additional checks no specific code changes in brave only line number changes in patches
| 1
|
337,491
| 24,542,486,335
|
IssuesEvent
|
2022-10-12 05:49:35
|
osism/testbed
|
https://api.github.com/repos/osism/testbed
|
closed
|
make the new ansible testbed rollout not depend on ~/src/github.com/osism
|
documentation
|
ref: https://docs.osism.tech/testbed/preparations.html
The testbed should not be dependent whether the git repo is checked out to this hard coded directory as it was before the ansible deployment move
|
1.0
|
make the new ansible testbed rollout not depend on ~/src/github.com/osism - ref: https://docs.osism.tech/testbed/preparations.html
The testbed should not be dependent whether the git repo is checked out to this hard coded directory as it was before the ansible deployment move
|
non_test
|
make the new ansible testbed rollout not depend on src github com osism ref the testbed should not be dependent whether the git repo is checked out to this hard coded directory as it was before the ansible deployment move
| 0
|
65,652
| 16,447,252,202
|
IssuesEvent
|
2021-05-20 21:13:59
|
ClangBuiltLinux/linux
|
https://api.github.com/repos/ClangBuiltLinux/linux
|
closed
|
-Wconstant-conversion in drivers/platform/surface/surface_aggregator_registry.c
|
[ARCH] x86 [BUG] linux-next [CONFIG] allmodconfig [PATCH] Accepted [Reported-by] kbuild test robot
|
ARCH=i386 make LLVM=1 LLVM_IAS=1 allmodconfig
```
drivers/platform/surface/surface_aggregator_registry.c:478:25: warning: implicit conversion from 'int' to '__u8' (aka 'unsigned char') changes value from 65535 to 255 [-Wconstant-conversion]
{ SSAM_VDEV(HUB, 0x02, SSAM_ANY_IID, 0x00) },
~ ^~~~~~~~~~~~
./include/linux/surface_aggregator/device.h:71:23: note: expanded from macro 'SSAM_ANY_IID'
#define SSAM_ANY_IID 0xffff
^~~~~~
./include/linux/surface_aggregator/device.h:126:63: note: expanded from macro 'SSAM_VDEV'
SSAM_DEVICE(SSAM_DOMAIN_VIRTUAL, SSAM_VIRTUAL_TC_##cat, tid, iid, fun)
^~~
./include/linux/surface_aggregator/device.h:102:41: note: expanded from macro 'SSAM_DEVICE'
.instance = ((iid) != SSAM_ANY_IID) ? (iid) : 0, \
^~~
```
|
1.0
|
-Wconstant-conversion in drivers/platform/surface/surface_aggregator_registry.c - ARCH=i386 make LLVM=1 LLVM_IAS=1 allmodconfig
```
drivers/platform/surface/surface_aggregator_registry.c:478:25: warning: implicit conversion from 'int' to '__u8' (aka 'unsigned char') changes value from 65535 to 255 [-Wconstant-conversion]
{ SSAM_VDEV(HUB, 0x02, SSAM_ANY_IID, 0x00) },
~ ^~~~~~~~~~~~
./include/linux/surface_aggregator/device.h:71:23: note: expanded from macro 'SSAM_ANY_IID'
#define SSAM_ANY_IID 0xffff
^~~~~~
./include/linux/surface_aggregator/device.h:126:63: note: expanded from macro 'SSAM_VDEV'
SSAM_DEVICE(SSAM_DOMAIN_VIRTUAL, SSAM_VIRTUAL_TC_##cat, tid, iid, fun)
^~~
./include/linux/surface_aggregator/device.h:102:41: note: expanded from macro 'SSAM_DEVICE'
.instance = ((iid) != SSAM_ANY_IID) ? (iid) : 0, \
^~~
```
|
non_test
|
wconstant conversion in drivers platform surface surface aggregator registry c arch make llvm llvm ias allmodconfig drivers platform surface surface aggregator registry c warning implicit conversion from int to aka unsigned char changes value from to ssam vdev hub ssam any iid include linux surface aggregator device h note expanded from macro ssam any iid define ssam any iid include linux surface aggregator device h note expanded from macro ssam vdev ssam device ssam domain virtual ssam virtual tc cat tid iid fun include linux surface aggregator device h note expanded from macro ssam device instance iid ssam any iid iid
| 0
|
94,003
| 8,461,739,954
|
IssuesEvent
|
2018-10-22 22:59:13
|
red/red
|
https://api.github.com/repos/red/red
|
closed
|
DRAW re-orders BOX coordinates
|
status.built status.tested type.bug
|
**Describe the bug**
`DRAW` re-orders of BOX coordinates and modifies its block argument.
**To Reproduce**
```
>> view [base 100x100 draw x: [box 10x0 20x10 box 20x0 10x10]]
>> x
== [box 10x0 20x10 box 10x0 20x10]
>> view [base 100x100 green draw x: [box 20x20 10x10 box 15x5 0x10]]
>> x
== [box 10x10 20x20 box 0x5 15x10]
```
**Expected behavior**
Draw block should not be modified
**Platform version:**
```
RED: [ branch: "master" tag: #v0.6.3 ahead: 1068 date: 7-Oct-2018/2:40:37 commit: #b4e7fff72801c9e7f563c11d6d722685ad8e88d9 ]
PLATFORM: [ name: "Windows 10" OS: 'Windows arch: 'x86-64 version: 10.0.0 build: 17134 ]
```
|
1.0
|
DRAW re-orders BOX coordinates - **Describe the bug**
`DRAW` re-orders of BOX coordinates and modifies its block argument.
**To Reproduce**
```
>> view [base 100x100 draw x: [box 10x0 20x10 box 20x0 10x10]]
>> x
== [box 10x0 20x10 box 10x0 20x10]
>> view [base 100x100 green draw x: [box 20x20 10x10 box 15x5 0x10]]
>> x
== [box 10x10 20x20 box 0x5 15x10]
```
**Expected behavior**
Draw block should not be modified
**Platform version:**
```
RED: [ branch: "master" tag: #v0.6.3 ahead: 1068 date: 7-Oct-2018/2:40:37 commit: #b4e7fff72801c9e7f563c11d6d722685ad8e88d9 ]
PLATFORM: [ name: "Windows 10" OS: 'Windows arch: 'x86-64 version: 10.0.0 build: 17134 ]
```
|
test
|
draw re orders box coordinates describe the bug draw re orders of box coordinates and modifies its block argument to reproduce view x view x expected behavior draw block should not be modified platform version red platform
| 1
|
53,329
| 6,310,403,251
|
IssuesEvent
|
2017-07-23 10:01:28
|
FloEdelmann/open-fixture-library
|
https://api.github.com/repos/FloEdelmann/open-fixture-library
|
opened
|
Run CLI plugin diff with test fixtures
|
component-test priority-medium
|
Add option to use test fixtures instead of manually defining them
|
1.0
|
Run CLI plugin diff with test fixtures - Add option to use test fixtures instead of manually defining them
|
test
|
run cli plugin diff with test fixtures add option to use test fixtures instead of manually defining them
| 1
|
290,942
| 25,108,958,061
|
IssuesEvent
|
2022-11-08 18:51:00
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
sql: st_distancespheroid with point with NaN coordinate causes panic
|
C-test-failure O-robot O-roachtest T-sql-queries branch-release-21.2
|
roachtest.sqlsmith/setup=seed/setting=no-mutations [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=6994303&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=6994303&tab=artifacts#/sqlsmith/setup=seed/setting=no-mutations) on release-21.2 @ [06fb4817f5ce494565674a1b4784d92ac6624fac](https://github.com/cockroachdb/cockroach/commits/06fb4817f5ce494565674a1b4784d92ac6624fac):
```
),
(
'2':::STRING,
(0.5890958543624928:::FLOAT8::FLOAT8 // (-0.40367659361358665):::FLOAT8::FLOAT8)::FLOAT8,
'7':::STRING
)
)
AS tab_13527 (col_32960, col_32961, col_32962)
)
SELECT
'"':::STRING AS col_32963,
cte_ref_1628.col_32956 AS col_32964,
st_distancespheroid(st_snaptogrid('01050000C00400000001020000C0040000000A2B7937D2DDF341CAEF56D6CA94FEC168909A5A5308D5C1600863B65513F9C10E9D7B3828CFF3415D754B6EE344F4C154EB8B48DC37EEC14E5053131963FA41E4B8F8F90180E941B433052AC359E2C1B0F9BD706AE0CA41E47A00106D23E6C1140CDEFC2066E541DC041E43D7E0E541D71DA60DCF5800C2C03C19D64662A94101020000C00400000078A3F3FA171BECC14906026AC73000C2BF39C72B6DC0FCC13CFE89583CADE64120EBED23DDB5C1C1C072A4065C53DCC1B04A51E92098F441A063BD5F67B2E841CCB94727FC86DCC1B8276303051FD84114B61A426749FC417483A4C01A68E341F252B7B34B6EEDC19289514C865EF14148C84B584F87F24114436730C149E04101020000C003000000F8CB40BB7D74FD41407A6D511432D741B0CD41FE895DD4418672254A1EB8014208EACF19E83CD541746AD58CB9170242C0B19FB99AFED94148AE2EF95896FE4178B997637B6BD6C164ABA2111EA8FD410CFDE813927BD7C190265FCF876A014201020000C0060000001065DCD70770F7C10F612AD0CC33F4C111FFA41FB47802C2265299CFB19A01422F77456D88D7F2C1A2EAE8CB9F09F4C150167B5B5309EA415A5DDD2C45E9F1418C125198484AE64153D5D0ED755DFAC1EA0005C2D148F1C1EC3F313A1519E241E2779FD007B7F341CB5DDDC5D00CF0C1C24CC5C279C0FDC188BB78838C7BF341F0942DF0B3FBF041906304A7FFB4D5C1982570D0B8FCDB412059D469B946BF4160C6D4DBF074E841586F81D38E05E641A14870D6117800C23C248B430E0CF9C1':::GEOMETRY::GEOMETRY, cte_ref_1628.col_32957::FLOAT8)::GEOMETRY::GEOMETRY, '010500000002000000010200000003000000000000000000244000000000000024400000000000003440000000000000344000000000000024400000000000004440010200000004000000000000000000444000000000000044400000000000003E400000000000003E40000000000000444000000000000034400000000000003E400000000000002440':::GEOMETRY::GEOMETRY)::FLOAT8
AS col_32965
FROM
with_5490 AS cte_ref_1628
WHERE
(false OR true)
ORDER BY
cte_ref_1628.col_32956 ASC;ping node 1: dial tcp 34.148.119.100:26257: connect: connection refused
HINT: node likely crashed, check logs in artifacts > logs/1.unredacted
cluster.go:1296,context.go:91,cluster.go:1284,test_runner.go:866: dead node detection: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod monitor teamcity-6994303-1666072367-12-n4cpu4 --oneshot --ignore-empty-nodes: exit status 1 3: 14601
1: dead (exit status 134)
4: 12463
2: 12621
Error: UNCLASSIFIED_PROBLEM: 1: dead (exit status 134)
(1) UNCLASSIFIED_PROBLEM
Wraps: (2) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/roachprod.Monitor
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/roachprod.go:596
| main.glob..func14
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:569
| main.wrap.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:123
| github.com/spf13/cobra.(*Command).execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:856
| github.com/spf13/cobra.(*Command).ExecuteC
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:960
| github.com/spf13/cobra.(*Command).Execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:897
| main.main
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1170
| runtime.main
| /usr/local/go/src/runtime/proc.go:250
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1571
Wraps: (3) 1: dead (exit status 134)
Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errutil.leafError
```
<details><summary>Reproduce</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #89960 roachtest: sqlsmith/setup=seed/setting=no-mutations failed [C-test-failure O-roachtest O-robot T-sql-queries branch-master branch-release-22.2 branch-release-22.2.0 release-blocker]
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-mutations.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-20594
|
2.0
|
sql: st_distancespheroid with point with NaN coordinate causes panic - roachtest.sqlsmith/setup=seed/setting=no-mutations [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=6994303&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=6994303&tab=artifacts#/sqlsmith/setup=seed/setting=no-mutations) on release-21.2 @ [06fb4817f5ce494565674a1b4784d92ac6624fac](https://github.com/cockroachdb/cockroach/commits/06fb4817f5ce494565674a1b4784d92ac6624fac):
```
),
(
'2':::STRING,
(0.5890958543624928:::FLOAT8::FLOAT8 // (-0.40367659361358665):::FLOAT8::FLOAT8)::FLOAT8,
'7':::STRING
)
)
AS tab_13527 (col_32960, col_32961, col_32962)
)
SELECT
'"':::STRING AS col_32963,
cte_ref_1628.col_32956 AS col_32964,
st_distancespheroid(st_snaptogrid('01050000C00400000001020000C0040000000A2B7937D2DDF341CAEF56D6CA94FEC168909A5A5308D5C1600863B65513F9C10E9D7B3828CFF3415D754B6EE344F4C154EB8B48DC37EEC14E5053131963FA41E4B8F8F90180E941B433052AC359E2C1B0F9BD706AE0CA41E47A00106D23E6C1140CDEFC2066E541DC041E43D7E0E541D71DA60DCF5800C2C03C19D64662A94101020000C00400000078A3F3FA171BECC14906026AC73000C2BF39C72B6DC0FCC13CFE89583CADE64120EBED23DDB5C1C1C072A4065C53DCC1B04A51E92098F441A063BD5F67B2E841CCB94727FC86DCC1B8276303051FD84114B61A426749FC417483A4C01A68E341F252B7B34B6EEDC19289514C865EF14148C84B584F87F24114436730C149E04101020000C003000000F8CB40BB7D74FD41407A6D511432D741B0CD41FE895DD4418672254A1EB8014208EACF19E83CD541746AD58CB9170242C0B19FB99AFED94148AE2EF95896FE4178B997637B6BD6C164ABA2111EA8FD410CFDE813927BD7C190265FCF876A014201020000C0060000001065DCD70770F7C10F612AD0CC33F4C111FFA41FB47802C2265299CFB19A01422F77456D88D7F2C1A2EAE8CB9F09F4C150167B5B5309EA415A5DDD2C45E9F1418C125198484AE64153D5D0ED755DFAC1EA0005C2D148F1C1EC3F313A1519E241E2779FD007B7F341CB5DDDC5D00CF0C1C24CC5C279C0FDC188BB78838C7BF341F0942DF0B3FBF041906304A7FFB4D5C1982570D0B8FCDB412059D469B946BF4160C6D4DBF074E841586F81D38E05E641A14870D6117800C23C248B430E0CF9C1':::GEOMETRY::GEOMETRY, cte_ref_1628.col_32957::FLOAT8)::GEOMETRY::GEOMETRY, '010500000002000000010200000003000000000000000000244000000000000024400000000000003440000000000000344000000000000024400000000000004440010200000004000000000000000000444000000000000044400000000000003E400000000000003E40000000000000444000000000000034400000000000003E400000000000002440':::GEOMETRY::GEOMETRY)::FLOAT8
AS col_32965
FROM
with_5490 AS cte_ref_1628
WHERE
(false OR true)
ORDER BY
cte_ref_1628.col_32956 ASC;ping node 1: dial tcp 34.148.119.100:26257: connect: connection refused
HINT: node likely crashed, check logs in artifacts > logs/1.unredacted
cluster.go:1296,context.go:91,cluster.go:1284,test_runner.go:866: dead node detection: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod monitor teamcity-6994303-1666072367-12-n4cpu4 --oneshot --ignore-empty-nodes: exit status 1 3: 14601
1: dead (exit status 134)
4: 12463
2: 12621
Error: UNCLASSIFIED_PROBLEM: 1: dead (exit status 134)
(1) UNCLASSIFIED_PROBLEM
Wraps: (2) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/roachprod.Monitor
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/roachprod.go:596
| main.glob..func14
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:569
| main.wrap.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:123
| github.com/spf13/cobra.(*Command).execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:856
| github.com/spf13/cobra.(*Command).ExecuteC
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:960
| github.com/spf13/cobra.(*Command).Execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:897
| main.main
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1170
| runtime.main
| /usr/local/go/src/runtime/proc.go:250
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1571
Wraps: (3) 1: dead (exit status 134)
Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errutil.leafError
```
<details><summary>Reproduce</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #89960 roachtest: sqlsmith/setup=seed/setting=no-mutations failed [C-test-failure O-roachtest O-robot T-sql-queries branch-master branch-release-22.2 branch-release-22.2.0 release-blocker]
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-mutations.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-20594
|
test
|
sql st distancespheroid with point with nan coordinate causes panic roachtest sqlsmith setup seed setting no mutations with on release string string as tab col col col select string as col cte ref col as col st distancespheroid st snaptogrid geometry geometry cte ref col geometry geometry geometry geometry as col from with as cte ref where false or true order by cte ref col asc ping node dial tcp connect connection refused hint node likely crashed check logs in artifacts logs unredacted cluster go context go cluster go test runner go dead node detection home agent work go src github com cockroachdb cockroach bin roachprod monitor teamcity oneshot ignore empty nodes exit status dead exit status error unclassified problem dead exit status unclassified problem wraps attached stack trace stack trace github com cockroachdb cockroach pkg roachprod monitor home agent work go src github com cockroachdb cockroach pkg roachprod roachprod go main glob home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go main wrap home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command executec home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go main main home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps dead exit status error types errors unclassified withstack withstack errutil leaferror reproduce see same failure on other branches roachtest sqlsmith setup seed setting no mutations failed cc cockroachdb sql queries jira issue crdb
| 1
|
324,067
| 27,775,038,679
|
IssuesEvent
|
2023-03-16 16:40:09
|
AxeWP/wp-graphql-headless-login
|
https://api.github.com/repos/AxeWP/wp-graphql-headless-login
|
closed
|
Add tests for OAuth2 - Generic Client mutations
|
good first issue 🐣 scope: tests 🧪 status: confirmed 📍 type: chore 🧹
|
### What problem does this address?
..
### What is your proposed solution?
..
### What alternatives have you considered?
_No response_
### Additional Context
There's a lot of possibilities to mock (and possibly bugs to flesh out).
See https://github.com/thephpleague/oauth2-client/blob/master/test/src/Provider/GenericProviderTest.php for an example.
|
1.0
|
Add tests for OAuth2 - Generic Client mutations - ### What problem does this address?
..
### What is your proposed solution?
..
### What alternatives have you considered?
_No response_
### Additional Context
There's a lot of possibilities to mock (and possibly bugs to flesh out).
See https://github.com/thephpleague/oauth2-client/blob/master/test/src/Provider/GenericProviderTest.php for an example.
|
test
|
add tests for generic client mutations what problem does this address what is your proposed solution what alternatives have you considered no response additional context there s a lot of possibilities to mock and possibly bugs to flesh out see for an example
| 1
|
182,753
| 14,148,671,422
|
IssuesEvent
|
2020-11-10 23:01:38
|
eclipse-theia/theia
|
https://api.github.com/repos/eclipse-theia/theia
|
closed
|
CI: stabilize 'api tests' on build
|
ci help wanted test
|
<!-- Please provide a detailed description of the bug. -->
#### Bug Description:
I've noticed for the past week or so (perhaps last week as well), that the build on Linux fails constantly for new pull-requests, and when merged to `master`. I often have to restart the build due to the intermittent failures, and it'd be good to investigate the issue and provide a more stable suite.
The errors look related to a timeout on tests present in the api test suites, namely for TypeScript:
- https://travis-ci.com/github/eclipse-theia/theia/jobs/415155353#L17659-L17669
<div align='center'>
<img width="746" alt="Screen Shot 2020-10-28 at 2 40 12 PM" src="https://user-images.githubusercontent.com/40359487/97481987-f040d180-192b-11eb-9c2a-99dca12a5311.png">
</div>
<!-- Please provide clear steps to reproduce the bug. -->
#### Steps to Reproduce:
1. observe the open pull-requests, or cron jobs (there is mostly an error during the Linux build for API tests)
<!-- Please provide any additional information available. -->
<!-- Additional information can be in the form of logs, screenshots, screencasts. -->
|
1.0
|
CI: stabilize 'api tests' on build - <!-- Please provide a detailed description of the bug. -->
#### Bug Description:
I've noticed for the past week or so (perhaps last week as well), that the build on Linux fails constantly for new pull-requests, and when merged to `master`. I often have to restart the build due to the intermittent failures, and it'd be good to investigate the issue and provide a more stable suite.
The errors look related to a timeout on tests present in the api test suites, namely for TypeScript:
- https://travis-ci.com/github/eclipse-theia/theia/jobs/415155353#L17659-L17669
<div align='center'>
<img width="746" alt="Screen Shot 2020-10-28 at 2 40 12 PM" src="https://user-images.githubusercontent.com/40359487/97481987-f040d180-192b-11eb-9c2a-99dca12a5311.png">
</div>
<!-- Please provide clear steps to reproduce the bug. -->
#### Steps to Reproduce:
1. observe the open pull-requests, or cron jobs (there is mostly an error during the Linux build for API tests)
<!-- Please provide any additional information available. -->
<!-- Additional information can be in the form of logs, screenshots, screencasts. -->
|
test
|
ci stabilize api tests on build bug description i ve noticed for the past week or so perhaps last week as well that the build on linux fails constantly for new pull requests and when merged to master i often have to restart the build due to the intermittent failures and it d be good to investigate the issue and provide a more stable suite the errors look related to a timeout on tests present in the api test suites namely for typescript img width alt screen shot at pm src steps to reproduce observe the open pull requests or cron jobs there is mostly an error during the linux build for api tests
| 1
|
118,857
| 10,013,814,532
|
IssuesEvent
|
2019-07-15 15:59:16
|
IBM/kui
|
https://api.github.com/repos/IBM/kui
|
closed
|
ibmcloud usage format has changed
|
tests
|
sometime around midnight 20190715, there was an update to the `ibmcloud` CLI that completely changed the format of their help/usage output. this breaks one of our tests.
|
1.0
|
ibmcloud usage format has changed - sometime around midnight 20190715, there was an update to the `ibmcloud` CLI that completely changed the format of their help/usage output. this breaks one of our tests.
|
test
|
ibmcloud usage format has changed sometime around midnight there was an update to the ibmcloud cli that completely changed the format of their help usage output this breaks one of our tests
| 1
|
254,514
| 27,393,559,328
|
IssuesEvent
|
2023-02-28 17:53:19
|
opensearch-project/oui
|
https://api.github.com/repos/opensearch-project/oui
|
closed
|
socket.io.slim-1.7.2.js: 1 vulnerabilities (highest severity is: 8.1) - autoclosed
|
security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>socket.io.slim-1.7.2.js</b></p></summary>
<p>node.js realtime framework server</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js">https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js</a></p>
<p>Path to vulnerable library: /packages/react-datepicker/node_modules/socket.io-client/dist/socket.io.slim.js</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/opensearch-project/oui/commit/bbca6f5de4b03c3c57a1333400bba2178b3aa99e">bbca6f5de4b03c3c57a1333400bba2178b3aa99e</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (socket.io.slim version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2020-0443](https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | socket.io.slim-1.7.2.js | Direct | socket.io - 2.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0443</summary>
### Vulnerable Library - <b>socket.io.slim-1.7.2.js</b></p>
<p>node.js realtime framework server</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js">https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js</a></p>
<p>Path to vulnerable library: /packages/react-datepicker/node_modules/socket.io-client/dist/socket.io.slim.js</p>
<p>
Dependency Hierarchy:
- :x: **socket.io.slim-1.7.2.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/opensearch-project/oui/commit/bbca6f5de4b03c3c57a1333400bba2178b3aa99e">bbca6f5de4b03c3c57a1333400bba2178b3aa99e</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In socket.io in versions 1.0.0 to 2.3.0 is vulnerable to Cross-Site Websocket Hijacking, it allows an attacker to bypass origin protection using special symbols include "`" and "$".
<p>Publish Date: 2020-02-20
<p>URL: <a href=https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7>WS-2020-0443</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hackerone.com/reports/931197">https://hackerone.com/reports/931197</a></p>
<p>Release Date: 2020-02-20</p>
<p>Fix Resolution: socket.io - 2.4.0</p>
</p>
<p></p>
</details>
|
True
|
socket.io.slim-1.7.2.js: 1 vulnerabilities (highest severity is: 8.1) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>socket.io.slim-1.7.2.js</b></p></summary>
<p>node.js realtime framework server</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js">https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js</a></p>
<p>Path to vulnerable library: /packages/react-datepicker/node_modules/socket.io-client/dist/socket.io.slim.js</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/opensearch-project/oui/commit/bbca6f5de4b03c3c57a1333400bba2178b3aa99e">bbca6f5de4b03c3c57a1333400bba2178b3aa99e</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (socket.io.slim version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2020-0443](https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | socket.io.slim-1.7.2.js | Direct | socket.io - 2.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0443</summary>
### Vulnerable Library - <b>socket.io.slim-1.7.2.js</b></p>
<p>node.js realtime framework server</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js">https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.2/socket.io.slim.js</a></p>
<p>Path to vulnerable library: /packages/react-datepicker/node_modules/socket.io-client/dist/socket.io.slim.js</p>
<p>
Dependency Hierarchy:
- :x: **socket.io.slim-1.7.2.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/opensearch-project/oui/commit/bbca6f5de4b03c3c57a1333400bba2178b3aa99e">bbca6f5de4b03c3c57a1333400bba2178b3aa99e</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In socket.io in versions 1.0.0 to 2.3.0 is vulnerable to Cross-Site Websocket Hijacking, it allows an attacker to bypass origin protection using special symbols include "`" and "$".
<p>Publish Date: 2020-02-20
<p>URL: <a href=https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7>WS-2020-0443</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hackerone.com/reports/931197">https://hackerone.com/reports/931197</a></p>
<p>Release Date: 2020-02-20</p>
<p>Fix Resolution: socket.io - 2.4.0</p>
</p>
<p></p>
</details>
|
non_test
|
socket io slim js vulnerabilities highest severity is autoclosed vulnerable library socket io slim js node js realtime framework server library home page a href path to vulnerable library packages react datepicker node modules socket io client dist socket io slim js found in head commit a href vulnerabilities cve severity cvss dependency type fixed in socket io slim version remediation available high socket io slim js direct socket io details ws vulnerable library socket io slim js node js realtime framework server library home page a href path to vulnerable library packages react datepicker node modules socket io client dist socket io slim js dependency hierarchy x socket io slim js vulnerable library found in head commit a href found in base branch main vulnerability details in socket io in versions to is vulnerable to cross site websocket hijacking it allows an attacker to bypass origin protection using special symbols include and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution socket io
| 0
|
17,697
| 12,508,504,672
|
IssuesEvent
|
2020-06-02 15:39:13
|
ampproject/amp-wp
|
https://api.github.com/repos/ampproject/amp-wp
|
closed
|
Dependency updates cannot be merged due to failing tests
|
Infrastructure
|
## Description
I've noticed since recently that [about half of the open PRs](https://github.com/ampproject/amp-wp/pulls?q=is%3Apr+is%3Aopen+author%3Arenovate-bot+created%3A2020-03-27..2020-05-04+) (26/49 currently) are from the Renovate bot to update dependencies, but they cannot be merged due to failing tests . Most of those PRs seem to have one thing in common: the E2E test fails due to the [`pupeteer` module not being found](https://travis-ci.org/github/ampproject/amp-wp/jobs/683329877#L884-L907):
```
Require stack:
- /home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/readConfig.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/global.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/setup.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/transform/build/ScriptTransformer.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/transform/build/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest-runtime/build/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/cli/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/jest.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest/node_modules/jest-cli/build/cli/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest/node_modules/jest-cli/build/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest/build/jest.js
- /home/travis/build/ampproject/amp-wp/node_modules/@wordpress/scripts/scripts/test-e2e.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
at Function.Module._load (internal/modules/cjs/loader.js:840:27)
at Module.require (internal/modules/cjs/loader.js:1019:19)
at require (internal/modules/cjs/helpers.js:77:18)
at getPuppeteer (/home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/readConfig.js:58:14)
at setup (/home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/global.js:21:50)
at async /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/runGlobalHook.js:82:11
at async waitForPromiseWithCleanup (/home/travis/build/ampproject/amp-wp/node_modules/@jest/transform/build/ScriptTransformer.js:216:5)
at async /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/runGlobalHook.js:72:9
at async pEachSeries (/home/travis/build/ampproject/amp-wp/node_modules/p-each-series/index.js:8:3)
```
Once that common issue has been dealt with, the PRs in question should be rebased and then each can be handled as accordingly.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* <!-- One or more bullet points for acceptance criteria. -->
## Implementation brief
* <!-- One or more bullet points for how to technically resolve the issue. For significant Implementation Design, it is ok use a Google document **accessible by anyone**. -->
## QA testing instructions
* <!-- One or more bullet points to describe how to test the implementation in QA. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
|
1.0
|
Dependency updates cannot be merged due to failing tests - ## Description
I've noticed since recently that [about half of the open PRs](https://github.com/ampproject/amp-wp/pulls?q=is%3Apr+is%3Aopen+author%3Arenovate-bot+created%3A2020-03-27..2020-05-04+) (26/49 currently) are from the Renovate bot to update dependencies, but they cannot be merged due to failing tests . Most of those PRs seem to have one thing in common: the E2E test fails due to the [`pupeteer` module not being found](https://travis-ci.org/github/ampproject/amp-wp/jobs/683329877#L884-L907):
```
Require stack:
- /home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/readConfig.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/global.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/setup.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/transform/build/ScriptTransformer.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/transform/build/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest-runtime/build/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/cli/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/jest.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest/node_modules/jest-cli/build/cli/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest/node_modules/jest-cli/build/index.js
- /home/travis/build/ampproject/amp-wp/node_modules/jest/build/jest.js
- /home/travis/build/ampproject/amp-wp/node_modules/@wordpress/scripts/scripts/test-e2e.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
at Function.Module._load (internal/modules/cjs/loader.js:840:27)
at Module.require (internal/modules/cjs/loader.js:1019:19)
at require (internal/modules/cjs/helpers.js:77:18)
at getPuppeteer (/home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/readConfig.js:58:14)
at setup (/home/travis/build/ampproject/amp-wp/node_modules/jest-environment-puppeteer/lib/global.js:21:50)
at async /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/runGlobalHook.js:82:11
at async waitForPromiseWithCleanup (/home/travis/build/ampproject/amp-wp/node_modules/@jest/transform/build/ScriptTransformer.js:216:5)
at async /home/travis/build/ampproject/amp-wp/node_modules/@jest/core/build/runGlobalHook.js:72:9
at async pEachSeries (/home/travis/build/ampproject/amp-wp/node_modules/p-each-series/index.js:8:3)
```
Once that common issue has been dealt with, the PRs in question should be rebased and then each can be handled as accordingly.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* <!-- One or more bullet points for acceptance criteria. -->
## Implementation brief
* <!-- One or more bullet points for how to technically resolve the issue. For significant Implementation Design, it is ok use a Google document **accessible by anyone**. -->
## QA testing instructions
* <!-- One or more bullet points to describe how to test the implementation in QA. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
|
non_test
|
dependency updates cannot be merged due to failing tests description i ve noticed since recently that currently are from the renovate bot to update dependencies but they cannot be merged due to failing tests most of those prs seem to have one thing in common the test fails due to the require stack home travis build ampproject amp wp node modules jest environment puppeteer lib readconfig js home travis build ampproject amp wp node modules jest environment puppeteer lib global js home travis build ampproject amp wp node modules jest environment puppeteer setup js home travis build ampproject amp wp node modules jest transform build scripttransformer js home travis build ampproject amp wp node modules jest transform build index js home travis build ampproject amp wp node modules jest runtime build index js home travis build ampproject amp wp node modules jest core build cli index js home travis build ampproject amp wp node modules jest core build jest js home travis build ampproject amp wp node modules jest node modules jest cli build cli index js home travis build ampproject amp wp node modules jest node modules jest cli build index js home travis build ampproject amp wp node modules jest build jest js home travis build ampproject amp wp node modules wordpress scripts scripts test js at function module resolvefilename internal modules cjs loader js at function module load internal modules cjs loader js at module require internal modules cjs loader js at require internal modules cjs helpers js at getpuppeteer home travis build ampproject amp wp node modules jest environment puppeteer lib readconfig js at setup home travis build ampproject amp wp node modules jest environment puppeteer lib global js at async home travis build ampproject amp wp node modules jest core build runglobalhook js at async waitforpromisewithcleanup home travis build ampproject amp wp node modules jest transform build scripttransformer js at async home travis build ampproject amp wp node modules jest core build runglobalhook js at async peachseries home travis build ampproject amp wp node modules p each series index js once that common issue has been dealt with the prs in question should be rebased and then each can be handled as accordingly do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria implementation brief qa testing instructions changelog entry
| 0
|
129,523
| 17,792,568,806
|
IssuesEvent
|
2021-08-31 17:58:01
|
EasyCorp/EasyAdminBundle
|
https://api.github.com/repos/EasyCorp/EasyAdminBundle
|
closed
|
Unexpected classes in form theme
|
bug help wanted good first issue design
|
**Describe the bug**
Someone reported on slack that this theme seems wrong here
https://github.com/EasyCorp/EasyAdminBundle/blob/master/src/Resources/views/crud/form_theme.html.twig#L705
**To Reproduce**
Not applicable
**(OPTIONAL) Additional context**
I'm not sure what's going on here and what the fix is. Just wanted to report it. Let me know if I can help.
|
1.0
|
Unexpected classes in form theme - **Describe the bug**
Someone reported on slack that this theme seems wrong here
https://github.com/EasyCorp/EasyAdminBundle/blob/master/src/Resources/views/crud/form_theme.html.twig#L705
**To Reproduce**
Not applicable
**(OPTIONAL) Additional context**
I'm not sure what's going on here and what the fix is. Just wanted to report it. Let me know if I can help.
|
non_test
|
unexpected classes in form theme describe the bug someone reported on slack that this theme seems wrong here to reproduce not applicable optional additional context i m not sure what s going on here and what the fix is just wanted to report it let me know if i can help
| 0
|
24,282
| 4,074,585,684
|
IssuesEvent
|
2016-05-28 15:13:03
|
methodic-io/tasks-and-goals
|
https://api.github.com/repos/methodic-io/tasks-and-goals
|
closed
|
Add test to ensure that all models respond to core date attributes
|
testing
|
created_at, updated_at, deleted_at
|
1.0
|
Add test to ensure that all models respond to core date attributes - created_at, updated_at, deleted_at
|
test
|
add test to ensure that all models respond to core date attributes created at updated at deleted at
| 1
|
10,551
| 3,126,158,392
|
IssuesEvent
|
2015-09-08 07:36:48
|
e-government-ua/iBP
|
https://api.github.com/repos/e-government-ua/iBP
|
reopened
|
Днепропетровск ЦНАП - Копії рішення міської ради про надання дозволу на розроблення проекту відведення земельної ділянки
|
in work test
|
Тех.карті - https://drive.google.com/file/d/0BydenhvN5xzeQ2lZdGRNYWJRUnk4VXUtTGlsUUpuVU92bElZ/view?usp=sharing
Заявление - https://docs.google.com/document/d/16ll4Wer7KnbCdUrdywbZrharMZs4w03mMapTIZ0tYRg/edit
|
1.0
|
Днепропетровск ЦНАП - Копії рішення міської ради про надання дозволу на розроблення проекту відведення земельної ділянки - Тех.карті - https://drive.google.com/file/d/0BydenhvN5xzeQ2lZdGRNYWJRUnk4VXUtTGlsUUpuVU92bElZ/view?usp=sharing
Заявление - https://docs.google.com/document/d/16ll4Wer7KnbCdUrdywbZrharMZs4w03mMapTIZ0tYRg/edit
|
test
|
днепропетровск цнап копії рішення міської ради про надання дозволу на розроблення проекту відведення земельної ділянки тех карті заявление
| 1
|
721,357
| 24,823,878,945
|
IssuesEvent
|
2022-10-25 18:48:59
|
gravitational/gravity
|
https://api.github.com/repos/gravitational/gravity
|
closed
|
Setup default storage class
|
kind/enhancement priority/1 component/openebs
|
When OpenEBS is enabled, Gravity clusters include two storage classes out of the box, openebs-hostpath and openebs-device, but there's not default storage class which means that a user has to specify storage class explicitly in their claim. To improve UX in this area we could do the following:
* Make "openebs-hostpath" the default storage class since it always works.
* Add a note to the Persistent Storage section of our docs about default storage class and changing the default storage class: https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/.
|
1.0
|
Setup default storage class - When OpenEBS is enabled, Gravity clusters include two storage classes out of the box, openebs-hostpath and openebs-device, but there's not default storage class which means that a user has to specify storage class explicitly in their claim. To improve UX in this area we could do the following:
* Make "openebs-hostpath" the default storage class since it always works.
* Add a note to the Persistent Storage section of our docs about default storage class and changing the default storage class: https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/.
|
non_test
|
setup default storage class when openebs is enabled gravity clusters include two storage classes out of the box openebs hostpath and openebs device but there s not default storage class which means that a user has to specify storage class explicitly in their claim to improve ux in this area we could do the following make openebs hostpath the default storage class since it always works add a note to the persistent storage section of our docs about default storage class and changing the default storage class
| 0
|
24,421
| 2,667,531,279
|
IssuesEvent
|
2015-03-22 18:05:37
|
GoogleCloudPlatform/kubernetes
|
https://api.github.com/repos/GoogleCloudPlatform/kubernetes
|
closed
|
Validating minion-1 never succeeds with vagrant #2
|
priority/support team/cluster-lifecycle
|
**VirtualBox** 4.3.24
**LinuxMint** 3.13.0-37-generic
**Docker** 1.0.1
**Vagrant** 1.7.2
*net-tools* are also installed.
```
Each machine instance has been created/updated.
Now waiting for the Salt provisioning process to complete on each machine.
This can take some time based on your network, disk, and cpu speed.
It is possible for an error to occur during Salt provision of cluster and this could loop forever.
Validating master
Validating minion-1
```
vagrant ssh minion-1 -c "ping kubernetes-master"
```
PING kubernetes-master (10.245.1.2) 56(84) bytes of data.
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=1 ttl=64 time=1.56 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=2 ttl=64 time=11.4 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=3 ttl=64 time=3.35 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=4 ttl=64 time=9.93 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=5 ttl=64 time=9.55 ms
```
sudo cat /var/log/salt/minion
```
2015-03-11 08:30:52,543 [salt.minion ][INFO ] Starting a new job with PID 9769
2015-03-11 08:30:52,544 [salt.minion ][INFO ] Returning information for job: 20150311083052887920
2015-03-11 08:30:52,597 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:30:52,597 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:30:55,512 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083055863950
2015-03-11 08:30:55,513 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083055863950', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:30:55,517 [salt.minion ][INFO ] Starting a new job with PID 9794
2015-03-11 08:30:55,519 [salt.minion ][INFO ] Returning information for job: 20150311083055863950
2015-03-11 08:30:56,364 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:30:56,365 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:30:56,519 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083056871176
2015-03-11 08:30:56,519 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083056871176', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:30:56,524 [salt.minion ][INFO ] Starting a new job with PID 9801
2015-03-11 08:30:56,525 [salt.minion ][INFO ] Returning information for job: 20150311083056871176
2015-03-11 08:30:57,248 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:30:57,249 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:02,750 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083103102341
2015-03-11 08:31:02,750 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083103102341', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:02,756 [salt.minion ][INFO ] Starting a new job with PID 9862
2015-03-11 08:31:02,757 [salt.minion ][INFO ] Returning information for job: 20150311083103102341
2015-03-11 08:31:02,808 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:02,809 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:07,380 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083107732564
2015-03-11 08:31:07,381 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083107732564', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:07,386 [salt.minion ][INFO ] Starting a new job with PID 9887
2015-03-11 08:31:07,387 [salt.minion ][INFO ] Returning information for job: 20150311083107732564
2015-03-11 08:31:07,478 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:07,478 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:08,016 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083108368247
2015-03-11 08:31:08,016 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083108368247', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:08,021 [salt.minion ][INFO ] Starting a new job with PID 9894
2015-03-11 08:31:08,022 [salt.minion ][INFO ] Returning information for job: 20150311083108368247
2015-03-11 08:31:08,078 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:08,078 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:12,979 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083113331237
2015-03-11 08:31:12,980 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083113331237', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:12,985 [salt.minion ][INFO ] Starting a new job with PID 9937
2015-03-11 08:31:12,986 [salt.minion ][INFO ] Returning information for job: 20150311083113331237
2015-03-11 08:31:13,046 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:13,047 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:18,206 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083118558304
2015-03-11 08:31:18,207 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083118558304', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:18,211 [salt.minion ][INFO ] Starting a new job with PID 9998
2015-03-11 08:31:18,212 [salt.minion ][INFO ] Returning information for job: 20150311083118558304
```
|
1.0
|
Validating minion-1 never succeeds with vagrant #2 - **VirtualBox** 4.3.24
**LinuxMint** 3.13.0-37-generic
**Docker** 1.0.1
**Vagrant** 1.7.2
*net-tools* are also installed.
```
Each machine instance has been created/updated.
Now waiting for the Salt provisioning process to complete on each machine.
This can take some time based on your network, disk, and cpu speed.
It is possible for an error to occur during Salt provision of cluster and this could loop forever.
Validating master
Validating minion-1
```
vagrant ssh minion-1 -c "ping kubernetes-master"
```
PING kubernetes-master (10.245.1.2) 56(84) bytes of data.
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=1 ttl=64 time=1.56 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=2 ttl=64 time=11.4 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=3 ttl=64 time=3.35 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=4 ttl=64 time=9.93 ms
64 bytes from kubernetes-master (10.245.1.2): icmp_seq=5 ttl=64 time=9.55 ms
```
sudo cat /var/log/salt/minion
```
2015-03-11 08:30:52,543 [salt.minion ][INFO ] Starting a new job with PID 9769
2015-03-11 08:30:52,544 [salt.minion ][INFO ] Returning information for job: 20150311083052887920
2015-03-11 08:30:52,597 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:30:52,597 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:30:55,512 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083055863950
2015-03-11 08:30:55,513 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083055863950', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:30:55,517 [salt.minion ][INFO ] Starting a new job with PID 9794
2015-03-11 08:30:55,519 [salt.minion ][INFO ] Returning information for job: 20150311083055863950
2015-03-11 08:30:56,364 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:30:56,365 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:30:56,519 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083056871176
2015-03-11 08:30:56,519 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083056871176', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:30:56,524 [salt.minion ][INFO ] Starting a new job with PID 9801
2015-03-11 08:30:56,525 [salt.minion ][INFO ] Returning information for job: 20150311083056871176
2015-03-11 08:30:57,248 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:30:57,249 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:02,750 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083103102341
2015-03-11 08:31:02,750 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083103102341', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:02,756 [salt.minion ][INFO ] Starting a new job with PID 9862
2015-03-11 08:31:02,757 [salt.minion ][INFO ] Returning information for job: 20150311083103102341
2015-03-11 08:31:02,808 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:02,809 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:07,380 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083107732564
2015-03-11 08:31:07,381 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083107732564', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:07,386 [salt.minion ][INFO ] Starting a new job with PID 9887
2015-03-11 08:31:07,387 [salt.minion ][INFO ] Returning information for job: 20150311083107732564
2015-03-11 08:31:07,478 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:07,478 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:08,016 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083108368247
2015-03-11 08:31:08,016 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083108368247', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:08,021 [salt.minion ][INFO ] Starting a new job with PID 9894
2015-03-11 08:31:08,022 [salt.minion ][INFO ] Returning information for job: 20150311083108368247
2015-03-11 08:31:08,078 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:08,078 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:12,979 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083113331237
2015-03-11 08:31:12,980 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083113331237', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:12,985 [salt.minion ][INFO ] Starting a new job with PID 9937
2015-03-11 08:31:12,986 [salt.minion ][INFO ] Returning information for job: 20150311083113331237
2015-03-11 08:31:13,046 [salt.crypt ][DEBUG ] Decrypting the current master AES key
2015-03-11 08:31:13,047 [salt.crypt ][DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
2015-03-11 08:31:18,206 [salt.minion ][INFO ] User vagrant Executing command grains.items with jid 20150311083118558304
2015-03-11 08:31:18,207 [salt.minion ][DEBUG ] Command details {'tgt_type': 'glob', 'jid': '20150311083118558304', 'tgt': '*', 'ret': '', 'user': 'vagrant', 'arg': [], 'fun': 'grains.items'}
2015-03-11 08:31:18,211 [salt.minion ][INFO ] Starting a new job with PID 9998
2015-03-11 08:31:18,212 [salt.minion ][INFO ] Returning information for job: 20150311083118558304
```
|
non_test
|
validating minion never succeeds with vagrant virtualbox linuxmint generic docker vagrant net tools are also installed each machine instance has been created updated now waiting for the salt provisioning process to complete on each machine this can take some time based on your network disk and cpu speed it is possible for an error to occur during salt provision of cluster and this could loop forever validating master validating minion vagrant ssh minion c ping kubernetes master ping kubernetes master bytes of data bytes from kubernetes master icmp seq ttl time ms bytes from kubernetes master icmp seq ttl time ms bytes from kubernetes master icmp seq ttl time ms bytes from kubernetes master icmp seq ttl time ms bytes from kubernetes master icmp seq ttl time ms sudo cat var log salt minion starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job decrypting the current master aes key loaded minion key etc salt pki minion minion pem user vagrant executing command grains items with jid command details tgt type glob jid tgt ret user vagrant arg fun grains items starting a new job with pid returning information for job
| 0
|
248,894
| 21,082,866,292
|
IssuesEvent
|
2022-04-03 06:44:43
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
roachtest: drain/early-exit-conn-wait failed
|
C-test-failure O-robot O-roachtest branch-master release-blocker
|
roachtest.drain/early-exit-conn-wait [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4771480&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4771480&tab=artifacts#/drain/early-exit-conn-wait) on master @ [71e32a6a5369dabde22043ca6ebbd11651404e5d](https://github.com/cockroachdb/cockroach/commits/71e32a6a5369dabde22043ca6ebbd11651404e5d):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/drain/early-exit-conn-wait/run_1
assertions.go:262,assertions.go:1332,require.go:1231,drain.go:224,drain.go:74,drain.go:38,test_runner.go:875:
Error Trace: drain.go:224
drain.go:74
drain.go:38
test_runner.go:875
asm_amd64.s:1581
Error: Received unexpected error:
pq: SET CLUSTER SETTING cannot be used inside a multi-statement transaction
Test: drain/early-exit-conn-wait
Messages: cannot set cluster setting
test_impl.go:259,require.go:1234,drain.go:224,drain.go:74,drain.go:38,test_runner.go:875:
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*drain/early-exit-conn-wait.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
2.0
|
roachtest: drain/early-exit-conn-wait failed - roachtest.drain/early-exit-conn-wait [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4771480&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4771480&tab=artifacts#/drain/early-exit-conn-wait) on master @ [71e32a6a5369dabde22043ca6ebbd11651404e5d](https://github.com/cockroachdb/cockroach/commits/71e32a6a5369dabde22043ca6ebbd11651404e5d):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/drain/early-exit-conn-wait/run_1
assertions.go:262,assertions.go:1332,require.go:1231,drain.go:224,drain.go:74,drain.go:38,test_runner.go:875:
Error Trace: drain.go:224
drain.go:74
drain.go:38
test_runner.go:875
asm_amd64.s:1581
Error: Received unexpected error:
pq: SET CLUSTER SETTING cannot be used inside a multi-statement transaction
Test: drain/early-exit-conn-wait
Messages: cannot set cluster setting
test_impl.go:259,require.go:1234,drain.go:224,drain.go:74,drain.go:38,test_runner.go:875:
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*drain/early-exit-conn-wait.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
test
|
roachtest drain early exit conn wait failed roachtest drain early exit conn wait with on master the test failed on branch master cloud gce test artifacts and logs in artifacts drain early exit conn wait run assertions go assertions go require go drain go drain go drain go test runner go error trace drain go drain go drain go test runner go asm s error received unexpected error pq set cluster setting cannot be used inside a multi statement transaction test drain early exit conn wait messages cannot set cluster setting test impl go require go drain go drain go drain go test runner go help see see cc cockroachdb sql experience
| 1
|
131,557
| 10,699,275,220
|
IssuesEvent
|
2019-10-23 20:34:42
|
cgeo/cgeo
|
https://api.github.com/repos/cgeo/cgeo
|
opened
|
c:geo can no longer be "ended" using back from main screen
|
Bug Field test Unverified
|
I just updated my Samsung S10 to Android 10 beta.
With current master I am not able to press the "back" key to put c:geo into background from main screen. I procedure I use regularly in the past.
It looks a bit like something happens (screen flickers, background gets grey) but the main screen remains. Other apps on my device dont have this problem.
|
1.0
|
c:geo can no longer be "ended" using back from main screen - I just updated my Samsung S10 to Android 10 beta.
With current master I am not able to press the "back" key to put c:geo into background from main screen. I procedure I use regularly in the past.
It looks a bit like something happens (screen flickers, background gets grey) but the main screen remains. Other apps on my device dont have this problem.
|
test
|
c geo can no longer be ended using back from main screen i just updated my samsung to android beta with current master i am not able to press the back key to put c geo into background from main screen i procedure i use regularly in the past it looks a bit like something happens screen flickers background gets grey but the main screen remains other apps on my device dont have this problem
| 1
|
6,535
| 2,850,045,050
|
IssuesEvent
|
2015-05-31 07:27:49
|
astralien3000/projet2016
|
https://api.github.com/repos/astralien3000/projet2016
|
opened
|
Servomoteurs hackés
|
buggybot elec soft test
|
Les servomoteurs TowerPro MG995 sont pas cher, puissants, mais ont 4 degrès de jeu dans leur asserv, ce qui n'est pas acceptable pour buggybot.
Je compte donc faire un test pour remplacer la carte de contrôle du serov par une carte perso, pour voir si je peux avoir de meilleurs résultats. Cela me permettra en plus de savoir l'angle réel du servomoteur, ce que je ne pouvais pas savoir avant.
Pour le moment, je test avec une arduino mega2560, et un driver L298N, mais il faudra déterminer une architecture électronique pour cette fonction. Je compte aussi ajouter un capteur de courant, ce qui me permettra de mesurer la puissance consommée du servo. D'ailleurs certains drivers moteurs permettent de connaitre le courant, il peut être intérressant de les utiliser !
|
1.0
|
Servomoteurs hackés - Les servomoteurs TowerPro MG995 sont pas cher, puissants, mais ont 4 degrès de jeu dans leur asserv, ce qui n'est pas acceptable pour buggybot.
Je compte donc faire un test pour remplacer la carte de contrôle du serov par une carte perso, pour voir si je peux avoir de meilleurs résultats. Cela me permettra en plus de savoir l'angle réel du servomoteur, ce que je ne pouvais pas savoir avant.
Pour le moment, je test avec une arduino mega2560, et un driver L298N, mais il faudra déterminer une architecture électronique pour cette fonction. Je compte aussi ajouter un capteur de courant, ce qui me permettra de mesurer la puissance consommée du servo. D'ailleurs certains drivers moteurs permettent de connaitre le courant, il peut être intérressant de les utiliser !
|
test
|
servomoteurs hackés les servomoteurs towerpro sont pas cher puissants mais ont degrès de jeu dans leur asserv ce qui n est pas acceptable pour buggybot je compte donc faire un test pour remplacer la carte de contrôle du serov par une carte perso pour voir si je peux avoir de meilleurs résultats cela me permettra en plus de savoir l angle réel du servomoteur ce que je ne pouvais pas savoir avant pour le moment je test avec une arduino et un driver mais il faudra déterminer une architecture électronique pour cette fonction je compte aussi ajouter un capteur de courant ce qui me permettra de mesurer la puissance consommée du servo d ailleurs certains drivers moteurs permettent de connaitre le courant il peut être intérressant de les utiliser
| 1
|
154,402
| 12,203,204,449
|
IssuesEvent
|
2020-04-30 10:12:04
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
closed
|
Saved passwords not imported from chrome browser to brave
|
OS/Windows QA/Test-Plan-Specified QA/Yes bug needs-more-info
|
<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Saved passwords not imported from chrome browser to brave
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile 1.7.x
2. Import bookmarks and settings from the welcome screen or `chrome://settings/importData`
3. Import bookmarks and saved passwords from chrome
4. Passwords are not imported from chrome to brave
## Actual result:
<!--Please add screenshots if needed-->
Saved passwords not imported from chrome browser to brave
## Expected result:
Passwords should be imported from chrome to brave
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.7.95 Chromium: 81.0.4044.92 (Official Build) (64-bit)
-- | --
Revision | e98e6f21168a55e7ba57202f56323911cd9d31d1-refs/branch-heads/4044@{#883}
OS | Windows 10 OS Version 1803 (Build 17134.1006)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/legacy_qa
|
1.0
|
Saved passwords not imported from chrome browser to brave - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Saved passwords not imported from chrome browser to brave
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile 1.7.x
2. Import bookmarks and settings from the welcome screen or `chrome://settings/importData`
3. Import bookmarks and saved passwords from chrome
4. Passwords are not imported from chrome to brave
## Actual result:
<!--Please add screenshots if needed-->
Saved passwords not imported from chrome browser to brave
## Expected result:
Passwords should be imported from chrome to brave
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.7.95 Chromium: 81.0.4044.92 (Official Build) (64-bit)
-- | --
Revision | e98e6f21168a55e7ba57202f56323911cd9d31d1-refs/branch-heads/4044@{#883}
OS | Windows 10 OS Version 1803 (Build 17134.1006)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/legacy_qa
|
test
|
saved passwords not imported from chrome browser to brave have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description saved passwords not imported from chrome browser to brave steps to reproduce clean profile x import bookmarks and settings from the welcome screen or chrome settings importdata import bookmarks and saved passwords from chrome passwords are not imported from chrome to brave actual result saved passwords not imported from chrome browser to brave expected result passwords should be imported from chrome to brave reproduces how often always brave version brave version info brave chromium official build bit revision refs branch heads os windows os version build version channel information can you reproduce this issue with the current release yes can you reproduce this issue with the beta channel yes can you reproduce this issue with the dev channel yes can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields na does the issue resolve itself when disabling brave rewards na is the issue reproducible on the latest version of chrome na miscellaneous information cc brave legacy qa
| 1
|
6,897
| 24,019,687,893
|
IssuesEvent
|
2022-09-15 06:25:24
|
AdamXweb/awesome-aussie
|
https://api.github.com/repos/AdamXweb/awesome-aussie
|
closed
|
[ADDITION] Weel
|
Awaiting Review Added to Airtable Automation from Airtable
|
### Category
Fintech
### Software to be added
Weel
### Supporting Material
URL: https://letsweel.com/
Description: Weel is an all-in-one smart corporate card and spend management platform.
Size:
HQ: Sydney
LinkedIn: https://www.linkedin.com/company/letsweel/
#### See Record on Airtable:
https://airtable.com/app0Ox7pXdrBUIn23/tblYbuZoILuVA0X3L/recrZw87yiZ7L5wIQ
|
1.0
|
[ADDITION] Weel - ### Category
Fintech
### Software to be added
Weel
### Supporting Material
URL: https://letsweel.com/
Description: Weel is an all-in-one smart corporate card and spend management platform.
Size:
HQ: Sydney
LinkedIn: https://www.linkedin.com/company/letsweel/
#### See Record on Airtable:
https://airtable.com/app0Ox7pXdrBUIn23/tblYbuZoILuVA0X3L/recrZw87yiZ7L5wIQ
|
non_test
|
weel category fintech software to be added weel supporting material url description weel is an all in one smart corporate card and spend management platform size hq sydney linkedin see record on airtable
| 0
|
27,443
| 13,249,321,977
|
IssuesEvent
|
2020-08-19 20:35:26
|
mozilla-mobile/fenix
|
https://api.github.com/repos/mozilla-mobile/fenix
|
closed
|
FNX2-13302 ⁃ Investigate cold startup regression 5/14 (15ms)
|
eng:performance
|
HANOOB:
* 5/10: 1.44284
* (intermediate dates are N/A)
* 5/14: 1.45973
We should find the root cause.
|
True
|
FNX2-13302 ⁃ Investigate cold startup regression 5/14 (15ms) - HANOOB:
* 5/10: 1.44284
* (intermediate dates are N/A)
* 5/14: 1.45973
We should find the root cause.
|
non_test
|
⁃ investigate cold startup regression hanoob intermediate dates are n a we should find the root cause
| 0
|
244,988
| 18,770,665,756
|
IssuesEvent
|
2021-11-06 19:30:59
|
terraform-aws-modules/terraform-aws-rds-aurora
|
https://api.github.com/repos/terraform-aws-modules/terraform-aws-rds-aurora
|
closed
|
Broken links in readme
|
bug help wanted good first issue documentation
|
## Description
the readme links for examples is broken when accessing from the terraform.io website
```
Autoscaling: A PostgreSQL cluster with enhanced monitoring and autoscaling enabled
Global Cluster: A PostgreSQL global cluster with clusters provisioned in two different region
MySQL: A simple MySQL cluster
PostgreSQL: A simple PostgreSQL cluster
S3 Import: A MySQL cluster created from a Percona Xtrabackup stored in S3
Serverless: Serverless PostgreSQL and MySQL clusters
```
https://registry.terraform.io/modules/terraform-aws-modules/rds-aurora/aws/latest
|
1.0
|
Broken links in readme - ## Description
the readme links for examples is broken when accessing from the terraform.io website
```
Autoscaling: A PostgreSQL cluster with enhanced monitoring and autoscaling enabled
Global Cluster: A PostgreSQL global cluster with clusters provisioned in two different region
MySQL: A simple MySQL cluster
PostgreSQL: A simple PostgreSQL cluster
S3 Import: A MySQL cluster created from a Percona Xtrabackup stored in S3
Serverless: Serverless PostgreSQL and MySQL clusters
```
https://registry.terraform.io/modules/terraform-aws-modules/rds-aurora/aws/latest
|
non_test
|
broken links in readme description the readme links for examples is broken when accessing from the terraform io website autoscaling a postgresql cluster with enhanced monitoring and autoscaling enabled global cluster a postgresql global cluster with clusters provisioned in two different region mysql a simple mysql cluster postgresql a simple postgresql cluster import a mysql cluster created from a percona xtrabackup stored in serverless serverless postgresql and mysql clusters
| 0
|
20,183
| 3,797,096,488
|
IssuesEvent
|
2016-03-23 05:19:05
|
Microsoft/vscode
|
https://api.github.com/repos/Microsoft/vscode
|
opened
|
[Debug]Error pop-up should go away once user fix all the errors and started debugging.
|
v-test
|
- VSCode Version: 0.10.12-alpha
- OS Version: Windows10
Steps to Reproduce:
1. Launch app and open a folder for "Blank Node.js TypeScript" project.
2. Click on debug icon from the view bar and set node debugger.
3. It will generate a launch.json file with some default settings.
4. Try to debug and verify error messages.
5 try to generate few more errors by updating invalid entries in launch.json.
6. Now fix all the error by updating launch.json and start debugging.
7. Verify command prompt and make sure it should not generate any error message.
Actual:
1. Debugger started and command prompt displaying message like below with error pop-up.
node --debug-brk=29322 --nolazy BlankNodeJSTypeScriptApp\server.js
Debugger listening on port 29322
2. Error message pop-up remains forever and user needs to click on close button to get rid from error popup.
3. Debug control action hidden behind the error pop-up.
Expected: Once user fixed the errors and start debugging then error pop-up should not be displayed.
|
1.0
|
[Debug]Error pop-up should go away once user fix all the errors and started debugging. - - VSCode Version: 0.10.12-alpha
- OS Version: Windows10
Steps to Reproduce:
1. Launch app and open a folder for "Blank Node.js TypeScript" project.
2. Click on debug icon from the view bar and set node debugger.
3. It will generate a launch.json file with some default settings.
4. Try to debug and verify error messages.
5 try to generate few more errors by updating invalid entries in launch.json.
6. Now fix all the error by updating launch.json and start debugging.
7. Verify command prompt and make sure it should not generate any error message.
Actual:
1. Debugger started and command prompt displaying message like below with error pop-up.
node --debug-brk=29322 --nolazy BlankNodeJSTypeScriptApp\server.js
Debugger listening on port 29322
2. Error message pop-up remains forever and user needs to click on close button to get rid from error popup.
3. Debug control action hidden behind the error pop-up.
Expected: Once user fixed the errors and start debugging then error pop-up should not be displayed.
|
test
|
error pop up should go away once user fix all the errors and started debugging vscode version alpha os version steps to reproduce launch app and open a folder for blank node js typescript project click on debug icon from the view bar and set node debugger it will generate a launch json file with some default settings try to debug and verify error messages try to generate few more errors by updating invalid entries in launch json now fix all the error by updating launch json and start debugging verify command prompt and make sure it should not generate any error message actual debugger started and command prompt displaying message like below with error pop up node debug brk nolazy blanknodejstypescriptapp server js debugger listening on port error message pop up remains forever and user needs to click on close button to get rid from error popup debug control action hidden behind the error pop up expected once user fixed the errors and start debugging then error pop up should not be displayed
| 1
|
38,083
| 8,656,115,584
|
IssuesEvent
|
2018-11-27 17:32:46
|
scipy/scipy
|
https://api.github.com/repos/scipy/scipy
|
closed
|
SciPy v1.2.0rc1 cannot be imported on Python 2.7.15
|
defect
|
My title says it all, basically.
When I try to import `scipy.stats` on Python 2.7.15 using SciPy v1.2.0rc1 (which, apparently, is on PyPI despite it being a development version), I get the following error (which was generated by Travis CI):
```
import scipy.stats
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/__init__.py:367: in <module>
from .stats import *
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/stats.py:173: in <module>
from . import distributions
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/distributions.py:10: in <module>
from ._distn_infrastructure import (entropy, rv_discrete, rv_continuous,
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/_distn_infrastructure.py:16: in <module>
from scipy.misc import doccer
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/misc/__init__.py:68: in <module>
from scipy.interpolate._pade import pade as _pade
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/interpolate/__init__.py:175: in <module>
from .interpolate import *
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/interpolate/interpolate.py:32: in <module>
from .interpnd import _ndim_coords_from_arrays
interpnd.pyx:1: in init scipy.interpolate.interpnd
???
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/__init__.py:104: in <module>
from . import transform
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/transform/__init__.py:22: in <module>
from .rotation import Rotation, Slerp
E File "/home/travis/virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/transform/rotation.py", line 1574
E SyntaxError: Non-ASCII character '\xe2' in file /home/travis/virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/transform/rotation.py on line 1575, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
```
If I attempt to do the same on Python 3.5/3.6/3.7, it works perfectly fine.
I'm using NumPy 1.15.4 and the Xenial distribution on Travis CI.
|
1.0
|
SciPy v1.2.0rc1 cannot be imported on Python 2.7.15 - My title says it all, basically.
When I try to import `scipy.stats` on Python 2.7.15 using SciPy v1.2.0rc1 (which, apparently, is on PyPI despite it being a development version), I get the following error (which was generated by Travis CI):
```
import scipy.stats
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/__init__.py:367: in <module>
from .stats import *
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/stats.py:173: in <module>
from . import distributions
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/distributions.py:10: in <module>
from ._distn_infrastructure import (entropy, rv_discrete, rv_continuous,
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/stats/_distn_infrastructure.py:16: in <module>
from scipy.misc import doccer
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/misc/__init__.py:68: in <module>
from scipy.interpolate._pade import pade as _pade
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/interpolate/__init__.py:175: in <module>
from .interpolate import *
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/interpolate/interpolate.py:32: in <module>
from .interpnd import _ndim_coords_from_arrays
interpnd.pyx:1: in init scipy.interpolate.interpnd
???
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/__init__.py:104: in <module>
from . import transform
../../../virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/transform/__init__.py:22: in <module>
from .rotation import Rotation, Slerp
E File "/home/travis/virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/transform/rotation.py", line 1574
E SyntaxError: Non-ASCII character '\xe2' in file /home/travis/virtualenv/python2.7.15/lib/python2.7/site-packages/scipy-1.2.0rc1-py2.7-linux-x86_64.egg/scipy/spatial/transform/rotation.py on line 1575, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
```
If I attempt to do the same on Python 3.5/3.6/3.7, it works perfectly fine.
I'm using NumPy 1.15.4 and the Xenial distribution on Travis CI.
|
non_test
|
scipy cannot be imported on python my title says it all basically when i try to import scipy stats on python using scipy which apparently is on pypi despite it being a development version i get the following error which was generated by travis ci import scipy stats virtualenv lib site packages scipy linux egg scipy stats init py in from stats import virtualenv lib site packages scipy linux egg scipy stats stats py in from import distributions virtualenv lib site packages scipy linux egg scipy stats distributions py in from distn infrastructure import entropy rv discrete rv continuous virtualenv lib site packages scipy linux egg scipy stats distn infrastructure py in from scipy misc import doccer virtualenv lib site packages scipy linux egg scipy misc init py in from scipy interpolate pade import pade as pade virtualenv lib site packages scipy linux egg scipy interpolate init py in from interpolate import virtualenv lib site packages scipy linux egg scipy interpolate interpolate py in from interpnd import ndim coords from arrays interpnd pyx in init scipy interpolate interpnd virtualenv lib site packages scipy linux egg scipy spatial init py in from import transform virtualenv lib site packages scipy linux egg scipy spatial transform init py in from rotation import rotation slerp e file home travis virtualenv lib site packages scipy linux egg scipy spatial transform rotation py line e syntaxerror non ascii character in file home travis virtualenv lib site packages scipy linux egg scipy spatial transform rotation py on line but no encoding declared see for details if i attempt to do the same on python it works perfectly fine i m using numpy and the xenial distribution on travis ci
| 0
|
69,406
| 17,660,330,550
|
IssuesEvent
|
2021-08-21 11:10:45
|
MovingBlocks/Terasology
|
https://api.github.com/repos/MovingBlocks/Terasology
|
opened
|
build: disentangle gradle & IDE build outputs
|
Category: Build/CI Topic: Stabilization
|
In gestalt-module 7, we can specify where to find the class files for a source module in the development workspace. This means we should be able to get rid of the `idea.outputDir` overrides in the build that have been directing IntelliJ to write its results to gradle's build directory.
I expect this to remove a major source of "you need to run gradle first" and/or "you need to clean first" workspace inconsistencies.
This is different than #4860, but they are closely related.
Part of #4015.
|
1.0
|
build: disentangle gradle & IDE build outputs - In gestalt-module 7, we can specify where to find the class files for a source module in the development workspace. This means we should be able to get rid of the `idea.outputDir` overrides in the build that have been directing IntelliJ to write its results to gradle's build directory.
I expect this to remove a major source of "you need to run gradle first" and/or "you need to clean first" workspace inconsistencies.
This is different than #4860, but they are closely related.
Part of #4015.
|
non_test
|
build disentangle gradle ide build outputs in gestalt module we can specify where to find the class files for a source module in the development workspace this means we should be able to get rid of the idea outputdir overrides in the build that have been directing intellij to write its results to gradle s build directory i expect this to remove a major source of you need to run gradle first and or you need to clean first workspace inconsistencies this is different than but they are closely related part of
| 0
|
7,461
| 3,984,059,813
|
IssuesEvent
|
2016-05-07 00:03:40
|
Linuxbrew/linuxbrew
|
https://api.github.com/repos/Linuxbrew/linuxbrew
|
closed
|
Problems installing on Chrome OS
|
build-error help wanted
|
I have tried installing Linuxbrew on Chrome OS (https://goo.gl/gUFvzc) multiple times already, but it doesn't work. The installation fails at line "brew install hello && brew test hello && brew remove hello". When I run the command it gives me the error message "/bin/bash: symbol lookup error: /bin/bash: undefined symbol: rl_signal_event_hook". I have also tried running "brew update" but running any brew command gives me the same error. Chromebrew works with no problem, though.
If it helps, my Chromebook info is the following:
Version 52.0.2715.0 canary (64-bit)
Platform 8240.0.0 (Official Build) canary-channel falco
Firmware Google_Falco.4389.92.0
|
1.0
|
Problems installing on Chrome OS - I have tried installing Linuxbrew on Chrome OS (https://goo.gl/gUFvzc) multiple times already, but it doesn't work. The installation fails at line "brew install hello && brew test hello && brew remove hello". When I run the command it gives me the error message "/bin/bash: symbol lookup error: /bin/bash: undefined symbol: rl_signal_event_hook". I have also tried running "brew update" but running any brew command gives me the same error. Chromebrew works with no problem, though.
If it helps, my Chromebook info is the following:
Version 52.0.2715.0 canary (64-bit)
Platform 8240.0.0 (Official Build) canary-channel falco
Firmware Google_Falco.4389.92.0
|
non_test
|
problems installing on chrome os i have tried installing linuxbrew on chrome os multiple times already but it doesn t work the installation fails at line brew install hello brew test hello brew remove hello when i run the command it gives me the error message bin bash symbol lookup error bin bash undefined symbol rl signal event hook i have also tried running brew update but running any brew command gives me the same error chromebrew works with no problem though if it helps my chromebook info is the following version canary bit platform official build canary channel falco firmware google falco
| 0
|
68,733
| 13,174,050,407
|
IssuesEvent
|
2020-08-11 21:33:09
|
CeuAzul/ADR
|
https://api.github.com/repos/CeuAzul/ADR
|
closed
|
Geometry variables are hardcoded in Aerodynamic_surface
|
2.x? code structure feature
|
Instead of having a hardcoded number of sections, we could have an iterable array of key-value pairs associated with each aerodynamic section. This way we could have any number of sections on each surface, extending it's analysis capabilities.
This also requires that the plane parameters are instantiated and passed in a different way.
|
1.0
|
Geometry variables are hardcoded in Aerodynamic_surface - 
Instead of having a hardcoded number of sections, we could have an iterable array of key-value pairs associated with each aerodynamic section. This way we could have any number of sections on each surface, extending it's analysis capabilities.
This also requires that the plane parameters are instantiated and passed in a different way.
|
non_test
|
geometry variables are hardcoded in aerodynamic surface instead of having a hardcoded number of sections we could have an iterable array of key value pairs associated with each aerodynamic section this way we could have any number of sections on each surface extending it s analysis capabilities this also requires that the plane parameters are instantiated and passed in a different way
| 0
|
386,987
| 26,709,834,822
|
IssuesEvent
|
2023-01-27 22:09:17
|
elastic/design-system-team
|
https://api.github.com/repos/elastic/design-system-team
|
opened
|
Guidelines for search UIs
|
Documentation KUI
|
## Design System work request template
Use this template to request additions or changes to design system documentation. The Design System (DS) team will triage requests, prioritze, and determine deliverables. Completed work will be broadly communicated through the DS newsletter with additional follow-ups to downstream teams impacted by the work.
-----
**As a requestor, complete the following section**
-----
### 1️⃣ What would you like to see added or updated in the design system?
_Key output of this work_
Guidelines establishing UI and UX guidelines for search experiences.
### 2️⃣ How will this be applied? Where do issues exist today?
_Describe the work needed in terms of the desired outcome. Include sample screenshots, if applicable_
Elastic. You know, for Search! 😬
Unsurprisingly, many of our UIs offer some form of search experience. From application to application, they could be more consistent and ought to provide similar capabilities where possible. These guidelines could consider things like loading indicators, type aheads, syntax handling for various languages (KQL, etc.), disabled and active states, etc.
Side note: how does Unified Search handle these? should it be updated too?
[screenshot(s) of the current state]
### 3️⃣ Which projects or areas of our products will be impacted?
_Identify any upcoming projects or existing views and associated teams that would benefit from this work. Upon completion, the Design Systems team can assist in ensuring they are implemented and adhered to._
Search is ubiquitous across Kibana. Implementation and adherence would need to be governed through many channels such as direct education, design reviews, scorecard findings, and shared component implementation (e.g. Unified Search).
-----
**The deliverables section will be completed by the Design System team during backlog grooming**
-----
### Target deliverables
- [x] UI designs (patterns with EUI components outlined)
- [x] Figma library updates
- [ ] EUI component library updates
- [x] Usage (UX) guidelines
- [x] Writing guidelines
- [ ] Data viz guidelines
- [ ] Research needed
- Accessibility review (required)
- Update design system docs site (required)
|
1.0
|
Guidelines for search UIs - ## Design System work request template
Use this template to request additions or changes to design system documentation. The Design System (DS) team will triage requests, prioritze, and determine deliverables. Completed work will be broadly communicated through the DS newsletter with additional follow-ups to downstream teams impacted by the work.
-----
**As a requestor, complete the following section**
-----
### 1️⃣ What would you like to see added or updated in the design system?
_Key output of this work_
Guidelines establishing UI and UX guidelines for search experiences.
### 2️⃣ How will this be applied? Where do issues exist today?
_Describe the work needed in terms of the desired outcome. Include sample screenshots, if applicable_
Elastic. You know, for Search! 😬
Unsurprisingly, many of our UIs offer some form of search experience. From application to application, they could be more consistent and ought to provide similar capabilities where possible. These guidelines could consider things like loading indicators, type aheads, syntax handling for various languages (KQL, etc.), disabled and active states, etc.
Side note: how does Unified Search handle these? should it be updated too?
[screenshot(s) of the current state]
### 3️⃣ Which projects or areas of our products will be impacted?
_Identify any upcoming projects or existing views and associated teams that would benefit from this work. Upon completion, the Design Systems team can assist in ensuring they are implemented and adhered to._
Search is ubiquitous across Kibana. Implementation and adherence would need to be governed through many channels such as direct education, design reviews, scorecard findings, and shared component implementation (e.g. Unified Search).
-----
**The deliverables section will be completed by the Design System team during backlog grooming**
-----
### Target deliverables
- [x] UI designs (patterns with EUI components outlined)
- [x] Figma library updates
- [ ] EUI component library updates
- [x] Usage (UX) guidelines
- [x] Writing guidelines
- [ ] Data viz guidelines
- [ ] Research needed
- Accessibility review (required)
- Update design system docs site (required)
|
non_test
|
guidelines for search uis design system work request template use this template to request additions or changes to design system documentation the design system ds team will triage requests prioritze and determine deliverables completed work will be broadly communicated through the ds newsletter with additional follow ups to downstream teams impacted by the work as a requestor complete the following section ️⃣ what would you like to see added or updated in the design system key output of this work guidelines establishing ui and ux guidelines for search experiences ️⃣ how will this be applied where do issues exist today describe the work needed in terms of the desired outcome include sample screenshots if applicable elastic you know for search 😬 unsurprisingly many of our uis offer some form of search experience from application to application they could be more consistent and ought to provide similar capabilities where possible these guidelines could consider things like loading indicators type aheads syntax handling for various languages kql etc disabled and active states etc side note how does unified search handle these should it be updated too ️⃣ which projects or areas of our products will be impacted identify any upcoming projects or existing views and associated teams that would benefit from this work upon completion the design systems team can assist in ensuring they are implemented and adhered to search is ubiquitous across kibana implementation and adherence would need to be governed through many channels such as direct education design reviews scorecard findings and shared component implementation e g unified search the deliverables section will be completed by the design system team during backlog grooming target deliverables ui designs patterns with eui components outlined figma library updates eui component library updates usage ux guidelines writing guidelines data viz guidelines research needed accessibility review required update design system docs site required
| 0
|
80,099
| 15,586,265,551
|
IssuesEvent
|
2021-03-18 01:32:51
|
peterwkc85/Spring_petclinic
|
https://api.github.com/repos/peterwkc85/Spring_petclinic
|
opened
|
CVE-2020-36180 (High) detected in jackson-databind-2.9.8.jar
|
security vulnerability
|
## CVE-2020-36180 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: Spring_petclinic/spring-petclinic-master/spring-petclinic-master/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-actuator-2.1.4.RELEASE.jar (Root Library)
- spring-boot-actuator-autoconfigure-2.1.4.RELEASE.jar
- :x: **jackson-databind-2.9.8.jar** (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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.
<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36180>CVE-2020-36180</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/3004">https://github.com/FasterXML/jackson-databind/issues/3004</a></p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</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-36180 (High) detected in jackson-databind-2.9.8.jar - ## CVE-2020-36180 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: Spring_petclinic/spring-petclinic-master/spring-petclinic-master/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-actuator-2.1.4.RELEASE.jar (Root Library)
- spring-boot-actuator-autoconfigure-2.1.4.RELEASE.jar
- :x: **jackson-databind-2.9.8.jar** (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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.
<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36180>CVE-2020-36180</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/3004">https://github.com/FasterXML/jackson-databind/issues/3004</a></p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file spring petclinic spring petclinic master spring petclinic master pom xml path to vulnerable library root repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter actuator release jar root library spring boot actuator autoconfigure release jar x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache commons cpdsadapter driveradaptercpds publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind step up your open source security game with whitesource
| 0
|
95,489
| 27,524,741,735
|
IssuesEvent
|
2023-03-06 17:14:04
|
lbl-srg/modelica-buildings
|
https://api.github.com/repos/lbl-srg/modelica-buildings
|
closed
|
Add SequenceBinary in package CDL.Integers
|
OpenBuildingControl
|
This issue is to add `SequenceBinary` blocks as discussed in ASHRAE231p meeting:
- [ ] output the total number of stages `y` that should be ON. It compares the input `u` with the each stage threshold. The block has a parameter `maxSta` which specifies maximum stages that could be ON. Each stage threshold are calculated by evenly distributing the [0, 1] to `maxSta`sections. For example, if the `maxSta=5`,
- when $u \in (0.0, 0.2] $, then `y=1`,
- when $u \in (0.2, 0.4] $, then `y=2`,
- when $u \in (0.4, 0.6] $, then `y=3`,
- when $u \in (0.6, 0.8] $, then `y=4`,
- when $u \in (0.8, 1.0] $, then `y=5`.
- [ ] It also has a minimum ON/OFF time of each stage, to avoid frequently stage change. One hysteresis will also be used to avoid chattering.
|
1.0
|
Add SequenceBinary in package CDL.Integers - This issue is to add `SequenceBinary` blocks as discussed in ASHRAE231p meeting:
- [ ] output the total number of stages `y` that should be ON. It compares the input `u` with the each stage threshold. The block has a parameter `maxSta` which specifies maximum stages that could be ON. Each stage threshold are calculated by evenly distributing the [0, 1] to `maxSta`sections. For example, if the `maxSta=5`,
- when $u \in (0.0, 0.2] $, then `y=1`,
- when $u \in (0.2, 0.4] $, then `y=2`,
- when $u \in (0.4, 0.6] $, then `y=3`,
- when $u \in (0.6, 0.8] $, then `y=4`,
- when $u \in (0.8, 1.0] $, then `y=5`.
- [ ] It also has a minimum ON/OFF time of each stage, to avoid frequently stage change. One hysteresis will also be used to avoid chattering.
|
non_test
|
add sequencebinary in package cdl integers this issue is to add sequencebinary blocks as discussed in meeting output the total number of stages y that should be on it compares the input u with the each stage threshold the block has a parameter maxsta which specifies maximum stages that could be on each stage threshold are calculated by evenly distributing the to maxsta sections for example if the maxsta when u in then y when u in then y when u in then y when u in then y when u in then y it also has a minimum on off time of each stage to avoid frequently stage change one hysteresis will also be used to avoid chattering
| 0
|
121,561
| 12,129,089,159
|
IssuesEvent
|
2020-04-22 21:46:53
|
cte-bits-goa/AutoMailer
|
https://api.github.com/repos/cte-bits-goa/AutoMailer
|
opened
|
Create Documentation
|
documentation
|
The codes are well maintained and modularized.
Add documentation Support.
|
1.0
|
Create Documentation - The codes are well maintained and modularized.
Add documentation Support.
|
non_test
|
create documentation the codes are well maintained and modularized add documentation support
| 0
|
306,228
| 26,449,159,177
|
IssuesEvent
|
2023-01-16 09:53:48
|
dart-lang/co19
|
https://api.github.com/repos/dart-lang/co19
|
closed
|
LanguageFeatures/Patterns/variable_A02_t01
|
bad-test
|
This test expects `Square.area` and `Rectangle.area` which is `Unit` to be printed as `n.00`, but `Unit.toString()` removes `.00`:
https://github.com/dart-lang/co19/blob/cd1d3fd226fdd6693d6d33986dbdb8416f7e81a2/LanguageFeatures/Patterns/variable_A02_t01.dart#L230-L247
https://github.com/dart-lang/co19/blob/cd1d3fd226fdd6693d6d33986dbdb8416f7e81a2/LanguageFeatures/Patterns/variable_A02_t01.dart#L146-L147
https://github.com/dart-lang/co19/blob/cd1d3fd226fdd6693d6d33986dbdb8416f7e81a2/LanguageFeatures/Patterns/patterns_lib.dart#L83
|
1.0
|
LanguageFeatures/Patterns/variable_A02_t01 - This test expects `Square.area` and `Rectangle.area` which is `Unit` to be printed as `n.00`, but `Unit.toString()` removes `.00`:
https://github.com/dart-lang/co19/blob/cd1d3fd226fdd6693d6d33986dbdb8416f7e81a2/LanguageFeatures/Patterns/variable_A02_t01.dart#L230-L247
https://github.com/dart-lang/co19/blob/cd1d3fd226fdd6693d6d33986dbdb8416f7e81a2/LanguageFeatures/Patterns/variable_A02_t01.dart#L146-L147
https://github.com/dart-lang/co19/blob/cd1d3fd226fdd6693d6d33986dbdb8416f7e81a2/LanguageFeatures/Patterns/patterns_lib.dart#L83
|
test
|
languagefeatures patterns variable this test expects square area and rectangle area which is unit to be printed as n but unit tostring removes
| 1
|
278,276
| 24,141,407,818
|
IssuesEvent
|
2022-09-21 15:05:27
|
r-lib/testthat
|
https://api.github.com/repos/r-lib/testthat
|
closed
|
Non-ASCII characters in test files lead to parsing errors on Windows
|
bug tests :blue_book:
|
This seems to be related to #1496 . I'm getting parsing errors on Windows when `test_file()`ing files that include non-ASCII characters, but which are in UTF-8. The attached file [the-test.zip](https://github.com/r-lib/testthat/files/8253486/the-test.zip) is an R script, just rename to extension `.R`. Running `enca -L polish` on that file will tell that it is indeed in UTF-8.
I'm getting:
```
testthat::test_file("the-test.R")
== Testing the-test.R ==============================================================================================
[ FAIL 0 | WARN 0 | SKIP 0 | PASS 0 ]Error in parse(con, n = -1, srcfile = srcfile, encoding = "UTF-8") :
the-test.R:1:24: unexpected $end
1: d <- tibble::tibble(ImiÄ™
^
```
so clearly some encoding issues. Digging further points to parsing:
```
> traceback()
12: parse(con, n = -1, srcfile = srcfile, encoding = "UTF-8")
11: source_file(path, child_env(env), wrap = wrap)
10: FUN(X[[i]], ...)
9: lapply(test_paths, test_one_file, env = env, wrap = wrap)
8: doTryCatch(return(expr), name, parentenv, handler)
7: tryCatchOne(expr, names, parentenv, handlers[[1L]])
6: tryCatchList(expr, classes, parentenv, handlers)
5: tryCatch(code, testthat_abort_reporter = function(cnd) {
cat(conditionMessage(cnd), "\n")
...
4: with_reporter(reporters$multi, lapply(test_paths, test_one_file,
env = env, wrap = wrap))
3: test_files(test_dir = test_dir, test_package = test_package,
test_paths = test_paths, load_helpers = load_helpers, reporter = reporter,
...
2: test_files(test_dir = dirname(path), test_package = package,
test_paths = basename(path), reporter = reporter, ...)
1: testthat::test_file("the-test.R")
```
Interstingly the test file seems to be read correctly by this line (did some tracing and inspected the result)
https://github.com/r-lib/testthat/blob/22a68dd85b65c95173424760a78955b6c55f3848/R/source.R#L18
but the call to `parse()` two steps later fails, even though `encoding` is set to UTF-8 everywhere (on the connection and for `parse()`).
<details>
<summary>Session info</summary>
- Session info ----------------------------------------------------------------------------------------------------
setting value
version R version 4.1.3 (2022-03-10)
os Windows 10 x64 (build 19042)
system x86_64, mingw32
ui RStudio
language (EN)
collate Polish_Poland.1250
ctype Polish_Poland.1250
tz Europe/Warsaw
date 2022-03-15
rstudio 2021.09.0+351 Ghost Orchid (desktop)
pandoc 2.17.1.1 @ C:\\PROGRA~3\\CHOCOL~1\\bin\\pandoc.exe
- Packages --------------------------------------------------------------------------------------------------------
package * version date (UTC) lib source
brio 1.1.3 2021-11-30 [1] CRAN (R 4.1.2)
cli 3.2.0 2022-02-14 [1] CRAN (R 4.1.2)
crayon 1.5.0 2022-02-14 [1] CRAN (R 4.1.2)
desc 1.4.1 2022-03-06 [1] CRAN (R 4.1.2)
ellipsis 0.3.2 2021-04-29 [1] CRAN (R 4.1.0)
fansi 1.0.2 2022-01-14 [1] CRAN (R 4.1.2)
glue 1.6.2 2022-02-24 [1] CRAN (R 4.1.2)
lifecycle 1.0.1 2021-09-24 [1] CRAN (R 4.1.1)
magrittr 2.0.2 2022-01-26 [1] CRAN (R 4.1.2)
pillar 1.7.0 2022-02-01 [1] CRAN (R 4.1.2)
pkgconfig 2.0.3 2019-09-22 [1] CRAN (R 4.1.0)
pkgload 1.2.4 2021-11-30 [1] CRAN (R 4.1.1)
R6 2.5.1 2021-08-19 [1] CRAN (R 4.1.1)
rlang 1.0.2 2022-03-04 [1] CRAN (R 4.1.2)
rprojroot 2.0.2 2020-11-15 [1] CRAN (R 4.1.0)
rsthemes 0.2.1.9000 2021-10-13 [1] Github (gadenbuie/rsthemes@19299e5)
rstudioapi 0.13 2020-11-12 [1] CRAN (R 4.1.0)
sessioninfo 1.2.2 2021-12-06 [1] CRAN (R 4.1.2)
testthat * 3.1.3 2022-03-15 [1] Github (r-lib/testthat@22a68dd)
tibble 3.1.6 2021-11-07 [1] CRAN (R 4.1.1)
utf8 1.2.2 2021-07-24 [1] CRAN (R 4.1.0)
vctrs 0.3.8 2021-04-29 [1] CRAN (R 4.1.0)
withr 2.5.0 2022-03-03 [1] CRAN (R 4.1.2)
[1] C:/Users/mbojanowski/Documents/R/library/x86_64-w64-mingw32/4.1
[2] C:/Users/mbojanowski/Documents/Programs/R-4.1.3/library
-------------------------------------------------------------------------------------------------------------------
</details>
|
1.0
|
Non-ASCII characters in test files lead to parsing errors on Windows - This seems to be related to #1496 . I'm getting parsing errors on Windows when `test_file()`ing files that include non-ASCII characters, but which are in UTF-8. The attached file [the-test.zip](https://github.com/r-lib/testthat/files/8253486/the-test.zip) is an R script, just rename to extension `.R`. Running `enca -L polish` on that file will tell that it is indeed in UTF-8.
I'm getting:
```
testthat::test_file("the-test.R")
== Testing the-test.R ==============================================================================================
[ FAIL 0 | WARN 0 | SKIP 0 | PASS 0 ]Error in parse(con, n = -1, srcfile = srcfile, encoding = "UTF-8") :
the-test.R:1:24: unexpected $end
1: d <- tibble::tibble(ImiÄ™
^
```
so clearly some encoding issues. Digging further points to parsing:
```
> traceback()
12: parse(con, n = -1, srcfile = srcfile, encoding = "UTF-8")
11: source_file(path, child_env(env), wrap = wrap)
10: FUN(X[[i]], ...)
9: lapply(test_paths, test_one_file, env = env, wrap = wrap)
8: doTryCatch(return(expr), name, parentenv, handler)
7: tryCatchOne(expr, names, parentenv, handlers[[1L]])
6: tryCatchList(expr, classes, parentenv, handlers)
5: tryCatch(code, testthat_abort_reporter = function(cnd) {
cat(conditionMessage(cnd), "\n")
...
4: with_reporter(reporters$multi, lapply(test_paths, test_one_file,
env = env, wrap = wrap))
3: test_files(test_dir = test_dir, test_package = test_package,
test_paths = test_paths, load_helpers = load_helpers, reporter = reporter,
...
2: test_files(test_dir = dirname(path), test_package = package,
test_paths = basename(path), reporter = reporter, ...)
1: testthat::test_file("the-test.R")
```
Interstingly the test file seems to be read correctly by this line (did some tracing and inspected the result)
https://github.com/r-lib/testthat/blob/22a68dd85b65c95173424760a78955b6c55f3848/R/source.R#L18
but the call to `parse()` two steps later fails, even though `encoding` is set to UTF-8 everywhere (on the connection and for `parse()`).
<details>
<summary>Session info</summary>
- Session info ----------------------------------------------------------------------------------------------------
setting value
version R version 4.1.3 (2022-03-10)
os Windows 10 x64 (build 19042)
system x86_64, mingw32
ui RStudio
language (EN)
collate Polish_Poland.1250
ctype Polish_Poland.1250
tz Europe/Warsaw
date 2022-03-15
rstudio 2021.09.0+351 Ghost Orchid (desktop)
pandoc 2.17.1.1 @ C:\\PROGRA~3\\CHOCOL~1\\bin\\pandoc.exe
- Packages --------------------------------------------------------------------------------------------------------
package * version date (UTC) lib source
brio 1.1.3 2021-11-30 [1] CRAN (R 4.1.2)
cli 3.2.0 2022-02-14 [1] CRAN (R 4.1.2)
crayon 1.5.0 2022-02-14 [1] CRAN (R 4.1.2)
desc 1.4.1 2022-03-06 [1] CRAN (R 4.1.2)
ellipsis 0.3.2 2021-04-29 [1] CRAN (R 4.1.0)
fansi 1.0.2 2022-01-14 [1] CRAN (R 4.1.2)
glue 1.6.2 2022-02-24 [1] CRAN (R 4.1.2)
lifecycle 1.0.1 2021-09-24 [1] CRAN (R 4.1.1)
magrittr 2.0.2 2022-01-26 [1] CRAN (R 4.1.2)
pillar 1.7.0 2022-02-01 [1] CRAN (R 4.1.2)
pkgconfig 2.0.3 2019-09-22 [1] CRAN (R 4.1.0)
pkgload 1.2.4 2021-11-30 [1] CRAN (R 4.1.1)
R6 2.5.1 2021-08-19 [1] CRAN (R 4.1.1)
rlang 1.0.2 2022-03-04 [1] CRAN (R 4.1.2)
rprojroot 2.0.2 2020-11-15 [1] CRAN (R 4.1.0)
rsthemes 0.2.1.9000 2021-10-13 [1] Github (gadenbuie/rsthemes@19299e5)
rstudioapi 0.13 2020-11-12 [1] CRAN (R 4.1.0)
sessioninfo 1.2.2 2021-12-06 [1] CRAN (R 4.1.2)
testthat * 3.1.3 2022-03-15 [1] Github (r-lib/testthat@22a68dd)
tibble 3.1.6 2021-11-07 [1] CRAN (R 4.1.1)
utf8 1.2.2 2021-07-24 [1] CRAN (R 4.1.0)
vctrs 0.3.8 2021-04-29 [1] CRAN (R 4.1.0)
withr 2.5.0 2022-03-03 [1] CRAN (R 4.1.2)
[1] C:/Users/mbojanowski/Documents/R/library/x86_64-w64-mingw32/4.1
[2] C:/Users/mbojanowski/Documents/Programs/R-4.1.3/library
-------------------------------------------------------------------------------------------------------------------
</details>
|
test
|
non ascii characters in test files lead to parsing errors on windows this seems to be related to i m getting parsing errors on windows when test file ing files that include non ascii characters but which are in utf the attached file is an r script just rename to extension r running enca l polish on that file will tell that it is indeed in utf i m getting testthat test file the test r testing the test r error in parse con n srcfile srcfile encoding utf the test r unexpected end d tibble tibble imiä™ so clearly some encoding issues digging further points to parsing traceback parse con n srcfile srcfile encoding utf source file path child env env wrap wrap fun x lapply test paths test one file env env wrap wrap dotrycatch return expr name parentenv handler trycatchone expr names parentenv handlers trycatchlist expr classes parentenv handlers trycatch code testthat abort reporter function cnd cat conditionmessage cnd n with reporter reporters multi lapply test paths test one file env env wrap wrap test files test dir test dir test package test package test paths test paths load helpers load helpers reporter reporter test files test dir dirname path test package package test paths basename path reporter reporter testthat test file the test r interstingly the test file seems to be read correctly by this line did some tracing and inspected the result but the call to parse two steps later fails even though encoding is set to utf everywhere on the connection and for parse session info session info setting value version r version os windows build system ui rstudio language en collate polish poland ctype polish poland tz europe warsaw date rstudio ghost orchid desktop pandoc c progra chocol bin pandoc exe packages package version date utc lib source brio cran r cli cran r crayon cran r desc cran r ellipsis cran r fansi cran r glue cran r lifecycle cran r magrittr cran r pillar cran r pkgconfig cran r pkgload cran r cran r rlang cran r rprojroot cran r rsthemes github gadenbuie rsthemes rstudioapi cran r sessioninfo cran r testthat github r lib testthat tibble cran r cran r vctrs cran r withr cran r c users mbojanowski documents r library c users mbojanowski documents programs r library
| 1
|
102,209
| 21,932,743,868
|
IssuesEvent
|
2022-05-23 11:13:36
|
Onelinerhub/onelinerhub
|
https://api.github.com/repos/Onelinerhub/onelinerhub
|
closed
|
Short solution needed: "chrome headless quit" (chrome-headless)
|
help wanted good first issue code chrome-headless
|
Please help us write most modern and shortest code solution for this issue:
**chrome headless quit** (technology: [chrome-headless](https://onelinerhub.com/chrome-headless))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request.
|
1.0
|
Short solution needed: "chrome headless quit" (chrome-headless) - Please help us write most modern and shortest code solution for this issue:
**chrome headless quit** (technology: [chrome-headless](https://onelinerhub.com/chrome-headless))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request.
|
non_test
|
short solution needed chrome headless quit chrome headless please help us write most modern and shortest code solution for this issue chrome headless quit technology fast way just write the code solution in the comments prefered way create with a new code file inside don t forget to explain solution link to this issue in comments of pull request
| 0
|
40,813
| 8,851,278,694
|
IssuesEvent
|
2019-01-08 15:23:50
|
firasdib/Regex101
|
https://api.github.com/repos/firasdib/Regex101
|
closed
|
Powershell Code-Generator
|
code generator help wanted
|
It would be really great to have a **Code-Generator for Windows Powershell's Select-String** -pattern command. It costs a lot of time to fiddle out how to write/escape my regexes working with regex101.com to make them work with powershell...
See eg https://regex101.com/r/sXVAsi/2 -> It works with the website, but not with Powershell...
|
1.0
|
Powershell Code-Generator - It would be really great to have a **Code-Generator for Windows Powershell's Select-String** -pattern command. It costs a lot of time to fiddle out how to write/escape my regexes working with regex101.com to make them work with powershell...
See eg https://regex101.com/r/sXVAsi/2 -> It works with the website, but not with Powershell...
|
non_test
|
powershell code generator it would be really great to have a code generator for windows powershell s select string pattern command it costs a lot of time to fiddle out how to write escape my regexes working with com to make them work with powershell see eg it works with the website but not with powershell
| 0
|
130,089
| 18,017,963,334
|
IssuesEvent
|
2021-09-16 15:47:41
|
OHS-Hosting-Infrastructure/complaint-tracker
|
https://api.github.com/repos/OHS-Hosting-Infrastructure/complaint-tracker
|
opened
|
Task from 133: Add error handling for HSES data
|
needs design task
|
This task is part of #133 : incorporating HSES staging data in the complaint tracker
This task is scoped to:
- [ ] handling different types of errors in response from HSES gracefully
- [ ] logging response
- [ ] providing the user with friendly information
We will require design for potential messages to replace "Placeholder text for the message, including any mitigation steps we need to share," which is currently what displays for no results.
|
1.0
|
Task from 133: Add error handling for HSES data - This task is part of #133 : incorporating HSES staging data in the complaint tracker
This task is scoped to:
- [ ] handling different types of errors in response from HSES gracefully
- [ ] logging response
- [ ] providing the user with friendly information
We will require design for potential messages to replace "Placeholder text for the message, including any mitigation steps we need to share," which is currently what displays for no results.
|
non_test
|
task from add error handling for hses data this task is part of incorporating hses staging data in the complaint tracker this task is scoped to handling different types of errors in response from hses gracefully logging response providing the user with friendly information we will require design for potential messages to replace placeholder text for the message including any mitigation steps we need to share which is currently what displays for no results
| 0
|
184,802
| 14,289,965,911
|
IssuesEvent
|
2020-11-23 20:06:49
|
github-vet/rangeclosure-findings
|
https://api.github.com/repos/github-vet/rangeclosure-findings
|
closed
|
mit-pdos/biscuit: src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go; 20 LoC
|
fresh small test
|
Found a possible issue in [mit-pdos/biscuit](https://www.github.com/mit-pdos/biscuit) at [src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go](https://github.com/mit-pdos/biscuit/blob/70d8496d1d31ec332f09200184229b743d433d45/src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go#L114-L133)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/mit-pdos/biscuit/blob/70d8496d1d31ec332f09200184229b743d433d45/src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go#L114-L133)
<details>
<summary>Click here to show the 20 line(s) of Go which triggered the analyzer.</summary>
```go
for _, c := range testcases {
if c.needDot && !haveDot {
continue
}
path := server.URL + c.path
for count := 0; count < 2; count++ {
wg.Add(1)
go func() {
defer wg.Done()
res, err := http.Get(path)
if err != nil {
t.Error("could not fetch", c.path, err)
return
}
if _, err = ioutil.ReadAll(res.Body); err != nil {
t.Error("could not read response", c.path, err)
}
}()
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 70d8496d1d31ec332f09200184229b743d433d45
|
1.0
|
mit-pdos/biscuit: src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go; 20 LoC -
Found a possible issue in [mit-pdos/biscuit](https://www.github.com/mit-pdos/biscuit) at [src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go](https://github.com/mit-pdos/biscuit/blob/70d8496d1d31ec332f09200184229b743d433d45/src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go#L114-L133)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/mit-pdos/biscuit/blob/70d8496d1d31ec332f09200184229b743d433d45/src/cmd/vendor/github.com/google/pprof/internal/driver/webui_test.go#L114-L133)
<details>
<summary>Click here to show the 20 line(s) of Go which triggered the analyzer.</summary>
```go
for _, c := range testcases {
if c.needDot && !haveDot {
continue
}
path := server.URL + c.path
for count := 0; count < 2; count++ {
wg.Add(1)
go func() {
defer wg.Done()
res, err := http.Get(path)
if err != nil {
t.Error("could not fetch", c.path, err)
return
}
if _, err = ioutil.ReadAll(res.Body); err != nil {
t.Error("could not read response", c.path, err)
}
}()
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 70d8496d1d31ec332f09200184229b743d433d45
|
test
|
mit pdos biscuit src cmd vendor github com google pprof internal driver webui test go loc found a possible issue in at the below snippet of go code triggered static analysis which searches for goroutines and or defer statements which capture loop variables click here to show the line s of go which triggered the analyzer go for c range testcases if c needdot havedot continue path server url c path for count count count wg add go func defer wg done res err http get path if err nil t error could not fetch c path err return if err ioutil readall res body err nil t error could not read response c path err leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
695,890
| 23,875,618,957
|
IssuesEvent
|
2022-09-07 18:44:51
|
lightningrodlabs/rea-playspace
|
https://api.github.com/repos/lightningrodlabs/rea-playspace
|
closed
|
Feature: add signals for changes so multiple people can see changes and aren't working on stale data
|
priority current sprint
|
Currently, we aren't sending signals for changes. This means that if multiple people are working on a plan, each time they make a change they overwrite the version on the DHT with their own local copy. If one person deletes something and another person edits their now stale in-memory copy, they will overwrite the deletion.
|
1.0
|
Feature: add signals for changes so multiple people can see changes and aren't working on stale data - Currently, we aren't sending signals for changes. This means that if multiple people are working on a plan, each time they make a change they overwrite the version on the DHT with their own local copy. If one person deletes something and another person edits their now stale in-memory copy, they will overwrite the deletion.
|
non_test
|
feature add signals for changes so multiple people can see changes and aren t working on stale data currently we aren t sending signals for changes this means that if multiple people are working on a plan each time they make a change they overwrite the version on the dht with their own local copy if one person deletes something and another person edits their now stale in memory copy they will overwrite the deletion
| 0
|
32,076
| 13,755,819,726
|
IssuesEvent
|
2020-10-06 18:58:28
|
cityofaustin/atd-data-tech
|
https://api.github.com/repos/cityofaustin/atd-data-tech
|
closed
|
Create Public ASMP WebApp
|
Need: 2-Should Have Service: Geo Type: Data Type: Map Request Workgroup: SDD
|
Previously an ask of Cole to:
> Update any public viewer that included the AMATP dataset with the ASMP street network, like the Property Profile tool.
But instead we'll create a separate ASMP viewer.
*Migrated from [atd-geospatial #132](https://github.com/cityofaustin/atd-geospatial/issues/132)*
|
1.0
|
Create Public ASMP WebApp - Previously an ask of Cole to:
> Update any public viewer that included the AMATP dataset with the ASMP street network, like the Property Profile tool.
But instead we'll create a separate ASMP viewer.
*Migrated from [atd-geospatial #132](https://github.com/cityofaustin/atd-geospatial/issues/132)*
|
non_test
|
create public asmp webapp previously an ask of cole to update any public viewer that included the amatp dataset with the asmp street network like the property profile tool but instead we ll create a separate asmp viewer migrated from
| 0
|
400,295
| 11,772,065,472
|
IssuesEvent
|
2020-03-16 02:32:17
|
bluecherrydvr/bluecherry-apps
|
https://api.github.com/repos/bluecherrydvr/bluecherry-apps
|
opened
|
IP camera detection no longer works
|
Bug ONVIF Priority High
|
Seems to be a problem with the latest nmap version (7.x). 6.x did wsdd discovery better.
|
1.0
|
IP camera detection no longer works - Seems to be a problem with the latest nmap version (7.x). 6.x did wsdd discovery better.
|
non_test
|
ip camera detection no longer works seems to be a problem with the latest nmap version x x did wsdd discovery better
| 0
|
13,427
| 3,332,536,656
|
IssuesEvent
|
2015-11-11 20:34:39
|
Automattic/_s
|
https://api.github.com/repos/Automattic/_s
|
closed
|
is_search check in jetpack infinite render
|
Needs Testing Second Opinion
|
Shouldn't there be `is_search` check in `inc/jetpack.php` `_s_infinite_scroll_render` function?
Something like this:
```
if ( is_search() ) :
get_template_part( 'template-parts/content', 'search' );
else :
get_template_part( 'template-parts/content', get_post_format() );
endif;
```
|
1.0
|
is_search check in jetpack infinite render - Shouldn't there be `is_search` check in `inc/jetpack.php` `_s_infinite_scroll_render` function?
Something like this:
```
if ( is_search() ) :
get_template_part( 'template-parts/content', 'search' );
else :
get_template_part( 'template-parts/content', get_post_format() );
endif;
```
|
test
|
is search check in jetpack infinite render shouldn t there be is search check in inc jetpack php s infinite scroll render function something like this if is search get template part template parts content search else get template part template parts content get post format endif
| 1
|
242,339
| 20,241,166,818
|
IssuesEvent
|
2022-02-14 09:25:41
|
pingcap/tiflow
|
https://api.github.com/repos/pingcap/tiflow
|
closed
|
DM TestFailToStartLeader
|
component/test type/enhancement area/dm
|
### Which jobs are flaking?
https://ci.pingcap.net/blue/organizations/jenkins/ut-check/detail/ut-check/1237/pipeline/
### Which test(s) are flaking?
TestFailToStartLeader
### Jenkins logs or GitHub Actions link
```log
[2022-02-10T10:59:54.496Z] goroutine 300 [semacquire, 4 minutes]:
[2022-02-10T10:59:54.496Z] sync.runtime_Semacquire(0xc001b6e090)
[2022-02-10T10:59:54.496Z] /usr/local/go/src/runtime/sema.go:56 +0x45
[2022-02-10T10:59:54.496Z] sync.(*WaitGroup).Wait(0xc001b6e088)
[2022-02-10T10:59:54.496Z] /usr/local/go/src/sync/waitgroup.go:130 +0xe5
[2022-02-10T10:59:54.496Z] github.com/pingcap/tiflow/dm/dm/master.(*Server).Close(0xc001b6e000)
[2022-02-10T10:59:54.496Z] /home/jenkins/agent/workspace/ut-check/tiflow/dm/dm/master/server.go:275 +0x15d
[2022-02-10T10:59:54.496Z] runtime.Goexit()
[2022-02-10T10:59:54.496Z] /usr/local/go/src/runtime/panic.go:632 +0x146
[2022-02-10T10:59:54.496Z] github.com/pingcap/check.(*C).stopNow(...)
[2022-02-10T10:59:54.496Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:108
[2022-02-10T10:59:54.496Z] github.com/pingcap/check.(*C).Assert(0xc0002b2c30, 0x5a8b180, 0x92a7060, 0x71e7438, 0x8d882c0, 0xc0010d59d8, 0x1, 0x1)
[2022-02-10T10:59:54.496Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/helpers.go:179 +0xc5
[2022-02-10T10:59:54.497Z] github.com/pingcap/tiflow/dm/dm/master.(*testElectionSuite).TestFailToStartLeader(0x9f17d98, 0xc0002b2c30)
[2022-02-10T10:59:54.497Z] /home/jenkins/agent/workspace/ut-check/tiflow/dm/dm/master/election_test.go:79 +0x103a
[2022-02-10T10:59:54.497Z] reflect.Value.call(0x5b4b8a0, 0x9f17d98, 0x213, 0x609a1a2, 0x4, 0xc0000e3ef0, 0x1, 0x1, 0xc000583d08, 0x4b4b4de, ...)
[2022-02-10T10:59:54.497Z] /usr/local/go/src/reflect/value.go:476 +0x99c
[2022-02-10T10:59:54.497Z] reflect.Value.Call(0x5b4b8a0, 0x9f17d98, 0x213, 0xc000583ef0, 0x1, 0x1, 0x0, 0x0, 0x0)
[2022-02-10T10:59:54.497Z] /usr/local/go/src/reflect/value.go:337 +0xd9
[2022-02-10T10:59:54.497Z] github.com/pingcap/check.(*suiteRunner).forkTest.func1(0xc0002b2c30)
[2022-02-10T10:59:54.497Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:850 +0xb3c
[2022-02-10T10:59:54.497Z] github.com/pingcap/check.(*suiteRunner).forkCall.func1(0xc001149830, 0xc0002b2c30, 0xc000bd2ea0)
[2022-02-10T10:59:54.497Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:739 +0x11e
[2022-02-10T10:59:54.497Z] created by github.com/pingcap/check.(*suiteRunner).forkCall
[2022-02-10T10:59:54.497Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:734 +0x4cd
[2022-02-10T10:59:54.497Z]
```
https://ci.pingcap.net/blue/organizations/jenkins/ut-check/detail/ut-check/1237/pipeline/
### Anything else we need to know
- Does this test exist for other branches as well?
- Has there been a high frequency of failure lately?
|
1.0
|
DM TestFailToStartLeader - ### Which jobs are flaking?
https://ci.pingcap.net/blue/organizations/jenkins/ut-check/detail/ut-check/1237/pipeline/
### Which test(s) are flaking?
TestFailToStartLeader
### Jenkins logs or GitHub Actions link
```log
[2022-02-10T10:59:54.496Z] goroutine 300 [semacquire, 4 minutes]:
[2022-02-10T10:59:54.496Z] sync.runtime_Semacquire(0xc001b6e090)
[2022-02-10T10:59:54.496Z] /usr/local/go/src/runtime/sema.go:56 +0x45
[2022-02-10T10:59:54.496Z] sync.(*WaitGroup).Wait(0xc001b6e088)
[2022-02-10T10:59:54.496Z] /usr/local/go/src/sync/waitgroup.go:130 +0xe5
[2022-02-10T10:59:54.496Z] github.com/pingcap/tiflow/dm/dm/master.(*Server).Close(0xc001b6e000)
[2022-02-10T10:59:54.496Z] /home/jenkins/agent/workspace/ut-check/tiflow/dm/dm/master/server.go:275 +0x15d
[2022-02-10T10:59:54.496Z] runtime.Goexit()
[2022-02-10T10:59:54.496Z] /usr/local/go/src/runtime/panic.go:632 +0x146
[2022-02-10T10:59:54.496Z] github.com/pingcap/check.(*C).stopNow(...)
[2022-02-10T10:59:54.496Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:108
[2022-02-10T10:59:54.496Z] github.com/pingcap/check.(*C).Assert(0xc0002b2c30, 0x5a8b180, 0x92a7060, 0x71e7438, 0x8d882c0, 0xc0010d59d8, 0x1, 0x1)
[2022-02-10T10:59:54.496Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/helpers.go:179 +0xc5
[2022-02-10T10:59:54.497Z] github.com/pingcap/tiflow/dm/dm/master.(*testElectionSuite).TestFailToStartLeader(0x9f17d98, 0xc0002b2c30)
[2022-02-10T10:59:54.497Z] /home/jenkins/agent/workspace/ut-check/tiflow/dm/dm/master/election_test.go:79 +0x103a
[2022-02-10T10:59:54.497Z] reflect.Value.call(0x5b4b8a0, 0x9f17d98, 0x213, 0x609a1a2, 0x4, 0xc0000e3ef0, 0x1, 0x1, 0xc000583d08, 0x4b4b4de, ...)
[2022-02-10T10:59:54.497Z] /usr/local/go/src/reflect/value.go:476 +0x99c
[2022-02-10T10:59:54.497Z] reflect.Value.Call(0x5b4b8a0, 0x9f17d98, 0x213, 0xc000583ef0, 0x1, 0x1, 0x0, 0x0, 0x0)
[2022-02-10T10:59:54.497Z] /usr/local/go/src/reflect/value.go:337 +0xd9
[2022-02-10T10:59:54.497Z] github.com/pingcap/check.(*suiteRunner).forkTest.func1(0xc0002b2c30)
[2022-02-10T10:59:54.497Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:850 +0xb3c
[2022-02-10T10:59:54.497Z] github.com/pingcap/check.(*suiteRunner).forkCall.func1(0xc001149830, 0xc0002b2c30, 0xc000bd2ea0)
[2022-02-10T10:59:54.497Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:739 +0x11e
[2022-02-10T10:59:54.497Z] created by github.com/pingcap/check.(*suiteRunner).forkCall
[2022-02-10T10:59:54.497Z] /go/pkg/mod/github.com/pingcap/check@v0.0.0-20211026125417-57bd13f7b5f0/check.go:734 +0x4cd
[2022-02-10T10:59:54.497Z]
```
https://ci.pingcap.net/blue/organizations/jenkins/ut-check/detail/ut-check/1237/pipeline/
### Anything else we need to know
- Does this test exist for other branches as well?
- Has there been a high frequency of failure lately?
|
test
|
dm testfailtostartleader which jobs are flaking which test s are flaking testfailtostartleader jenkins logs or github actions link log goroutine sync runtime semacquire usr local go src runtime sema go sync waitgroup wait usr local go src sync waitgroup go github com pingcap tiflow dm dm master server close home jenkins agent workspace ut check tiflow dm dm master server go runtime goexit usr local go src runtime panic go github com pingcap check c stopnow go pkg mod github com pingcap check check go github com pingcap check c assert go pkg mod github com pingcap check helpers go github com pingcap tiflow dm dm master testelectionsuite testfailtostartleader home jenkins agent workspace ut check tiflow dm dm master election test go reflect value call usr local go src reflect value go reflect value call usr local go src reflect value go github com pingcap check suiterunner forktest go pkg mod github com pingcap check check go github com pingcap check suiterunner forkcall go pkg mod github com pingcap check check go created by github com pingcap check suiterunner forkcall go pkg mod github com pingcap check check go anything else we need to know does this test exist for other branches as well has there been a high frequency of failure lately
| 1
|
248,724
| 21,054,362,632
|
IssuesEvent
|
2022-04-01 00:33:17
|
A-Zahra/Prototype_03
|
https://api.github.com/repos/A-Zahra/Prototype_03
|
closed
|
Playtest Feedback - Madeline Zaytsoff
|
Playtest_03
|
1. How did you find the game story/concept?
I like the concept! Maybe it was the visuals but I was having a trouble drawing the connection between the jewellery and technical gameplay.
2. Was it hard to play in angular view? Would it be better to make the camera view straight top view?
I tried both just to see and I definitely like the angular view better.
3. What was the game difficulty level?
I'm not sure because I was mostly confused about the counting as sometimes it would work and sometimes it wouldn't.
4. Did you find anything annoying?
The colour target shown on the grey display could be bigger and more noticeable.
5. Do you have any suggestions? What can be the next level of this game?
Oh! Maybe you then have to sort those gems into a certain way on necklaces that you then get scored on depending what jewels you use.
6. Do you think the color displayed on the screen should always match at least one of the containers' colors? Or it is good as it is now?
It should always match one otherwise the player may think there's an error. (Unless that's what you want)
7. How many jewels could you collect?
0 the first play through, and then after I restarted I got 5
|
1.0
|
Playtest Feedback - Madeline Zaytsoff - 1. How did you find the game story/concept?
I like the concept! Maybe it was the visuals but I was having a trouble drawing the connection between the jewellery and technical gameplay.
2. Was it hard to play in angular view? Would it be better to make the camera view straight top view?
I tried both just to see and I definitely like the angular view better.
3. What was the game difficulty level?
I'm not sure because I was mostly confused about the counting as sometimes it would work and sometimes it wouldn't.
4. Did you find anything annoying?
The colour target shown on the grey display could be bigger and more noticeable.
5. Do you have any suggestions? What can be the next level of this game?
Oh! Maybe you then have to sort those gems into a certain way on necklaces that you then get scored on depending what jewels you use.
6. Do you think the color displayed on the screen should always match at least one of the containers' colors? Or it is good as it is now?
It should always match one otherwise the player may think there's an error. (Unless that's what you want)
7. How many jewels could you collect?
0 the first play through, and then after I restarted I got 5
|
test
|
playtest feedback madeline zaytsoff how did you find the game story concept i like the concept maybe it was the visuals but i was having a trouble drawing the connection between the jewellery and technical gameplay was it hard to play in angular view would it be better to make the camera view straight top view i tried both just to see and i definitely like the angular view better what was the game difficulty level i m not sure because i was mostly confused about the counting as sometimes it would work and sometimes it wouldn t did you find anything annoying the colour target shown on the grey display could be bigger and more noticeable do you have any suggestions what can be the next level of this game oh maybe you then have to sort those gems into a certain way on necklaces that you then get scored on depending what jewels you use do you think the color displayed on the screen should always match at least one of the containers colors or it is good as it is now it should always match one otherwise the player may think there s an error unless that s what you want how many jewels could you collect the first play through and then after i restarted i got
| 1
|
93,054
| 8,392,732,264
|
IssuesEvent
|
2018-10-09 18:28:14
|
vincaslt/vscode-highlight-matching-tag
|
https://api.github.com/repos/vincaslt/vscode-highlight-matching-tag
|
closed
|
make suggestion very slow
|
test data needed
|
use this extension, suggetsion very slow, when disable this extension, it is very quickly
|
1.0
|
make suggestion very slow - use this extension, suggetsion very slow, when disable this extension, it is very quickly
|
test
|
make suggestion very slow use this extension suggetsion very slow when disable this extension it is very quickly
| 1
|
84,987
| 10,577,623,389
|
IssuesEvent
|
2019-10-07 20:31:49
|
fecgov/fec-cms
|
https://api.github.com/repos/fecgov/fec-cms
|
closed
|
Testing ticket: Where individual contributions come from
|
Testing idea Work: UX/Design
|
**What we're after:**
This is a testing ticket to test Where individual contributions come from and implement any outstanding issues that must be resolved before making this feature live.
### Related issues
- https://github.com/fecgov/fec-cms/issues/2929
- https://github.com/fecgov/fec-cms/issues/3204
- https://github.com/fecgov/fec-cms/pull/3208
### Completion criteria
- [x] hold meeting with testers/devs to identify testing steps
- [x] decide what testing steps are needed to satisfy thorough testing for #2929
- [ ] document work still needed and determine priority level
|
1.0
|
Testing ticket: Where individual contributions come from - **What we're after:**
This is a testing ticket to test Where individual contributions come from and implement any outstanding issues that must be resolved before making this feature live.
### Related issues
- https://github.com/fecgov/fec-cms/issues/2929
- https://github.com/fecgov/fec-cms/issues/3204
- https://github.com/fecgov/fec-cms/pull/3208
### Completion criteria
- [x] hold meeting with testers/devs to identify testing steps
- [x] decide what testing steps are needed to satisfy thorough testing for #2929
- [ ] document work still needed and determine priority level
|
non_test
|
testing ticket where individual contributions come from what we re after this is a testing ticket to test where individual contributions come from and implement any outstanding issues that must be resolved before making this feature live related issues completion criteria hold meeting with testers devs to identify testing steps decide what testing steps are needed to satisfy thorough testing for document work still needed and determine priority level
| 0
|
53,556
| 6,334,907,834
|
IssuesEvent
|
2017-07-26 17:41:49
|
Princeton-CDH/derrida-django
|
https://api.github.com/repos/Princeton-CDH/derrida-django
|
closed
|
interventions: indicate verbal or non-verbal interventions
|
awaiting testing
|
As a data editor, I want to see an indicator on the Django admin site that shows whether an intervention is verbal or non-verbal, so I can more easily distinguish these important categories.
Brought up and completed in #31.
|
1.0
|
interventions: indicate verbal or non-verbal interventions - As a data editor, I want to see an indicator on the Django admin site that shows whether an intervention is verbal or non-verbal, so I can more easily distinguish these important categories.
Brought up and completed in #31.
|
test
|
interventions indicate verbal or non verbal interventions as a data editor i want to see an indicator on the django admin site that shows whether an intervention is verbal or non verbal so i can more easily distinguish these important categories brought up and completed in
| 1
|
81,657
| 31,233,490,438
|
IssuesEvent
|
2023-08-20 01:25:16
|
microsoft/TypeScript
|
https://api.github.com/repos/microsoft/TypeScript
|
closed
|
parseIsolatedEntityName doesn't return correct pos
|
Not a Defect
|
### 🔎 Search Terms
parseIsolatedEntityName,pos,invalid
### 🕗 Version & Regression Information
Fails on `typescript@5.1.6` and `typescript@next`.
### 💻 Code
```ts
import ts from "npm:typescript@next";
console.log(ts.parseIsolatedEntityName(" aa ", ts.ScriptTarget.ESNext));
```
### 🙁 Actual behavior
```
$ deno run --check --allow-read code.ts
IdentifierObject {
pos: 0,
end: 4,
flags: 262144,
modifierFlagsCache: 0,
transformFlags: 0,
parent: undefined,
kind: 80,
escapedText: "aa",
jsDoc: undefined,
flowNode: undefined,
symbol: undefined
}
```
The value of `pos` is 0 even though the identifier doesn't start at position 0.
### 🙂 Expected behavior
```
$ deno run --check --allow-read code.ts
IdentifierObject {
pos: 2,
end: 4,
flags: 262144,
modifierFlagsCache: 0,
transformFlags: 0,
parent: undefined,
kind: 80,
escapedText: "aa",
jsDoc: undefined,
flowNode: undefined,
symbol: undefined
}
```
The value of `pos` is 2.
### Additional information about the issue
Deno is used for simplicity but same behavior would be displayed using nodejs
|
1.0
|
parseIsolatedEntityName doesn't return correct pos - ### 🔎 Search Terms
parseIsolatedEntityName,pos,invalid
### 🕗 Version & Regression Information
Fails on `typescript@5.1.6` and `typescript@next`.
### 💻 Code
```ts
import ts from "npm:typescript@next";
console.log(ts.parseIsolatedEntityName(" aa ", ts.ScriptTarget.ESNext));
```
### 🙁 Actual behavior
```
$ deno run --check --allow-read code.ts
IdentifierObject {
pos: 0,
end: 4,
flags: 262144,
modifierFlagsCache: 0,
transformFlags: 0,
parent: undefined,
kind: 80,
escapedText: "aa",
jsDoc: undefined,
flowNode: undefined,
symbol: undefined
}
```
The value of `pos` is 0 even though the identifier doesn't start at position 0.
### 🙂 Expected behavior
```
$ deno run --check --allow-read code.ts
IdentifierObject {
pos: 2,
end: 4,
flags: 262144,
modifierFlagsCache: 0,
transformFlags: 0,
parent: undefined,
kind: 80,
escapedText: "aa",
jsDoc: undefined,
flowNode: undefined,
symbol: undefined
}
```
The value of `pos` is 2.
### Additional information about the issue
Deno is used for simplicity but same behavior would be displayed using nodejs
|
non_test
|
parseisolatedentityname doesn t return correct pos 🔎 search terms parseisolatedentityname pos invalid 🕗 version regression information fails on typescript and typescript next 💻 code ts import ts from npm typescript next console log ts parseisolatedentityname aa ts scripttarget esnext 🙁 actual behavior deno run check allow read code ts identifierobject pos end flags modifierflagscache transformflags parent undefined kind escapedtext aa jsdoc undefined flownode undefined symbol undefined the value of pos is even though the identifier doesn t start at position 🙂 expected behavior deno run check allow read code ts identifierobject pos end flags modifierflagscache transformflags parent undefined kind escapedtext aa jsdoc undefined flownode undefined symbol undefined the value of pos is additional information about the issue deno is used for simplicity but same behavior would be displayed using nodejs
| 0
|
387,835
| 26,740,367,068
|
IssuesEvent
|
2023-01-30 12:32:58
|
executablebooks/mystjs
|
https://api.github.com/repos/executablebooks/mystjs
|
opened
|
[jtex] Creating a template guide should link to the `files` docs
|
documentation
|
In this section of the guide https://myst.tools/docs/jtex/create-a-latex-template#content-imports-and-packages the `files` section of the `template.yml` is mentioned, but is not easy to find. We should add a link to this section https://myst.tools/docs/jtex/template-yml#template-files
|
1.0
|
[jtex] Creating a template guide should link to the `files` docs - In this section of the guide https://myst.tools/docs/jtex/create-a-latex-template#content-imports-and-packages the `files` section of the `template.yml` is mentioned, but is not easy to find. We should add a link to this section https://myst.tools/docs/jtex/template-yml#template-files
|
non_test
|
creating a template guide should link to the files docs in this section of the guide the files section of the template yml is mentioned but is not easy to find we should add a link to this section
| 0
|
11,251
| 9,292,715,442
|
IssuesEvent
|
2019-03-22 04:37:24
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
How to create AKS nodes with large disk
|
container-service/svc cxp product-question triaged
|
Hello,
Is it possible to manually choose the size of disk storage (e.g. 1TB) independently of the VM cpu and memory size?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: dc89d962-27d5-2ebd-4e8d-092948eb92a3
* Version Independent ID: 49e054ed-b4c7-f4d7-b88f-68a0ff61035d
* Content: [Operator best practices - Storage in Azure Kubernetes Services (AKS)](https://docs.microsoft.com/en-us/azure/aks/operator-best-practices-storage#feedback)
* Content Source: [articles/aks/operator-best-practices-storage.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/operator-best-practices-storage.md)
* Service: **container-service**
* GitHub Login: @iainfoulds
* Microsoft Alias: **iainfou**
|
1.0
|
How to create AKS nodes with large disk - Hello,
Is it possible to manually choose the size of disk storage (e.g. 1TB) independently of the VM cpu and memory size?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: dc89d962-27d5-2ebd-4e8d-092948eb92a3
* Version Independent ID: 49e054ed-b4c7-f4d7-b88f-68a0ff61035d
* Content: [Operator best practices - Storage in Azure Kubernetes Services (AKS)](https://docs.microsoft.com/en-us/azure/aks/operator-best-practices-storage#feedback)
* Content Source: [articles/aks/operator-best-practices-storage.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/operator-best-practices-storage.md)
* Service: **container-service**
* GitHub Login: @iainfoulds
* Microsoft Alias: **iainfou**
|
non_test
|
how to create aks nodes with large disk hello is it possible to manually choose the size of disk storage e g independently of the vm cpu and memory size document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service container service github login iainfoulds microsoft alias iainfou
| 0
|
233,095
| 18,947,723,198
|
IssuesEvent
|
2021-11-18 12:03:19
|
theupdateframework/python-tuf
|
https://api.github.com/repos/theupdateframework/python-tuf
|
closed
|
ngtests: add tests toggling consistent snapshot
|
testing backlog
|
**Description of issue or feature request**:
Currently different configurations of `consistent_snapshot`, `prefix_targets_with_hash` are tested in `test_updater_ng.py` which uses pre-generated test files.
After adding support for non-consistent snapshot #1637, analyze what would be meaningful consistent snapshot tests that preferably don't duplicate the tests code for each config and implement them using `RepositorySimulator`.
|
1.0
|
ngtests: add tests toggling consistent snapshot - **Description of issue or feature request**:
Currently different configurations of `consistent_snapshot`, `prefix_targets_with_hash` are tested in `test_updater_ng.py` which uses pre-generated test files.
After adding support for non-consistent snapshot #1637, analyze what would be meaningful consistent snapshot tests that preferably don't duplicate the tests code for each config and implement them using `RepositorySimulator`.
|
test
|
ngtests add tests toggling consistent snapshot description of issue or feature request currently different configurations of consistent snapshot prefix targets with hash are tested in test updater ng py which uses pre generated test files after adding support for non consistent snapshot analyze what would be meaningful consistent snapshot tests that preferably don t duplicate the tests code for each config and implement them using repositorysimulator
| 1
|
754,349
| 26,383,151,475
|
IssuesEvent
|
2023-01-12 10:12:15
|
googleapis/java-securitycenter
|
https://api.github.com/repos/googleapis/java-securitycenter
|
closed
|
The build failed
|
priority: p1 type: bug api: securitycenter flakybot: issue
|
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 0c859e55b72f230ebeb48b42a540e5200448e3e2
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/0f26ea38-8516-4566-b967-1f6551459456), [Sponge](http://sponge2/0f26ea38-8516-4566-b967-1f6551459456)
status: failed
<details><summary>Test output</summary><br><pre>java.lang.AssertionError:
Dataset was not deleted.
com.google.cloud.bigquery.BigQueryException: Dataset java-docs-samples-testing:sampledataset is still in use
at org.junit.Assert.fail(Assert.java:89)
at com.google.cloud.examples.securitycenter.snippets.BigQueryExportIT.deleteBigQueryDataset(BigQueryExportIT.java:119)
at com.google.cloud.examples.securitycenter.snippets.BigQueryExportIT.cleanUp(BigQueryExportIT.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
</pre></details>
|
1.0
|
The build failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 0c859e55b72f230ebeb48b42a540e5200448e3e2
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/0f26ea38-8516-4566-b967-1f6551459456), [Sponge](http://sponge2/0f26ea38-8516-4566-b967-1f6551459456)
status: failed
<details><summary>Test output</summary><br><pre>java.lang.AssertionError:
Dataset was not deleted.
com.google.cloud.bigquery.BigQueryException: Dataset java-docs-samples-testing:sampledataset is still in use
at org.junit.Assert.fail(Assert.java:89)
at com.google.cloud.examples.securitycenter.snippets.BigQueryExportIT.deleteBigQueryDataset(BigQueryExportIT.java:119)
at com.google.cloud.examples.securitycenter.snippets.BigQueryExportIT.cleanUp(BigQueryExportIT.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
</pre></details>
|
non_test
|
the build failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output java lang assertionerror dataset was not deleted com google cloud bigquery bigqueryexception dataset java docs samples testing sampledataset is still in use at org junit assert fail assert java at com google cloud examples securitycenter snippets bigqueryexportit deletebigquerydataset bigqueryexportit java at com google cloud examples securitycenter snippets bigqueryexportit cleanup bigqueryexportit java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements runafters invokemethod runafters java at org junit internal runners statements runafters evaluate runafters java at org junit runners parentrunner evaluate parentrunner java at org junit runners parentrunner run parentrunner java at org apache maven surefire execute java at org apache maven surefire executewithrerun java at org apache maven surefire executetestset java at org apache maven surefire invoke java at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java at org apache maven surefire booter forkedbooter execute forkedbooter java at org apache maven surefire booter forkedbooter run forkedbooter java at org apache maven surefire booter forkedbooter main forkedbooter java
| 0
|
101,701
| 12,701,192,072
|
IssuesEvent
|
2020-06-22 17:41:46
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
opened
|
Search results card focus state
|
bug design frontend needs-grooming vsa vsa-facilities
|
## What happened?
When selecting a pin from the map on Facility Locator, it highlights the corresponding item in the list in the left sidebar, and looks like this:
Screen Shot 2020-06-18 at 1.35.49 PM.png
The blue inset box shadow isn’t consistent with the focus style elsewhere on VA.gov.
## Desired behavior
Active state’s inset box shadow should be the 2px yellow border used across VA.gov to indicate focus states
Screen Shot 2020-06-18 at 1.36.28 PM.png_Describe in detail what went wrong; screenshots, videos, or gifs are strongly encouraged_
## Acceptance Criteria
- [ ] Focus state for search results cards uses 2px yellow border and is consistent with design system
## How to configure this issue
- [ ] **Attached to a Milestone** (when will this be completed?)
- [ ] **Attached to Epic** (what body of work is this a part of? possibly `Ongoing Maintenance`)
- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`)
- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)
- [ ] **Labeled with `Bug`**
|
1.0
|
Search results card focus state - ## What happened?
When selecting a pin from the map on Facility Locator, it highlights the corresponding item in the list in the left sidebar, and looks like this:
Screen Shot 2020-06-18 at 1.35.49 PM.png
The blue inset box shadow isn’t consistent with the focus style elsewhere on VA.gov.
## Desired behavior
Active state’s inset box shadow should be the 2px yellow border used across VA.gov to indicate focus states
Screen Shot 2020-06-18 at 1.36.28 PM.png_Describe in detail what went wrong; screenshots, videos, or gifs are strongly encouraged_
## Acceptance Criteria
- [ ] Focus state for search results cards uses 2px yellow border and is consistent with design system
## How to configure this issue
- [ ] **Attached to a Milestone** (when will this be completed?)
- [ ] **Attached to Epic** (what body of work is this a part of? possibly `Ongoing Maintenance`)
- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`)
- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)
- [ ] **Labeled with `Bug`**
|
non_test
|
search results card focus state what happened when selecting a pin from the map on facility locator it highlights the corresponding item in the list in the left sidebar and looks like this screen shot at pm png the blue inset box shadow isn’t consistent with the focus style elsewhere on va gov desired behavior active state’s inset box shadow should be the yellow border used across va gov to indicate focus states screen shot at pm png describe in detail what went wrong screenshots videos or gifs are strongly encouraged acceptance criteria focus state for search results cards uses yellow border and is consistent with design system how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug
| 0
|
10,213
| 3,090,305,651
|
IssuesEvent
|
2015-08-26 05:16:45
|
e-government-ua/i
|
https://api.github.com/repos/e-government-ua/i
|
closed
|
На бэке централа доработать сервис getServicesTree дополнительными фильтрами
|
active hi priority test
|
- [x] 1) Добавить в сервис getServicesTree так, чтоб если название услуги начинается с символа "_", то выводить такой элемент каталога только если флаг bTest в классе GeneralConfig равняется true (иначе не включать его в выдаваемый каталог)
- [x] 2) Добавить в сервис getServicesTree опциональный параметр "asID_Place_UA" , где через запятую, приходит массив строк-ИД мест.
Например:
getServicesTree?asID_Place_UA=3200000000,8000000000
где:
sID_UA = "3200000000" (КИЇВСЬКА ОБЛАСТЬ/М.КИЇВ)
sID_UA = "8000000000" (М.КИЇВ)
(коды взяты из всеукраинского классификатора мест: http://www.ukrstat.gov.ua/klasf/klasif/koatuu.rar)
Если параметр asID_Place_UA задан, то накладывать фильтр на выдаваемый каталог услуг. т.е. выводить только те услуги, в которых в подуслугах (в ServiceData) есть те, которые находятся в указанных регионах или городах. (связанные сущности Region и City)
ВАЖНО: При этом, пока что:
3200000000 - приравнивать к региону "Киевский"
8000000000 - приравнивать к городу"Киев"
Остальные коды пока вообще игнорировать!!!
(т.е. выдавать полный каталог, если ни одного из вышеперечисленных кодов не указано)
|
1.0
|
На бэке централа доработать сервис getServicesTree дополнительными фильтрами - - [x] 1) Добавить в сервис getServicesTree так, чтоб если название услуги начинается с символа "_", то выводить такой элемент каталога только если флаг bTest в классе GeneralConfig равняется true (иначе не включать его в выдаваемый каталог)
- [x] 2) Добавить в сервис getServicesTree опциональный параметр "asID_Place_UA" , где через запятую, приходит массив строк-ИД мест.
Например:
getServicesTree?asID_Place_UA=3200000000,8000000000
где:
sID_UA = "3200000000" (КИЇВСЬКА ОБЛАСТЬ/М.КИЇВ)
sID_UA = "8000000000" (М.КИЇВ)
(коды взяты из всеукраинского классификатора мест: http://www.ukrstat.gov.ua/klasf/klasif/koatuu.rar)
Если параметр asID_Place_UA задан, то накладывать фильтр на выдаваемый каталог услуг. т.е. выводить только те услуги, в которых в подуслугах (в ServiceData) есть те, которые находятся в указанных регионах или городах. (связанные сущности Region и City)
ВАЖНО: При этом, пока что:
3200000000 - приравнивать к региону "Киевский"
8000000000 - приравнивать к городу"Киев"
Остальные коды пока вообще игнорировать!!!
(т.е. выдавать полный каталог, если ни одного из вышеперечисленных кодов не указано)
|
test
|
на бэке централа доработать сервис getservicestree дополнительными фильтрами добавить в сервис getservicestree так чтоб если название услуги начинается с символа то выводить такой элемент каталога только если флаг btest в классе generalconfig равняется true иначе не включать его в выдаваемый каталог добавить в сервис getservicestree опциональный параметр asid place ua где через запятую приходит массив строк ид мест например getservicestree asid place ua где sid ua київська область м київ sid ua м київ коды взяты из всеукраинского классификатора мест если параметр asid place ua задан то накладывать фильтр на выдаваемый каталог услуг т е выводить только те услуги в которых в подуслугах в servicedata есть те которые находятся в указанных регионах или городах связанные сущности region и city важно при этом пока что приравнивать к региону киевский приравнивать к городу киев остальные коды пока вообще игнорировать т е выдавать полный каталог если ни одного из вышеперечисленных кодов не указано
| 1
|
154,413
| 12,203,415,615
|
IssuesEvent
|
2020-04-30 10:33:44
|
status-im/nim-beacon-chain
|
https://api.github.com/repos/status-im/nim-beacon-chain
|
closed
|
Cleanup CI cache
|
low priority test suite
|
After https://github.com/status-im/nim-beacon-chain/pull/550 we should clean the cache on all CI.
- remove the *.tar.xz in all CACHE_DIR which corresponds to json-tests
- remove LFS related code in .nimble, MAKEFILE, Appveyor, Travis config
- remove dependencies for packing or lfs like XZ if they are not part of build-essentials
|
1.0
|
Cleanup CI cache - After https://github.com/status-im/nim-beacon-chain/pull/550 we should clean the cache on all CI.
- remove the *.tar.xz in all CACHE_DIR which corresponds to json-tests
- remove LFS related code in .nimble, MAKEFILE, Appveyor, Travis config
- remove dependencies for packing or lfs like XZ if they are not part of build-essentials
|
test
|
cleanup ci cache after we should clean the cache on all ci remove the tar xz in all cache dir which corresponds to json tests remove lfs related code in nimble makefile appveyor travis config remove dependencies for packing or lfs like xz if they are not part of build essentials
| 1
|
280,341
| 24,296,522,415
|
IssuesEvent
|
2022-09-29 10:30:26
|
google/android-fhir
|
https://api.github.com/repos/google/android-fhir
|
closed
|
The checkbox is very close to the left edge
|
type:bug effort:xsmall ux ux testing
|
**Describe the bug**
The checkbox is very close to the left edge.
**Component**
Core library, SDC library, reference app, or SDC gallery app
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Smartphone (please complete the following information):**
- Device: [e.g. Pixel4a emulator]
- Android version: [e.g. Settings -> About phone -> Android version]
- Build number: [e.g. Settings -> About phone -> Build number]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
**Would you like to work on the issue?**
Please state if this issue should be assigned to you or who you think could help to solve this issue.
|
1.0
|
The checkbox is very close to the left edge - **Describe the bug**
The checkbox is very close to the left edge.
**Component**
Core library, SDC library, reference app, or SDC gallery app
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Smartphone (please complete the following information):**
- Device: [e.g. Pixel4a emulator]
- Android version: [e.g. Settings -> About phone -> Android version]
- Build number: [e.g. Settings -> About phone -> Build number]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
**Would you like to work on the issue?**
Please state if this issue should be assigned to you or who you think could help to solve this issue.
|
test
|
the checkbox is very close to the left edge describe the bug the checkbox is very close to the left edge component core library sdc library reference app or sdc gallery app to reproduce steps to reproduce the behavior go to click on scroll down to see error expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem smartphone please complete the following information device android version build number version additional context add any other context about the problem here would you like to work on the issue please state if this issue should be assigned to you or who you think could help to solve this issue
| 1
|
131,903
| 10,721,795,116
|
IssuesEvent
|
2019-10-27 06:28:02
|
symfony/symfony-docs
|
https://api.github.com/repos/symfony/symfony-docs
|
closed
|
Overriding services for functional testing
|
DependencyInjection Testing
|
Next to https://github.com/symfony/symfony/issues/23311
Some people are used to `set()` a service in the container for mocking it in functional tests (see https://stackoverflow.com/a/19726963/4363634) but as of 3.3, setting/resetting a predefined service is deprecated.
The right solution is to load testing specific config (https://github.com/symfony/symfony/pull/21533#issuecomment-302101055).
I think we should add an example to the docs.
|
1.0
|
Overriding services for functional testing - Next to https://github.com/symfony/symfony/issues/23311
Some people are used to `set()` a service in the container for mocking it in functional tests (see https://stackoverflow.com/a/19726963/4363634) but as of 3.3, setting/resetting a predefined service is deprecated.
The right solution is to load testing specific config (https://github.com/symfony/symfony/pull/21533#issuecomment-302101055).
I think we should add an example to the docs.
|
test
|
overriding services for functional testing next to some people are used to set a service in the container for mocking it in functional tests see but as of setting resetting a predefined service is deprecated the right solution is to load testing specific config i think we should add an example to the docs
| 1
|
200,379
| 22,765,964,803
|
IssuesEvent
|
2022-07-08 04:25:27
|
classicvalues/vscode-main
|
https://api.github.com/repos/classicvalues/vscode-main
|
closed
|
CVE-2021-37712 (High) detected in tar-6.0.5.tgz, tar-2.2.2.tgz - autoclosed
|
security vulnerability
|
## CVE-2021-37712 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>tar-6.0.5.tgz</b>, <b>tar-2.2.2.tgz</b></p></summary>
<p>
<details><summary><b>tar-6.0.5.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-6.0.5.tgz">https://registry.npmjs.org/tar/-/tar-6.0.5.tgz</a></p>
<p>
Dependency Hierarchy:
- copy-webpack-plugin-6.4.1.tgz (Root Library)
- cacache-15.0.5.tgz
- :x: **tar-6.0.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>tar-2.2.2.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.2.tgz">https://registry.npmjs.org/tar/-/tar-2.2.2.tgz</a></p>
<p>
Dependency Hierarchy:
- gulp-untar-0.0.7.tgz (Root Library)
- :x: **tar-2.2.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/LaudateCorpus1/vscode-main/commit/cab0eed4c740ec7c44e5f848efd39d6383967c19">cab0eed4c740ec7c44e5f848efd39d6383967c19</a></p>
<p>Found in base branch: <b>dev1</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 npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37712>CVE-2021-37712</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p">https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 6.1.9</p>
<p>Direct dependency fix Resolution (copy-webpack-plugin): 7.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-37712 (High) detected in tar-6.0.5.tgz, tar-2.2.2.tgz - autoclosed - ## CVE-2021-37712 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>tar-6.0.5.tgz</b>, <b>tar-2.2.2.tgz</b></p></summary>
<p>
<details><summary><b>tar-6.0.5.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-6.0.5.tgz">https://registry.npmjs.org/tar/-/tar-6.0.5.tgz</a></p>
<p>
Dependency Hierarchy:
- copy-webpack-plugin-6.4.1.tgz (Root Library)
- cacache-15.0.5.tgz
- :x: **tar-6.0.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>tar-2.2.2.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.2.tgz">https://registry.npmjs.org/tar/-/tar-2.2.2.tgz</a></p>
<p>
Dependency Hierarchy:
- gulp-untar-0.0.7.tgz (Root Library)
- :x: **tar-2.2.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/LaudateCorpus1/vscode-main/commit/cab0eed4c740ec7c44e5f848efd39d6383967c19">cab0eed4c740ec7c44e5f848efd39d6383967c19</a></p>
<p>Found in base branch: <b>dev1</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 npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37712>CVE-2021-37712</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p">https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 6.1.9</p>
<p>Direct dependency fix Resolution (copy-webpack-plugin): 7.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in tar tgz tar tgz autoclosed cve high severity vulnerability vulnerable libraries tar tgz tar tgz tar tgz tar for node library home page a href dependency hierarchy copy webpack plugin tgz root library cacache tgz x tar tgz vulnerable library tar tgz tar for node library home page a href dependency hierarchy gulp untar tgz root library x tar tgz vulnerable library found in head commit a href found in base branch vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite and arbitrary code execution vulnerability node tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted this is in part achieved by ensuring that extracted directories are not symlinks additionally in order to prevent unnecessary stat calls to determine whether a given path is a directory paths are cached when directories are created this logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value additionally on windows systems long path portions would resolve to the same file system entities as their short path counterparts a specially crafted tar archive could thus include a directory with one form of the path followed by a symbolic link with a different string that resolves to the same file system entity followed by a file using the first form by first creating a directory and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem it was thus possible to bypass node tar symlink checks on directories essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location thus allowing arbitrary file creation and overwrite these issues were addressed in releases and the branch of node tar has been deprecated and did not receive patches for these issues if you are still using a release we recommend you update to a more recent version of node tar if this is not possible a workaround is available in the referenced ghsa publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar direct dependency fix resolution copy webpack plugin step up your open source security game with mend
| 0
|
80,929
| 10,218,018,413
|
IssuesEvent
|
2019-08-15 14:58:58
|
stalgiag/p5.xr
|
https://api.github.com/repos/stalgiag/p5.xr
|
opened
|
Make README into documentation of how to get started
|
documentation release
|
This is an intermediary step to allow people to start playing around until #57 is complete.
|
1.0
|
Make README into documentation of how to get started - This is an intermediary step to allow people to start playing around until #57 is complete.
|
non_test
|
make readme into documentation of how to get started this is an intermediary step to allow people to start playing around until is complete
| 0
|
362,624
| 10,729,969,242
|
IssuesEvent
|
2019-10-28 16:31:32
|
OpeningDesign/CTR
|
https://api.github.com/repos/OpeningDesign/CTR
|
closed
|
Magic-paks
|
1st º Priority
|
http://www.magic-pak.com/
CUSTOMER SUPPORT, TECHNICAL SUPPORT AND GENERAL INQUIRIES: 1-800-448-5872
ARCHITECT AND ENGINEER DESIGN SUPPORT: 1-866-282-7257
|
1.0
|
Magic-paks - http://www.magic-pak.com/
CUSTOMER SUPPORT, TECHNICAL SUPPORT AND GENERAL INQUIRIES: 1-800-448-5872
ARCHITECT AND ENGINEER DESIGN SUPPORT: 1-866-282-7257
|
non_test
|
magic paks customer support technical support and general inquiries architect and engineer design support
| 0
|
334,276
| 29,829,622,815
|
IssuesEvent
|
2023-06-18 05:10:44
|
unifyai/ivy
|
https://api.github.com/repos/unifyai/ivy
|
reopened
|
Fix arithmetic_operations.test_numpy_vdot
|
NumPy Frontend Sub Task Failing Test
|
| | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|
1.0
|
Fix arithmetic_operations.test_numpy_vdot - | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5283333212/jobs/9559439206"><img src=https://img.shields.io/badge/-success-success></a>
|
test
|
fix arithmetic operations test numpy vdot torch a href src numpy a href src jax a href src tensorflow a href src paddle a href src
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.