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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
159,511 | 12,477,764,011 | IssuesEvent | 2020-05-29 15:29:38 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Failing test: X-Pack Jest Tests.x-pack/plugins/siem/public/endpoint_hosts/view - when on the hosts page when there is a selected host in the url when showing host Policy Response panel should include the back to details link | failed-test | A test failed on a tracked branch
```
Error: Unable to find an element by: [data-test-subj="hostDetailsPolicyResponseAttentionBadge"]
<body
class="euiBody--hasFlyout"
>
<div>
<div
class="euiPage sc-AxhCb kfdknK endpoint--isListView"
data-test-subj="hostPage"
>
<main
class="euiPageBody"
>
<div
class="euiPageHeader euiPageHeader--responsive endpoint-header"
>
<div
class="euiPageHeaderSection"
data-test-subj="pageViewHeaderLeft"
>
<h1
class="euiTitle euiTitle--large"
data-test-subj="pageViewHeaderLeftTitle"
>
Hosts
</h1>
</div>
</div>
<div
class="euiPanel euiPanel--paddingLarge euiPageContent endpoint-page-content"
>
<div
class="euiPageContentBody"
data-test-subj="pageViewBodyContent"
>
<div>
<div
data-focus-guard="true"
style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"
tabindex="0"
/>
<div
data-focus-guard="true"
style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"
tabindex="1"
/>
<div
data-focus-lock-disabled="false"
>
<div
class="euiFlyout euiFlyout--small"
data-test-subj="hostDetailsFlyout"
role="dialog"
tabindex="0"
>
<button
aria-label="Close this dialog"
class="euiButtonIcon euiButtonIcon--text euiFlyout__closeButton"
data-test-subj="euiFlyoutCloseButton"
type="button"
>
<div
aria-hidden="true"
class="euiButtonIcon__icon"
data-euiicon-type="cross"
/>
</button>
<div
class="euiFlyoutHeader euiFlyoutHeader--hasBorder"
>
<h2
class="euiTitle euiTitle--small"
data-test-subj="hostDetailsFlyoutTitle"
>
Host-uq3rm8aaip
</h2>
</div>
<div
class="euiFlyoutHeader sc-AxiKw eJMLAZ hasButtons"
data-test-subj="hostDetailsPolicyResponseFlyoutHeader"
>
<div
class="buttons"
>
<a
class="euiButtonEmpty euiButtonEmpty--primary euiButtonEmpty--xSmall flyoutSubHeaderBackButton"
data-test-subj="flyoutSubHeaderBackButton"
href="?page_index=0&page_size=10&selected_host=1"
rel="noreferrer"
>
<span
class="euiButtonEmpty__content back-button-content"
>
<div
aria-hidden="true"
class="euiButtonEmpty__icon"
data-euiicon-type="arrowLeft"
/>
<span
class="euiButtonEmpty__text back-button-content-text"
>
Endpoint Details
</span>
</span>
</a>
</div>
<div
class="flyout-content"
/>
</div>
<div
class="euiFlyoutBody"
data-test-subj="hostDetailsPolicyResponseFlyoutBody"
>
<div
class="euiFlyoutBody__overflow"
>
<div
class="euiFlyoutBody__overflowContent"
>
<div
class="euiText euiText--medium"
data-test-subj="hostDetailsPolicyResponseFlyoutTitle"
>
<h4>
Policy Response
</h4>
</div>
<div
class="euiAccordion sc-AxirZ hEhyvi"
data-test-subj="hostDetailsPolicyResponseConfigAccordion"
>
<div
class="euiAccordion__triggerWrapper"
>
<button
aria-controls="i68465861-a0ca-11ea-8376-975e3ef35b62"
aria-expanded="false"
...
at getElementError (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:22:10)
at args (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:76:13)
at /var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:86:105
at onMutation (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:46:24)
at Promise (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:62:5)
at new Promise (<anonymous>)
at waitForElement (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:22:10)
at asyncWrapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:67:54)
at /var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/react/dist/pure.js:51:22
at batchedUpdates$1 (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/react-dom/cjs/react-dom.development.js:24386:12)
at act (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/react-dom/cjs/react-dom-test-utils.development.js:1092:14)
at asyncAct (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/react/dist/act-compat.js:118:12)
at Object.asyncWrapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/react/dist/pure.js:50:35)
at waitForElementWrapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:67:35)
at findAllByTestId (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:86:98)
at Object.it (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/x-pack/plugins/siem/public/endpoint_hosts/view/index.test.tsx:366:45)
at Object.asyncJestTest (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:102:37)
at resolve (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/queueRunner.js:43:12)
at new Promise (<anonymous>)
at mapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/queueRunner.js:26:19)
at promise.then (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/queueRunner.js:73:41)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/5437/)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Jest Tests.x-pack/plugins/siem/public/endpoint_hosts/view","test.name":"when on the hosts page when there is a selected host in the url when showing host Policy Response panel should include the back to details link","test.failCount":1}} --> | 1.0 | Failing test: X-Pack Jest Tests.x-pack/plugins/siem/public/endpoint_hosts/view - when on the hosts page when there is a selected host in the url when showing host Policy Response panel should include the back to details link - A test failed on a tracked branch
```
Error: Unable to find an element by: [data-test-subj="hostDetailsPolicyResponseAttentionBadge"]
<body
class="euiBody--hasFlyout"
>
<div>
<div
class="euiPage sc-AxhCb kfdknK endpoint--isListView"
data-test-subj="hostPage"
>
<main
class="euiPageBody"
>
<div
class="euiPageHeader euiPageHeader--responsive endpoint-header"
>
<div
class="euiPageHeaderSection"
data-test-subj="pageViewHeaderLeft"
>
<h1
class="euiTitle euiTitle--large"
data-test-subj="pageViewHeaderLeftTitle"
>
Hosts
</h1>
</div>
</div>
<div
class="euiPanel euiPanel--paddingLarge euiPageContent endpoint-page-content"
>
<div
class="euiPageContentBody"
data-test-subj="pageViewBodyContent"
>
<div>
<div
data-focus-guard="true"
style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"
tabindex="0"
/>
<div
data-focus-guard="true"
style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"
tabindex="1"
/>
<div
data-focus-lock-disabled="false"
>
<div
class="euiFlyout euiFlyout--small"
data-test-subj="hostDetailsFlyout"
role="dialog"
tabindex="0"
>
<button
aria-label="Close this dialog"
class="euiButtonIcon euiButtonIcon--text euiFlyout__closeButton"
data-test-subj="euiFlyoutCloseButton"
type="button"
>
<div
aria-hidden="true"
class="euiButtonIcon__icon"
data-euiicon-type="cross"
/>
</button>
<div
class="euiFlyoutHeader euiFlyoutHeader--hasBorder"
>
<h2
class="euiTitle euiTitle--small"
data-test-subj="hostDetailsFlyoutTitle"
>
Host-uq3rm8aaip
</h2>
</div>
<div
class="euiFlyoutHeader sc-AxiKw eJMLAZ hasButtons"
data-test-subj="hostDetailsPolicyResponseFlyoutHeader"
>
<div
class="buttons"
>
<a
class="euiButtonEmpty euiButtonEmpty--primary euiButtonEmpty--xSmall flyoutSubHeaderBackButton"
data-test-subj="flyoutSubHeaderBackButton"
href="?page_index=0&page_size=10&selected_host=1"
rel="noreferrer"
>
<span
class="euiButtonEmpty__content back-button-content"
>
<div
aria-hidden="true"
class="euiButtonEmpty__icon"
data-euiicon-type="arrowLeft"
/>
<span
class="euiButtonEmpty__text back-button-content-text"
>
Endpoint Details
</span>
</span>
</a>
</div>
<div
class="flyout-content"
/>
</div>
<div
class="euiFlyoutBody"
data-test-subj="hostDetailsPolicyResponseFlyoutBody"
>
<div
class="euiFlyoutBody__overflow"
>
<div
class="euiFlyoutBody__overflowContent"
>
<div
class="euiText euiText--medium"
data-test-subj="hostDetailsPolicyResponseFlyoutTitle"
>
<h4>
Policy Response
</h4>
</div>
<div
class="euiAccordion sc-AxirZ hEhyvi"
data-test-subj="hostDetailsPolicyResponseConfigAccordion"
>
<div
class="euiAccordion__triggerWrapper"
>
<button
aria-controls="i68465861-a0ca-11ea-8376-975e3ef35b62"
aria-expanded="false"
...
at getElementError (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:22:10)
at args (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:76:13)
at /var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:86:105
at onMutation (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:46:24)
at Promise (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:62:5)
at new Promise (<anonymous>)
at waitForElement (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:22:10)
at asyncWrapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:67:54)
at /var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/react/dist/pure.js:51:22
at batchedUpdates$1 (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/react-dom/cjs/react-dom.development.js:24386:12)
at act (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/react-dom/cjs/react-dom-test-utils.development.js:1092:14)
at asyncAct (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/react/dist/act-compat.js:118:12)
at Object.asyncWrapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/react/dist/pure.js:50:35)
at waitForElementWrapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/wait-for-element.js:67:35)
at findAllByTestId (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:86:98)
at Object.it (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/x-pack/plugins/siem/public/endpoint_hosts/view/index.test.tsx:366:45)
at Object.asyncJestTest (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:102:37)
at resolve (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/queueRunner.js:43:12)
at new Promise (<anonymous>)
at mapper (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/queueRunner.js:26:19)
at promise.then (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/node_modules/jest-jasmine2/build/queueRunner.js:73:41)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/5437/)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Jest Tests.x-pack/plugins/siem/public/endpoint_hosts/view","test.name":"when on the hosts page when there is a selected host in the url when showing host Policy Response panel should include the back to details link","test.failCount":1}} --> | test | failing test x pack jest tests x pack plugins siem public endpoint hosts view when on the hosts page when there is a selected host in the url when showing host policy response panel should include the back to details link a test failed on a tracked branch error unable to find an element by body class euibody hasflyout div class euipage sc axhcb kfdknk endpoint islistview data test subj hostpage main class euipagebody div class euipageheader euipageheader responsive endpoint header div class euipageheadersection data test subj pageviewheaderleft class euititle euititle large data test subj pageviewheaderlefttitle hosts div class euipanel euipanel paddinglarge euipagecontent endpoint page content div class euipagecontentbody data test subj pageviewbodycontent div data focus guard true style width height padding overflow hidden position fixed top left tabindex div data focus guard true style width height padding overflow hidden position fixed top left tabindex div data focus lock disabled false div class euiflyout euiflyout small data test subj hostdetailsflyout role dialog tabindex button aria label close this dialog class euibuttonicon euibuttonicon text euiflyout closebutton data test subj euiflyoutclosebutton type button div aria hidden true class euibuttonicon icon data euiicon type cross div class euiflyoutheader euiflyoutheader hasborder class euititle euititle small data test subj hostdetailsflyouttitle host div class euiflyoutheader sc axikw ejmlaz hasbuttons data test subj hostdetailspolicyresponseflyoutheader div class buttons a class euibuttonempty euibuttonempty primary euibuttonempty xsmall flyoutsubheaderbackbutton data test subj flyoutsubheaderbackbutton href page index page size selected host rel noreferrer span class euibuttonempty content back button content div aria hidden true class euibuttonempty icon data euiicon type arrowleft span class euibuttonempty text back button content text endpoint details div class flyout content div class euiflyoutbody data test subj hostdetailspolicyresponseflyoutbody div class euiflyoutbody overflow div class euiflyoutbody overflowcontent div class euitext euitext medium data test subj hostdetailspolicyresponseflyouttitle policy response div class euiaccordion sc axirz hehyvi data test subj hostdetailspolicyresponseconfigaccordion div class euiaccordion triggerwrapper button aria controls aria expanded false at getelementerror var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist query helpers js at args var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist query helpers js at var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist query helpers js at onmutation var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist wait for element js at promise var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist wait for element js at new promise at waitforelement var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist wait for element js at asyncwrapper var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist wait for element js at var lib jenkins workspace elastic kibana x kibana node modules testing library react dist pure js at batchedupdates var lib jenkins workspace elastic kibana x kibana node modules react dom cjs react dom development js at act var lib jenkins workspace elastic kibana x kibana node modules react dom cjs react dom test utils development js at asyncact var lib jenkins workspace elastic kibana x kibana node modules testing library react dist act compat js at object asyncwrapper var lib jenkins workspace elastic kibana x kibana node modules testing library react dist pure js at waitforelementwrapper var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist wait for element js at findallbytestid var lib jenkins workspace elastic kibana x kibana node modules testing library dom dist query helpers js at object it var lib jenkins workspace elastic kibana x kibana x pack plugins siem public endpoint hosts view index test tsx at object asyncjesttest var lib jenkins workspace elastic kibana x kibana node modules jest build jasmineasyncinstall js at resolve var lib jenkins workspace elastic kibana x kibana node modules jest build queuerunner js at new promise at mapper var lib jenkins workspace elastic kibana x kibana node modules jest build queuerunner js at promise then var lib jenkins workspace elastic kibana x kibana node modules jest build queuerunner js first failure | 1 |
176,474 | 28,100,561,009 | IssuesEvent | 2023-03-30 19:07:55 | chapel-lang/chapel | https://api.github.com/repos/chapel-lang/chapel | closed | Finalize interface of array.count (so we no longer consider it unstable) | type: Design area: Libraries / Modules post-release type: Chapel 2.0 | Currently (as discussed here: https://github.com/chapel-lang/chapel/issues/18089#issuecomment-1276500706) we have `count` marked as unstable in arrays due to the thought that we might want to change its interface to be more consistent with uses of counts in other datastructures.
Here's the interfaces as they exist in different modules:
`proc string.count(pattern: string, indices: range(?) = this.indices):int`
`proc bytes.count(pattern: bytes, indices: range(?) = this.indices):int`
`proc list.count(x: eltType):int`
`proc array.count(val: this.eltType):int`
Taking a look at this it seems like the only real question is: "should we allow count in list/array" to take a range? Since this is an optional parameter we can always add it in later without breaking existing code so I don't really see a need for this to remain unstable in the interim.
Also taking a look at this it seems like if we do want to keep this unstable in Chapel 2.0 we should similarly mark it unstable in string, bytes, and list. | 1.0 | Finalize interface of array.count (so we no longer consider it unstable) - Currently (as discussed here: https://github.com/chapel-lang/chapel/issues/18089#issuecomment-1276500706) we have `count` marked as unstable in arrays due to the thought that we might want to change its interface to be more consistent with uses of counts in other datastructures.
Here's the interfaces as they exist in different modules:
`proc string.count(pattern: string, indices: range(?) = this.indices):int`
`proc bytes.count(pattern: bytes, indices: range(?) = this.indices):int`
`proc list.count(x: eltType):int`
`proc array.count(val: this.eltType):int`
Taking a look at this it seems like the only real question is: "should we allow count in list/array" to take a range? Since this is an optional parameter we can always add it in later without breaking existing code so I don't really see a need for this to remain unstable in the interim.
Also taking a look at this it seems like if we do want to keep this unstable in Chapel 2.0 we should similarly mark it unstable in string, bytes, and list. | non_test | finalize interface of array count so we no longer consider it unstable currently as discussed here we have count marked as unstable in arrays due to the thought that we might want to change its interface to be more consistent with uses of counts in other datastructures here s the interfaces as they exist in different modules proc string count pattern string indices range this indices int proc bytes count pattern bytes indices range this indices int proc list count x elttype int proc array count val this elttype int taking a look at this it seems like the only real question is should we allow count in list array to take a range since this is an optional parameter we can always add it in later without breaking existing code so i don t really see a need for this to remain unstable in the interim also taking a look at this it seems like if we do want to keep this unstable in chapel we should similarly mark it unstable in string bytes and list | 0 |
180,363 | 13,930,155,208 | IssuesEvent | 2020-10-22 01:39:41 | OpenMined/PySyft | https://api.github.com/repos/OpenMined/PySyft | closed | Add torch.Tensor.gt_ to allowlist and test suite | Priority: 2 - High :cold_sweat: Severity: 3 - Medium :unamused: Status: Available :wave: Type: New Feature :heavy_plus_sign: Type: Testing :test_tube: |
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.gt_
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.gt_') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.gt_ actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.gt_ is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.gt_ returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
| 2.0 | Add torch.Tensor.gt_ to allowlist and test suite -
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.gt_
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.gt_') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.gt_ actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.gt_ is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.gt_ returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
| test | add torch tensor gt to allowlist and test suite description this issue is a part of syft epic in this issue you will be adding support for remote execution of the torch tensor gt method or property this might be a really small project literally a one liner or it might require adding significant functionality to pysyft or to the testing suite in order to make sure the feature is both functional and tested step run tests and scripts pre commit sh before you get started with this project let s make sure you have everything building and testing correctly clone the codebase and run pip uninstall syft followed by pip install e then run the pre commit file which will also run the tests scripts pre commit sh if all of these tests pass continue on if not make sure you have all the dependencies in requirements txt installed etc step uncomment your method in the allowlist py file inside you will find a huge dictionary of methods find your method and uncomment the line its on at the time of writing this issue warning this may have changed the dictionary maps from the string name of the method in your case torch tensor gt to the string representation of the type the method returns step run unit tests run the following python setup py test and wait to see if some of the tests fail why might the tests fail now i m so glad you asked in this file you ll find the torch method test suite it automatically loads all methods from the allowlist py file you modified in the previous step it attempts to test them step if you get a failing test if you get a failing test this could be for one of a few reasons reason the testing suite passed in non compatible arguments the testing suite is pretty dumb it literally just has a permutation of possible arguments to pass into every method on torch tensors so if one of those permutations doesn t work for your method aka perhaps it tries to call your method without any arguments but torch tensor gt actually requires some then the test will fail if the error hasn t been seen before if this happens don t worry just look inside the only test in that file and look for the huge lists of error types to ignore add your error to the list and keep going warning make sure that the testing suite actually tests your method via remote execution once you ve gotten all the tests passing aka if the testing suite doesn t have any matching argument permutations for your method then you re literally creating a bunch of unit tests that do absolutely nothing if this is the case then add more argument types to the testing suite so that your argument gets run via remote execution do not close this issue until you can verify that torch tensor gt is actually executed remotely inside of a unit tests and not skipped aka at least one of the test all allowlisted tensor methods work remotely on all types unit tests with your method should run all the way to the end instead of skipping the last part note adding another argument type might require some serialization work if we don t support arguments of that type yet if so this is your job to add it to the protobuf files in order to close this issue reason torch tensor gt returns a non supported type if this happens you ve got a little bit of work in front of you we don t have pointer objects to very many remote object types so if your method returns anything other than a single tensor you probably need to add support for the type it returns such as a bool none int or other types important do not return the value itself to the end user return a pointer object to that type note at the time of writing there are several core pieces of syft not yet working to allow you to return any type other than a torch tensor if you re not comfortable investigating what those might be skip this issue and try again later once someone else has solved these issues reason there s something else broken chase those stack traces talk to friends in slack look at how other methods are supported this is a challenging project in a fast moving codebase and don t forget if this project seems to complex there are plenty of others that might be easier | 1 |
89,360 | 11,217,786,005 | IssuesEvent | 2020-01-07 10:01:04 | litmuschaos/litmus | https://api.github.com/repos/litmuschaos/litmus | closed | Create resource exhaustion (CPU) chaos experiment at container level | area/litmus artifact/litmusbook kind/chaos-experiment kind/feature state/design-in-progress | <!--
Thanks for filing an issue! Before hitting the button, please answer these questions.
Describe *in detail* the feature/behavior/change you'd like to see.
Be ready for followup questions, and please respond in a timely
manner. If we think a feature already exists, we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.
-->
Today, the resource exhaustion chaos experiment (generic/cpu-hog) has been implemented at a node-level. This needs to be implemented at a container level as well. This is a significant requirement, where the idea is to obtain the impact of resource chaos on targeted applications without increasing the blast radius of the experiment itself.
Some of the possible approaches include:
- Injecting a resource-exhaustion process into the target container which may run stress/stress-ng tools
- Inhibiting resources to the target container by limiting/patching minimal resources against it
| 1.0 | Create resource exhaustion (CPU) chaos experiment at container level - <!--
Thanks for filing an issue! Before hitting the button, please answer these questions.
Describe *in detail* the feature/behavior/change you'd like to see.
Be ready for followup questions, and please respond in a timely
manner. If we think a feature already exists, we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.
-->
Today, the resource exhaustion chaos experiment (generic/cpu-hog) has been implemented at a node-level. This needs to be implemented at a container level as well. This is a significant requirement, where the idea is to obtain the impact of resource chaos on targeted applications without increasing the blast radius of the experiment itself.
Some of the possible approaches include:
- Injecting a resource-exhaustion process into the target container which may run stress/stress-ng tools
- Inhibiting resources to the target container by limiting/patching minimal resources against it
| non_test | create resource exhaustion cpu chaos experiment at container level thanks for filing an issue before hitting the button please answer these questions describe in detail the feature behavior change you d like to see be ready for followup questions and please respond in a timely manner if we think a feature already exists we might close your issue if we re wrong please feel free to reopen it and explain why today the resource exhaustion chaos experiment generic cpu hog has been implemented at a node level this needs to be implemented at a container level as well this is a significant requirement where the idea is to obtain the impact of resource chaos on targeted applications without increasing the blast radius of the experiment itself some of the possible approaches include injecting a resource exhaustion process into the target container which may run stress stress ng tools inhibiting resources to the target container by limiting patching minimal resources against it | 0 |
120,742 | 17,644,270,345 | IssuesEvent | 2021-08-20 02:05:51 | DavidSpek/kale | https://api.github.com/repos/DavidSpek/kale | opened | CVE-2021-37691 (Medium) detected in tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl, tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl | security vulnerability | ## CVE-2021-37691 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b>, <b>tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>
<details><summary><b>tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/7b/c5/a97ed48fcc878e36bb05a3ea700c077360853c0994473a8f6b0ab4c2ddd2/tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/7b/c5/a97ed48fcc878e36bb05a3ea700c077360853c0994473a8f6b0ab4c2ddd2/tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: kale/examples/dog-breed-classification/requirements/requirements.txt</p>
<p>Path to vulnerable library: kale/examples/dog-breed-classification/requirements/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</details>
<details><summary><b>tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ef/73/205b5e7f8fe086ffe4165d984acb2c49fa3086f330f03099378753982d2e/tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ef/73/205b5e7f8fe086ffe4165d984acb2c49fa3086f330f03099378753982d2e/tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: kale/examples/taxi-cab-classification/requirements.txt</p>
<p>Path to vulnerable library: kale/examples/taxi-cab-classification/requirements.txt</p>
<p>
Dependency Hierarchy:
- tfx_bsl-0.21.4-cp27-cp27mu-manylinux2010_x86_64.whl (Root Library)
- :x: **tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). We have patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9. The fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37691>CVE-2021-37691</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27qf-jwm8-g7f3">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27qf-jwm8-g7f3</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-37691 (Medium) detected in tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl, tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl - ## CVE-2021-37691 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b>, <b>tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>
<details><summary><b>tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/7b/c5/a97ed48fcc878e36bb05a3ea700c077360853c0994473a8f6b0ab4c2ddd2/tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/7b/c5/a97ed48fcc878e36bb05a3ea700c077360853c0994473a8f6b0ab4c2ddd2/tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: kale/examples/dog-breed-classification/requirements/requirements.txt</p>
<p>Path to vulnerable library: kale/examples/dog-breed-classification/requirements/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.0.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</details>
<details><summary><b>tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ef/73/205b5e7f8fe086ffe4165d984acb2c49fa3086f330f03099378753982d2e/tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ef/73/205b5e7f8fe086ffe4165d984acb2c49fa3086f330f03099378753982d2e/tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: kale/examples/taxi-cab-classification/requirements.txt</p>
<p>Path to vulnerable library: kale/examples/taxi-cab-classification/requirements.txt</p>
<p>
Dependency Hierarchy:
- tfx_bsl-0.21.4-cp27-cp27mu-manylinux2010_x86_64.whl (Root Library)
- :x: **tensorflow-2.1.0-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). We have patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9. The fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37691>CVE-2021-37691</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27qf-jwm8-g7f3">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27qf-jwm8-g7f3</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in tensorflow whl tensorflow whl cve medium severity vulnerability vulnerable libraries tensorflow whl tensorflow whl tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file kale examples dog breed classification requirements requirements txt path to vulnerable library kale examples dog breed classification requirements requirements txt dependency hierarchy x tensorflow whl vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file kale examples taxi cab classification requirements txt path to vulnerable library kale examples taxi cab classification requirements txt dependency hierarchy tfx bsl whl root library x tensorflow whl vulnerable library found in base branch master vulnerability details tensorflow is an end to end open source platform for machine learning in affected versions an attacker can craft a tflite model that would trigger a division by zero error in lsh we have patched the issue in github commit the fix will be included in tensorflow we will also cherrypick thiscommit on tensorflow tensorflow and tensorflow as these are also affected and still in supported range publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu step up your open source security game with whitesource | 0 |
77,248 | 26,878,857,931 | IssuesEvent | 2023-02-05 11:40:31 | zed-industries/feedback | https://api.github.com/repos/zed-industries/feedback | opened | Refactoring in vim normal mode using f2 doesn't switch to editing mode | defect triage | ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
If I remain in vim normal mode and use `f2` to refactor a variable name, then the editor remains in normal mode.
Instead, it should switch to editing mode.
### Environment
MacBook Pro intel 2020, Venture, latest Zed.
### If applicable, add mockups / screenshots to help explain present your vision of the feature
_No response_
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
_No response_ | 1.0 | Refactoring in vim normal mode using f2 doesn't switch to editing mode - ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
If I remain in vim normal mode and use `f2` to refactor a variable name, then the editor remains in normal mode.
Instead, it should switch to editing mode.
### Environment
MacBook Pro intel 2020, Venture, latest Zed.
### If applicable, add mockups / screenshots to help explain present your vision of the feature
_No response_
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
_No response_ | non_test | refactoring in vim normal mode using doesn t switch to editing mode check for existing issues completed describe the bug provide steps to reproduce it if i remain in vim normal mode and use to refactor a variable name then the editor remains in normal mode instead it should switch to editing mode environment macbook pro intel venture latest zed if applicable add mockups screenshots to help explain present your vision of the feature no response if applicable attach your library logs zed zed log file to this issue if you only need the most recent lines you can run the zed open log command palette action to see the last no response | 0 |
183,122 | 14,200,570,113 | IssuesEvent | 2020-11-16 05:48:03 | remirror/remirror | https://api.github.com/repos/remirror/remirror | closed | New package `@remirror/extension-codemirror` | package: remirror :purple_circle: status: experimental :test_tube: type: feature :sparkles: type: new package :package: | ### Description
While the current code block extension works fine, it isn't a code editor. There's a lot of functionality that `codemirror` would provide for free which isn't available in the current implementation.
- [ ] Explore work required to add a cross-platform implementation of codemirror.
### Context
It would be great if I could jump straight to codemirror6 but, it looks like it's still a work in progress. | 1.0 | New package `@remirror/extension-codemirror` - ### Description
While the current code block extension works fine, it isn't a code editor. There's a lot of functionality that `codemirror` would provide for free which isn't available in the current implementation.
- [ ] Explore work required to add a cross-platform implementation of codemirror.
### Context
It would be great if I could jump straight to codemirror6 but, it looks like it's still a work in progress. | test | new package remirror extension codemirror description while the current code block extension works fine it isn t a code editor there s a lot of functionality that codemirror would provide for free which isn t available in the current implementation explore work required to add a cross platform implementation of codemirror context it would be great if i could jump straight to but it looks like it s still a work in progress | 1 |
34,621 | 4,934,344,041 | IssuesEvent | 2016-11-28 18:49:01 | medic/medic-webapp | https://api.github.com/repos/medic/medic-webapp | closed | Make migrations compatible with CouchDB 2.0 | 4 - Acceptance Testing | We have two or three migrations that use temporary views which have been removed in couchdb v2. Use either mango or create then delete persistent views to achieve the same result.
| 1.0 | Make migrations compatible with CouchDB 2.0 - We have two or three migrations that use temporary views which have been removed in couchdb v2. Use either mango or create then delete persistent views to achieve the same result.
| test | make migrations compatible with couchdb we have two or three migrations that use temporary views which have been removed in couchdb use either mango or create then delete persistent views to achieve the same result | 1 |
382,631 | 26,507,968,652 | IssuesEvent | 2023-01-18 15:07:33 | sovity/edc-extensions | https://api.github.com/repos/sovity/edc-extensions | closed | docs: update README with git bash | documentation | I would add that under Windows e.g. Git Bash can be used. I tested the script with Git Bash and it works fine.
_Originally posted by @ip312 in https://github.com/sovity/edc-extensions/issues/19#issuecomment-1386761662_
| 1.0 | docs: update README with git bash - I would add that under Windows e.g. Git Bash can be used. I tested the script with Git Bash and it works fine.
_Originally posted by @ip312 in https://github.com/sovity/edc-extensions/issues/19#issuecomment-1386761662_
| non_test | docs update readme with git bash i would add that under windows e g git bash can be used i tested the script with git bash and it works fine originally posted by in | 0 |
201,893 | 15,816,257,958 | IssuesEvent | 2021-04-05 12:48:44 | NFT-DAO/Governance-HOLON | https://api.github.com/repos/NFT-DAO/Governance-HOLON | closed | 01-Our-Projects | 01-Our-Projects Business-Plan documentation | - [x] Lock existing text in current version of Business Plan
- [x] Convert to markdown
- [x] Migrate "01-Our-Projects" to /01-Our-Projects/ folder | 1.0 | 01-Our-Projects - - [x] Lock existing text in current version of Business Plan
- [x] Convert to markdown
- [x] Migrate "01-Our-Projects" to /01-Our-Projects/ folder | non_test | our projects lock existing text in current version of business plan convert to markdown migrate our projects to our projects folder | 0 |
96,237 | 27,784,902,156 | IssuesEvent | 2023-03-17 01:47:28 | ziglang/zig | https://api.github.com/repos/ziglang/zig | opened | communicate the error when a test fails in release mode | enhancement contributor friendly zig build system | Extracted from https://github.com/ziglang/zig/pull/14647.
Running unit tests via the build system in release mode with a failure currently looks like this:
```zig
const std = @import("std");
test "oops" {
try std.testing.expect(false);
}
```
```
andy@ark ~/t/abc [1]> zig build test -Doptimize=ReleaseFast
run test: error: 'test.oops' failed
run test: error: the following test command failed:
/home/andy/tmp/abc/zig-cache/o/a12abb147b3c725378efb29b200da6fa/test --listen=-
Build Summary: 1/3 steps succeeded; 1 failed; 0/1 tests passed; 1 failed (disable with -fno-summary)
test transitive failure
└─ run test 0/1 passed, 1 failed
└─ zig test ReleaseFast native success 6s MaxRSS:171M
error: the following build command failed with exit code 1:
/home/andy/tmp/abc/zig-cache/o/689850d0ce8aa0fb1a06ce5b6bf02f7b/build /home/andy/Downloads/zig/build-release/stage3/bin/zig /home/andy/tmp/abc /home/andy/tmp/abc/zig-cache /home/andy/.cache/zig test -Doptimize=ReleaseFast
```
There is one piece of information that is lost, which is the fact that the test failed with `error.TestUnexpectedResult`. This information could be communicated via the TestResult message over test protocol, or the test runner could simply print the error name to stderr before reporting a failure. | 1.0 | communicate the error when a test fails in release mode - Extracted from https://github.com/ziglang/zig/pull/14647.
Running unit tests via the build system in release mode with a failure currently looks like this:
```zig
const std = @import("std");
test "oops" {
try std.testing.expect(false);
}
```
```
andy@ark ~/t/abc [1]> zig build test -Doptimize=ReleaseFast
run test: error: 'test.oops' failed
run test: error: the following test command failed:
/home/andy/tmp/abc/zig-cache/o/a12abb147b3c725378efb29b200da6fa/test --listen=-
Build Summary: 1/3 steps succeeded; 1 failed; 0/1 tests passed; 1 failed (disable with -fno-summary)
test transitive failure
└─ run test 0/1 passed, 1 failed
└─ zig test ReleaseFast native success 6s MaxRSS:171M
error: the following build command failed with exit code 1:
/home/andy/tmp/abc/zig-cache/o/689850d0ce8aa0fb1a06ce5b6bf02f7b/build /home/andy/Downloads/zig/build-release/stage3/bin/zig /home/andy/tmp/abc /home/andy/tmp/abc/zig-cache /home/andy/.cache/zig test -Doptimize=ReleaseFast
```
There is one piece of information that is lost, which is the fact that the test failed with `error.TestUnexpectedResult`. This information could be communicated via the TestResult message over test protocol, or the test runner could simply print the error name to stderr before reporting a failure. | non_test | communicate the error when a test fails in release mode extracted from running unit tests via the build system in release mode with a failure currently looks like this zig const std import std test oops try std testing expect false andy ark t abc zig build test doptimize releasefast run test error test oops failed run test error the following test command failed home andy tmp abc zig cache o test listen build summary steps succeeded failed tests passed failed disable with fno summary test transitive failure └─ run test passed failed └─ zig test releasefast native success maxrss error the following build command failed with exit code home andy tmp abc zig cache o build home andy downloads zig build release bin zig home andy tmp abc home andy tmp abc zig cache home andy cache zig test doptimize releasefast there is one piece of information that is lost which is the fact that the test failed with error testunexpectedresult this information could be communicated via the testresult message over test protocol or the test runner could simply print the error name to stderr before reporting a failure | 0 |
117,831 | 15,179,288,193 | IssuesEvent | 2021-02-14 18:55:38 | mui-org/material-ui | https://api.github.com/repos/mui-org/material-ui | reopened | [TextField] Make filled variant background / hover / focus states lighter | component: TextField good first issue material design | <!--- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
Hello,
I find the new filled variant TextField's background too dark.
How were the different rgba values picked? (https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/FilledInput/FilledInput.js#L17)
I tried using a [tool to calculate contrast ratio](https://contrast-ratio.com/#%23E8E8E8-on-%23FFFFFF) between the main background and the filled background on [material design example](https://material.io/design/components/text-fields.html#filled-text-field) and here are the difference between material-design examples and material-ui for each states :
| State| Material Design Spec|Material-UI|
|-------------|-------------|-----|
|Inactive|1.22|1.21|
|Activated|1.22|1.51|
|Focused|1.62|1.51|
|Hover|1.34|1.34|
|Error|1.22|1.51|
|Disabled|1.38|1.38|
These numbers are based on a light theme.
We can see that according to the specs, there is a difference between the focused state and the activated state in term of background color (the activated one is the same color as the inactive one, which is lighter than the focused one). You can see the different states [here](https://material.io/design/components/text-fields.html#filled-text-field), at the "States" section.
I suppose we should at least respect the "activated" state background color, so the contrast is better when typing. | 1.0 | [TextField] Make filled variant background / hover / focus states lighter - <!--- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
Hello,
I find the new filled variant TextField's background too dark.
How were the different rgba values picked? (https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/FilledInput/FilledInput.js#L17)
I tried using a [tool to calculate contrast ratio](https://contrast-ratio.com/#%23E8E8E8-on-%23FFFFFF) between the main background and the filled background on [material design example](https://material.io/design/components/text-fields.html#filled-text-field) and here are the difference between material-design examples and material-ui for each states :
| State| Material Design Spec|Material-UI|
|-------------|-------------|-----|
|Inactive|1.22|1.21|
|Activated|1.22|1.51|
|Focused|1.62|1.51|
|Hover|1.34|1.34|
|Error|1.22|1.51|
|Disabled|1.38|1.38|
These numbers are based on a light theme.
We can see that according to the specs, there is a difference between the focused state and the activated state in term of background color (the activated one is the same color as the inactive one, which is lighter than the focused one). You can see the different states [here](https://material.io/design/components/text-fields.html#filled-text-field), at the "States" section.
I suppose we should at least respect the "activated" state background color, so the contrast is better when typing. | non_test | make filled variant background hover focus states lighter thank you very much for contributing to material ui by creating an issue ❤️ to avoid duplicate issues we ask you to check off the following list this is not a x issue i have searched the of this repository and believe that this is not a duplicate hello i find the new filled variant textfield s background too dark how were the different rgba values picked i tried using a between the main background and the filled background on and here are the difference between material design examples and material ui for each states state material design spec material ui inactive activated focused hover error disabled these numbers are based on a light theme we can see that according to the specs there is a difference between the focused state and the activated state in term of background color the activated one is the same color as the inactive one which is lighter than the focused one you can see the different states at the states section i suppose we should at least respect the activated state background color so the contrast is better when typing | 0 |
86,728 | 24,936,367,011 | IssuesEvent | 2022-10-31 15:25:23 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | [Mono] System.Text.RegularExpressions.Tests source generator tests crash in DeflateInit2_ | area-VM-meta-mono in-pr Known Build Error | ```
=================================================================
Managed Stacktrace:
=================================================================
at <unknown> <0xffffffff>
at <unknown> <0xffffffff>
at ZLibStreamHandle:DeflateInit2_ <0x00073>
at System.IO.Compression.ZLibNative:CreateZLibStreamForDeflate <0x000a3>
at System.IO.Compression.Deflater:.ctor <0x00133>
at System.IO.Compression.DeflateStream:InitializeDeflater <0x00087>
at System.IO.Compression.DeflateStream:.ctor <0x0006b>
at System.IO.Compression.DeflateStream:.ctor <0x0004b>
at System.Reflection.PortableExecutable.DebugDirectoryBuilder:WriteEmbeddedPortablePdbData <0x00107>
at System.Reflection.PortableExecutable.DebugDirectoryBuilder:AddEmbeddedPortablePdbEntry <0x00087>
at Microsoft.Cci.PeWriter:WritePeToStream <0x00cdb>
at Microsoft.CodeAnalysis.Compilation:SerializePeToStream <0x001b7>
at Microsoft.CodeAnalysis.Compilation:SerializeToPeStream <0x006f7>
at Microsoft.CodeAnalysis.Compilation:Emit <0x00587>
```
## Build Information
Log: https://dev.azure.com/dnceng-public/public/_build/results?buildId=53859&view=ms.vss-test-web.build-test-results-tab&runId=1102432&paneView=debug&resultId=196512
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=53859
Build error leg or test failing: System.Text.RegularExpressions.Tests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime/pull/77088
```json
{
"ErrorMessage": "at ZLibStreamHandle:DeflateInit2_",
"BuildRetry": false
}
```
<!--Known issue error report start -->
### Report
|Build|Definition|Test|Pull Request|
|---|---|---|---|
|[56035](https://dev.azure.com/dnceng-public/public/_build/results?buildId=56035)|dotnet/runtime|[System.Text.RegularExpressions.Tests.WorkItemExecution](https://dev.azure.com/dnceng-public/public/_build/results?buildId=56035&view=ms.vss-test-web.build-test-results-tab&runId=1149346&resultId=196550)|dotnet/runtime#77170|
|[53859](https://dev.azure.com/dnceng-public/public/_build/results?buildId=53859)|dotnet/runtime|[System.Text.RegularExpressions.Tests.WorkItemExecution](https://dev.azure.com/dnceng-public/public/_build/results?buildId=53859&view=ms.vss-test-web.build-test-results-tab&runId=1102432&resultId=196512)|dotnet/runtime#77088|
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|0|2|
<!--Known issue error report end --> | 1.0 | [Mono] System.Text.RegularExpressions.Tests source generator tests crash in DeflateInit2_ - ```
=================================================================
Managed Stacktrace:
=================================================================
at <unknown> <0xffffffff>
at <unknown> <0xffffffff>
at ZLibStreamHandle:DeflateInit2_ <0x00073>
at System.IO.Compression.ZLibNative:CreateZLibStreamForDeflate <0x000a3>
at System.IO.Compression.Deflater:.ctor <0x00133>
at System.IO.Compression.DeflateStream:InitializeDeflater <0x00087>
at System.IO.Compression.DeflateStream:.ctor <0x0006b>
at System.IO.Compression.DeflateStream:.ctor <0x0004b>
at System.Reflection.PortableExecutable.DebugDirectoryBuilder:WriteEmbeddedPortablePdbData <0x00107>
at System.Reflection.PortableExecutable.DebugDirectoryBuilder:AddEmbeddedPortablePdbEntry <0x00087>
at Microsoft.Cci.PeWriter:WritePeToStream <0x00cdb>
at Microsoft.CodeAnalysis.Compilation:SerializePeToStream <0x001b7>
at Microsoft.CodeAnalysis.Compilation:SerializeToPeStream <0x006f7>
at Microsoft.CodeAnalysis.Compilation:Emit <0x00587>
```
## Build Information
Log: https://dev.azure.com/dnceng-public/public/_build/results?buildId=53859&view=ms.vss-test-web.build-test-results-tab&runId=1102432&paneView=debug&resultId=196512
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=53859
Build error leg or test failing: System.Text.RegularExpressions.Tests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime/pull/77088
```json
{
"ErrorMessage": "at ZLibStreamHandle:DeflateInit2_",
"BuildRetry": false
}
```
<!--Known issue error report start -->
### Report
|Build|Definition|Test|Pull Request|
|---|---|---|---|
|[56035](https://dev.azure.com/dnceng-public/public/_build/results?buildId=56035)|dotnet/runtime|[System.Text.RegularExpressions.Tests.WorkItemExecution](https://dev.azure.com/dnceng-public/public/_build/results?buildId=56035&view=ms.vss-test-web.build-test-results-tab&runId=1149346&resultId=196550)|dotnet/runtime#77170|
|[53859](https://dev.azure.com/dnceng-public/public/_build/results?buildId=53859)|dotnet/runtime|[System.Text.RegularExpressions.Tests.WorkItemExecution](https://dev.azure.com/dnceng-public/public/_build/results?buildId=53859&view=ms.vss-test-web.build-test-results-tab&runId=1102432&resultId=196512)|dotnet/runtime#77088|
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|0|2|
<!--Known issue error report end --> | non_test | system text regularexpressions tests source generator tests crash in managed stacktrace at at at zlibstreamhandle at system io compression zlibnative createzlibstreamfordeflate at system io compression deflater ctor at system io compression deflatestream initializedeflater at system io compression deflatestream ctor at system io compression deflatestream ctor at system reflection portableexecutable debugdirectorybuilder writeembeddedportablepdbdata at system reflection portableexecutable debugdirectorybuilder addembeddedportablepdbentry at microsoft cci pewriter writepetostream at microsoft codeanalysis compilation serializepetostream at microsoft codeanalysis compilation serializetopestream at microsoft codeanalysis compilation emit build information log build build error leg or test failing system text regularexpressions tests workitemexecution pull request json errormessage at zlibstreamhandle buildretry false report build definition test pull request summary hour hit count day hit count month count | 0 |
408,901 | 27,714,701,011 | IssuesEvent | 2023-03-14 16:13:11 | emacs-elsa/Elsa | https://api.github.com/repos/emacs-elsa/Elsa | reopened | Add type for eieio classes | enhancement scope:types package:eieio scope:documentation | What we need at minimum:
- [x] Parse the properties and get their types from native eieio type annotations
- [x] Add annotation syntax for slots with more complex types
- [x] Resolve the type hierarchy (what is parent of what and what can be substituted for what).
- [x] Teach `oref` and `oset` to work with this information.
| 1.0 | Add type for eieio classes - What we need at minimum:
- [x] Parse the properties and get their types from native eieio type annotations
- [x] Add annotation syntax for slots with more complex types
- [x] Resolve the type hierarchy (what is parent of what and what can be substituted for what).
- [x] Teach `oref` and `oset` to work with this information.
| non_test | add type for eieio classes what we need at minimum parse the properties and get their types from native eieio type annotations add annotation syntax for slots with more complex types resolve the type hierarchy what is parent of what and what can be substituted for what teach oref and oset to work with this information | 0 |
46,481 | 13,170,451,185 | IssuesEvent | 2020-08-11 15:11:08 | shaundmorris/ddf | https://api.github.com/repos/shaundmorris/ddf | closed | WS-2018-0210 Low Severity Vulnerability detected by WhiteSource | security vulnerability wontfix | ## WS-2018-0210 - Low Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>path: /tmp/git/ddf/libs/libs-pomfix/node_modules/babel-core/node_modules/lodash/package.json</p>
<p>
<p>Library home page: <a href=http://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz>http://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
Dependency Hierarchy:
- standard-5.4.1.tgz (Root Library)
- standard-engine-2.2.5.tgz
- eslint-1.9.0.tgz
- inquirer-0.11.4.tgz
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the node_module "lodash" before version 4.17.11 the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.
<p>Publish Date: 2018-11-25
<p>URL: <a href=https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad>WS-2018-0210</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>3.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad">https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad</a></p>
<p>Release Date: 2018-08-31</p>
<p>Fix Resolution: Replace or update the following files: lodash.js, test.js</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2018-0210 Low Severity Vulnerability detected by WhiteSource - ## WS-2018-0210 - Low Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>path: /tmp/git/ddf/libs/libs-pomfix/node_modules/babel-core/node_modules/lodash/package.json</p>
<p>
<p>Library home page: <a href=http://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz>http://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
Dependency Hierarchy:
- standard-5.4.1.tgz (Root Library)
- standard-engine-2.2.5.tgz
- eslint-1.9.0.tgz
- inquirer-0.11.4.tgz
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the node_module "lodash" before version 4.17.11 the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.
<p>Publish Date: 2018-11-25
<p>URL: <a href=https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad>WS-2018-0210</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>3.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad">https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad</a></p>
<p>Release Date: 2018-08-31</p>
<p>Fix Resolution: Replace or update the following files: lodash.js, test.js</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 | ws low severity vulnerability detected by whitesource ws low severity vulnerability vulnerable library lodash tgz the modern build of lodash modular utilities path tmp git ddf libs libs pomfix node modules babel core node modules lodash package json library home page a href dependency hierarchy standard tgz root library standard engine tgz eslint tgz inquirer tgz x lodash tgz vulnerable library vulnerability details in the node module lodash before version the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of the object prototype these properties will be present on all objects publish date url a href cvss score details base score metrics not available suggested fix type change files origin a href release date fix resolution replace or update the following files lodash js test js step up your open source security game with whitesource | 0 |
219,651 | 17,104,133,227 | IssuesEvent | 2021-07-09 15:11:30 | RockefellerArchiveCenter/aurora | https://api.github.com/repos/RockefellerArchiveCenter/aurora | closed | Improve unit test coverage of User views | unit tests | ## Is your feature request related to a problem? Please describe.
The user views are not fully covered by unit tests.
## Describe the solution you'd like
Add or enhance tests to improve coverage.
## Additional context
Missing lines:
- 40
- 48-54
- 74
- 103-104
- 127
- 137-139
- 142
- 145-147
- 164-166 | 1.0 | Improve unit test coverage of User views - ## Is your feature request related to a problem? Please describe.
The user views are not fully covered by unit tests.
## Describe the solution you'd like
Add or enhance tests to improve coverage.
## Additional context
Missing lines:
- 40
- 48-54
- 74
- 103-104
- 127
- 137-139
- 142
- 145-147
- 164-166 | test | improve unit test coverage of user views is your feature request related to a problem please describe the user views are not fully covered by unit tests describe the solution you d like add or enhance tests to improve coverage additional context missing lines | 1 |
117,016 | 15,038,310,976 | IssuesEvent | 2021-02-02 17:17:59 | hydroshare/hydroshare | https://api.github.com/repos/hydroshare/hydroshare | closed | Facets contain duplicates and incorrect items | BLOCKED Discover bug design phase needed | The facets on the discover page are not curated. This is problematic because it results in both duplicate and incorrect values in the facets. For example, some names appear multiple times in the "Author" filter because a name may be associated with more than one account. Similarly, some names in the "Author" filter are not human names. This is because users are allowed to enter any value in the author field. Examples are shown below.
| 1.0 | Facets contain duplicates and incorrect items - The facets on the discover page are not curated. This is problematic because it results in both duplicate and incorrect values in the facets. For example, some names appear multiple times in the "Author" filter because a name may be associated with more than one account. Similarly, some names in the "Author" filter are not human names. This is because users are allowed to enter any value in the author field. Examples are shown below.
| non_test | facets contain duplicates and incorrect items the facets on the discover page are not curated this is problematic because it results in both duplicate and incorrect values in the facets for example some names appear multiple times in the author filter because a name may be associated with more than one account similarly some names in the author filter are not human names this is because users are allowed to enter any value in the author field examples are shown below | 0 |
345,312 | 24,852,782,515 | IssuesEvent | 2022-10-26 21:46:39 | FTBTeam/FTB-Modpack-Issues | https://api.github.com/repos/FTBTeam/FTB-Modpack-Issues | closed | [Bug]: Quest Twisting the Essence of Life reward contains visible Command | state: Fixed in Dev :hammer_and_wrench: 2: Documentation FTB Inferno | ### Modpack
FTB Inferno
### Modpack version
1.0.3
### Log Files
N/A
### Describe the bug
One of rewards of the Twisting the Essence of Life quest is visible command.
### Steps to reproduce
Open the mentioned quest and check the rewards.
### Expected behaviour
Command is not visible.
### Screenshots
### Additional information
_No response_ | 1.0 | [Bug]: Quest Twisting the Essence of Life reward contains visible Command - ### Modpack
FTB Inferno
### Modpack version
1.0.3
### Log Files
N/A
### Describe the bug
One of rewards of the Twisting the Essence of Life quest is visible command.
### Steps to reproduce
Open the mentioned quest and check the rewards.
### Expected behaviour
Command is not visible.
### Screenshots
### Additional information
_No response_ | non_test | quest twisting the essence of life reward contains visible command modpack ftb inferno modpack version log files n a describe the bug one of rewards of the twisting the essence of life quest is visible command steps to reproduce open the mentioned quest and check the rewards expected behaviour command is not visible screenshots additional information no response | 0 |
49,785 | 6,040,058,922 | IssuesEvent | 2017-06-10 10:23:47 | shaarli/netscape-bookmark-parser | https://api.github.com/repos/shaarli/netscape-bookmark-parser | closed | Importing descriptions | enhancement tests | I had a problem importing descriptions from an old scuttle installation.
Is it possible that the regexp pattern is too specific? I had to change the pattern in line 148
https://github.com/shaarli/netscape-bookmark-parser/blob/master/NetscapeBookmarkParser.php#L148
from
`/note="(.*?)"<\/a>/i`
to
`/note="(.*?)"/i`
ie. removing the requirement for the description to be immediately followed by the closing anchor-tag. (my export had attributes like the tags and the date etc in between the description and the closing anchor.
also, the description in the scuttle export is called "description", instead of "note". so maybe the parser could check for both versions? | 1.0 | Importing descriptions - I had a problem importing descriptions from an old scuttle installation.
Is it possible that the regexp pattern is too specific? I had to change the pattern in line 148
https://github.com/shaarli/netscape-bookmark-parser/blob/master/NetscapeBookmarkParser.php#L148
from
`/note="(.*?)"<\/a>/i`
to
`/note="(.*?)"/i`
ie. removing the requirement for the description to be immediately followed by the closing anchor-tag. (my export had attributes like the tags and the date etc in between the description and the closing anchor.
also, the description in the scuttle export is called "description", instead of "note". so maybe the parser could check for both versions? | test | importing descriptions i had a problem importing descriptions from an old scuttle installation is it possible that the regexp pattern is too specific i had to change the pattern in line from note i to note i ie removing the requirement for the description to be immediately followed by the closing anchor tag my export had attributes like the tags and the date etc in between the description and the closing anchor also the description in the scuttle export is called description instead of note so maybe the parser could check for both versions | 1 |
226,110 | 17,949,438,297 | IssuesEvent | 2021-09-12 12:48:05 | TWiStErRob/net.twisterrob.cinema | https://api.github.com/repos/TWiStErRob/net.twisterrob.cinema | reopened | Update Node and NPM | is:feature in:web in:nodejs in:test | ```
> twisterrob-cinema-web-backend@ postinstall P:\projects\workspace\Cineworld Cinema\Heroku\backend
> echo Installed Backend dependencies
Installed Backend dependencies
added 271 packages from 197 contributors and audited 273 packages in 5.088s
found 55 vulnerabilities (20 low, 14 moderate, 21 high)
run `npm audit fix` to fix them, or `npm audit` for details
╭────────────────────────────────────────────────────────────────╮
│ │
│ New major version of npm available! 6.2.0 -> 7.23.0 │
│ Changelog: https://github.com/npm/cli/releases/tag/v7.23.0 │
│ Run npm install -g npm to update! │
│ │
╰────────────────────────────────────────────────────────────────╯
``` | 1.0 | Update Node and NPM - ```
> twisterrob-cinema-web-backend@ postinstall P:\projects\workspace\Cineworld Cinema\Heroku\backend
> echo Installed Backend dependencies
Installed Backend dependencies
added 271 packages from 197 contributors and audited 273 packages in 5.088s
found 55 vulnerabilities (20 low, 14 moderate, 21 high)
run `npm audit fix` to fix them, or `npm audit` for details
╭────────────────────────────────────────────────────────────────╮
│ │
│ New major version of npm available! 6.2.0 -> 7.23.0 │
│ Changelog: https://github.com/npm/cli/releases/tag/v7.23.0 │
│ Run npm install -g npm to update! │
│ │
╰────────────────────────────────────────────────────────────────╯
``` | test | update node and npm twisterrob cinema web backend postinstall p projects workspace cineworld cinema heroku backend echo installed backend dependencies installed backend dependencies added packages from contributors and audited packages in found vulnerabilities low moderate high run npm audit fix to fix them or npm audit for details ╭────────────────────────────────────────────────────────────────╮ │ │ │ new major version of npm available │ │ changelog │ │ run npm install g npm to update │ │ │ ╰────────────────────────────────────────────────────────────────╯ | 1 |
209,235 | 16,011,456,285 | IssuesEvent | 2021-04-20 11:07:52 | urapadmin/kiosk | https://api.github.com/repos/urapadmin/kiosk | closed | typo in feature deletion warning | filemaker small test-stage | Was testing #768 and noticed a teeny tiny typo in the feature deletion warning ("realy" should be "really").
Don't kill me. | 1.0 | typo in feature deletion warning - Was testing #768 and noticed a teeny tiny typo in the feature deletion warning ("realy" should be "really").
Don't kill me. | test | typo in feature deletion warning was testing and noticed a teeny tiny typo in the feature deletion warning realy should be really don t kill me | 1 |
15,657 | 8,997,708,231 | IssuesEvent | 2019-02-02 15:06:21 | VirtusLab/git-machete | https://api.github.com/repos/VirtusLab/git-machete | opened | Optimize fetching the repository state via git commands | performance | Especially:
1. Avoid multiple runs of `git rev-parse`, better fetch as much as possible via a single `git for-each-ref` run
2. Optimize is-ancestor check - first check if the SHAs of the given revisions are equal, also cache the merge-bases instead of just doing the `merge-base --is-ancestor` check to enable the inverted ancestor check
3. Check if git version is >= 2.14.2, if so then fetch reflogs for all desired branches in a single run (as opposed to fetching them one-by-one, which is necessary on git < 2.14.2 due to a subtle bug in how reflogs are walked). | True | Optimize fetching the repository state via git commands - Especially:
1. Avoid multiple runs of `git rev-parse`, better fetch as much as possible via a single `git for-each-ref` run
2. Optimize is-ancestor check - first check if the SHAs of the given revisions are equal, also cache the merge-bases instead of just doing the `merge-base --is-ancestor` check to enable the inverted ancestor check
3. Check if git version is >= 2.14.2, if so then fetch reflogs for all desired branches in a single run (as opposed to fetching them one-by-one, which is necessary on git < 2.14.2 due to a subtle bug in how reflogs are walked). | non_test | optimize fetching the repository state via git commands especially avoid multiple runs of git rev parse better fetch as much as possible via a single git for each ref run optimize is ancestor check first check if the shas of the given revisions are equal also cache the merge bases instead of just doing the merge base is ancestor check to enable the inverted ancestor check check if git version is if so then fetch reflogs for all desired branches in a single run as opposed to fetching them one by one which is necessary on git due to a subtle bug in how reflogs are walked | 0 |
95,407 | 8,557,771,227 | IssuesEvent | 2018-11-08 16:28:54 | LiskHQ/lisk-hub | https://api.github.com/repos/LiskHQ/lisk-hub | closed | Enable component tests in Jest L106-L115 | type: test | Tests should be fixed so that these lines can be uncommented and Jest tests pass
https://github.com/LiskHQ/lisk-hub/blob/ddaa5709fafd6f91bcca20a90a770dc4335c5b3c/jest.config.js#L106-L115 | 1.0 | Enable component tests in Jest L106-L115 - Tests should be fixed so that these lines can be uncommented and Jest tests pass
https://github.com/LiskHQ/lisk-hub/blob/ddaa5709fafd6f91bcca20a90a770dc4335c5b3c/jest.config.js#L106-L115 | test | enable component tests in jest tests should be fixed so that these lines can be uncommented and jest tests pass | 1 |
195,194 | 14,706,899,940 | IssuesEvent | 2021-01-04 20:39:48 | phetsims/bending-light | https://api.github.com/repos/phetsims/bending-light | closed | CT Bounds mismatch after validateBounds | type:automated-testing | ```
bending-light : fuzz : unbuilt : assertSlow
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/bending-light/bending-light_en.html?continuousTest=%7B%22test%22%3A%5B%22bending-light%22%2C%22fuzz%22%2C%22unbuilt%22%2C%22assertSlow%22%5D%2C%22snapshotName%22%3A%22snapshot-1606867678068%22%2C%22timestamp%22%3A1606882690164%7D&brand=phet&eall&fuzz&memoryLimit=1000
Query: brand=phet&eall&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/assert/js/assert.js:25:13)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1369:23
at ShadedRectangle.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1374:10)
at Node.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1218:29)
at TinyStaticProperty.get (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyStaticProperty.js:38:10)
at TinyStaticProperty.get value [as value] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyProperty.js:52:17)
at Node.getBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1784:32)
at Node.getRightBottom (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3131:17)
at Node.get rightBottom [as rightBottom] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3133:35)
at new NodeProperty (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/util/NodeProperty.js:25:16)
id: Bayes Chrome
Snapshot from 12/1/2020, 5:07:58 PM
----------------------------------
bending-light : fuzz : unbuilt : assertSlow
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/bending-light/bending-light_en.html?continuousTest=%7B%22test%22%3A%5B%22bending-light%22%2C%22fuzz%22%2C%22unbuilt%22%2C%22assertSlow%22%5D%2C%22snapshotName%22%3A%22snapshot-1606867678068%22%2C%22timestamp%22%3A1606898506453%7D&brand=phet&eall&fuzz&memoryLimit=1000
Query: brand=phet&eall&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/assert/js/assert.js:25:13)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1369:23
at ShadedRectangle.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1374:10)
at Node.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1218:29)
at TinyStaticProperty.get (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyStaticProperty.js:38:10)
at TinyStaticProperty.get value [as value] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyProperty.js:52:17)
at Node.getBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1784:32)
at Node.getRightBottom (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3131:17)
at Node.get rightBottom [as rightBottom] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3133:35)
at new NodeProperty (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/util/NodeProperty.js:25:16)
id: Bayes Chrome
Snapshot from 12/1/2020, 5:07:58 PM
----------------------------------
bending-light : fuzz : unbuilt : assertSlow
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/bending-light/bending-light_en.html?continuousTest=%7B%22test%22%3A%5B%22bending-light%22%2C%22fuzz%22%2C%22unbuilt%22%2C%22assertSlow%22%5D%2C%22snapshotName%22%3A%22snapshot-1606867678068%22%2C%22timestamp%22%3A1606914135332%7D&brand=phet&eall&fuzz&memoryLimit=1000
Query: brand=phet&eall&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/assert/js/assert.js:25:13)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1369:23
at ShadedRectangle.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1374:10)
at Node.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1218:29)
at TinyStaticProperty.get (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyStaticProperty.js:38:10)
at TinyStaticProperty.get value [as value] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyProperty.js:52:17)
at Node.getBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1784:32)
at Node.getRightBottom (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3131:17)
at Node.get rightBottom [as rightBottom] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3133:35)
at new NodeProperty (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/util/NodeProperty.js:25:16)
id: Bayes Chrome
Snapshot from 12/1/2020, 5:07:58 PM
``` | 1.0 | CT Bounds mismatch after validateBounds - ```
bending-light : fuzz : unbuilt : assertSlow
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/bending-light/bending-light_en.html?continuousTest=%7B%22test%22%3A%5B%22bending-light%22%2C%22fuzz%22%2C%22unbuilt%22%2C%22assertSlow%22%5D%2C%22snapshotName%22%3A%22snapshot-1606867678068%22%2C%22timestamp%22%3A1606882690164%7D&brand=phet&eall&fuzz&memoryLimit=1000
Query: brand=phet&eall&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/assert/js/assert.js:25:13)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1369:23
at ShadedRectangle.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1374:10)
at Node.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1218:29)
at TinyStaticProperty.get (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyStaticProperty.js:38:10)
at TinyStaticProperty.get value [as value] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyProperty.js:52:17)
at Node.getBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1784:32)
at Node.getRightBottom (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3131:17)
at Node.get rightBottom [as rightBottom] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3133:35)
at new NodeProperty (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/util/NodeProperty.js:25:16)
id: Bayes Chrome
Snapshot from 12/1/2020, 5:07:58 PM
----------------------------------
bending-light : fuzz : unbuilt : assertSlow
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/bending-light/bending-light_en.html?continuousTest=%7B%22test%22%3A%5B%22bending-light%22%2C%22fuzz%22%2C%22unbuilt%22%2C%22assertSlow%22%5D%2C%22snapshotName%22%3A%22snapshot-1606867678068%22%2C%22timestamp%22%3A1606898506453%7D&brand=phet&eall&fuzz&memoryLimit=1000
Query: brand=phet&eall&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/assert/js/assert.js:25:13)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1369:23
at ShadedRectangle.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1374:10)
at Node.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1218:29)
at TinyStaticProperty.get (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyStaticProperty.js:38:10)
at TinyStaticProperty.get value [as value] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyProperty.js:52:17)
at Node.getBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1784:32)
at Node.getRightBottom (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3131:17)
at Node.get rightBottom [as rightBottom] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3133:35)
at new NodeProperty (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/util/NodeProperty.js:25:16)
id: Bayes Chrome
Snapshot from 12/1/2020, 5:07:58 PM
----------------------------------
bending-light : fuzz : unbuilt : assertSlow
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/bending-light/bending-light_en.html?continuousTest=%7B%22test%22%3A%5B%22bending-light%22%2C%22fuzz%22%2C%22unbuilt%22%2C%22assertSlow%22%5D%2C%22snapshotName%22%3A%22snapshot-1606867678068%22%2C%22timestamp%22%3A1606914135332%7D&brand=phet&eall&fuzz&memoryLimit=1000
Query: brand=phet&eall&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
Error: Assertion failed: Bounds mismatch after validateBounds: [x:(8.849999999999994,126.15),y:(11,69)], expected: [x:(5.849999999999994,129.15),y:(8,72)]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/assert/js/assert.js:25:13)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1369:23
at ShadedRectangle.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1374:10)
at Node.validateBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1218:29)
at TinyStaticProperty.get (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyStaticProperty.js:38:10)
at TinyStaticProperty.get value [as value] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/axon/js/TinyProperty.js:52:17)
at Node.getBounds (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:1784:32)
at Node.getRightBottom (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3131:17)
at Node.get rightBottom [as rightBottom] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/nodes/Node.js:3133:35)
at new NodeProperty (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1606867678068/scenery/js/util/NodeProperty.js:25:16)
id: Bayes Chrome
Snapshot from 12/1/2020, 5:07:58 PM
``` | test | ct bounds mismatch after validatebounds bending light fuzz unbuilt assertslow query brand phet eall fuzz memorylimit uncaught error assertion failed bounds mismatch after validatebounds expected error assertion failed bounds mismatch after validatebounds expected at window assertions assertfunction at at shadedrectangle validatebounds at node validatebounds at tinystaticproperty get at tinystaticproperty get value at node getbounds at node getrightbottom at node get rightbottom at new nodeproperty id bayes chrome snapshot from pm bending light fuzz unbuilt assertslow query brand phet eall fuzz memorylimit uncaught error assertion failed bounds mismatch after validatebounds expected error assertion failed bounds mismatch after validatebounds expected at window assertions assertfunction at at shadedrectangle validatebounds at node validatebounds at tinystaticproperty get at tinystaticproperty get value at node getbounds at node getrightbottom at node get rightbottom at new nodeproperty id bayes chrome snapshot from pm bending light fuzz unbuilt assertslow query brand phet eall fuzz memorylimit uncaught error assertion failed bounds mismatch after validatebounds expected error assertion failed bounds mismatch after validatebounds expected at window assertions assertfunction at at shadedrectangle validatebounds at node validatebounds at tinystaticproperty get at tinystaticproperty get value at node getbounds at node getrightbottom at node get rightbottom at new nodeproperty id bayes chrome snapshot from pm | 1 |
324,360 | 9,888,415,406 | IssuesEvent | 2019-06-25 11:30:33 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | en.m.wikipedia.org - design is broken | browser-firefox-mobile engine-gecko priority-critical | <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://en.m.wikipedia.org/wiki/List_of_most_expensive_paintings
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: No
**Problem type**: Design is broken
**Description**: Wikipedia table sorting broken on mobile
**Steps to Reproduce**:
No arrows to sort tables unless in desktop mode.
[](https://webcompat.com/uploads/2019/6/81155b14-1e15-4792-a15c-33d285c61324.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190621074959</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | en.m.wikipedia.org - design is broken - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://en.m.wikipedia.org/wiki/List_of_most_expensive_paintings
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: No
**Problem type**: Design is broken
**Description**: Wikipedia table sorting broken on mobile
**Steps to Reproduce**:
No arrows to sort tables unless in desktop mode.
[](https://webcompat.com/uploads/2019/6/81155b14-1e15-4792-a15c-33d285c61324.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190621074959</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | en m wikipedia org design is broken url browser version firefox mobile operating system android tested another browser no problem type design is broken description wikipedia table sorting broken on mobile steps to reproduce no arrows to sort tables unless in desktop mode browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen true mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel nightly from with ❤️ | 0 |
146,869 | 11,759,616,371 | IssuesEvent | 2020-03-13 17:38:23 | MichaIng/DietPi | https://api.github.com/repos/MichaIng/DietPi | closed | Pinebook | Suspend to RAM not working | Kernel related Known Issue Pinebook Testing/testers required :arrow_down_small: | #### Required Information:
- DietPi version | `cat /DietPi/dietpi/.version`
```
#!/bin/bash
G_DIETPI_VERSION_CORE=6
G_DIETPI_VERSION_SUB=18
G_DIETPI_VERSION_RC=14
G_GITBRANCH=master
G_GITOWNER=Fourdee
```
- Distro version | `echo $G_DISTRO_NAME` or `cat /etc/debian_version`
`stretch`
- Kernel version | `uname -a`
`Linux DietPi 4.19.2-sunxi64 #92 SMP Thu Nov 22 19:26:30 CET 2018 aarch64 GNU/Linux`
- SBC device | `echo $G_HW_MODEL_DESCRIPTION` or (EG: RPi3)
`Pinebook 1080p (aarch64)`
- Power supply used | (EG: 5V 1A RAVpower)
`5V 3A (official Pinebook power supply)`
- SDcard used | (EG: SanDisk ultra)
`16GB internal eMMC`
#### Steps to reproduce:
<!-- Explain how to reproduce the issue -->
1. Install DietPi on Pinebook; flash the image on an SD card and then dd it on the internal eMMC module, as per instructions here https://github.com/Fourdee/DietPi/issues/2299#issue-385428882
2. run `systemctl suspend` as root
#### Expected behaviour:
<!-- What SHOULD be happening? -->
- System suspends to RAM
#### Actual behaviour:
<!-- What IS happening? -->
- Screen goes black for a while and normal execution resumes. Additionally X server crashes.
#### Extra details:
<!-- Please post any extra details that might help solve the issue -->
- dmesg output after attempt:
```
[ 632.792505] PM: suspend entry (s2idle)
[ 632.792515] PM: Syncing filesystems ... done.
[ 632.962214] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 632.964271] OOM killer disabled.
[ 632.964273] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 632.965687] Suspending console(s) (use no_console_suspend to debug)
[ 632.981420] RTL871X: suspend start
[ 632.981456] RTL871X: rtw_cmd_thread(wlan0) stop_req:1, break
[ 632.982027] RTL871X: rtw_dev_unload: driver not in IPS
[ 632.988747] RTL871X: rtw suspend success in 4 ms
[ 632.988770] dpm_run_callback(): pm_generic_suspend+0x0/0x40 returns -38
[ 632.988780] PM: Device mmc1:0001:1 failed to suspend async: error -38
[ 633.060889] PM: Some devices failed to suspend, or early wake event detected
[ 633.162077] OOM killer enabled.
[ 633.162082] Restarting tasks ... done.
[ 633.163973] PM: suspend exit
[ 633.164189] PM: suspend entry (s2idle)
[ 633.164192] PM: Syncing filesystems ... done.
[ 633.193336] r8152 1-1:1.0 eth0: carrier on
[ 633.346619] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 633.348601] OOM killer disabled.
[ 633.348603] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 633.350026] Suspending console(s) (use no_console_suspend to debug)
[ 636.356700] dpm_run_callback(): pm_generic_suspend+0x0/0x40 returns -38
[ 636.356714] PM: Device mmc1:0001:1 failed to suspend async: error -38
[ 636.356744] PM: Some devices failed to suspend, or early wake event detected
[ 636.477527] r8152 1-1:1.0 eth0: carrier on
[ 636.505808] OOM killer enabled.
[ 636.505812] Restarting tasks ... done.
[ 636.550309] PM: suspend exit
``` | 2.0 | Pinebook | Suspend to RAM not working - #### Required Information:
- DietPi version | `cat /DietPi/dietpi/.version`
```
#!/bin/bash
G_DIETPI_VERSION_CORE=6
G_DIETPI_VERSION_SUB=18
G_DIETPI_VERSION_RC=14
G_GITBRANCH=master
G_GITOWNER=Fourdee
```
- Distro version | `echo $G_DISTRO_NAME` or `cat /etc/debian_version`
`stretch`
- Kernel version | `uname -a`
`Linux DietPi 4.19.2-sunxi64 #92 SMP Thu Nov 22 19:26:30 CET 2018 aarch64 GNU/Linux`
- SBC device | `echo $G_HW_MODEL_DESCRIPTION` or (EG: RPi3)
`Pinebook 1080p (aarch64)`
- Power supply used | (EG: 5V 1A RAVpower)
`5V 3A (official Pinebook power supply)`
- SDcard used | (EG: SanDisk ultra)
`16GB internal eMMC`
#### Steps to reproduce:
<!-- Explain how to reproduce the issue -->
1. Install DietPi on Pinebook; flash the image on an SD card and then dd it on the internal eMMC module, as per instructions here https://github.com/Fourdee/DietPi/issues/2299#issue-385428882
2. run `systemctl suspend` as root
#### Expected behaviour:
<!-- What SHOULD be happening? -->
- System suspends to RAM
#### Actual behaviour:
<!-- What IS happening? -->
- Screen goes black for a while and normal execution resumes. Additionally X server crashes.
#### Extra details:
<!-- Please post any extra details that might help solve the issue -->
- dmesg output after attempt:
```
[ 632.792505] PM: suspend entry (s2idle)
[ 632.792515] PM: Syncing filesystems ... done.
[ 632.962214] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 632.964271] OOM killer disabled.
[ 632.964273] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 632.965687] Suspending console(s) (use no_console_suspend to debug)
[ 632.981420] RTL871X: suspend start
[ 632.981456] RTL871X: rtw_cmd_thread(wlan0) stop_req:1, break
[ 632.982027] RTL871X: rtw_dev_unload: driver not in IPS
[ 632.988747] RTL871X: rtw suspend success in 4 ms
[ 632.988770] dpm_run_callback(): pm_generic_suspend+0x0/0x40 returns -38
[ 632.988780] PM: Device mmc1:0001:1 failed to suspend async: error -38
[ 633.060889] PM: Some devices failed to suspend, or early wake event detected
[ 633.162077] OOM killer enabled.
[ 633.162082] Restarting tasks ... done.
[ 633.163973] PM: suspend exit
[ 633.164189] PM: suspend entry (s2idle)
[ 633.164192] PM: Syncing filesystems ... done.
[ 633.193336] r8152 1-1:1.0 eth0: carrier on
[ 633.346619] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 633.348601] OOM killer disabled.
[ 633.348603] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 633.350026] Suspending console(s) (use no_console_suspend to debug)
[ 636.356700] dpm_run_callback(): pm_generic_suspend+0x0/0x40 returns -38
[ 636.356714] PM: Device mmc1:0001:1 failed to suspend async: error -38
[ 636.356744] PM: Some devices failed to suspend, or early wake event detected
[ 636.477527] r8152 1-1:1.0 eth0: carrier on
[ 636.505808] OOM killer enabled.
[ 636.505812] Restarting tasks ... done.
[ 636.550309] PM: suspend exit
``` | test | pinebook suspend to ram not working required information dietpi version cat dietpi dietpi version bin bash g dietpi version core g dietpi version sub g dietpi version rc g gitbranch master g gitowner fourdee distro version echo g distro name or cat etc debian version stretch kernel version uname a linux dietpi smp thu nov cet gnu linux sbc device echo g hw model description or eg pinebook power supply used eg ravpower official pinebook power supply sdcard used eg sandisk ultra internal emmc steps to reproduce install dietpi on pinebook flash the image on an sd card and then dd it on the internal emmc module as per instructions here run systemctl suspend as root expected behaviour system suspends to ram actual behaviour screen goes black for a while and normal execution resumes additionally x server crashes extra details dmesg output after attempt pm suspend entry pm syncing filesystems done freezing user space processes elapsed seconds done oom killer disabled freezing remaining freezable tasks elapsed seconds done suspending console s use no console suspend to debug suspend start rtw cmd thread stop req break rtw dev unload driver not in ips rtw suspend success in ms dpm run callback pm generic suspend returns pm device failed to suspend async error pm some devices failed to suspend or early wake event detected oom killer enabled restarting tasks done pm suspend exit pm suspend entry pm syncing filesystems done carrier on freezing user space processes elapsed seconds done oom killer disabled freezing remaining freezable tasks elapsed seconds done suspending console s use no console suspend to debug dpm run callback pm generic suspend returns pm device failed to suspend async error pm some devices failed to suspend or early wake event detected carrier on oom killer enabled restarting tasks done pm suspend exit | 1 |
12,091 | 7,693,271,818 | IssuesEvent | 2018-05-18 02:34:17 | coreos/bugs | https://api.github.com/repos/coreos/bugs | closed | eth0: Removing non-existent address / breaks DHCP static binding | area/usability component/networkd kind/bug team/os | # Issue Report #
<!-- Fill in either the 'Bug' or 'Feature Request' section -->
## Bug ##
CoreOS on VMware starts non-existent interface (eth0), breaks DHCP static bindings
### Container Linux Version ###
```
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1298.5.0
VERSION_ID=1298.5.0
BUILD_ID=2017-02-28-0013
PRETTY_NAME="Container Linux by CoreOS 1298.5.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
```
### Environment ###
VMWare
### Expected Behavior ###
CoreOS should start up and receive it's DHCP static address assignment (via static-binding on MAC address) on ens192 via network DHCP server.
### Actual Behavior ###
CoreOS starts up with eth0, receives it's DHCP statically bound address on eth0; stops and removes eth0, then configures a new interface (ens192) which gets a random DHCP assigned address from the lease pool.
### Reproduction Steps ###
Create a DHCP static assignment (via MAC address) on a network device (DHCPD) for the primary interface, which should be ens192. Start up the VM in VMware. You should see two bindings in the DHCP lease table for the same MAC address; VM will be available on the non-statically assigned address (from the dynamic lease pool).
### Other Information ###
from "journalctl -u systemd-networkd":
```-- Reboot --
Mar 14 21:35:39 localhost systemd[1]: Starting Network Service...
Mar 14 21:35:39 localhost systemd-networkd[223]: Enumeration completed
Mar 14 21:35:39 localhost systemd[1]: Started Network Service.
Mar 14 21:35:39 localhost systemd-networkd[223]: lo: Configured
Mar 14 21:35:39 localhost systemd-networkd[223]: eth0: IPv6 enabled for interface: Success
Mar 14 21:35:39 localhost systemd-networkd[223]: eth0: Gained carrier
Mar 14 21:35:40 localhost systemd[1]: Stopping Network Service...
Mar 14 21:35:40 localhost systemd-networkd[223]: eth0: Removing non-existent address: fe80::20c:29ff:fe69:9e9f/64 (valid forever)
Mar 14 21:35:40 localhost systemd-networkd[223]: eth0: DHCPv4 address 10.0.254.10/26 via 10.0.254.1
Mar 14 21:35:40 localhost systemd-networkd[223]: lo: Lost carrier
Mar 14 21:35:40 localhost systemd[1]: Stopped Network Service.
Mar 14 21:35:43 localhost systemd[1]: Starting Network Service...
Mar 14 21:35:43 localhost systemd-networkd[926]: Enumeration completed
Mar 14 21:35:43 localhost systemd-networkd[926]: ens192: IPv6 enabled for interface: Success
Mar 14 21:35:43 localhost systemd-networkd[926]: lo: Configured
Mar 14 21:35:43 localhost systemd-networkd[926]: ens192: Gained carrier
Mar 14 21:35:43 localhost systemd[1]: Started Network Service.
Mar 14 21:35:44 localhost systemd-networkd[926]: ens192: DHCPv4 address 10.0.254.47/26 via 10.0.254.1
Mar 14 21:35:45 localhost systemd-networkd[926]: ens192: Gained IPv6LL
Mar 14 21:35:59 localhost systemd-networkd[926]: ens192: Configured
```
10.0.254.10 is the address which should be getting assigned to ens192. I've also attempted to disable eth0 using a network unit like so:
```
$ cat /etc/systemd/network/00-eth0.network
[Match]
Name=eth*
[Network]
DHCP=no
```
also tried assigning a static IP to eth0, just to prevent DHCP, but fails to resolve the issue. | True | eth0: Removing non-existent address / breaks DHCP static binding - # Issue Report #
<!-- Fill in either the 'Bug' or 'Feature Request' section -->
## Bug ##
CoreOS on VMware starts non-existent interface (eth0), breaks DHCP static bindings
### Container Linux Version ###
```
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1298.5.0
VERSION_ID=1298.5.0
BUILD_ID=2017-02-28-0013
PRETTY_NAME="Container Linux by CoreOS 1298.5.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
```
### Environment ###
VMWare
### Expected Behavior ###
CoreOS should start up and receive it's DHCP static address assignment (via static-binding on MAC address) on ens192 via network DHCP server.
### Actual Behavior ###
CoreOS starts up with eth0, receives it's DHCP statically bound address on eth0; stops and removes eth0, then configures a new interface (ens192) which gets a random DHCP assigned address from the lease pool.
### Reproduction Steps ###
Create a DHCP static assignment (via MAC address) on a network device (DHCPD) for the primary interface, which should be ens192. Start up the VM in VMware. You should see two bindings in the DHCP lease table for the same MAC address; VM will be available on the non-statically assigned address (from the dynamic lease pool).
### Other Information ###
from "journalctl -u systemd-networkd":
```-- Reboot --
Mar 14 21:35:39 localhost systemd[1]: Starting Network Service...
Mar 14 21:35:39 localhost systemd-networkd[223]: Enumeration completed
Mar 14 21:35:39 localhost systemd[1]: Started Network Service.
Mar 14 21:35:39 localhost systemd-networkd[223]: lo: Configured
Mar 14 21:35:39 localhost systemd-networkd[223]: eth0: IPv6 enabled for interface: Success
Mar 14 21:35:39 localhost systemd-networkd[223]: eth0: Gained carrier
Mar 14 21:35:40 localhost systemd[1]: Stopping Network Service...
Mar 14 21:35:40 localhost systemd-networkd[223]: eth0: Removing non-existent address: fe80::20c:29ff:fe69:9e9f/64 (valid forever)
Mar 14 21:35:40 localhost systemd-networkd[223]: eth0: DHCPv4 address 10.0.254.10/26 via 10.0.254.1
Mar 14 21:35:40 localhost systemd-networkd[223]: lo: Lost carrier
Mar 14 21:35:40 localhost systemd[1]: Stopped Network Service.
Mar 14 21:35:43 localhost systemd[1]: Starting Network Service...
Mar 14 21:35:43 localhost systemd-networkd[926]: Enumeration completed
Mar 14 21:35:43 localhost systemd-networkd[926]: ens192: IPv6 enabled for interface: Success
Mar 14 21:35:43 localhost systemd-networkd[926]: lo: Configured
Mar 14 21:35:43 localhost systemd-networkd[926]: ens192: Gained carrier
Mar 14 21:35:43 localhost systemd[1]: Started Network Service.
Mar 14 21:35:44 localhost systemd-networkd[926]: ens192: DHCPv4 address 10.0.254.47/26 via 10.0.254.1
Mar 14 21:35:45 localhost systemd-networkd[926]: ens192: Gained IPv6LL
Mar 14 21:35:59 localhost systemd-networkd[926]: ens192: Configured
```
10.0.254.10 is the address which should be getting assigned to ens192. I've also attempted to disable eth0 using a network unit like so:
```
$ cat /etc/systemd/network/00-eth0.network
[Match]
Name=eth*
[Network]
DHCP=no
```
also tried assigning a static IP to eth0, just to prevent DHCP, but fails to resolve the issue. | non_test | removing non existent address breaks dhcp static binding issue report bug coreos on vmware starts non existent interface breaks dhcp static bindings container linux version name container linux by coreos id coreos version version id build id pretty name container linux by coreos ladybug ansi color home url bug report url environment vmware expected behavior coreos should start up and receive it s dhcp static address assignment via static binding on mac address on via network dhcp server actual behavior coreos starts up with receives it s dhcp statically bound address on stops and removes then configures a new interface which gets a random dhcp assigned address from the lease pool reproduction steps create a dhcp static assignment via mac address on a network device dhcpd for the primary interface which should be start up the vm in vmware you should see two bindings in the dhcp lease table for the same mac address vm will be available on the non statically assigned address from the dynamic lease pool other information from journalctl u systemd networkd reboot mar localhost systemd starting network service mar localhost systemd networkd enumeration completed mar localhost systemd started network service mar localhost systemd networkd lo configured mar localhost systemd networkd enabled for interface success mar localhost systemd networkd gained carrier mar localhost systemd stopping network service mar localhost systemd networkd removing non existent address valid forever mar localhost systemd networkd address via mar localhost systemd networkd lo lost carrier mar localhost systemd stopped network service mar localhost systemd starting network service mar localhost systemd networkd enumeration completed mar localhost systemd networkd enabled for interface success mar localhost systemd networkd lo configured mar localhost systemd networkd gained carrier mar localhost systemd started network service mar localhost systemd networkd address via mar localhost systemd networkd gained mar localhost systemd networkd configured is the address which should be getting assigned to i ve also attempted to disable using a network unit like so cat etc systemd network network name eth dhcp no also tried assigning a static ip to just to prevent dhcp but fails to resolve the issue | 0 |
183,246 | 14,218,901,983 | IssuesEvent | 2020-11-17 12:30:55 | SAPDocuments/Tutorials | https://api.github.com/repos/SAPDocuments/Tutorials | closed | Screenshot update required for create site step | SCPTest | Open https://developers.sap.com/tutorials/cp-portal-cloud-foundry-create-site.html
Step 1- Provide the site name
Remark- Screenshot should be updated
Actual
Expected
| 1.0 | Screenshot update required for create site step - Open https://developers.sap.com/tutorials/cp-portal-cloud-foundry-create-site.html
Step 1- Provide the site name
Remark- Screenshot should be updated
Actual
Expected
| test | screenshot update required for create site step open step provide the site name remark screenshot should be updated actual expected | 1 |
147,543 | 11,795,945,738 | IssuesEvent | 2020-03-18 09:53:53 | jenkins-x/jx | https://api.github.com/repos/jenkins-x/jx | closed | Create BDD test which verifies that changes propagate to previews | area/bdd area/test kind/task lifecycle/stale priority/important-soon | We have BDD tests which generate a pull request and verify that a preview environment gets created, however, these tests don't verify that the preview environment contains the update. In case of a website, we should, for example, verify that some text gets updated.
This followed up on #5064 | 1.0 | Create BDD test which verifies that changes propagate to previews - We have BDD tests which generate a pull request and verify that a preview environment gets created, however, these tests don't verify that the preview environment contains the update. In case of a website, we should, for example, verify that some text gets updated.
This followed up on #5064 | test | create bdd test which verifies that changes propagate to previews we have bdd tests which generate a pull request and verify that a preview environment gets created however these tests don t verify that the preview environment contains the update in case of a website we should for example verify that some text gets updated this followed up on | 1 |
15,706 | 5,168,225,312 | IssuesEvent | 2017-01-17 21:03:18 | perseids-project/plokamos | https://api.github.com/repos/perseids-project/plokamos | opened | comments needed on model constructor | code review | comments are needed to explain the reason for the complex use of promises on the execution of the sparql queries in the model constructor | 1.0 | comments needed on model constructor - comments are needed to explain the reason for the complex use of promises on the execution of the sparql queries in the model constructor | non_test | comments needed on model constructor comments are needed to explain the reason for the complex use of promises on the execution of the sparql queries in the model constructor | 0 |
60,120 | 6,671,813,986 | IssuesEvent | 2017-10-04 09:01:01 | mantidproject/mantid | https://api.github.com/repos/mantidproject/mantid | closed | Unscripted Testing ISIS SANS (v2 GUI) | Quality: Manual Tests | 1. Read http://www.mantidproject.org/Unscripted_Manual_Testing
1. Comment against this ticket the OS environment you are testing against.
1. Don't spend more than a few hours on the testing as fatigue will kick in.
1. If you find errors in the possibly scant documentation, then correct them.
1. Close the this issue once you are done.
If you find bugs:
* Search to see if an issue already exists
* create an issue if it is new
* Urgent bugs or crashes should by against the current release, and assigned to a developer, then go and talk to the developer if possible.
* Less urgent bugs should be against a subsequent release, and assigned if the correct developer is known.
### Specific Notes:
Speak to Anton | 1.0 | Unscripted Testing ISIS SANS (v2 GUI) - 1. Read http://www.mantidproject.org/Unscripted_Manual_Testing
1. Comment against this ticket the OS environment you are testing against.
1. Don't spend more than a few hours on the testing as fatigue will kick in.
1. If you find errors in the possibly scant documentation, then correct them.
1. Close the this issue once you are done.
If you find bugs:
* Search to see if an issue already exists
* create an issue if it is new
* Urgent bugs or crashes should by against the current release, and assigned to a developer, then go and talk to the developer if possible.
* Less urgent bugs should be against a subsequent release, and assigned if the correct developer is known.
### Specific Notes:
Speak to Anton | test | unscripted testing isis sans gui read comment against this ticket the os environment you are testing against don t spend more than a few hours on the testing as fatigue will kick in if you find errors in the possibly scant documentation then correct them close the this issue once you are done if you find bugs search to see if an issue already exists create an issue if it is new urgent bugs or crashes should by against the current release and assigned to a developer then go and talk to the developer if possible less urgent bugs should be against a subsequent release and assigned if the correct developer is known specific notes speak to anton | 1 |
345,820 | 30,845,910,160 | IssuesEvent | 2023-08-02 13:43:18 | inverse-inc/packetfence | https://api.github.com/repos/inverse-inc/packetfence | closed | PF 13: Wired web auth broken on Cisco 2960 | Type: Bug Priority: Critical Status: Tested and works | PF version:
````
root@debian-pf1:/usr/local/pf# dpkg -l packetfence
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-====================================================-============-=========================================================
ii packetfence 13.0.0+20230727212935+948084463+0011+devel+bullseye1 all PacketFence network registration / worm mitigation system
````
Error log:
````
Jul 28 10:55:02 debian-pf1 httpd.portal-docker-wrapper[3111101]: 192.168.126.199 - - [28/Jul/2023:10:55:02 -0400] "GET /Cisco::Catalyst_2960G/sid1c8ecf HTTP/1.1" 501 439 522 514389 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.183"
````
During the Switch module refactor, since the Catalyst_2960 module was changed, the web auth does not work.
logs/packetfence.log
````
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] handling radius autz request: from switch_ip => (192.168.126
.253), connection_type => Ethernet-NoEAP,switch_mac => (5c:50:15:c2:eb:0b), mac => [00:e0:4c:68:09:e3], port => 10111, username => "00e04c6809e3" (pf::radius::author
ize)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] Instantiate profile default (pf::Connection::ProfileFactory:
:_from_profile)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] is of status unreg; belongs into registration VLAN (pf::role
::getRegistrationRole)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] (192.168.126.253) Added role registration to the returned RA
DIUS Access-Accept (pf::Switch::returnRadiusAccessAccept)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] Adding web authentication redirection to reply using role: '
registration' and URL: 'http://192.168.126.50/Cisco::Catalyst_2960G/sid1c8ecf' (pf::Switch::Cisco::Cisco_IOS_12_x::returnRadiusAccessAccept)
```` | 1.0 | PF 13: Wired web auth broken on Cisco 2960 - PF version:
````
root@debian-pf1:/usr/local/pf# dpkg -l packetfence
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-====================================================-============-=========================================================
ii packetfence 13.0.0+20230727212935+948084463+0011+devel+bullseye1 all PacketFence network registration / worm mitigation system
````
Error log:
````
Jul 28 10:55:02 debian-pf1 httpd.portal-docker-wrapper[3111101]: 192.168.126.199 - - [28/Jul/2023:10:55:02 -0400] "GET /Cisco::Catalyst_2960G/sid1c8ecf HTTP/1.1" 501 439 522 514389 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.183"
````
During the Switch module refactor, since the Catalyst_2960 module was changed, the web auth does not work.
logs/packetfence.log
````
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] handling radius autz request: from switch_ip => (192.168.126
.253), connection_type => Ethernet-NoEAP,switch_mac => (5c:50:15:c2:eb:0b), mac => [00:e0:4c:68:09:e3], port => 10111, username => "00e04c6809e3" (pf::radius::author
ize)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] Instantiate profile default (pf::Connection::ProfileFactory:
:_from_profile)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] is of status unreg; belongs into registration VLAN (pf::role
::getRegistrationRole)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] (192.168.126.253) Added role registration to the returned RA
DIUS Access-Accept (pf::Switch::returnRadiusAccessAccept)
Jul 28 10:54:58 debian-pf2 httpd.aaa-docker-wrapper[2749637]: httpd.aaa(9) INFO: [mac:00:e0:4c:68:09:e3] Adding web authentication redirection to reply using role: '
registration' and URL: 'http://192.168.126.50/Cisco::Catalyst_2960G/sid1c8ecf' (pf::Switch::Cisco::Cisco_IOS_12_x::returnRadiusAccessAccept)
```` | test | pf wired web auth broken on cisco pf version root debian usr local pf dpkg l packetfence desired unknown install remove purge hold status not inst conf files unpacked half conf half inst trig await trig pend err none reinst required status err uppercase bad name version architecture description ii packetfence devel all packetfence network registration worm mitigation system error log jul debian httpd portal docker wrapper get cisco catalyst http mozilla windows nt applewebkit khtml like gecko chrome safari edg during the switch module refactor since the catalyst module was changed the web auth does not work logs packetfence log jul debian httpd aaa docker wrapper httpd aaa info handling radius autz request from switch ip connection type ethernet noeap switch mac eb mac port username pf radius author ize jul debian httpd aaa docker wrapper httpd aaa info instantiate profile default pf connection profilefactory from profile jul debian httpd aaa docker wrapper httpd aaa info is of status unreg belongs into registration vlan pf role getregistrationrole jul debian httpd aaa docker wrapper httpd aaa info added role registration to the returned ra dius access accept pf switch returnradiusaccessaccept jul debian httpd aaa docker wrapper httpd aaa info adding web authentication redirection to reply using role registration and url pf switch cisco cisco ios x returnradiusaccessaccept | 1 |
36,367 | 9,797,128,543 | IssuesEvent | 2019-06-11 09:16:07 | ShaikASK/Testing | https://api.github.com/repos/ShaikASK/Testing | closed | Workflows Default Step & Candidate Module : Deleted contractor Information webform from “Design Webform” screen is getting displayed at default workflows step and also at candidate module | Candidate Module Defect Design Webform HR Admin Module P1 Release #4 Build # 2 Workflow | Steps To Replicate :
1.Launch the URL
2.Sign in as HR admin user
3.Go to Design webform
4.Delete “Contractor Information” static webform
5.Go to Workflows
6.Create a Workflow
Experienced Behavior : Observed that already deleted contractor Information webform is getting displayed at default workflows step and also candidate at module (Refer Screen Shot)
Expected Behavior : Ensure that webform deleted from “Design Webform” screen should not be displayed at default workflows step and at candidate module
| 1.0 | Workflows Default Step & Candidate Module : Deleted contractor Information webform from “Design Webform” screen is getting displayed at default workflows step and also at candidate module - Steps To Replicate :
1.Launch the URL
2.Sign in as HR admin user
3.Go to Design webform
4.Delete “Contractor Information” static webform
5.Go to Workflows
6.Create a Workflow
Experienced Behavior : Observed that already deleted contractor Information webform is getting displayed at default workflows step and also candidate at module (Refer Screen Shot)
Expected Behavior : Ensure that webform deleted from “Design Webform” screen should not be displayed at default workflows step and at candidate module
| non_test | workflows default step candidate module deleted contractor information webform from “design webform” screen is getting displayed at default workflows step and also at candidate module steps to replicate launch the url sign in as hr admin user go to design webform delete “contractor information” static webform go to workflows create a workflow experienced behavior observed that already deleted contractor information webform is getting displayed at default workflows step and also candidate at module refer screen shot expected behavior ensure that webform deleted from “design webform” screen should not be displayed at default workflows step and at candidate module | 0 |
8,386 | 10,417,909,942 | IssuesEvent | 2019-09-15 03:01:28 | TheCodex6824/ThaumicAugmentation | https://api.github.com/repos/TheCodex6824/ThaumicAugmentation | closed | Morphic Tool EnderIO Compat [Bug] | Compatibility | If you infuse EnderIO tools with Morphic Tool infusion EnderIO upgrades would be lost despite NBT tags saving.
| True | Morphic Tool EnderIO Compat [Bug] - If you infuse EnderIO tools with Morphic Tool infusion EnderIO upgrades would be lost despite NBT tags saving.
| non_test | morphic tool enderio compat if you infuse enderio tools with morphic tool infusion enderio upgrades would be lost despite nbt tags saving | 0 |
14,963 | 5,028,595,016 | IssuesEvent | 2016-12-15 18:41:48 | phetsims/capacitor-lab-basics | https://api.github.com/repos/phetsims/capacitor-lab-basics | closed | model.md and implementation.md documentation | dev:code-review status:ready-for-review | Should exist at capacitor-lab-basics/doc/, as noted in the code review guidelines:
> doc/
> model.md
> implementation-notes.md
> - Does model.md adequately describe the model, in terms appropriate for teachers?
> - Does implementation-notes.md adequately describe the implementation, with an overview that will be useful to future maintainers?
For code review: https://github.com/phetsims/capacitor-lab-basics/issues/117 | 1.0 | model.md and implementation.md documentation - Should exist at capacitor-lab-basics/doc/, as noted in the code review guidelines:
> doc/
> model.md
> implementation-notes.md
> - Does model.md adequately describe the model, in terms appropriate for teachers?
> - Does implementation-notes.md adequately describe the implementation, with an overview that will be useful to future maintainers?
For code review: https://github.com/phetsims/capacitor-lab-basics/issues/117 | non_test | model md and implementation md documentation should exist at capacitor lab basics doc as noted in the code review guidelines doc model md implementation notes md does model md adequately describe the model in terms appropriate for teachers does implementation notes md adequately describe the implementation with an overview that will be useful to future maintainers for code review | 0 |
189,023 | 14,482,980,540 | IssuesEvent | 2020-12-10 14:38:26 | Rebirth-of-the-Night/Rebirth-Of-The-Night | https://api.github.com/repos/Rebirth-of-the-Night/Rebirth-Of-The-Night | closed | nether wasp[CRASH] | RotN bug mod bug needs testing | <!-- ISSUES NOT USING OUR TEMPLATE WILL NOT BE CONSIDERED AND WILL BE CLOSED! -->
**Describe the crash**
sometimes when you kill a nether wasp your game continues running but mobs cant be attacked and don't move. while blocks can be broken but don't drop. When you leave the world the game crashes and when you relog it is corrupted and you need to delete the nether dimension in order to continue.
also when I managed to relog after serval attempts I was able to get on but several issues emerged
first being my difficulty was set to peaceful which was the last mode I hade it on while using creative trying to find my mount that glitched. the second I was getting a crash log from breaking blocks with a pick of mine.
**To Reproduce**
enter the nether and when you kill a nether wasp it will sometimes corrupt the game possibly depending on where you are in the world and if something loads not sure.
the second issue just relog a few times and you get on (this only happened my second time with this bug.
also deleting the nether fixes it as well but (for my first attempt.
**Crash Log**
don't have a crash log but I have the latest file no crash report due to the kind of crash)
none of the websites seem to be able to support the latest lof of this size sadly.
not even paste.gg can support it.
says it to large.
For the second crash from logging in is
http://hastebin.net/ohefobonal.rb
**Info (please complete the following information):**
- Modpack Version: 2.77.5
- Server or Singleplayer: single player
- Version the world was created on 2.77.5
**Additional context**
from what I can tell. possibly open JDK (I can't seem to delete it even from the consol controles possibly has to do with the gd launcher) this is all I can gather I am also using 5 extra mods which should not impact it in the slightest (2 dynamic tree addon mods being aether and twilight forest. also using mending fix, torch slab, and smooth scrolling everywhere.)
the time of posting this crash this is my second time encountering it the first time I fixed it by deleting the nether the second I reblogged and have yet to delete the nether. (I don't know what latest log and crash log are for the original crash) | 1.0 | nether wasp[CRASH] - <!-- ISSUES NOT USING OUR TEMPLATE WILL NOT BE CONSIDERED AND WILL BE CLOSED! -->
**Describe the crash**
sometimes when you kill a nether wasp your game continues running but mobs cant be attacked and don't move. while blocks can be broken but don't drop. When you leave the world the game crashes and when you relog it is corrupted and you need to delete the nether dimension in order to continue.
also when I managed to relog after serval attempts I was able to get on but several issues emerged
first being my difficulty was set to peaceful which was the last mode I hade it on while using creative trying to find my mount that glitched. the second I was getting a crash log from breaking blocks with a pick of mine.
**To Reproduce**
enter the nether and when you kill a nether wasp it will sometimes corrupt the game possibly depending on where you are in the world and if something loads not sure.
the second issue just relog a few times and you get on (this only happened my second time with this bug.
also deleting the nether fixes it as well but (for my first attempt.
**Crash Log**
don't have a crash log but I have the latest file no crash report due to the kind of crash)
none of the websites seem to be able to support the latest lof of this size sadly.
not even paste.gg can support it.
says it to large.
For the second crash from logging in is
http://hastebin.net/ohefobonal.rb
**Info (please complete the following information):**
- Modpack Version: 2.77.5
- Server or Singleplayer: single player
- Version the world was created on 2.77.5
**Additional context**
from what I can tell. possibly open JDK (I can't seem to delete it even from the consol controles possibly has to do with the gd launcher) this is all I can gather I am also using 5 extra mods which should not impact it in the slightest (2 dynamic tree addon mods being aether and twilight forest. also using mending fix, torch slab, and smooth scrolling everywhere.)
the time of posting this crash this is my second time encountering it the first time I fixed it by deleting the nether the second I reblogged and have yet to delete the nether. (I don't know what latest log and crash log are for the original crash) | test | nether wasp describe the crash sometimes when you kill a nether wasp your game continues running but mobs cant be attacked and don t move while blocks can be broken but don t drop when you leave the world the game crashes and when you relog it is corrupted and you need to delete the nether dimension in order to continue also when i managed to relog after serval attempts i was able to get on but several issues emerged first being my difficulty was set to peaceful which was the last mode i hade it on while using creative trying to find my mount that glitched the second i was getting a crash log from breaking blocks with a pick of mine to reproduce enter the nether and when you kill a nether wasp it will sometimes corrupt the game possibly depending on where you are in the world and if something loads not sure the second issue just relog a few times and you get on this only happened my second time with this bug also deleting the nether fixes it as well but for my first attempt crash log don t have a crash log but i have the latest file no crash report due to the kind of crash none of the websites seem to be able to support the latest lof of this size sadly not even paste gg can support it says it to large for the second crash from logging in is info please complete the following information modpack version server or singleplayer single player version the world was created on additional context from what i can tell possibly open jdk i can t seem to delete it even from the consol controles possibly has to do with the gd launcher this is all i can gather i am also using extra mods which should not impact it in the slightest dynamic tree addon mods being aether and twilight forest also using mending fix torch slab and smooth scrolling everywhere the time of posting this crash this is my second time encountering it the first time i fixed it by deleting the nether the second i reblogged and have yet to delete the nether i don t know what latest log and crash log are for the original crash | 1 |
13,417 | 3,332,324,329 | IssuesEvent | 2015-11-11 19:38:13 | t2davis/Squad | https://api.github.com/repos/t2davis/Squad | opened | buddybuild feedback from mutobrittney@gmail.com on build #11: Maybe add name to who added what expense/bill | 1.0 BetaTester | Feedback from mutobrittney@gmail.com : Maybe add name to who added what expense/bill
<img src="https://s3-us-west-2.amazonaws.com/buddybuild-screenshots/5642b68257de0f0100c2f1c9/5642f4b857de0f0100c2f1f1/ef1dc027-b0e5-46cd-9246-23fcf35e7e21.jpg" width="33%" height="33%" /> | 1.0 | buddybuild feedback from mutobrittney@gmail.com on build #11: Maybe add name to who added what expense/bill - Feedback from mutobrittney@gmail.com : Maybe add name to who added what expense/bill
<img src="https://s3-us-west-2.amazonaws.com/buddybuild-screenshots/5642b68257de0f0100c2f1c9/5642f4b857de0f0100c2f1f1/ef1dc027-b0e5-46cd-9246-23fcf35e7e21.jpg" width="33%" height="33%" /> | test | buddybuild feedback from mutobrittney gmail com on build maybe add name to who added what expense bill feedback from mutobrittney gmail com maybe add name to who added what expense bill | 1 |
103,210 | 12,880,713,045 | IssuesEvent | 2020-07-12 07:45:13 | lshadler/game-jam-july-2020 | https://api.github.com/repos/lshadler/game-jam-july-2020 | closed | Sound effects | sound design | Add sound effects for things
-collecting music notes
-Getting hit
-tomatoes hitting the ground
-jumping/landing?
-Drum rolling | 1.0 | Sound effects - Add sound effects for things
-collecting music notes
-Getting hit
-tomatoes hitting the ground
-jumping/landing?
-Drum rolling | non_test | sound effects add sound effects for things collecting music notes getting hit tomatoes hitting the ground jumping landing drum rolling | 0 |
436,550 | 30,558,246,158 | IssuesEvent | 2023-07-20 13:06:16 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Doc: Appearance Tools needs update | [Type] Developer Documentation Global Styles | ### Description
[The list for Appearance Tools](https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-support/#appearance-tools) is missing
- dimensions: minHeight
- position: sticky
### Step-by-step reproduction instructions
n/a
### Screenshots, screen recording, code snippet
Current list
<img width="320" alt="Screenshot 2023-07-20 at 09 49 59" src="https://github.com/WordPress/gutenberg/assets/39980/23da03b1-526f-41c4-b7ed-19787a67b6e4">
### Environment info
n/a
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes | 1.0 | Doc: Appearance Tools needs update - ### Description
[The list for Appearance Tools](https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-support/#appearance-tools) is missing
- dimensions: minHeight
- position: sticky
### Step-by-step reproduction instructions
n/a
### Screenshots, screen recording, code snippet
Current list
<img width="320" alt="Screenshot 2023-07-20 at 09 49 59" src="https://github.com/WordPress/gutenberg/assets/39980/23da03b1-526f-41c4-b7ed-19787a67b6e4">
### Environment info
n/a
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes | non_test | doc appearance tools needs update description is missing dimensions minheight position sticky step by step reproduction instructions n a screenshots screen recording code snippet current list img width alt screenshot at src environment info n a please confirm that you have searched existing issues in the repo yes please confirm that you have tested with all plugins deactivated except gutenberg yes | 0 |
136,783 | 18,751,472,541 | IssuesEvent | 2021-11-05 02:55:44 | Dima2022/Resiliency-Studio | https://api.github.com/repos/Dima2022/Resiliency-Studio | opened | CVE-2018-14042 (Medium) detected in bootstrap-3.3.7.js, bootstrap-3.3.7.min.js | security vulnerability | ## CVE-2018-14042 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bootstrap-3.3.7.js</b>, <b>bootstrap-3.3.7.min.js</b></p></summary>
<p>
<details><summary><b>bootstrap-3.3.7.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /resiliency-studio-ui/src/main/webapp/app/components/lib/js/bootstrap.js,/resiliency-studio-ui/target/resiliency-studio-ui/app/components/lib/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.js** (Vulnerable Library)
</details>
<details><summary><b>bootstrap-3.3.7.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: Resiliency-Studio/resiliency-studio-ui/src/main/webapp/index.html</p>
<p>Path to vulnerable library: /resiliency-studio-ui/target/resiliency-studio-ui/app/components/lib/js/bootstrap.min.js,/resiliency-studio-ui/src/main/webapp/app/components/lib/js/bootstrap.min.js,/resiliency-studio-ui/src/main/webapp/app/components/lib/js/bootstrap.min.js,/resiliency-studio-ui/target/resiliency-studio-ui/app/components/lib/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2022/Resiliency-Studio/commit/27f5ba6623ed8d6b149733f3ad245fc8133f1ffc">27f5ba6623ed8d6b149733f3ad245fc8133f1ffc</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.7","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0"},{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.7","packageFilePaths":["/resiliency-studio-ui/src/main/webapp/index.html","/resiliency-studio-ui/target/resiliency-studio-ui/index.html"],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-14042","vulnerabilityDetails":"In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-14042 (Medium) detected in bootstrap-3.3.7.js, bootstrap-3.3.7.min.js - ## CVE-2018-14042 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bootstrap-3.3.7.js</b>, <b>bootstrap-3.3.7.min.js</b></p></summary>
<p>
<details><summary><b>bootstrap-3.3.7.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /resiliency-studio-ui/src/main/webapp/app/components/lib/js/bootstrap.js,/resiliency-studio-ui/target/resiliency-studio-ui/app/components/lib/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.js** (Vulnerable Library)
</details>
<details><summary><b>bootstrap-3.3.7.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: Resiliency-Studio/resiliency-studio-ui/src/main/webapp/index.html</p>
<p>Path to vulnerable library: /resiliency-studio-ui/target/resiliency-studio-ui/app/components/lib/js/bootstrap.min.js,/resiliency-studio-ui/src/main/webapp/app/components/lib/js/bootstrap.min.js,/resiliency-studio-ui/src/main/webapp/app/components/lib/js/bootstrap.min.js,/resiliency-studio-ui/target/resiliency-studio-ui/app/components/lib/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2022/Resiliency-Studio/commit/27f5ba6623ed8d6b149733f3ad245fc8133f1ffc">27f5ba6623ed8d6b149733f3ad245fc8133f1ffc</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.7","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0"},{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.7","packageFilePaths":["/resiliency-studio-ui/src/main/webapp/index.html","/resiliency-studio-ui/target/resiliency-studio-ui/index.html"],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-14042","vulnerabilityDetails":"In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_test | cve medium detected in bootstrap js bootstrap min js cve medium severity vulnerability vulnerable libraries bootstrap js bootstrap min js bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library resiliency studio ui src main webapp app components lib js bootstrap js resiliency studio ui target resiliency studio ui app components lib js bootstrap js dependency hierarchy x bootstrap js vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file resiliency studio resiliency studio ui src main webapp index html path to vulnerable library resiliency studio ui target resiliency studio ui app components lib js bootstrap min js resiliency studio ui src main webapp app components lib js bootstrap min js resiliency studio ui src main webapp app components lib js bootstrap min js resiliency studio ui target resiliency studio ui app components lib js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the data container property of tooltip publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org webjars npm bootstrap org webjars bootstrap isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree twitter bootstrap isminimumfixversionavailable true minimumfixversion org webjars npm bootstrap org webjars bootstrap packagetype javascript packagename twitter bootstrap packageversion packagefilepaths istransitivedependency false dependencytree twitter bootstrap isminimumfixversionavailable true minimumfixversion org webjars npm bootstrap org webjars bootstrap basebranches vulnerabilityidentifier cve vulnerabilitydetails in bootstrap before xss is possible in the data container property of tooltip vulnerabilityurl | 0 |
345,475 | 30,816,299,302 | IssuesEvent | 2023-08-01 13:40:48 | Chae-So/Back-End | https://api.github.com/repos/Chae-So/Back-End | opened | 커뮤니티 리뷰 도메인 기능 개발 | settings feature test | ## Description
커뮤니티 리뷰 도메인 기능 개발
## Todo
- [x] 커뮤니티 도메인 작성, 조회 리스트, 좋아요 기능 등 개발
- [x] 커뮤니티 리뷰 도메인 작성, 조회 기능 개발
| 1.0 | 커뮤니티 리뷰 도메인 기능 개발 - ## Description
커뮤니티 리뷰 도메인 기능 개발
## Todo
- [x] 커뮤니티 도메인 작성, 조회 리스트, 좋아요 기능 등 개발
- [x] 커뮤니티 리뷰 도메인 작성, 조회 기능 개발
| test | 커뮤니티 리뷰 도메인 기능 개발 description 커뮤니티 리뷰 도메인 기능 개발 todo 커뮤니티 도메인 작성 조회 리스트 좋아요 기능 등 개발 커뮤니티 리뷰 도메인 작성 조회 기능 개발 | 1 |
62,890 | 6,819,653,700 | IssuesEvent | 2017-11-07 10:58:49 | subutai-io/tray | https://api.github.com/repos/subutai-io/tray | closed | [Windows] Tray keeps crashing | bug critical testing | It crashes periodically without any activity. However it is worst when generating an SSH key. | 1.0 | [Windows] Tray keeps crashing - It crashes periodically without any activity. However it is worst when generating an SSH key. | test | tray keeps crashing it crashes periodically without any activity however it is worst when generating an ssh key | 1 |
262,048 | 22,790,884,041 | IssuesEvent | 2022-07-10 01:26:04 | backend-br/vagas | https://api.github.com/repos/backend-br/vagas | closed | [remoto] Pessoa Desenvolvedora Fullstack PHP e JS - Pleno @ Feedz | CLT Pleno PHP JavaScript Remoto Presencial Testes automatizados HTML CSS FullStack Stale | 🚀 A FEEDZ:
Nosso propósito é criar ambientes de trabalho mais felizes! Aqui temos um ambiente de trabalho focado na cooperação entre Devs, confiamos no trabalho de nossos colaboradores e por isso acreditamos que nossos desenvolvedores devem ter autonomia!
Prezamos pela liberdade de falar o que se pensa e pelos feedbacks constantes, além de ter um time realmente diverso 💙 Temos também flexibilidade de horários. Tem que resolver alguma coisa? Sem problema.
Estamos buscando uma pessoa para o cargo de Pessoa Desenvolvedora Fullstack Pleno (PHP e JS) que irá atuar no nosso time de Produto, trazendo melhorias e desenvolvendo dentro dos módulos na plataforma da Feedz! Quer impactar mais de 100 mil usuários diretamente? Então vem pro ninho 💛
📚 RESPONSABILIDADES E ATIVIDADES:
Desenvolvimento backend com PHP;
Desenvolvimento de frontend com CSS, HTML e JavaScript;
Implementar códigos coerentes, coesos, claros e alinhados ao Clean Code;
Aplicar boas práticas alinhadas com o time no desenvolvimento (desenvolvimento seguro, patterns, automação, etc);
Trabalhar com o desenvolvimento de módulos dentro da plataforma;
Desenvolvimento e aplicação de testes automatizados;
Desenvolvimento de API sob demanda;
Fazer a gestão da informação das demandas atualizando o status dos projetos.
🥇 PRÉ-REQUISITOS:
Mínimo de 3 anos de experiência em desenvolvimento web com PHP;
Mínimo de 3 anos de experiência em desenvolvimento web com Javascript, HTML, CSS;
Experiência com testes e API;
Estar trabalhando atualmente com as tecnologias de nossa stack;
Experiência com banco de dados relacional;
Gostar de trabalhar em time. Pessoa Desenvolvedora sozinha não faz verão!
🎯DIFERENCIAIS:
Ter trabalhado em empresas SaaS;
Ter trabalhado com empresas com mais de 10 mil usuários.
✨ BENEFÍCIOS:
100% Home Office (não iremos voltar ao trabalho presencial!!)
Envio de todos os equipamentos para o trabalho remoto(inclusive mesa e cadeira de escritório 😉)
Vale Comida (R$700)
Plano de Saúde Unimed(subsidiado pela Feedz)
Plano odontológico Nacional da Bradesco Dental(subsidiado pela Feedz)
Auxílio Parrot Feliz (R$100/mês de investimento no desenvolvimento pessoal, saúde física ou mental do Parrot)
Auxílio Contas (R$160/mês)
Auxílio Parrot Casamenteiro(R$250 quando Parrots casam)
Auxílio Ninhada(R$250 no nascimento ou adoção de pequenos Parrots)
Happy Bird(day) (um dia de folga no mês de aniversário)
Licença paternidade estendida(21 dias)
Licença maternidade estendida(6 meses)
Descontos nas empresas conveniadas com a ACATE
Ifood Office (voucher para usar dentro do app em alguns eventos internos)
💰 SALÁRIO R$5.300 A 7.000* (CLT)
*A DEPENDER DO TEMPO DE EXPERIÊNCIA
Candidate-se em: https://enliztjob.app.link/v8VQubluLpb | 1.0 | [remoto] Pessoa Desenvolvedora Fullstack PHP e JS - Pleno @ Feedz - 🚀 A FEEDZ:
Nosso propósito é criar ambientes de trabalho mais felizes! Aqui temos um ambiente de trabalho focado na cooperação entre Devs, confiamos no trabalho de nossos colaboradores e por isso acreditamos que nossos desenvolvedores devem ter autonomia!
Prezamos pela liberdade de falar o que se pensa e pelos feedbacks constantes, além de ter um time realmente diverso 💙 Temos também flexibilidade de horários. Tem que resolver alguma coisa? Sem problema.
Estamos buscando uma pessoa para o cargo de Pessoa Desenvolvedora Fullstack Pleno (PHP e JS) que irá atuar no nosso time de Produto, trazendo melhorias e desenvolvendo dentro dos módulos na plataforma da Feedz! Quer impactar mais de 100 mil usuários diretamente? Então vem pro ninho 💛
📚 RESPONSABILIDADES E ATIVIDADES:
Desenvolvimento backend com PHP;
Desenvolvimento de frontend com CSS, HTML e JavaScript;
Implementar códigos coerentes, coesos, claros e alinhados ao Clean Code;
Aplicar boas práticas alinhadas com o time no desenvolvimento (desenvolvimento seguro, patterns, automação, etc);
Trabalhar com o desenvolvimento de módulos dentro da plataforma;
Desenvolvimento e aplicação de testes automatizados;
Desenvolvimento de API sob demanda;
Fazer a gestão da informação das demandas atualizando o status dos projetos.
🥇 PRÉ-REQUISITOS:
Mínimo de 3 anos de experiência em desenvolvimento web com PHP;
Mínimo de 3 anos de experiência em desenvolvimento web com Javascript, HTML, CSS;
Experiência com testes e API;
Estar trabalhando atualmente com as tecnologias de nossa stack;
Experiência com banco de dados relacional;
Gostar de trabalhar em time. Pessoa Desenvolvedora sozinha não faz verão!
🎯DIFERENCIAIS:
Ter trabalhado em empresas SaaS;
Ter trabalhado com empresas com mais de 10 mil usuários.
✨ BENEFÍCIOS:
100% Home Office (não iremos voltar ao trabalho presencial!!)
Envio de todos os equipamentos para o trabalho remoto(inclusive mesa e cadeira de escritório 😉)
Vale Comida (R$700)
Plano de Saúde Unimed(subsidiado pela Feedz)
Plano odontológico Nacional da Bradesco Dental(subsidiado pela Feedz)
Auxílio Parrot Feliz (R$100/mês de investimento no desenvolvimento pessoal, saúde física ou mental do Parrot)
Auxílio Contas (R$160/mês)
Auxílio Parrot Casamenteiro(R$250 quando Parrots casam)
Auxílio Ninhada(R$250 no nascimento ou adoção de pequenos Parrots)
Happy Bird(day) (um dia de folga no mês de aniversário)
Licença paternidade estendida(21 dias)
Licença maternidade estendida(6 meses)
Descontos nas empresas conveniadas com a ACATE
Ifood Office (voucher para usar dentro do app em alguns eventos internos)
💰 SALÁRIO R$5.300 A 7.000* (CLT)
*A DEPENDER DO TEMPO DE EXPERIÊNCIA
Candidate-se em: https://enliztjob.app.link/v8VQubluLpb | test | pessoa desenvolvedora fullstack php e js pleno feedz 🚀 a feedz nosso propósito é criar ambientes de trabalho mais felizes aqui temos um ambiente de trabalho focado na cooperação entre devs confiamos no trabalho de nossos colaboradores e por isso acreditamos que nossos desenvolvedores devem ter autonomia prezamos pela liberdade de falar o que se pensa e pelos feedbacks constantes além de ter um time realmente diverso 💙 temos também flexibilidade de horários tem que resolver alguma coisa sem problema estamos buscando uma pessoa para o cargo de pessoa desenvolvedora fullstack pleno php e js que irá atuar no nosso time de produto trazendo melhorias e desenvolvendo dentro dos módulos na plataforma da feedz quer impactar mais de mil usuários diretamente então vem pro ninho 💛 📚 responsabilidades e atividades desenvolvimento backend com php desenvolvimento de frontend com css html e javascript implementar códigos coerentes coesos claros e alinhados ao clean code aplicar boas práticas alinhadas com o time no desenvolvimento desenvolvimento seguro patterns automação etc trabalhar com o desenvolvimento de módulos dentro da plataforma desenvolvimento e aplicação de testes automatizados desenvolvimento de api sob demanda fazer a gestão da informação das demandas atualizando o status dos projetos 🥇 pré requisitos mínimo de anos de experiência em desenvolvimento web com php mínimo de anos de experiência em desenvolvimento web com javascript html css experiência com testes e api estar trabalhando atualmente com as tecnologias de nossa stack experiência com banco de dados relacional gostar de trabalhar em time pessoa desenvolvedora sozinha não faz verão 🎯diferenciais ter trabalhado em empresas saas ter trabalhado com empresas com mais de mil usuários ✨ benefícios home office não iremos voltar ao trabalho presencial envio de todos os equipamentos para o trabalho remoto inclusive mesa e cadeira de escritório 😉 vale comida r plano de saúde unimed subsidiado pela feedz plano odontológico nacional da bradesco dental subsidiado pela feedz auxílio parrot feliz r mês de investimento no desenvolvimento pessoal saúde física ou mental do parrot auxílio contas r mês auxílio parrot casamenteiro r quando parrots casam auxílio ninhada r no nascimento ou adoção de pequenos parrots happy bird day um dia de folga no mês de aniversário licença paternidade estendida dias licença maternidade estendida meses descontos nas empresas conveniadas com a acate ifood office voucher para usar dentro do app em alguns eventos internos 💰 salário r a clt a depender do tempo de experiência candidate se em | 1 |
132,333 | 10,741,537,408 | IssuesEvent | 2019-10-29 20:27:12 | knative/serving | https://api.github.com/repos/knative/serving | closed | Improve Filesystem Conformance tests | area/test-and-release kind/feature | <!-- If you need to report a security issue with Knative, send an email to knative-security@googlegroups.com. -->
## In what area(s)?
<!-- Remove the '> ' to select -->
> /area API
> /area autoscale
> /area build
> /area monitoring
> /area networking
/area test-and-release
<!--
Other classifications:
> /kind good-first-issue
> /kind process
> /kind spec
/kind proposal
-->
## Describe the feature
Our filesystem conformance tests currently check for existence of files and mode bits where required. However, this check is not necessarily sufficient to ensure that the file is accessible to all compliant containers. We should extend this test to actually attempt to read/write files (where applicable) to ensure that nothing else is blocking access.
Related to https://github.com/knative/serving/pull/4074#pullrequestreview-236734576
| 1.0 | Improve Filesystem Conformance tests - <!-- If you need to report a security issue with Knative, send an email to knative-security@googlegroups.com. -->
## In what area(s)?
<!-- Remove the '> ' to select -->
> /area API
> /area autoscale
> /area build
> /area monitoring
> /area networking
/area test-and-release
<!--
Other classifications:
> /kind good-first-issue
> /kind process
> /kind spec
/kind proposal
-->
## Describe the feature
Our filesystem conformance tests currently check for existence of files and mode bits where required. However, this check is not necessarily sufficient to ensure that the file is accessible to all compliant containers. We should extend this test to actually attempt to read/write files (where applicable) to ensure that nothing else is blocking access.
Related to https://github.com/knative/serving/pull/4074#pullrequestreview-236734576
| test | improve filesystem conformance tests in what area s to select area api area autoscale area build area monitoring area networking area test and release other classifications kind good first issue kind process kind spec kind proposal describe the feature our filesystem conformance tests currently check for existence of files and mode bits where required however this check is not necessarily sufficient to ensure that the file is accessible to all compliant containers we should extend this test to actually attempt to read write files where applicable to ensure that nothing else is blocking access related to | 1 |
1,934 | 11,136,334,071 | IssuesEvent | 2019-12-20 16:21:34 | wazuh/wazuh-qa | https://api.github.com/repos/wazuh/wazuh-qa | closed | Syscheck automated tests: Check duplicate entries are ignored. | automation component/fim | Working branch | Platform
-- | --
| Linux/Windows/macOS
Description
----------
In case a folder is specified in more than one `directories` tag, syscheck must monitor the last entry, overriding the rest of the entries.
For example, with the following configuration:
```
<directories realtime="yes">/home/user</directories>
<directories whodata="yes">/home/user</directories>
```
The folder `/home/Skeptor` must be monitored with whodata mode.
The test must also include entries with a trailing slash in a single comma-separated stanza.
Syscheck must have only one entry in `directories` tags like this: `<directories>/home/user, /home/user</directories>` | 1.0 | Syscheck automated tests: Check duplicate entries are ignored. - Working branch | Platform
-- | --
| Linux/Windows/macOS
Description
----------
In case a folder is specified in more than one `directories` tag, syscheck must monitor the last entry, overriding the rest of the entries.
For example, with the following configuration:
```
<directories realtime="yes">/home/user</directories>
<directories whodata="yes">/home/user</directories>
```
The folder `/home/Skeptor` must be monitored with whodata mode.
The test must also include entries with a trailing slash in a single comma-separated stanza.
Syscheck must have only one entry in `directories` tags like this: `<directories>/home/user, /home/user</directories>` | non_test | syscheck automated tests check duplicate entries are ignored working branch platform linux windows macos description in case a folder is specified in more than one directories tag syscheck must monitor the last entry overriding the rest of the entries for example with the following configuration home user home user the folder home skeptor must be monitored with whodata mode the test must also include entries with a trailing slash in a single comma separated stanza syscheck must have only one entry in directories tags like this home user home user | 0 |
20,710 | 3,834,891,096 | IssuesEvent | 2016-04-01 12:05:08 | red/red | https://api.github.com/repos/red/red | closed | Issue with console when using `view [window]` | status.built status.tested type.review | 1) Start the red console.
2) Type `view [window]`
3) Press ENTER.
=> Two windows open up. One at the Center of the Screen (Lets call it A). Another at the top of the screen (Lets call it B).
Now, if you close the window B.
=>
```
*** Runtime Error 1: access violation
*** at: 928059ADh
```
If __INSTEAD OF__ window B, you close window A
=> You get a blinking cursor in the console. But no `red>>` prompt. So you are unable to do anything in the console. You need to close and reopen the console if you want to use Red.
| 1.0 | Issue with console when using `view [window]` - 1) Start the red console.
2) Type `view [window]`
3) Press ENTER.
=> Two windows open up. One at the Center of the Screen (Lets call it A). Another at the top of the screen (Lets call it B).
Now, if you close the window B.
=>
```
*** Runtime Error 1: access violation
*** at: 928059ADh
```
If __INSTEAD OF__ window B, you close window A
=> You get a blinking cursor in the console. But no `red>>` prompt. So you are unable to do anything in the console. You need to close and reopen the console if you want to use Red.
| test | issue with console when using view start the red console type view press enter two windows open up one at the center of the screen lets call it a another at the top of the screen lets call it b now if you close the window b runtime error access violation at if instead of window b you close window a you get a blinking cursor in the console but no red prompt so you are unable to do anything in the console you need to close and reopen the console if you want to use red | 1 |
63,206 | 6,829,273,127 | IssuesEvent | 2017-11-08 23:38:12 | equella/Equella | https://api.github.com/repos/equella/Equella | closed | Download file viewer bypasses VIEW_RESTRICTED_ATTACHMENTS security | bug Ready for 6.5 GA Testing | If you restrict an attachment you shouldn't be able to download the file unless you have `VIEW_RESTRICTED_ATTACHMENTS`. However you can construct a URL which has the name of the file + the download viewer `"vi=save"` and download the file if you have VIEW_ITEM or VIEW_ATTACHMENTS. | 1.0 | Download file viewer bypasses VIEW_RESTRICTED_ATTACHMENTS security - If you restrict an attachment you shouldn't be able to download the file unless you have `VIEW_RESTRICTED_ATTACHMENTS`. However you can construct a URL which has the name of the file + the download viewer `"vi=save"` and download the file if you have VIEW_ITEM or VIEW_ATTACHMENTS. | test | download file viewer bypasses view restricted attachments security if you restrict an attachment you shouldn t be able to download the file unless you have view restricted attachments however you can construct a url which has the name of the file the download viewer vi save and download the file if you have view item or view attachments | 1 |
189,658 | 15,192,592,122 | IssuesEvent | 2021-02-15 22:24:10 | bazelbuild/bazel | https://api.github.com/repos/bazelbuild/bazel | closed | Comment in examples of runfiles provider is out of date. | P3 team-Starlark type: documentation (cleanup) | https://bazel.build/versions/master/docs/skylark/cookbook.html
The comments here talk about setting the fields on the struct returned, yet this is using the newer api of directly returning providers. | 1.0 | Comment in examples of runfiles provider is out of date. - https://bazel.build/versions/master/docs/skylark/cookbook.html
The comments here talk about setting the fields on the struct returned, yet this is using the newer api of directly returning providers. | non_test | comment in examples of runfiles provider is out of date the comments here talk about setting the fields on the struct returned yet this is using the newer api of directly returning providers | 0 |
323,867 | 27,755,481,290 | IssuesEvent | 2023-03-16 01:54:25 | TheCheatsrichter/Gw2_Launchbuddy | https://api.github.com/repos/TheCheatsrichter/Gw2_Launchbuddy | closed | Auto Login Not Working Properly | type:bug status:testing no-issue-activity | First thanks for all your hard work!
I lack proper knowledge of how the game client works but it seems something with a recent update causes launch buddy to hang when trying to launch the game. It easily takes upwards of a minute to fully load into character select even after "cancel" is clicked on the wait timer.
I backed up to v3.0.3 and I still had the issue.
If anyone else is experiencing this I'd love to hear any solutions. | 1.0 | Auto Login Not Working Properly - First thanks for all your hard work!
I lack proper knowledge of how the game client works but it seems something with a recent update causes launch buddy to hang when trying to launch the game. It easily takes upwards of a minute to fully load into character select even after "cancel" is clicked on the wait timer.
I backed up to v3.0.3 and I still had the issue.
If anyone else is experiencing this I'd love to hear any solutions. | test | auto login not working properly first thanks for all your hard work i lack proper knowledge of how the game client works but it seems something with a recent update causes launch buddy to hang when trying to launch the game it easily takes upwards of a minute to fully load into character select even after cancel is clicked on the wait timer i backed up to and i still had the issue if anyone else is experiencing this i d love to hear any solutions | 1 |
127,862 | 27,144,089,875 | IssuesEvent | 2023-02-16 18:29:15 | golang/vulndb | https://api.github.com/repos/golang/vulndb | closed | x/vulndb: potential Go vuln in github.com/git-for-windows/git: CVE-2023-22743 | excluded: NOT_GO_CODE | CVE-2023-22743 references [github.com/git-for-windows/git](https://github.com/git-for-windows/git), which may be a Go module.
Description:
Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.
References:
- NIST: https://nvd.nist.gov/vuln/detail/CVE-2023-22743
- JSON: https://github.com/CVEProject/cvelist/tree/c97d185bc218cb03912de125f38b027c4b18ab86/2023/22xxx/CVE-2023-22743.json
- fix: https://github.com/git-for-windows/git/security/advisories/GHSA-p2x9-prp4-8gvq
- web: https://github.com/git-for-windows/git/security/advisories/GHSA-gf48-x3vr-j5c3
- web: https://attack.mitre.org/techniques/T1574/002/
- web: https://github.com/git-for-windows/git/releases/tag/v2.39.2.windows.1
- web: https://learn.microsoft.com/en-us/windows/win32/controls/cookbook-overview?redirectedfrom=MSDN#using-comctl32dll-version-6-in-an-application-that-uses-only-standard-extensions
- web: https://learn.microsoft.com/en-us/windows/win32/sbscs/about-side-by-side-assemblies-
- Imported by: https://pkg.go.dev/github.com/git-for-windows/git?tab=importedby
Cross references:
- Module github.com/git-for-windows/git appears in issue #419 NOT_GO_CODE
- Module github.com/git-for-windows/git appears in issue #420 NOT_GO_CODE
- Module github.com/git-for-windows/git appears in issue #514 NOT_GO_CODE
- Module github.com/git-for-windows/git appears in issue #1498 NOT_GO_CODE
See [doc/triage.md](https://github.com/golang/vulndb/blob/master/doc/triage.md) for instructions on how to triage this report.
```
modules:
- module: github.com/git-for-windows/git
packages:
- package: git
description: |
Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.
cves:
- CVE-2023-22743
references:
- fix: https://github.com/git-for-windows/git/security/advisories/GHSA-p2x9-prp4-8gvq
- web: https://github.com/git-for-windows/git/security/advisories/GHSA-gf48-x3vr-j5c3
- web: https://attack.mitre.org/techniques/T1574/002/
- web: https://github.com/git-for-windows/git/releases/tag/v2.39.2.windows.1
- web: https://learn.microsoft.com/en-us/windows/win32/controls/cookbook-overview?redirectedfrom=MSDN#using-comctl32dll-version-6-in-an-application-that-uses-only-standard-extensions
- web: https://learn.microsoft.com/en-us/windows/win32/sbscs/about-side-by-side-assemblies-
``` | 1.0 | x/vulndb: potential Go vuln in github.com/git-for-windows/git: CVE-2023-22743 - CVE-2023-22743 references [github.com/git-for-windows/git](https://github.com/git-for-windows/git), which may be a Go module.
Description:
Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.
References:
- NIST: https://nvd.nist.gov/vuln/detail/CVE-2023-22743
- JSON: https://github.com/CVEProject/cvelist/tree/c97d185bc218cb03912de125f38b027c4b18ab86/2023/22xxx/CVE-2023-22743.json
- fix: https://github.com/git-for-windows/git/security/advisories/GHSA-p2x9-prp4-8gvq
- web: https://github.com/git-for-windows/git/security/advisories/GHSA-gf48-x3vr-j5c3
- web: https://attack.mitre.org/techniques/T1574/002/
- web: https://github.com/git-for-windows/git/releases/tag/v2.39.2.windows.1
- web: https://learn.microsoft.com/en-us/windows/win32/controls/cookbook-overview?redirectedfrom=MSDN#using-comctl32dll-version-6-in-an-application-that-uses-only-standard-extensions
- web: https://learn.microsoft.com/en-us/windows/win32/sbscs/about-side-by-side-assemblies-
- Imported by: https://pkg.go.dev/github.com/git-for-windows/git?tab=importedby
Cross references:
- Module github.com/git-for-windows/git appears in issue #419 NOT_GO_CODE
- Module github.com/git-for-windows/git appears in issue #420 NOT_GO_CODE
- Module github.com/git-for-windows/git appears in issue #514 NOT_GO_CODE
- Module github.com/git-for-windows/git appears in issue #1498 NOT_GO_CODE
See [doc/triage.md](https://github.com/golang/vulndb/blob/master/doc/triage.md) for instructions on how to triage this report.
```
modules:
- module: github.com/git-for-windows/git
packages:
- package: git
description: |
Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.
cves:
- CVE-2023-22743
references:
- fix: https://github.com/git-for-windows/git/security/advisories/GHSA-p2x9-prp4-8gvq
- web: https://github.com/git-for-windows/git/security/advisories/GHSA-gf48-x3vr-j5c3
- web: https://attack.mitre.org/techniques/T1574/002/
- web: https://github.com/git-for-windows/git/releases/tag/v2.39.2.windows.1
- web: https://learn.microsoft.com/en-us/windows/win32/controls/cookbook-overview?redirectedfrom=MSDN#using-comctl32dll-version-6-in-an-application-that-uses-only-standard-extensions
- web: https://learn.microsoft.com/en-us/windows/win32/sbscs/about-side-by-side-assemblies-
``` | non_test | x vulndb potential go vuln in github com git for windows git cve cve references which may be a go module description git for windows is the windows port of the revision control system git prior to git for windows version by carefully crafting dll and putting into a subdirectory of a specific name living next to the git for windows installer windows can be tricked into side loading said dll this potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the git for windows installer with elevation version contains a patch for this issue some workarounds are available never leave untrusted files in the downloads folder or its sub folders before executing the git for windows installer or move the installer into a different directory before executing it references nist json fix web web web web web imported by cross references module github com git for windows git appears in issue not go code module github com git for windows git appears in issue not go code module github com git for windows git appears in issue not go code module github com git for windows git appears in issue not go code see for instructions on how to triage this report modules module github com git for windows git packages package git description git for windows is the windows port of the revision control system git prior to git for windows version by carefully crafting dll and putting into a subdirectory of a specific name living next to the git for windows installer windows can be tricked into side loading said dll this potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the git for windows installer with elevation version contains a patch for this issue some workarounds are available never leave untrusted files in the downloads folder or its sub folders before executing the git for windows installer or move the installer into a different directory before executing it cves cve references fix web web web web web | 0 |
63,976 | 18,097,592,262 | IssuesEvent | 2021-09-22 10:47:30 | vector-im/element-ios | https://api.github.com/repos/vector-im/element-ios | opened | Sharing photos via another app + system share doesn't work | T-Defect A-Media S-Major O-Uncommon | ### Steps to reproduce
1. Go to photos app
2. Share/send in the bottom left of the screen
3. Select Element (or in my case Delight)
4. Select a Room or a Person to share with
5. See pop up asking if you want to cancel or send
6. Select "Send"
### What happened?
### What did you expect?
Image is sent
### What happened?
Click event is registered and image is not sent.
This is sometimes reproducible.
### Your phone model
_No response_
### Operating system version
14.6
### Application version
Gil's version for testing spaces 22 Sept build
### Homeserver
_No response_
### Have you submitted a rageshake?
No | 1.0 | Sharing photos via another app + system share doesn't work - ### Steps to reproduce
1. Go to photos app
2. Share/send in the bottom left of the screen
3. Select Element (or in my case Delight)
4. Select a Room or a Person to share with
5. See pop up asking if you want to cancel or send
6. Select "Send"
### What happened?
### What did you expect?
Image is sent
### What happened?
Click event is registered and image is not sent.
This is sometimes reproducible.
### Your phone model
_No response_
### Operating system version
14.6
### Application version
Gil's version for testing spaces 22 Sept build
### Homeserver
_No response_
### Have you submitted a rageshake?
No | non_test | sharing photos via another app system share doesn t work steps to reproduce go to photos app share send in the bottom left of the screen select element or in my case delight select a room or a person to share with see pop up asking if you want to cancel or send select send what happened what did you expect image is sent what happened click event is registered and image is not sent this is sometimes reproducible your phone model no response operating system version application version gil s version for testing spaces sept build homeserver no response have you submitted a rageshake no | 0 |
27,121 | 4,281,846,648 | IssuesEvent | 2016-07-15 06:10:49 | Terracotta-OSS/galvan | https://api.github.com/repos/Terracotta-OSS/galvan | closed | ServerProcess.start() returns before server's JVM process is launched on window | requires re-test | As shown in the below code snippet, the start() method doesn't wait for JVM process to be launched on Windows. This can cause test to hang if the stop() is immediately invoked right after start. This problem was observed in one of the ehcache clustered tests causing the build to hang on Windows.
// Wait for the server to enter started.
synchronized (this) {
if (TestHelpers.isWindows()){
//windows start script doesn't emit this event, so skip it.
this.isScriptReady = true;
}
while (!this.isScriptReady) {
try {
wait();
} catch (InterruptedException e) {
// We can't recover from interruption here.
Assert.unexpected(e);
}
}
} | 1.0 | ServerProcess.start() returns before server's JVM process is launched on window - As shown in the below code snippet, the start() method doesn't wait for JVM process to be launched on Windows. This can cause test to hang if the stop() is immediately invoked right after start. This problem was observed in one of the ehcache clustered tests causing the build to hang on Windows.
// Wait for the server to enter started.
synchronized (this) {
if (TestHelpers.isWindows()){
//windows start script doesn't emit this event, so skip it.
this.isScriptReady = true;
}
while (!this.isScriptReady) {
try {
wait();
} catch (InterruptedException e) {
// We can't recover from interruption here.
Assert.unexpected(e);
}
}
} | test | serverprocess start returns before server s jvm process is launched on window as shown in the below code snippet the start method doesn t wait for jvm process to be launched on windows this can cause test to hang if the stop is immediately invoked right after start this problem was observed in one of the ehcache clustered tests causing the build to hang on windows wait for the server to enter started synchronized this if testhelpers iswindows windows start script doesn t emit this event so skip it this isscriptready true while this isscriptready try wait catch interruptedexception e we can t recover from interruption here assert unexpected e | 1 |
597,226 | 18,158,542,521 | IssuesEvent | 2021-09-27 06:48:28 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | closed | Unclassified Authentication Failure when invoking the API with JWT tokens | Type/Bug Priority/Normal | ### Description:
Unclassified Authentication Failure when invoking the API by using JWT token from the ForgeRock Key Manager
### Steps to reproduce:
- Configure ForgeRock key manager via the admin portal.
- Publish an API via the publisher portal.
- Go to the dev portal and create an application.
- Generate application keys and JWT access tokens by using the ForgeRock Key Manager.
- Invoke the API and able to get the below response.
- Furthermore, able to see the below error stack trace in the carbon logs.
```
[2021-09-02 20:23:39,206] ERROR - APIAuthenticationHandler API authentication failure due to Unclassified Authentication Failure
org.wso2.carbon.apimgt.gateway.handlers.security.APISecurityException: Unclassified Authentication Failure
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.isAuthenticate_aroundBody42(APIAuthenticationHandler.java:442) ~[org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.isAuthenticate(APIAuthenticationHandler.java:422) ~[org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.handleRequest_aroundBody36(APIAuthenticationHandler.java:353) [org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.handleRequest(APIAuthenticationHandler.java:317) [org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.apache.synapse.api.API.process(API.java:389) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.AbstractApiHandler.apiProcessNonDefaultStrategy(AbstractApiHandler.java:107) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.AbstractApiHandler.identifyAPI(AbstractApiHandler.java:127) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.AbstractApiHandler.dispatchToAPI(AbstractApiHandler.java:59) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.rest.RestRequestHandler.dispatchToAPI(RestRequestHandler.java:84) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.rest.RestRequestHandler.process(RestRequestHandler.java:70) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:54) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:344) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:101) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) [axis2_1.6.1.wso2v63_1.jar:?]
at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:375) [synapse-nhttp-transport_2.1.7.wso2v227_4.jar:?]
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:434) [synapse-nhttp-transport_2.1.7.wso2v227_4.jar:?]
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:182) [synapse-nhttp-transport_2.1.7.wso2v227_4.jar:?]
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) [axis2_1.6.1.wso2v63_1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
```
### Affected Product Version:
4.0.0 | 1.0 | Unclassified Authentication Failure when invoking the API with JWT tokens - ### Description:
Unclassified Authentication Failure when invoking the API by using JWT token from the ForgeRock Key Manager
### Steps to reproduce:
- Configure ForgeRock key manager via the admin portal.
- Publish an API via the publisher portal.
- Go to the dev portal and create an application.
- Generate application keys and JWT access tokens by using the ForgeRock Key Manager.
- Invoke the API and able to get the below response.
- Furthermore, able to see the below error stack trace in the carbon logs.
```
[2021-09-02 20:23:39,206] ERROR - APIAuthenticationHandler API authentication failure due to Unclassified Authentication Failure
org.wso2.carbon.apimgt.gateway.handlers.security.APISecurityException: Unclassified Authentication Failure
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.isAuthenticate_aroundBody42(APIAuthenticationHandler.java:442) ~[org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.isAuthenticate(APIAuthenticationHandler.java:422) ~[org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.handleRequest_aroundBody36(APIAuthenticationHandler.java:353) [org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.handleRequest(APIAuthenticationHandler.java:317) [org.wso2.carbon.apimgt.gateway_9.0.174.29.jar:?]
at org.apache.synapse.api.API.process(API.java:389) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.AbstractApiHandler.apiProcessNonDefaultStrategy(AbstractApiHandler.java:107) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.AbstractApiHandler.identifyAPI(AbstractApiHandler.java:127) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.AbstractApiHandler.dispatchToAPI(AbstractApiHandler.java:59) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.rest.RestRequestHandler.dispatchToAPI(RestRequestHandler.java:84) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.api.rest.RestRequestHandler.process(RestRequestHandler.java:70) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:54) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:344) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:101) [synapse-core_2.1.7.wso2v227_3.jar:2.1.7-wso2v227.3]
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) [axis2_1.6.1.wso2v63_1.jar:?]
at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:375) [synapse-nhttp-transport_2.1.7.wso2v227_4.jar:?]
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:434) [synapse-nhttp-transport_2.1.7.wso2v227_4.jar:?]
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:182) [synapse-nhttp-transport_2.1.7.wso2v227_4.jar:?]
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) [axis2_1.6.1.wso2v63_1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
```
### Affected Product Version:
4.0.0 | non_test | unclassified authentication failure when invoking the api with jwt tokens description unclassified authentication failure when invoking the api by using jwt token from the forgerock key manager steps to reproduce configure forgerock key manager via the admin portal publish an api via the publisher portal go to the dev portal and create an application generate application keys and jwt access tokens by using the forgerock key manager invoke the api and able to get the below response furthermore able to see the below error stack trace in the carbon logs error apiauthenticationhandler api authentication failure due to unclassified authentication failure org carbon apimgt gateway handlers security apisecurityexception unclassified authentication failure at org carbon apimgt gateway handlers security apiauthenticationhandler isauthenticate apiauthenticationhandler java at org carbon apimgt gateway handlers security apiauthenticationhandler isauthenticate apiauthenticationhandler java at org carbon apimgt gateway handlers security apiauthenticationhandler handlerequest apiauthenticationhandler java at org carbon apimgt gateway handlers security apiauthenticationhandler handlerequest apiauthenticationhandler java at org apache synapse api api process api java at org apache synapse api abstractapihandler apiprocessnondefaultstrategy abstractapihandler java at org apache synapse api abstractapihandler identifyapi abstractapihandler java at org apache synapse api abstractapihandler dispatchtoapi abstractapihandler java at org apache synapse api rest restrequesthandler dispatchtoapi restrequesthandler java at org apache synapse api rest restrequesthandler process restrequesthandler java at org apache synapse rest restrequesthandler process restrequesthandler java at org apache synapse core injectmessage java at org apache synapse core synapsemessagereceiver receive synapsemessagereceiver java at org apache engine axisengine receive axisengine java at org apache synapse transport passthru serverworker processnonentityenclosingresthandler serverworker java at org apache synapse transport passthru serverworker processentityenclosingrequest serverworker java at org apache synapse transport passthru serverworker run serverworker java at org apache transport base threads nativeworkerpool run nativeworkerpool 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 affected product version | 0 |
32,721 | 4,787,608,698 | IssuesEvent | 2016-10-30 03:35:35 | SegMail/SegMail | https://api.github.com/repos/SegMail/SegMail | closed | Check if list is setup properly before generating signup codes | Feature Ready for Int Tests | If list attributes like Send As or confirmation email not assigned, should not allow client to generate any signup codes. | 1.0 | Check if list is setup properly before generating signup codes - If list attributes like Send As or confirmation email not assigned, should not allow client to generate any signup codes. | test | check if list is setup properly before generating signup codes if list attributes like send as or confirmation email not assigned should not allow client to generate any signup codes | 1 |
22,484 | 3,960,853,052 | IssuesEvent | 2016-05-02 09:30:40 | hazelcast/hazelcast | https://api.github.com/repos/hazelcast/hazelcast | reopened | [TEST-FAILURE] ClientMapIssueTest.testListenerRegistrations | Team: Client Type: Test-Failure | https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.maintenance/com.hazelcast$hazelcast-client/387/testReport/junit/com.hazelcast.client.map/ClientMapIssueTest/testListenerRegistrations/
```
java.lang.AssertionError: there should be only one registrations expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at com.hazelcast.client.map.ClientMapIssueTest.testListenerRegistrations(ClientMapIssueTest.java:92)
```
| 1.0 | [TEST-FAILURE] ClientMapIssueTest.testListenerRegistrations - https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.maintenance/com.hazelcast$hazelcast-client/387/testReport/junit/com.hazelcast.client.map/ClientMapIssueTest/testListenerRegistrations/
```
java.lang.AssertionError: there should be only one registrations expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at com.hazelcast.client.map.ClientMapIssueTest.testListenerRegistrations(ClientMapIssueTest.java:92)
```
| test | clientmapissuetest testlistenerregistrations java lang assertionerror there should be only one registrations expected but was at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at org junit assert assertequals assert java at com hazelcast client map clientmapissuetest testlistenerregistrations clientmapissuetest java | 1 |
244,935 | 20,731,312,436 | IssuesEvent | 2022-03-14 09:42:34 | gameserverapp/Platform | https://api.github.com/repos/gameserverapp/Platform | closed | inherit shop pack "ignore player status" when sending via task | improvement status: to be tested task | **Describe the issue**
Sending a shop pack set to ignore online status as part of a triggered task improperly waits for the player to be online.
**Section**
Deliveries
**Additional context**
[https://dash.gameserverapp.com/task/history/1605449](https://dash.gameserverapp.com/task/history/1605449)
| 1.0 | inherit shop pack "ignore player status" when sending via task - **Describe the issue**
Sending a shop pack set to ignore online status as part of a triggered task improperly waits for the player to be online.
**Section**
Deliveries
**Additional context**
[https://dash.gameserverapp.com/task/history/1605449](https://dash.gameserverapp.com/task/history/1605449)
| test | inherit shop pack ignore player status when sending via task describe the issue sending a shop pack set to ignore online status as part of a triggered task improperly waits for the player to be online section deliveries additional context | 1 |
257,676 | 22,200,750,164 | IssuesEvent | 2022-06-07 10:57:38 | mozilla/addons-frontend | https://api.github.com/repos/mozilla/addons-frontend | closed | Migrate /components/TestUserProfileHead.js to react-testing-library | component: testing priority: p3 | Migrate /components/TestUserProfileHead.js to react-testing-library | 1.0 | Migrate /components/TestUserProfileHead.js to react-testing-library - Migrate /components/TestUserProfileHead.js to react-testing-library | test | migrate components testuserprofilehead js to react testing library migrate components testuserprofilehead js to react testing library | 1 |
4,726 | 24,393,000,501 | IssuesEvent | 2022-10-04 16:41:24 | carbon-design-system/carbon | https://api.github.com/repos/carbon-design-system/carbon | closed | [Bug]: Search - clear button does not call `onChange` with proper event | severity: 3 type: bug 🐛 status: waiting for maintainer response 💬 | ### Package
@carbon/react
### Browser
Chrome
### Package version
1.12.0
### React version
18.2.0
### Description
When clicking the close button after inputting text and clicking outside the component to trigger a blur/defocus event, the component is not collapsed even though the text input is empty.
In the Search component, when the Close button is clicked, `clearInput` is called. The event passed to the handler is for the button click.
When the Search component's `value` prop is undefined/null, then the `onChange` prop is called with the button click event.
When the Search component's `value` prop is defined, then the `onChange` prop is called with a modified event:
```js
{
...event.target,
target: { value: '' },
}
```
This event is not constructed properly and should either be a simple mock event:
```js
{
target: { value: '' }
}
```
or overwriting the value:
```js
{
...event,
target: {
...event.target,
value: '',
},
}
```
### Reproduction/example
https://react.carbondesignsystem.com/?path=/story/components-search--expandable
### Steps to reproduce
https://react.carbondesignsystem.com/?path=/story/components-search--expandable
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md)
- [X] I checked the [current issues](https://github.com/carbon-design-system/carbon/issues) for duplicate problems | True | [Bug]: Search - clear button does not call `onChange` with proper event - ### Package
@carbon/react
### Browser
Chrome
### Package version
1.12.0
### React version
18.2.0
### Description
When clicking the close button after inputting text and clicking outside the component to trigger a blur/defocus event, the component is not collapsed even though the text input is empty.
In the Search component, when the Close button is clicked, `clearInput` is called. The event passed to the handler is for the button click.
When the Search component's `value` prop is undefined/null, then the `onChange` prop is called with the button click event.
When the Search component's `value` prop is defined, then the `onChange` prop is called with a modified event:
```js
{
...event.target,
target: { value: '' },
}
```
This event is not constructed properly and should either be a simple mock event:
```js
{
target: { value: '' }
}
```
or overwriting the value:
```js
{
...event,
target: {
...event.target,
value: '',
},
}
```
### Reproduction/example
https://react.carbondesignsystem.com/?path=/story/components-search--expandable
### Steps to reproduce
https://react.carbondesignsystem.com/?path=/story/components-search--expandable
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md)
- [X] I checked the [current issues](https://github.com/carbon-design-system/carbon/issues) for duplicate problems | non_test | search clear button does not call onchange with proper event package carbon react browser chrome package version react version description when clicking the close button after inputting text and clicking outside the component to trigger a blur defocus event the component is not collapsed even though the text input is empty in the search component when the close button is clicked clearinput is called the event passed to the handler is for the button click when the search component s value prop is undefined null then the onchange prop is called with the button click event when the search component s value prop is defined then the onchange prop is called with a modified event js event target target value this event is not constructed properly and should either be a simple mock event js target value or overwriting the value js event target event target value reproduction example steps to reproduce code of conduct i agree to follow this project s i checked the for duplicate problems | 0 |
234,505 | 19,186,838,590 | IssuesEvent | 2021-12-05 10:50:12 | lokka30/LevelledMobs | https://api.github.com/repos/lokka30/LevelledMobs | closed | Request: Levelled spawn eggs | enhancement needs testing priority: medium | https://www.spigotmc.org/members/british89.355307/ suggested:
> Would be amazing if you could do /lm egg [ENTITY] [LEVEL] to get a mob of any level in an egg for mob arenas
Link to suggestion: https://www.spigotmc.org/threads/levelledmobs-for-1-14-x-1-16-x.412953/page-11#post-4125137
Initial thoughts: need to listen for hand-placement, dispencing of the eggs. Possibly warn users when they click on spawners with it | 1.0 | Request: Levelled spawn eggs - https://www.spigotmc.org/members/british89.355307/ suggested:
> Would be amazing if you could do /lm egg [ENTITY] [LEVEL] to get a mob of any level in an egg for mob arenas
Link to suggestion: https://www.spigotmc.org/threads/levelledmobs-for-1-14-x-1-16-x.412953/page-11#post-4125137
Initial thoughts: need to listen for hand-placement, dispencing of the eggs. Possibly warn users when they click on spawners with it | test | request levelled spawn eggs suggested would be amazing if you could do lm egg to get a mob of any level in an egg for mob arenas link to suggestion initial thoughts need to listen for hand placement dispencing of the eggs possibly warn users when they click on spawners with it | 1 |
13,254 | 10,169,513,499 | IssuesEvent | 2019-08-08 00:52:48 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Accessing data from multiple simulations | interface/infrastructure newfeature | As discussed with Drew .... I'd like to be able to do a numerical (e.g. regression) or logical test across data from multiple simulations. This would aid sensibility testing for starters. A simple example would be a simulation with an Experiment node in which the factors are increasing the amount of water available to the plant. Across those simulations we should see a consistent pattern of behaviour and the point of interest is the general pattern (increasing, decreasing, parabolic, asymptotic) rather than the actual values. While these patterns can be graphed it does not seem to be possible to do anything like calculating a regression in a script or indicating that a test has passed or failed with it. This would be a useful feature. | 1.0 | Accessing data from multiple simulations - As discussed with Drew .... I'd like to be able to do a numerical (e.g. regression) or logical test across data from multiple simulations. This would aid sensibility testing for starters. A simple example would be a simulation with an Experiment node in which the factors are increasing the amount of water available to the plant. Across those simulations we should see a consistent pattern of behaviour and the point of interest is the general pattern (increasing, decreasing, parabolic, asymptotic) rather than the actual values. While these patterns can be graphed it does not seem to be possible to do anything like calculating a regression in a script or indicating that a test has passed or failed with it. This would be a useful feature. | non_test | accessing data from multiple simulations as discussed with drew i d like to be able to do a numerical e g regression or logical test across data from multiple simulations this would aid sensibility testing for starters a simple example would be a simulation with an experiment node in which the factors are increasing the amount of water available to the plant across those simulations we should see a consistent pattern of behaviour and the point of interest is the general pattern increasing decreasing parabolic asymptotic rather than the actual values while these patterns can be graphed it does not seem to be possible to do anything like calculating a regression in a script or indicating that a test has passed or failed with it this would be a useful feature | 0 |
14,431 | 4,927,364,976 | IssuesEvent | 2016-11-26 18:03:09 | fossasia/labs.fossasia.org | https://api.github.com/repos/fossasia/labs.fossasia.org | closed | Fix the blog showcase section on fossasia.org | code-in GCI mini-project | Please refer to the project issue here: https://github.com/fossasia/fossasia.org/issues/41
The set up of http://blog.fossasia.org has changed as we moved the blog from Drupal to Wordpress. The result is that the showcase section "Blog" on the page does not work anymore. Please re-implement it on http://fossasia.org.
| 1.0 | Fix the blog showcase section on fossasia.org - Please refer to the project issue here: https://github.com/fossasia/fossasia.org/issues/41
The set up of http://blog.fossasia.org has changed as we moved the blog from Drupal to Wordpress. The result is that the showcase section "Blog" on the page does not work anymore. Please re-implement it on http://fossasia.org.
| non_test | fix the blog showcase section on fossasia org please refer to the project issue here the set up of has changed as we moved the blog from drupal to wordpress the result is that the showcase section blog on the page does not work anymore please re implement it on | 0 |
93,895 | 8,453,287,278 | IssuesEvent | 2018-10-20 14:16:33 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | [CI] IndexRecoveryIT.testRerouteRecovery : Paths exist that should have been deleted | :Distributed/Recovery >test-failure v6.4.1 v7.0.0 | Build failures: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.4+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java10,nodes=virtual&&linux/21/console
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/224/console
Root cause:
```
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=5109, name=elasticsearch[node_t0][clusterApplierService#updateTask][T#1], state=RUNNABLE, group=TGRP-IndexRecoveryIT]
at __randomizedtesting.SeedInfo.seed([E8CEC7E4E4750104:456574B0D12D6346]:0)
Caused by: java.lang.AssertionError: Paths exist that should have been deleted: [/var/lib/jenkins/workspace/elastic+elasticsearch+6.4+matrix-java-periodic/ES_BUILD_JAVA/java10/ES_RUNTIME_JAVA/java10/nodes/virtual&&linux/server/build/testrun/integTest/J1/temp/org.elasticsearch.indices.recovery.IndexRecoveryIT_E8CEC7E4E4750104-001/tempDir-004/data/nodes/0/indices/RJoRvWIVRDyM1toTfMV2tw/0]
at __randomizedtesting.SeedInfo.seed([E8CEC7E4E4750104]:0)
at org.elasticsearch.env.NodeEnvironment.assertPathsDoNotExist(NodeEnvironment.java:469)
at org.elasticsearch.env.NodeEnvironment.deleteShardDirectoryUnderLock(NodeEnvironment.java:459)
at org.elasticsearch.env.NodeEnvironment.deleteShardDirectorySafe(NodeEnvironment.java:399)
at org.elasticsearch.indices.IndicesService.deleteShardStore(IndicesService.java:770)
at org.elasticsearch.indices.store.IndicesStore$ShardActiveResponseHandler.lambda$allNodesResponded$2(IndicesStore.java:288)
at org.elasticsearch.cluster.service.ClusterApplierService.lambda$runOnApplierThread$0(ClusterApplierService.java:306)
at org.elasticsearch.cluster.service.ClusterApplierService$UpdateTask.apply(ClusterApplierService.java:155)
at org.elasticsearch.cluster.service.ClusterApplierService.runTask(ClusterApplierService.java:399)
at org.elasticsearch.cluster.service.ClusterApplierService$UpdateTask.run(ClusterApplierService.java:160)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:624)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:244)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:207)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)
```
It does not reproduce:
```
REPRODUCE WITH: ./gradlew :server:integTest \
-Dtests.seed=B4F936D0EF2B4D07 \
-Dtests.class=org.elasticsearch.indices.recovery.IndexRecoveryIT \
-Dtests.method="testRerouteRecovery" \
-Dtests.security.manager=true \
-Dtests.locale=fr-TN \
-Dtests.timezone=Eire
```
| 1.0 | [CI] IndexRecoveryIT.testRerouteRecovery : Paths exist that should have been deleted - Build failures: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.4+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java10,nodes=virtual&&linux/21/console
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/224/console
Root cause:
```
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=5109, name=elasticsearch[node_t0][clusterApplierService#updateTask][T#1], state=RUNNABLE, group=TGRP-IndexRecoveryIT]
at __randomizedtesting.SeedInfo.seed([E8CEC7E4E4750104:456574B0D12D6346]:0)
Caused by: java.lang.AssertionError: Paths exist that should have been deleted: [/var/lib/jenkins/workspace/elastic+elasticsearch+6.4+matrix-java-periodic/ES_BUILD_JAVA/java10/ES_RUNTIME_JAVA/java10/nodes/virtual&&linux/server/build/testrun/integTest/J1/temp/org.elasticsearch.indices.recovery.IndexRecoveryIT_E8CEC7E4E4750104-001/tempDir-004/data/nodes/0/indices/RJoRvWIVRDyM1toTfMV2tw/0]
at __randomizedtesting.SeedInfo.seed([E8CEC7E4E4750104]:0)
at org.elasticsearch.env.NodeEnvironment.assertPathsDoNotExist(NodeEnvironment.java:469)
at org.elasticsearch.env.NodeEnvironment.deleteShardDirectoryUnderLock(NodeEnvironment.java:459)
at org.elasticsearch.env.NodeEnvironment.deleteShardDirectorySafe(NodeEnvironment.java:399)
at org.elasticsearch.indices.IndicesService.deleteShardStore(IndicesService.java:770)
at org.elasticsearch.indices.store.IndicesStore$ShardActiveResponseHandler.lambda$allNodesResponded$2(IndicesStore.java:288)
at org.elasticsearch.cluster.service.ClusterApplierService.lambda$runOnApplierThread$0(ClusterApplierService.java:306)
at org.elasticsearch.cluster.service.ClusterApplierService$UpdateTask.apply(ClusterApplierService.java:155)
at org.elasticsearch.cluster.service.ClusterApplierService.runTask(ClusterApplierService.java:399)
at org.elasticsearch.cluster.service.ClusterApplierService$UpdateTask.run(ClusterApplierService.java:160)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:624)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:244)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:207)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)
```
It does not reproduce:
```
REPRODUCE WITH: ./gradlew :server:integTest \
-Dtests.seed=B4F936D0EF2B4D07 \
-Dtests.class=org.elasticsearch.indices.recovery.IndexRecoveryIT \
-Dtests.method="testRerouteRecovery" \
-Dtests.security.manager=true \
-Dtests.locale=fr-TN \
-Dtests.timezone=Eire
```
| test | indexrecoveryit testrerouterecovery paths exist that should have been deleted build failures root cause com carrotsearch randomizedtesting uncaughtexceptionerror captured an uncaught exception in thread thread state runnable group tgrp indexrecoveryit at randomizedtesting seedinfo seed caused by java lang assertionerror paths exist that should have been deleted at randomizedtesting seedinfo seed at org elasticsearch env nodeenvironment assertpathsdonotexist nodeenvironment java at org elasticsearch env nodeenvironment deletesharddirectoryunderlock nodeenvironment java at org elasticsearch env nodeenvironment deletesharddirectorysafe nodeenvironment java at org elasticsearch indices indicesservice deleteshardstore indicesservice java at org elasticsearch indices store indicesstore shardactiveresponsehandler lambda allnodesresponded indicesstore java at org elasticsearch cluster service clusterapplierservice lambda runonapplierthread clusterapplierservice java at org elasticsearch cluster service clusterapplierservice updatetask apply clusterapplierservice java at org elasticsearch cluster service clusterapplierservice runtask clusterapplierservice java at org elasticsearch cluster service clusterapplierservice updatetask run clusterapplierservice 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 base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java it does not reproduce reproduce with gradlew server integtest dtests seed dtests class org elasticsearch indices recovery indexrecoveryit dtests method testrerouterecovery dtests security manager true dtests locale fr tn dtests timezone eire | 1 |
83,651 | 7,878,330,131 | IssuesEvent | 2018-06-26 09:53:50 | Cadiducho/40ServidoresMC | https://api.github.com/repos/Cadiducho/40ServidoresMC | closed | Problema con el plugin | Error | Bug Necesita Test | Hola, les vengo a comentar del siguiente error, el cual hace que las modalidades se lageen y por ello terminen saturando el servidor y se reinicie forzosamente.
```Current Thread: Server thread
[20:55:21] [Spigot Watchdog Thread/ERROR]: PID: 17 | Suspended: false | Native: true | State: RUNNABLE
[20:55:21] [Spigot Watchdog Thread/ERROR]: Stack:
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.PlainSocketImpl.socketConnect(Native Method)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.Socket.connect(Socket.java:589)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.Socket.connect(Socket.java:538)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.NetworkClient.doConnect(NetworkClient.java:180)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.New(HttpClient.java:339)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.New(HttpClient.java:357)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.util.Util.readUrl(Util.java:88)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.cmd.VoteCMD.run(VoteCMD.java:32)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.CommandManager.onCmd(CommandManager.java:55)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.BukkitPlugin.onCommand(BukkitPlugin.java:101)
[20:55:21] [Spigot Watchdog Thread/ERROR]: org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
[20:55:21] [Spigot Watchdog Thread/ERROR]: org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:141)
[20:55:21] [Spigot Watchdog Thread/ERROR]: org.bukkit.craftbukkit.v1_8_R3.CraftServer.dispatchCommand(CraftServer.java:641)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PlayerConnection.handleCommand(PlayerConnection.java:1165)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PlayerConnection.a(PlayerConnection.java:1000)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PacketPlayInChat.a(PacketPlayInChat.java:45)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PacketPlayInChat.a(PacketPlayInChat.java:1)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PlayerConnectionUtils$1.run(SourceFile:13)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.util.concurrent.FutureTask.run(FutureTask.java:266)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.SystemUtils.a(SourceFile:44)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:771)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:378)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:710)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:613)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.lang.Thread.run(Thread.java:748)
```
Podrían solucionar esto o decirme porque causa este problema? | 1.0 | Problema con el plugin | Error - Hola, les vengo a comentar del siguiente error, el cual hace que las modalidades se lageen y por ello terminen saturando el servidor y se reinicie forzosamente.
```Current Thread: Server thread
[20:55:21] [Spigot Watchdog Thread/ERROR]: PID: 17 | Suspended: false | Native: true | State: RUNNABLE
[20:55:21] [Spigot Watchdog Thread/ERROR]: Stack:
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.PlainSocketImpl.socketConnect(Native Method)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.Socket.connect(Socket.java:589)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.net.Socket.connect(Socket.java:538)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.NetworkClient.doConnect(NetworkClient.java:180)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.New(HttpClient.java:339)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.http.HttpClient.New(HttpClient.java:357)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
[20:55:21] [Spigot Watchdog Thread/ERROR]: sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.util.Util.readUrl(Util.java:88)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.cmd.VoteCMD.run(VoteCMD.java:32)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.CommandManager.onCmd(CommandManager.java:55)
[20:55:21] [Spigot Watchdog Thread/ERROR]: com.cadiducho.cservidoresmc.bukkit.BukkitPlugin.onCommand(BukkitPlugin.java:101)
[20:55:21] [Spigot Watchdog Thread/ERROR]: org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
[20:55:21] [Spigot Watchdog Thread/ERROR]: org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:141)
[20:55:21] [Spigot Watchdog Thread/ERROR]: org.bukkit.craftbukkit.v1_8_R3.CraftServer.dispatchCommand(CraftServer.java:641)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PlayerConnection.handleCommand(PlayerConnection.java:1165)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PlayerConnection.a(PlayerConnection.java:1000)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PacketPlayInChat.a(PacketPlayInChat.java:45)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PacketPlayInChat.a(PacketPlayInChat.java:1)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.PlayerConnectionUtils$1.run(SourceFile:13)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.util.concurrent.FutureTask.run(FutureTask.java:266)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.SystemUtils.a(SourceFile:44)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:771)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:378)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:710)
[20:55:21] [Spigot Watchdog Thread/ERROR]: net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:613)
[20:55:21] [Spigot Watchdog Thread/ERROR]: java.lang.Thread.run(Thread.java:748)
```
Podrían solucionar esto o decirme porque causa este problema? | test | problema con el plugin error hola les vengo a comentar del siguiente error el cual hace que las modalidades se lageen y por ello terminen saturando el servidor y se reinicie forzosamente current thread server thread pid suspended false native true state runnable stack java net plainsocketimpl socketconnect native method java net abstractplainsocketimpl doconnect abstractplainsocketimpl java java net abstractplainsocketimpl connecttoaddress abstractplainsocketimpl java java net abstractplainsocketimpl connect abstractplainsocketimpl java java net sockssocketimpl connect sockssocketimpl java java net socket connect socket java java net socket connect socket java sun net networkclient doconnect networkclient java sun net sun net sun net sun net sun net sun net sun net sun net sun net sun net sun net com cadiducho cservidoresmc bukkit util util readurl util java com cadiducho cservidoresmc bukkit cmd votecmd run votecmd java com cadiducho cservidoresmc bukkit commandmanager oncmd commandmanager java com cadiducho cservidoresmc bukkit bukkitplugin oncommand bukkitplugin java org bukkit command plugincommand execute plugincommand java org bukkit command simplecommandmap dispatch simplecommandmap java org bukkit craftbukkit craftserver dispatchcommand craftserver java net minecraft server playerconnection handlecommand playerconnection java net minecraft server playerconnection a playerconnection java net minecraft server packetplayinchat a packetplayinchat java net minecraft server packetplayinchat a packetplayinchat java net minecraft server playerconnectionutils run sourcefile java util concurrent executors runnableadapter call executors java java util concurrent futuretask run futuretask java net minecraft server systemutils a sourcefile net minecraft server minecraftserver b minecraftserver java net minecraft server dedicatedserver b dedicatedserver java net minecraft server minecraftserver a minecraftserver java net minecraft server minecraftserver run minecraftserver java java lang thread run thread java podrían solucionar esto o decirme porque causa este problema | 1 |
649,685 | 21,317,556,434 | IssuesEvent | 2022-04-16 14:52:12 | DimensionDev/Maskbook | https://api.github.com/repos/DimensionDev/Maskbook | closed | [Bug] Can't load assets list and balance | Priority: P1 (Now) Platform: Web (Firefox only) Will Not Fix Type: Bug | ## Bug Info
### How to reproduce?
Missing method fetchERC20TokensFromTokenLists
Missing method getAssetsList
### What happened?
### What should happen?
## Environment
### Mask Version:
- [x] (Browser) Installed from the extension store (version: )
- [ ] (App) Installed from the app store (version: )
- [ ] master branch
- [ ] Build of version/commit hash:
(Please write down build command/flags if there is anything special)
### System
<!-- Correct the version if it is not the case -->
- [ ] Windows 10
- [x] Mac OS X Catalina
- [ ] Linux: <!-- What distro? -->
### Platform/Browser
<!-- Correct the version if it is not the case -->
- [ ] Latest Chrome (stable channel)
- [x] Latest Firefox (stable channel)
- [ ] Android 11
- [ ] iOS 14
| 1.0 | [Bug] Can't load assets list and balance - ## Bug Info
### How to reproduce?
Missing method fetchERC20TokensFromTokenLists
Missing method getAssetsList
### What happened?
### What should happen?
## Environment
### Mask Version:
- [x] (Browser) Installed from the extension store (version: )
- [ ] (App) Installed from the app store (version: )
- [ ] master branch
- [ ] Build of version/commit hash:
(Please write down build command/flags if there is anything special)
### System
<!-- Correct the version if it is not the case -->
- [ ] Windows 10
- [x] Mac OS X Catalina
- [ ] Linux: <!-- What distro? -->
### Platform/Browser
<!-- Correct the version if it is not the case -->
- [ ] Latest Chrome (stable channel)
- [x] Latest Firefox (stable channel)
- [ ] Android 11
- [ ] iOS 14
| non_test | can t load assets list and balance bug info how to reproduce missing method missing method getassetslist what happened what should happen environment mask version browser installed from the extension store version app installed from the app store version master branch build of version commit hash please write down build command flags if there is anything special system windows mac os x catalina linux platform browser latest chrome stable channel latest firefox stable channel android ios | 0 |
29,394 | 23,976,544,787 | IssuesEvent | 2022-09-13 12:05:13 | localstack/localstack | https://api.github.com/repos/localstack/localstack | closed | ElastiCache and RDS instance want to use the same Port | type: bug status: resolved/fixed area: infrastructure status: response required status: confirmed | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
I am running a script to set up a local stack environment. When running the following commands there is an issue with Redis and MySQL fighting for the same port.
```
echo "Create an Mysql RDS Instance"
awslocal rds create-db-instance \
--db-instance-identifier devops-toolkit \
--db-instance-class db.t3.micro \
--engine mysql \
--master-user-password 12345678 \
--master-username admin \
--allocated-storage 5
sleep 5
echo "Create a Redis Cache Cluster"
awslocal elasticache create-cache-cluster --cache-cluster-id cluster-1
```
This can be seen in the logs
```
2022-09-01T07:49:51.054 INFO --- [ Thread-119] l.s.rds.engine_mysql : Starting MySQL RDS server on port 4510 (backend port 4510) - database "test", user "admin"
2022-09-01T07:49:53.245 INFO --- [ asgi_gw_0] l.s.elasticache.provider : Waiting for Redis server on tcp://localhost:4510 to start
2022-09-01T07:49:53.259 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:C 01 Sep 2022 07:49:53.258 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2022-09-01T07:49:53.259 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:C 01 Sep 2022 07:49:53.258 # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=1181, just started
2022-09-01T07:49:53.259 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:C 01 Sep 2022 07:49:53.258 # Configuration loaded
2022-09-01T07:49:53.265 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:M 01 Sep 2022 07:49:53.265 * Running mode=standalone, port=4510.
2022-09-01T07:49:53.265 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:M 01 Sep 2022 07:49:53.265 # Server initialized
2022-09-01T07:49:53.266 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:M 01 Sep 2022 07:49:53.265 # WARNING you have Transparent Huge Pages (THP) support en
```
And then results in mysql errors
```
ERROR: 'cat /tmp/tmpfbw8o1x_ | mysql --socket /tmp/mysql-states/09a73ec8/mysqld.sock': exit code 1; output: b"ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql-states/09a73ec8/mysqld.sock' (2)\n"
```
Any ideas, thanks in advance ✌️
### Expected Behavior
The two services should be run on different ports, is the the possibility to preconfigure the port on which each service is run?
### How are you starting LocalStack?
With the `localstack` script
### Steps To Reproduce
Run this simple script
```
localstack start -d
echo "wait for local stack to start"
sleep 10
echo "Now trying to configure local stack"
echo "Create an Mysql RDS Instance"
awslocal rds create-db-instance \
--db-instance-identifier devops-toolkit \
--db-instance-class db.t3.micro \
--engine mysql \
--master-user-password 12345678 \
--master-username admin \
--allocated-storage 5
sleep 5
echo "Create a Redis Cache Cluster"
awslocal elasticache create-cache-cluster --cache-cluster-id cluster-1
```
### Environment
```markdown
- OS: MacOS 11
- LocalStack: latest
```
### Anything else?
_No response_ | 1.0 | ElastiCache and RDS instance want to use the same Port - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
I am running a script to set up a local stack environment. When running the following commands there is an issue with Redis and MySQL fighting for the same port.
```
echo "Create an Mysql RDS Instance"
awslocal rds create-db-instance \
--db-instance-identifier devops-toolkit \
--db-instance-class db.t3.micro \
--engine mysql \
--master-user-password 12345678 \
--master-username admin \
--allocated-storage 5
sleep 5
echo "Create a Redis Cache Cluster"
awslocal elasticache create-cache-cluster --cache-cluster-id cluster-1
```
This can be seen in the logs
```
2022-09-01T07:49:51.054 INFO --- [ Thread-119] l.s.rds.engine_mysql : Starting MySQL RDS server on port 4510 (backend port 4510) - database "test", user "admin"
2022-09-01T07:49:53.245 INFO --- [ asgi_gw_0] l.s.elasticache.provider : Waiting for Redis server on tcp://localhost:4510 to start
2022-09-01T07:49:53.259 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:C 01 Sep 2022 07:49:53.258 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2022-09-01T07:49:53.259 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:C 01 Sep 2022 07:49:53.258 # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=1181, just started
2022-09-01T07:49:53.259 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:C 01 Sep 2022 07:49:53.258 # Configuration loaded
2022-09-01T07:49:53.265 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:M 01 Sep 2022 07:49:53.265 * Running mode=standalone, port=4510.
2022-09-01T07:49:53.265 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:M 01 Sep 2022 07:49:53.265 # Server initialized
2022-09-01T07:49:53.266 INFO --- [ Thread-123] l.s.elasticache.redis : 1181:M 01 Sep 2022 07:49:53.265 # WARNING you have Transparent Huge Pages (THP) support en
```
And then results in mysql errors
```
ERROR: 'cat /tmp/tmpfbw8o1x_ | mysql --socket /tmp/mysql-states/09a73ec8/mysqld.sock': exit code 1; output: b"ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql-states/09a73ec8/mysqld.sock' (2)\n"
```
Any ideas, thanks in advance ✌️
### Expected Behavior
The two services should be run on different ports, is the the possibility to preconfigure the port on which each service is run?
### How are you starting LocalStack?
With the `localstack` script
### Steps To Reproduce
Run this simple script
```
localstack start -d
echo "wait for local stack to start"
sleep 10
echo "Now trying to configure local stack"
echo "Create an Mysql RDS Instance"
awslocal rds create-db-instance \
--db-instance-identifier devops-toolkit \
--db-instance-class db.t3.micro \
--engine mysql \
--master-user-password 12345678 \
--master-username admin \
--allocated-storage 5
sleep 5
echo "Create a Redis Cache Cluster"
awslocal elasticache create-cache-cluster --cache-cluster-id cluster-1
```
### Environment
```markdown
- OS: MacOS 11
- LocalStack: latest
```
### Anything else?
_No response_ | non_test | elasticache and rds instance want to use the same port is there an existing issue for this i have searched the existing issues current behavior i am running a script to set up a local stack environment when running the following commands there is an issue with redis and mysql fighting for the same port echo create an mysql rds instance awslocal rds create db instance db instance identifier devops toolkit db instance class db micro engine mysql master user password master username admin allocated storage sleep echo create a redis cache cluster awslocal elasticache create cache cluster cache cluster id cluster this can be seen in the logs info l s rds engine mysql starting mysql rds server on port backend port database test user admin info l s elasticache provider waiting for redis server on tcp localhost to start info l s elasticache redis c sep redis is starting info l s elasticache redis c sep redis version bits commit modified pid just started info l s elasticache redis c sep configuration loaded info l s elasticache redis m sep running mode standalone port info l s elasticache redis m sep server initialized info l s elasticache redis m sep warning you have transparent huge pages thp support en and then results in mysql errors error cat tmp mysql socket tmp mysql states mysqld sock exit code output b error can t connect to local mysql server through socket tmp mysql states mysqld sock n any ideas thanks in advance ✌️ expected behavior the two services should be run on different ports is the the possibility to preconfigure the port on which each service is run how are you starting localstack with the localstack script steps to reproduce run this simple script localstack start d echo wait for local stack to start sleep echo now trying to configure local stack echo create an mysql rds instance awslocal rds create db instance db instance identifier devops toolkit db instance class db micro engine mysql master user password master username admin allocated storage sleep echo create a redis cache cluster awslocal elasticache create cache cluster cache cluster id cluster environment markdown os macos localstack latest anything else no response | 0 |
9,542 | 13,539,217,175 | IssuesEvent | 2020-09-16 13:11:48 | pianeu/USZ_multiThreshold_validation | https://api.github.com/repos/pianeu/USZ_multiThreshold_validation | closed | Read in auditory threshold data from USZ multiThreshold test battery into R and convert it into one dataframe | User requirement | **Description:**
As a user I can read in auditory threshold data from USZ multiThreshold test battery into R and convert it into one dataframe.
**Linkage to related documents:**
Functional specification: #2
Test: #3
| 1.0 | Read in auditory threshold data from USZ multiThreshold test battery into R and convert it into one dataframe - **Description:**
As a user I can read in auditory threshold data from USZ multiThreshold test battery into R and convert it into one dataframe.
**Linkage to related documents:**
Functional specification: #2
Test: #3
| non_test | read in auditory threshold data from usz multithreshold test battery into r and convert it into one dataframe description as a user i can read in auditory threshold data from usz multithreshold test battery into r and convert it into one dataframe linkage to related documents functional specification test | 0 |
596,383 | 18,104,208,972 | IssuesEvent | 2021-09-22 17:18:20 | NOAA-GSL/VxLegacyIngest | https://api.github.com/repos/NOAA-GSL/VxLegacyIngest | closed | Add LAMP data to ceiling/visibility vx | Type: Task Priority: High | ---
Author Name: **molly.b.smith** (molly.b.smith)
Original Redmine Issue: 66158, https://vlab.ncep.noaa.gov/redmine/issues/66158
Original Date: 2019-07-17
Original Assignee: molly.b.smith
---
According to Bob, the data files are located at /public/data/grids/lamp/2p5km/grib2/
| 1.0 | Add LAMP data to ceiling/visibility vx - ---
Author Name: **molly.b.smith** (molly.b.smith)
Original Redmine Issue: 66158, https://vlab.ncep.noaa.gov/redmine/issues/66158
Original Date: 2019-07-17
Original Assignee: molly.b.smith
---
According to Bob, the data files are located at /public/data/grids/lamp/2p5km/grib2/
| non_test | add lamp data to ceiling visibility vx author name molly b smith molly b smith original redmine issue original date original assignee molly b smith according to bob the data files are located at public data grids lamp | 0 |
320,686 | 27,450,990,276 | IssuesEvent | 2023-03-02 17:21:20 | ComputationalRadiationPhysics/picongpu | https://api.github.com/repos/ComputationalRadiationPhysics/picongpu | closed | cuSTL shared memory can be invalid | bug component: PMacc affects latest release | In some cases `PMacc::container::CT::SharedBuffer` can be invalid:
- if it is used in another method in the same stack level where it is created
- if the object `SharedBuffer` or the `Cursor` of it is stored as member of an object
At the moment it is not clear if the restrictions above are enough as workaround.
| 1.0 | cuSTL shared memory can be invalid - In some cases `PMacc::container::CT::SharedBuffer` can be invalid:
- if it is used in another method in the same stack level where it is created
- if the object `SharedBuffer` or the `Cursor` of it is stored as member of an object
At the moment it is not clear if the restrictions above are enough as workaround.
| test | custl shared memory can be invalid in some cases pmacc container ct sharedbuffer can be invalid if it is used in another method in the same stack level where it is created if the object sharedbuffer or the cursor of it is stored as member of an object at the moment it is not clear if the restrictions above are enough as workaround | 1 |
207,418 | 15,815,668,723 | IssuesEvent | 2021-04-05 11:46:24 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | [maps] android_google_map_test shows `No tests ran.` | P3 a: tests found in release: 1.27 has reproducible steps p: first party p: maps plugin | [android_google_map_test](packages/google_maps_flutter/google_maps_flutter/test/android_google_map_test.dart) does not run because of [`@TestOn('android')`](https://github.com/flutter/plugins/blob/f47dbdf372feefea9268f3c03d9b2b4cd3ae2626/packages/google_maps_flutter/google_maps_flutter/test/android_google_map_test.dart#L5) annotation.
On removing the annotation the test runs and fails, because of the assertion [`Platform.isAndroid`](https://github.com/flutter/plugins/blob/f47dbdf372feefea9268f3c03d9b2b4cd3ae2626/packages/google_maps_flutter/google_maps_flutter/lib/src/google_map.dart#L469) which is false as the test is not integration test and not running on android.
I think the test is unnecessary as there is already integration test [`testLiteModeEnabled`](https://github.com/flutter/plugins/blob/f47dbdf372feefea9268f3c03d9b2b4cd3ae2626/packages/google_maps_flutter/google_maps_flutter/example/integration_test/google_maps_test.dart#L268).
## Steps to Reproduce
1. `flutter test .\packages\google_maps_flutter\google_maps_flutter\test\android_google_map_test.dart` | 1.0 | [maps] android_google_map_test shows `No tests ran.` - [android_google_map_test](packages/google_maps_flutter/google_maps_flutter/test/android_google_map_test.dart) does not run because of [`@TestOn('android')`](https://github.com/flutter/plugins/blob/f47dbdf372feefea9268f3c03d9b2b4cd3ae2626/packages/google_maps_flutter/google_maps_flutter/test/android_google_map_test.dart#L5) annotation.
On removing the annotation the test runs and fails, because of the assertion [`Platform.isAndroid`](https://github.com/flutter/plugins/blob/f47dbdf372feefea9268f3c03d9b2b4cd3ae2626/packages/google_maps_flutter/google_maps_flutter/lib/src/google_map.dart#L469) which is false as the test is not integration test and not running on android.
I think the test is unnecessary as there is already integration test [`testLiteModeEnabled`](https://github.com/flutter/plugins/blob/f47dbdf372feefea9268f3c03d9b2b4cd3ae2626/packages/google_maps_flutter/google_maps_flutter/example/integration_test/google_maps_test.dart#L268).
## Steps to Reproduce
1. `flutter test .\packages\google_maps_flutter\google_maps_flutter\test\android_google_map_test.dart` | test | android google map test shows no tests ran packages google maps flutter google maps flutter test android google map test dart does not run because of annotation on removing the annotation the test runs and fails because of the assertion which is false as the test is not integration test and not running on android i think the test is unnecessary as there is already integration test steps to reproduce flutter test packages google maps flutter google maps flutter test android google map test dart | 1 |
94,385 | 19,538,331,101 | IssuesEvent | 2021-12-31 13:13:13 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | closed | DOC: whatsnew format for minor enhancements/bug-fixes | Docs Code Style Clean | Admittedly this is extremely minor, but it's something that has always irked me. Currently for minor (single-line, not a section) enhancements and bug-fixes, we have the format:
> This is sentence one (GH28527)
which on its own is perfectly fine. However when a line has multiple sentences:
> This is sentence one. This is sentence two (GH28527)
the lack of a period at the end looks off to me. I'd prefer if we did full sentences for each line followed by the GH link at the end, this way a multi-sentence doesn't look so odd.
> This is sentence one. (GH28527)
> This is sentence one. This is sentence two. (GH28527)
Another option is to limit one-line notes to being a single sentence (which I'm opposed to), and of course we could just stay with it as is. If we are to make any changes, I'd do it for the version minor/major version after 1.3.0.
cc @simonjayhawkins | 1.0 | DOC: whatsnew format for minor enhancements/bug-fixes - Admittedly this is extremely minor, but it's something that has always irked me. Currently for minor (single-line, not a section) enhancements and bug-fixes, we have the format:
> This is sentence one (GH28527)
which on its own is perfectly fine. However when a line has multiple sentences:
> This is sentence one. This is sentence two (GH28527)
the lack of a period at the end looks off to me. I'd prefer if we did full sentences for each line followed by the GH link at the end, this way a multi-sentence doesn't look so odd.
> This is sentence one. (GH28527)
> This is sentence one. This is sentence two. (GH28527)
Another option is to limit one-line notes to being a single sentence (which I'm opposed to), and of course we could just stay with it as is. If we are to make any changes, I'd do it for the version minor/major version after 1.3.0.
cc @simonjayhawkins | non_test | doc whatsnew format for minor enhancements bug fixes admittedly this is extremely minor but it s something that has always irked me currently for minor single line not a section enhancements and bug fixes we have the format this is sentence one which on its own is perfectly fine however when a line has multiple sentences this is sentence one this is sentence two the lack of a period at the end looks off to me i d prefer if we did full sentences for each line followed by the gh link at the end this way a multi sentence doesn t look so odd this is sentence one this is sentence one this is sentence two another option is to limit one line notes to being a single sentence which i m opposed to and of course we could just stay with it as is if we are to make any changes i d do it for the version minor major version after cc simonjayhawkins | 0 |
131,973 | 10,726,027,119 | IssuesEvent | 2019-10-28 08:25:28 | ballerina-platform/ballerina-lang | https://api.github.com/repos/ballerina-platform/ballerina-lang | closed | BBEs are missing for lang lib operations | Area/Language BetaTesting Type/Docs | **Description:**
BBEs are missing for most of the newly introduced lang lib operations.
Example: arrays | 1.0 | BBEs are missing for lang lib operations - **Description:**
BBEs are missing for most of the newly introduced lang lib operations.
Example: arrays | test | bbes are missing for lang lib operations description bbes are missing for most of the newly introduced lang lib operations example arrays | 1 |
255,673 | 21,944,045,081 | IssuesEvent | 2022-05-23 21:29:19 | catalyst-cooperative/pudl | https://api.github.com/repos/catalyst-cooperative/pudl | opened | Auto-merge bot PRs that pass CI | testing | We now have @pre-commit-ci and @dependabot making PRs to update the versions of various packages we depend on. Basically we just merge the PRs manually if all the checks pass without looking too hard now and... that's kind of a waste of time, especially now that we're running CI in a growing number of repos.
* [x] Separate tests, notifications, and dependabot PR merge into separate dependent jobs in the `tox-pytest` workflow.
* [ ] Make sure that dependabot merges work as expected and has the permissions required.
* [ ] Create a separate `pre-commit-ci-auto-merge` workflow that runs on the completion of PR CI (run by us, rather than the PR author) and automatically merges a passing PR that was created by the @pre-commit-ci bot.
* [ ] Integrate this automation into all our repositories that have CI, dependabot, and pre-commit.ci set up. | 1.0 | Auto-merge bot PRs that pass CI - We now have @pre-commit-ci and @dependabot making PRs to update the versions of various packages we depend on. Basically we just merge the PRs manually if all the checks pass without looking too hard now and... that's kind of a waste of time, especially now that we're running CI in a growing number of repos.
* [x] Separate tests, notifications, and dependabot PR merge into separate dependent jobs in the `tox-pytest` workflow.
* [ ] Make sure that dependabot merges work as expected and has the permissions required.
* [ ] Create a separate `pre-commit-ci-auto-merge` workflow that runs on the completion of PR CI (run by us, rather than the PR author) and automatically merges a passing PR that was created by the @pre-commit-ci bot.
* [ ] Integrate this automation into all our repositories that have CI, dependabot, and pre-commit.ci set up. | test | auto merge bot prs that pass ci we now have pre commit ci and dependabot making prs to update the versions of various packages we depend on basically we just merge the prs manually if all the checks pass without looking too hard now and that s kind of a waste of time especially now that we re running ci in a growing number of repos separate tests notifications and dependabot pr merge into separate dependent jobs in the tox pytest workflow make sure that dependabot merges work as expected and has the permissions required create a separate pre commit ci auto merge workflow that runs on the completion of pr ci run by us rather than the pr author and automatically merges a passing pr that was created by the pre commit ci bot integrate this automation into all our repositories that have ci dependabot and pre commit ci set up | 1 |
235,235 | 19,318,024,122 | IssuesEvent | 2021-12-14 00:07:22 | Azure/azure-sdk-for-go | https://api.github.com/repos/Azure/azure-sdk-for-go | opened | Add offline managed identity tests | Azure.Identity test-enhancement | i.e. validate the client creates the correct request for each platform:
- [ ] App Service (2017-09-01)
- [ ] Arc
- [ ] Cloud Shell
- [ ] IMDS
- [x] Service Fabric | 1.0 | Add offline managed identity tests - i.e. validate the client creates the correct request for each platform:
- [ ] App Service (2017-09-01)
- [ ] Arc
- [ ] Cloud Shell
- [ ] IMDS
- [x] Service Fabric | test | add offline managed identity tests i e validate the client creates the correct request for each platform app service arc cloud shell imds service fabric | 1 |
504,896 | 14,623,295,364 | IssuesEvent | 2020-12-23 02:56:00 | EUCweb/BIS-F | https://api.github.com/repos/EUCweb/BIS-F | reopened | EventLog is moved, but Path is never changed | Priority: Low Status: Completed Type: Bug | issues with Event log redirections on some Projects, i beleive the commonality is IF BIS-F is run to move the event logs to say "D: but then that needs to be changed to "E" - I am not sure why, but it only changes some event logs and leaves the rest broken
Fix it with the following script
https://gallery.technet.microsoft.com/scriptcenter/Change-the-path-of-the-f86d2427 | 1.0 | EventLog is moved, but Path is never changed - issues with Event log redirections on some Projects, i beleive the commonality is IF BIS-F is run to move the event logs to say "D: but then that needs to be changed to "E" - I am not sure why, but it only changes some event logs and leaves the rest broken
Fix it with the following script
https://gallery.technet.microsoft.com/scriptcenter/Change-the-path-of-the-f86d2427 | non_test | eventlog is moved but path is never changed issues with event log redirections on some projects i beleive the commonality is if bis f is run to move the event logs to say d but then that needs to be changed to e i am not sure why but it only changes some event logs and leaves the rest broken fix it with the following script | 0 |
158,162 | 12,404,847,745 | IssuesEvent | 2020-05-21 16:13:37 | openPMD/openPMD-api | https://api.github.com/repos/openPMD/openPMD-api | opened | Example: READ_WRITE with Pipelining | tests | Write an example that tests if a
- known maximum size but
- written with open/close of a series in between
into the same variable works (of if we have to keep the handles open).
This is a special (easier) case of #658, such as writing slices of fields in a pipelining sweep or boosted frame - lab frame back-transformation. | 1.0 | Example: READ_WRITE with Pipelining - Write an example that tests if a
- known maximum size but
- written with open/close of a series in between
into the same variable works (of if we have to keep the handles open).
This is a special (easier) case of #658, such as writing slices of fields in a pipelining sweep or boosted frame - lab frame back-transformation. | test | example read write with pipelining write an example that tests if a known maximum size but written with open close of a series in between into the same variable works of if we have to keep the handles open this is a special easier case of such as writing slices of fields in a pipelining sweep or boosted frame lab frame back transformation | 1 |
100,726 | 8,752,752,245 | IssuesEvent | 2018-12-14 05:00:39 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | closed | Testing 14 : ApiV1IssuesJobIdIdGetQueryParamPagesizeDdos | Testing 14 | Project : Testing 14
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=YzFmNGM3MDAtMDFkZC00MjJkLWJjMTItNDgwYzhlMjU1Mjk5; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 14 Dec 2018 04:58:28 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/issues/job-id/FJzhgHKd?pageSize=1001&status=FJzhgHKd
Request :
Response :
{
"timestamp" : "2018-12-14T04:58:29.332+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/issues/job-id/FJzhgHKd"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | 1.0 | Testing 14 : ApiV1IssuesJobIdIdGetQueryParamPagesizeDdos - Project : Testing 14
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=YzFmNGM3MDAtMDFkZC00MjJkLWJjMTItNDgwYzhlMjU1Mjk5; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 14 Dec 2018 04:58:28 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/issues/job-id/FJzhgHKd?pageSize=1001&status=FJzhgHKd
Request :
Response :
{
"timestamp" : "2018-12-14T04:58:29.332+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/issues/job-id/FJzhgHKd"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | test | testing project testing job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api issues job id fjzhghkd logs assertion resolved to result assertion resolved to result fx bot | 1 |
59,842 | 14,663,266,371 | IssuesEvent | 2020-12-29 09:19:06 | tensorflow/tensorflow | https://api.github.com/repos/tensorflow/tensorflow | opened | Error when build TF 1.13.2 from the source | type:build/install | <em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em>
**System information**
- OS Platform and Distribution: Linux Ubuntu 16.04/18.04
- TensorFlow installed from source
- TensorFlow version: 1.13.2
- Python version: 2.7
- Installed using: docker
- Bazel version: 0.19.2
- GCC/Compiler version: 4.9
- CUDA/cuDNN version: 10.0, 7
- GPU model and memory: T4, 32GB
**Describe the problem**
I tried to install TF from the source following instructions here, https://github.com/tensorflow/docs/blob/r1.13/site/en/install/source.md#build-from-source.
However some error occurs: ERROR: /home/cluster/tensorflow/tensorflow/core/kernels/BUILD:593:1: C++ compilation of rule '//tensorflow/core/kernels:eigen_contraction_kernel' failed (Exit 1). Any suggestions?
| 1.0 | Error when build TF 1.13.2 from the source - <em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em>
**System information**
- OS Platform and Distribution: Linux Ubuntu 16.04/18.04
- TensorFlow installed from source
- TensorFlow version: 1.13.2
- Python version: 2.7
- Installed using: docker
- Bazel version: 0.19.2
- GCC/Compiler version: 4.9
- CUDA/cuDNN version: 10.0, 7
- GPU model and memory: T4, 32GB
**Describe the problem**
I tried to install TF from the source following instructions here, https://github.com/tensorflow/docs/blob/r1.13/site/en/install/source.md#build-from-source.
However some error occurs: ERROR: /home/cluster/tensorflow/tensorflow/core/kernels/BUILD:593:1: C++ compilation of rule '//tensorflow/core/kernels:eigen_contraction_kernel' failed (Exit 1). Any suggestions?
| non_test | error when build tf from the source please make sure that this is a build installation issue as per our we only address code doc bugs performance issues feature requests and build installation issues on github tag build template system information os platform and distribution linux ubuntu tensorflow installed from source tensorflow version python version installed using docker bazel version gcc compiler version cuda cudnn version gpu model and memory describe the problem i tried to install tf from the source following instructions here however some error occurs error home cluster tensorflow tensorflow core kernels build c compilation of rule tensorflow core kernels eigen contraction kernel failed exit any suggestions | 0 |
542,470 | 15,860,996,598 | IssuesEvent | 2021-04-08 09:48:14 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.academy.com - design is broken | browser-safari os-mac priority-normal | <!-- @browser: Safari 13.1 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/70019 -->
**URL**: https://www.academy.com/
**Browser / Version**: Safari 13.1
**Operating System**: Mac OS X 10.15.4
**Tested Another Browser**: Yes Safari
**Problem type**: Design is broken
**Description**: Items not fully visible
**Steps to Reproduce**:
Search bar opens while page is loading, once it loads search bar disappears.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.academy.com - design is broken - <!-- @browser: Safari 13.1 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/70019 -->
**URL**: https://www.academy.com/
**Browser / Version**: Safari 13.1
**Operating System**: Mac OS X 10.15.4
**Tested Another Browser**: Yes Safari
**Problem type**: Design is broken
**Description**: Items not fully visible
**Steps to Reproduce**:
Search bar opens while page is loading, once it loads search bar disappears.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | design is broken url browser version safari operating system mac os x tested another browser yes safari problem type design is broken description items not fully visible steps to reproduce search bar opens while page is loading once it loads search bar disappears browser configuration none from with ❤️ | 0 |
314,143 | 26,978,190,393 | IssuesEvent | 2023-02-09 11:05:30 | celestiaorg/orchestrator-relayer | https://api.github.com/repos/celestiaorg/orchestrator-relayer | closed | Add tests for EVM signing methods | good first issue testing evm | As discussed under https://github.com/celestiaorg/orchestrator-relayer/pull/38#pullrequestreview-1234035405, we should add unit tests for the EVM related code especially the signing methods.
Some tests could be copied from the [V1 implementation](https://github.com/celestiaorg/celestia-app/tree/qgb-integration/x/qgb/orchestrator/test). | 1.0 | Add tests for EVM signing methods - As discussed under https://github.com/celestiaorg/orchestrator-relayer/pull/38#pullrequestreview-1234035405, we should add unit tests for the EVM related code especially the signing methods.
Some tests could be copied from the [V1 implementation](https://github.com/celestiaorg/celestia-app/tree/qgb-integration/x/qgb/orchestrator/test). | test | add tests for evm signing methods as discussed under we should add unit tests for the evm related code especially the signing methods some tests could be copied from the | 1 |
29,019 | 4,466,995,204 | IssuesEvent | 2016-08-25 01:46:04 | Automattic/jetpack | https://api.github.com/repos/Automattic/jetpack | opened | Deploy Script + Travis: Keep travis.yml | General Unit Tests | When using the deploy to master-stable tool, the older Travis config is being used.
This is due to https://github.com/Automattic/jetpack/blob/master/tools/deploy-to-master-stable-branch.sh#L56 which is excluding what is excluded from SVN, which includes the travis file.
We probably have two solutions:
1. Manually cherry-pick Travis updates to master-stable whenever we make them
2. Edit the build script to intentionally include them back.
I'm doing 1 now to catch up while we decide if we need 2. | 1.0 | Deploy Script + Travis: Keep travis.yml - When using the deploy to master-stable tool, the older Travis config is being used.
This is due to https://github.com/Automattic/jetpack/blob/master/tools/deploy-to-master-stable-branch.sh#L56 which is excluding what is excluded from SVN, which includes the travis file.
We probably have two solutions:
1. Manually cherry-pick Travis updates to master-stable whenever we make them
2. Edit the build script to intentionally include them back.
I'm doing 1 now to catch up while we decide if we need 2. | test | deploy script travis keep travis yml when using the deploy to master stable tool the older travis config is being used this is due to which is excluding what is excluded from svn which includes the travis file we probably have two solutions manually cherry pick travis updates to master stable whenever we make them edit the build script to intentionally include them back i m doing now to catch up while we decide if we need | 1 |
527,035 | 15,307,489,495 | IssuesEvent | 2021-02-24 20:58:52 | mozilla/jetstream | https://api.github.com/repos/mozilla/jetstream | closed | Associate help text and friendly names with metrics | P1 - High Priority enhancement | Breakdown:
- [x] Land support in mozanalysis (mozilla/mozanalysis#99)
- [x] Land support in jetstream (#246)
- [ ] Document
- [x] Come up with a plan for exposing these to Experimenter (#335)
- [x] Implement plan! (#296)
Mozanalysis metrics don't have a concept of a human-friendly name or a documentation string. Lunascope will need something like that!
There's an architectural decision to make about whether to push that responsibility down into mozanalysis or to create a new Diagon metric object that's a superset of the mozanalysis metric.
┆Issue is synchronized with this [Jira Task](https://jira.mozilla.com/browse/CIRRUS-28)
┆Issue Number: CIRRUS-28
| 1.0 | Associate help text and friendly names with metrics - Breakdown:
- [x] Land support in mozanalysis (mozilla/mozanalysis#99)
- [x] Land support in jetstream (#246)
- [ ] Document
- [x] Come up with a plan for exposing these to Experimenter (#335)
- [x] Implement plan! (#296)
Mozanalysis metrics don't have a concept of a human-friendly name or a documentation string. Lunascope will need something like that!
There's an architectural decision to make about whether to push that responsibility down into mozanalysis or to create a new Diagon metric object that's a superset of the mozanalysis metric.
┆Issue is synchronized with this [Jira Task](https://jira.mozilla.com/browse/CIRRUS-28)
┆Issue Number: CIRRUS-28
| non_test | associate help text and friendly names with metrics breakdown land support in mozanalysis mozilla mozanalysis land support in jetstream document come up with a plan for exposing these to experimenter implement plan mozanalysis metrics don t have a concept of a human friendly name or a documentation string lunascope will need something like that there s an architectural decision to make about whether to push that responsibility down into mozanalysis or to create a new diagon metric object that s a superset of the mozanalysis metric ┆issue is synchronized with this ┆issue number cirrus | 0 |
59,278 | 24,709,119,692 | IssuesEvent | 2022-10-19 22:04:14 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | [BUG] Microsoft.Azure.ServiceBus is restricted to namespaces with a fully quantified domain. | Service Bus Service Attention Client customer-reported feature-request issue-addressed | **Describe the bug**
This is part way between a bug and a feature, so feel free to choose which.
Currently, the Microsoft.Azure.ServiceBus client mandates that the namespace endpoint includes a `.` in it. Therefore ensuring that only "real" domains can be used. This precludes using something that is hosted on `localhost`. This seems like something that shouldn't be there as locally contacting servicebus should be ok.
**Expected behavior**
A servicebus namespace can be specified without a `.` e.g. `localhost`
**Actual behavior (include Exception or Stack Trace)**
An exception is thrown on startup.
**To Reproduce**
Have a namespace that is `localhost`, start the client and you'll see it fail.
**Environment:**
All environment, there's nothing specific here.
**Notes:**
The line of code that does this is:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Microsoft.Azure.ServiceBus/src/ServiceBusConnectionStringBuilder.cs#L174
This restriction is not in `Azure.Messaging.ServiceBus`
| 2.0 | [BUG] Microsoft.Azure.ServiceBus is restricted to namespaces with a fully quantified domain. - **Describe the bug**
This is part way between a bug and a feature, so feel free to choose which.
Currently, the Microsoft.Azure.ServiceBus client mandates that the namespace endpoint includes a `.` in it. Therefore ensuring that only "real" domains can be used. This precludes using something that is hosted on `localhost`. This seems like something that shouldn't be there as locally contacting servicebus should be ok.
**Expected behavior**
A servicebus namespace can be specified without a `.` e.g. `localhost`
**Actual behavior (include Exception or Stack Trace)**
An exception is thrown on startup.
**To Reproduce**
Have a namespace that is `localhost`, start the client and you'll see it fail.
**Environment:**
All environment, there's nothing specific here.
**Notes:**
The line of code that does this is:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Microsoft.Azure.ServiceBus/src/ServiceBusConnectionStringBuilder.cs#L174
This restriction is not in `Azure.Messaging.ServiceBus`
| non_test | microsoft azure servicebus is restricted to namespaces with a fully quantified domain describe the bug this is part way between a bug and a feature so feel free to choose which currently the microsoft azure servicebus client mandates that the namespace endpoint includes a in it therefore ensuring that only real domains can be used this precludes using something that is hosted on localhost this seems like something that shouldn t be there as locally contacting servicebus should be ok expected behavior a servicebus namespace can be specified without a e g localhost actual behavior include exception or stack trace an exception is thrown on startup to reproduce have a namespace that is localhost start the client and you ll see it fail environment all environment there s nothing specific here notes the line of code that does this is this restriction is not in azure messaging servicebus | 0 |
213,240 | 16,507,192,415 | IssuesEvent | 2021-05-25 20:54:45 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | sql/tests: TestRandomSyntaxSchemaChangeColumn failed | C-test-failure branch-master | [sql/tests.TestRandomSyntaxSchemaChangeColumn failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2862755&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=2862755&tab=artifacts#/) on [master @ 9a335c3b2eaac8a5b36ed4e4299be0bbb3d9f548](https://github.com/cockroachdb/cockroach/commits/9a335c3b2eaac8a5b36ed4e4299be0bbb3d9f548):
```
[14:52:40]
[post issues]
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553553 [select, 2 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/kv/kvserver/protectedts/ptcache.(*Cache).periodicallyRefreshProtectedtsCache(0xc01a8acbb0, 0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/kv/kvserver/protectedts/ptcache/cache.go:160 +0x25b
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc017a32600)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553583 [select, 1 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/sql/catalog/lease.(*Manager).PeriodicallyRefreshSomeLeases.func1(0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/sql/catalog/lease/lease.go:1808 +0x285
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc017a32e50)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553324 [select, 5 minutes]:
[14:52:40]
[post issues] google.golang.org/grpc.(*ccBalancerWrapper).watcher(0xc008ed7ac0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:69 +0xc8
[14:52:40]
[post issues] created by google.golang.org/grpc.newCCBalancerWrapper
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:60 +0x172
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553286 [select, 5 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/sql.(*DistSQLPlanner).initRunners.func1(0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/sql/distsql_running.go:105 +0x13d
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc006286c10)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553316 [chan receive, 5 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/server.(*Server).startServeUI.func1(0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:2022 +0x53
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc004556160)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] rsg_test.go:186: SELECT 1 executed successfully: probably a slow statement
[14:52:40]
[post issues] rsg_test.go:755: Crash detected:
[14:52:40]
[post issues] ALTER TABLE ident.ident ADD IF NOT EXISTS SURVIVE INTERVAL DAY TO MINUTE [ ]
[14:52:40]
[post issues]
[14:52:40]
[post issues] Stack trace:
[14:52:40]
[post issues] timeout: "ALTER TABLE ident.ident ADD IF NOT EXISTS SURVIVE INTERVAL DAY TO MINUTE [ ]". currently executing: map[ALTER TABLE ident.ident ADD IF NOT EXISTS SURVIVE INTERVAL DAY TO MINUTE [ ]:1]
[14:52:40]
[post issues] rsg_test.go:764: 6923 executions, 1292 successful
[14:52:40]
[post issues] rsg_test.go:401: -- test log scope end --
[14:52:40]
[post issues] test logs left over in: /go/src/github.com/cockroachdb/cockroach/artifacts/logTestRandomSyntaxSchemaChangeColumn880718491
[14:52:40]
[post issues] --- FAIL: TestRandomSyntaxSchemaChangeColumn (357.99s)
[14:52:40]
[post issues] ```
[14:52:40]
[post issues] <details><summary>Reproduce</summary>
[14:52:40]
[post issues] <p>
[14:52:40]
[post issues] <p>To reproduce, try:
[14:52:40]
[post issues] ```bash
[14:52:40]
[post issues] make stressrace TESTS=TestRandomSyntaxSchemaChangeColumn PKG=./pkg/sql/tests TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1
[14:52:40]
[post issues] ```
[14:52:40]
[post issues] </p>
[14:52:40]
[post issues] </p>
[14:52:40]
[post issues] </details>
[14:52:40]
[post issues] <details><summary>Same failure on other branches</summary>
[14:52:40]
[post issues] <p>
[14:52:40]
[post issues] - #63202 sql/tests: TestRandomSyntaxSchemaChangeColumn failed [C-test-failure O-robot branch-release-20.1]</p>
[14:52:40]
[post issues] </details>
[14:52:40]
[post issues] [See this test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRandomSyntaxSchemaChangeColumn.*&sort=title+created&display=lastcommented+project)
[14:52:40]
[post issues] <sub>[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub>
[14:52:40]
[post issues] ", Labels:["O-robot" "C-test-failure" "branch-master"], Assignee:"mjibson"}: POST https://api.github.com/repos/cockroachdb/cockroach/issues: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid Message:}]
[14:52:40]
[Run Random Syntax tests] artifacts (7s)
[14:52:47]
[Run Random Syntax tests] exit status
[14:52:47]
[Run Random Syntax tests] Process exited with code 2
[14:52:47]
[Step 2/2] Process exited with code 2 (Step: Command Line)
[14:52:47]
[Step 2/2] Step Command Line failed
[14:52:47]
Publishing internal artifacts (4s)
[14:52:47]
Publishing artifacts (5s)
[14:52:53]
Build finished
```
cc @ajwerner | 1.0 | sql/tests: TestRandomSyntaxSchemaChangeColumn failed - [sql/tests.TestRandomSyntaxSchemaChangeColumn failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2862755&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=2862755&tab=artifacts#/) on [master @ 9a335c3b2eaac8a5b36ed4e4299be0bbb3d9f548](https://github.com/cockroachdb/cockroach/commits/9a335c3b2eaac8a5b36ed4e4299be0bbb3d9f548):
```
[14:52:40]
[post issues]
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553553 [select, 2 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/kv/kvserver/protectedts/ptcache.(*Cache).periodicallyRefreshProtectedtsCache(0xc01a8acbb0, 0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/kv/kvserver/protectedts/ptcache/cache.go:160 +0x25b
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc017a32600)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553583 [select, 1 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/sql/catalog/lease.(*Manager).PeriodicallyRefreshSomeLeases.func1(0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/sql/catalog/lease/lease.go:1808 +0x285
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc017a32e50)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553324 [select, 5 minutes]:
[14:52:40]
[post issues] google.golang.org/grpc.(*ccBalancerWrapper).watcher(0xc008ed7ac0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:69 +0xc8
[14:52:40]
[post issues] created by google.golang.org/grpc.newCCBalancerWrapper
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:60 +0x172
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553286 [select, 5 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/sql.(*DistSQLPlanner).initRunners.func1(0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/sql/distsql_running.go:105 +0x13d
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc006286c10)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] goroutine 8553316 [chan receive, 5 minutes]:
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/server.(*Server).startServeUI.func1(0x5bcca60, 0xc00b9329f0)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/server/server.go:2022 +0x53
[14:52:40]
[post issues] github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask.func1(0xc007dda200, 0x5bcca60, 0xc00b9329f0, 0x0, 0xc004556160)
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:351 +0xb9
[14:52:40]
[post issues] created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTask
[14:52:40]
[post issues] /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:346 +0xfc
[14:52:40]
[post issues]
[14:52:40]
[post issues] rsg_test.go:186: SELECT 1 executed successfully: probably a slow statement
[14:52:40]
[post issues] rsg_test.go:755: Crash detected:
[14:52:40]
[post issues] ALTER TABLE ident.ident ADD IF NOT EXISTS SURVIVE INTERVAL DAY TO MINUTE [ ]
[14:52:40]
[post issues]
[14:52:40]
[post issues] Stack trace:
[14:52:40]
[post issues] timeout: "ALTER TABLE ident.ident ADD IF NOT EXISTS SURVIVE INTERVAL DAY TO MINUTE [ ]". currently executing: map[ALTER TABLE ident.ident ADD IF NOT EXISTS SURVIVE INTERVAL DAY TO MINUTE [ ]:1]
[14:52:40]
[post issues] rsg_test.go:764: 6923 executions, 1292 successful
[14:52:40]
[post issues] rsg_test.go:401: -- test log scope end --
[14:52:40]
[post issues] test logs left over in: /go/src/github.com/cockroachdb/cockroach/artifacts/logTestRandomSyntaxSchemaChangeColumn880718491
[14:52:40]
[post issues] --- FAIL: TestRandomSyntaxSchemaChangeColumn (357.99s)
[14:52:40]
[post issues] ```
[14:52:40]
[post issues] <details><summary>Reproduce</summary>
[14:52:40]
[post issues] <p>
[14:52:40]
[post issues] <p>To reproduce, try:
[14:52:40]
[post issues] ```bash
[14:52:40]
[post issues] make stressrace TESTS=TestRandomSyntaxSchemaChangeColumn PKG=./pkg/sql/tests TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1
[14:52:40]
[post issues] ```
[14:52:40]
[post issues] </p>
[14:52:40]
[post issues] </p>
[14:52:40]
[post issues] </details>
[14:52:40]
[post issues] <details><summary>Same failure on other branches</summary>
[14:52:40]
[post issues] <p>
[14:52:40]
[post issues] - #63202 sql/tests: TestRandomSyntaxSchemaChangeColumn failed [C-test-failure O-robot branch-release-20.1]</p>
[14:52:40]
[post issues] </details>
[14:52:40]
[post issues] [See this test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRandomSyntaxSchemaChangeColumn.*&sort=title+created&display=lastcommented+project)
[14:52:40]
[post issues] <sub>[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub>
[14:52:40]
[post issues] ", Labels:["O-robot" "C-test-failure" "branch-master"], Assignee:"mjibson"}: POST https://api.github.com/repos/cockroachdb/cockroach/issues: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid Message:}]
[14:52:40]
[Run Random Syntax tests] artifacts (7s)
[14:52:47]
[Run Random Syntax tests] exit status
[14:52:47]
[Run Random Syntax tests] Process exited with code 2
[14:52:47]
[Step 2/2] Process exited with code 2 (Step: Command Line)
[14:52:47]
[Step 2/2] Step Command Line failed
[14:52:47]
Publishing internal artifacts (4s)
[14:52:47]
Publishing artifacts (5s)
[14:52:53]
Build finished
```
cc @ajwerner | test | sql tests testrandomsyntaxschemachangecolumn failed with on go src github com cockroachdb cockroach pkg util stop stopper go goroutine github com cockroachdb cockroach pkg kv kvserver protectedts ptcache cache periodicallyrefreshprotectedtscache go src github com cockroachdb cockroach pkg kv kvserver protectedts ptcache cache go github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go created by github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go goroutine github com cockroachdb cockroach pkg sql catalog lease manager periodicallyrefreshsomeleases go src github com cockroachdb cockroach pkg sql catalog lease lease go github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go created by github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go goroutine google golang org grpc ccbalancerwrapper watcher go src github com cockroachdb cockroach vendor google golang org grpc balancer conn wrappers go created by google golang org grpc newccbalancerwrapper go src github com cockroachdb cockroach vendor google golang org grpc balancer conn wrappers go goroutine github com cockroachdb cockroach pkg sql distsqlplanner initrunners go src github com cockroachdb cockroach pkg sql distsql running go github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go created by github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go goroutine github com cockroachdb cockroach pkg server server startserveui go src github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go created by github com cockroachdb cockroach pkg util stop stopper runasynctask go src github com cockroachdb cockroach pkg util stop stopper go rsg test go select executed successfully probably a slow statement rsg test go crash detected alter table ident ident add if not exists survive interval day to minute stack trace timeout alter table ident ident add if not exists survive interval day to minute currently executing map rsg test go executions successful rsg test go test log scope end test logs left over in go src github com cockroachdb cockroach artifacts fail testrandomsyntaxschemachangecolumn reproduce to reproduce try bash make stressrace tests testrandomsyntaxschemachangecolumn pkg pkg sql tests testtimeout stressflags timeout same failure on other branches sql tests testrandomsyntaxschemachangecolumn failed labels assignee mjibson post validation failed artifacts exit status process exited with code process exited with code step command line step command line failed publishing internal artifacts publishing artifacts build finished cc ajwerner | 1 |
170,259 | 26,927,819,084 | IssuesEvent | 2023-02-07 14:55:07 | statsmodels/statsmodels | https://api.github.com/repos/statsmodels/statsmodels | opened | SUMM/ENH/REF: statsmodels 1.0 | type-enh comp-base design type-refactor | Statsmodels 1.0 is still far in the future
Some thoughts on wishlist and requirements
- consistent returns of function, e.g. HolderTuple
- consistent methods and attributes across models
- for and with consistent post-estimation
- we might still need categories of models, eg. MLE versus moment estimators, OLS/WLS, GLM and GMM
- flake and pep8 (but no "black"ening of code that I maintain.
- related: code patterns. LGTM/CodeQL has a large number of false positives. Do we want to simplify some code to make the "bot" happy?
- stable frameworky classes,
- GenericLikelihoodModel (or alternative new class)
- GMM
- Multilink and multipart models (generic class still missing)
- missing core methods and models, especially those that need to be based on new pattern and structure
- generic multilink models
- generic multipart models (not clear what we need), as in ZI, hurdle models, Copula models, generic truncated/censored or inflated models. (several submodels)
- multi-endog and multivariate models, copula regression models would be multi-endog and multi-part
- endogeneity and two step models, IV
- there is some overlap in the latter 3 model categories in either data handling, model structure or results structure.
- code cleanup
- public, and commonly used methods (models, functions): those should be ok after refactoring for consistency, unit test coverage is ok
- public methods with unused (?) extensions: need more unit test and verify methods. This affects mainly inherited methods in new classes and methods that come from combining different options. e.g. var_weights and freq_weights in GLM are not supported for all cov_types and post-estimation results.
- public models or functions not advertised. Some parts look public but are not in docs and might have insufficient unit tests.
- private methods. In some case we don't clearly distinguish between private and public methods. Either privatize some or make them stable (stable api, sufficient unit test coverage). This applies to many helper and tool functions that were created for internal support but have a public name.
- unused code: remove it unless there is a strong reason to keep it. e.g. sandbox.
(This will be a lot of work if we want to publish sandbox code that is 70% or 80% finished. e.g. I don't want to throw away sandbox.distributions unless superseded by scipy or newer statsmodels code.)
- tsa
- no idea
- ...
I think we can do most over several pre-1.0 releases so that 1.0 would not have a large backwards compatibility impact.
one example for CodeQL problem and inconsistent returns:
We have several functions where the number of returns depends on an option. CodeQL cannot figure out in all cases what the appropriate tuple length is, and then reports false positives. If we always return a HolderTuple or similar, then that would not be the case. (This is in functions that were written a long time ago.)
| 1.0 | SUMM/ENH/REF: statsmodels 1.0 - Statsmodels 1.0 is still far in the future
Some thoughts on wishlist and requirements
- consistent returns of function, e.g. HolderTuple
- consistent methods and attributes across models
- for and with consistent post-estimation
- we might still need categories of models, eg. MLE versus moment estimators, OLS/WLS, GLM and GMM
- flake and pep8 (but no "black"ening of code that I maintain.
- related: code patterns. LGTM/CodeQL has a large number of false positives. Do we want to simplify some code to make the "bot" happy?
- stable frameworky classes,
- GenericLikelihoodModel (or alternative new class)
- GMM
- Multilink and multipart models (generic class still missing)
- missing core methods and models, especially those that need to be based on new pattern and structure
- generic multilink models
- generic multipart models (not clear what we need), as in ZI, hurdle models, Copula models, generic truncated/censored or inflated models. (several submodels)
- multi-endog and multivariate models, copula regression models would be multi-endog and multi-part
- endogeneity and two step models, IV
- there is some overlap in the latter 3 model categories in either data handling, model structure or results structure.
- code cleanup
- public, and commonly used methods (models, functions): those should be ok after refactoring for consistency, unit test coverage is ok
- public methods with unused (?) extensions: need more unit test and verify methods. This affects mainly inherited methods in new classes and methods that come from combining different options. e.g. var_weights and freq_weights in GLM are not supported for all cov_types and post-estimation results.
- public models or functions not advertised. Some parts look public but are not in docs and might have insufficient unit tests.
- private methods. In some case we don't clearly distinguish between private and public methods. Either privatize some or make them stable (stable api, sufficient unit test coverage). This applies to many helper and tool functions that were created for internal support but have a public name.
- unused code: remove it unless there is a strong reason to keep it. e.g. sandbox.
(This will be a lot of work if we want to publish sandbox code that is 70% or 80% finished. e.g. I don't want to throw away sandbox.distributions unless superseded by scipy or newer statsmodels code.)
- tsa
- no idea
- ...
I think we can do most over several pre-1.0 releases so that 1.0 would not have a large backwards compatibility impact.
one example for CodeQL problem and inconsistent returns:
We have several functions where the number of returns depends on an option. CodeQL cannot figure out in all cases what the appropriate tuple length is, and then reports false positives. If we always return a HolderTuple or similar, then that would not be the case. (This is in functions that were written a long time ago.)
| non_test | summ enh ref statsmodels statsmodels is still far in the future some thoughts on wishlist and requirements consistent returns of function e g holdertuple consistent methods and attributes across models for and with consistent post estimation we might still need categories of models eg mle versus moment estimators ols wls glm and gmm flake and but no black ening of code that i maintain related code patterns lgtm codeql has a large number of false positives do we want to simplify some code to make the bot happy stable frameworky classes genericlikelihoodmodel or alternative new class gmm multilink and multipart models generic class still missing missing core methods and models especially those that need to be based on new pattern and structure generic multilink models generic multipart models not clear what we need as in zi hurdle models copula models generic truncated censored or inflated models several submodels multi endog and multivariate models copula regression models would be multi endog and multi part endogeneity and two step models iv there is some overlap in the latter model categories in either data handling model structure or results structure code cleanup public and commonly used methods models functions those should be ok after refactoring for consistency unit test coverage is ok public methods with unused extensions need more unit test and verify methods this affects mainly inherited methods in new classes and methods that come from combining different options e g var weights and freq weights in glm are not supported for all cov types and post estimation results public models or functions not advertised some parts look public but are not in docs and might have insufficient unit tests private methods in some case we don t clearly distinguish between private and public methods either privatize some or make them stable stable api sufficient unit test coverage this applies to many helper and tool functions that were created for internal support but have a public name unused code remove it unless there is a strong reason to keep it e g sandbox this will be a lot of work if we want to publish sandbox code that is or finished e g i don t want to throw away sandbox distributions unless superseded by scipy or newer statsmodels code tsa no idea i think we can do most over several pre releases so that would not have a large backwards compatibility impact one example for codeql problem and inconsistent returns we have several functions where the number of returns depends on an option codeql cannot figure out in all cases what the appropriate tuple length is and then reports false positives if we always return a holdertuple or similar then that would not be the case this is in functions that were written a long time ago | 0 |
204,071 | 15,398,714,540 | IssuesEvent | 2021-03-04 00:36:58 | nucleus-security/Test-repo | https://api.github.com/repos/nucleus-security/Test-repo | opened | Nucleus - Project: Ticketing Rules now apply to all vulnerabilities - [High] - CentOS Security Update for kernel (CESA-2019:2473) | Testing | Source: QUALYS
Finding Description: CentOS has released security update for kernel to fix the vulnerabilities.<p>Affected Products:<br /><br />centos 6
Impact: This vulnerability could be exploited to gain complete access to sensitive information. Malicious users could also use this vulnerability to change all the contents or configuration on the system. Additionally this vulnerability can also be used to cause a complete denial of service and could render the resource completely unavailable.</p>
Target(s): Asset name: 45.55.254.143
IP: 45.55.254.143
Solution: To resolve this issue, upgrade to the latest packages which contain a patch. Refer to CentOS advisory <a href="https://lists.centos.org/pipermail/centos-announce/2019-august/023404.html">centos 6</a> for updates and patch information.
<p>Patch:<br />
Following are links for downloading patches to fix the vulnerabilities:
</p><p> <a href="https://lists.centos.org/pipermail/centos-announce/2019-august/023404.html">CESA-2019:2473: centos 6</a></p>
References:
ID:256652
CVE:CVE-2019-5489,CVE-2017-17805,CVE-2018-17972,CVE-2019-1125
Category:CentOS
PCI Flagged:1
Vendor References:CESA-2019:2473 centos 6
Bugtraq IDs:106478,105525,102291
Severity: High
Date Discovered: 2020-01-07 14:35:48
Nucleus Notification Rules Triggered: GitHub Rule
Project Name: Ticketing Rules now apply to all vulnerabilities
| 1.0 | Nucleus - Project: Ticketing Rules now apply to all vulnerabilities - [High] - CentOS Security Update for kernel (CESA-2019:2473) - Source: QUALYS
Finding Description: CentOS has released security update for kernel to fix the vulnerabilities.<p>Affected Products:<br /><br />centos 6
Impact: This vulnerability could be exploited to gain complete access to sensitive information. Malicious users could also use this vulnerability to change all the contents or configuration on the system. Additionally this vulnerability can also be used to cause a complete denial of service and could render the resource completely unavailable.</p>
Target(s): Asset name: 45.55.254.143
IP: 45.55.254.143
Solution: To resolve this issue, upgrade to the latest packages which contain a patch. Refer to CentOS advisory <a href="https://lists.centos.org/pipermail/centos-announce/2019-august/023404.html">centos 6</a> for updates and patch information.
<p>Patch:<br />
Following are links for downloading patches to fix the vulnerabilities:
</p><p> <a href="https://lists.centos.org/pipermail/centos-announce/2019-august/023404.html">CESA-2019:2473: centos 6</a></p>
References:
ID:256652
CVE:CVE-2019-5489,CVE-2017-17805,CVE-2018-17972,CVE-2019-1125
Category:CentOS
PCI Flagged:1
Vendor References:CESA-2019:2473 centos 6
Bugtraq IDs:106478,105525,102291
Severity: High
Date Discovered: 2020-01-07 14:35:48
Nucleus Notification Rules Triggered: GitHub Rule
Project Name: Ticketing Rules now apply to all vulnerabilities
| test | nucleus project ticketing rules now apply to all vulnerabilities centos security update for kernel cesa source qualys finding description centos has released security update for kernel to fix the vulnerabilities affected products centos impact this vulnerability could be exploited to gain complete access to sensitive information malicious users could also use this vulnerability to change all the contents or configuration on the system additionally this vulnerability can also be used to cause a complete denial of service and could render the resource completely unavailable target s asset name ip solution to resolve this issue upgrade to the latest packages which contain a patch refer to centos advisory for updates and patch information patch following are links for downloading patches to fix the vulnerabilities references id cve cve cve cve cve category centos pci flagged vendor references cesa centos bugtraq ids severity high date discovered nucleus notification rules triggered github rule project name ticketing rules now apply to all vulnerabilities | 1 |
28,317 | 2,700,934,954 | IssuesEvent | 2015-04-04 18:43:09 | CenterForOpenScience/osf.io | https://api.github.com/repos/CenterForOpenScience/osf.io | closed | Warning for making a component public should specifically mention the component | 5 - Pending Review Priority - Low | As it is right now, the warning message displayed when making a **component** public displays as:
This message is misleading, as it indicates that the entire project will become public. I think this could be re-worded to inform the user that:
1. This component will now be public and all information within it should be assumed to be public forever, etc.
2. The rest of the project, including other components, will **NOT** be public
| 1.0 | Warning for making a component public should specifically mention the component - As it is right now, the warning message displayed when making a **component** public displays as:
This message is misleading, as it indicates that the entire project will become public. I think this could be re-worded to inform the user that:
1. This component will now be public and all information within it should be assumed to be public forever, etc.
2. The rest of the project, including other components, will **NOT** be public
| non_test | warning for making a component public should specifically mention the component as it is right now the warning message displayed when making a component public displays as this message is misleading as it indicates that the entire project will become public i think this could be re worded to inform the user that this component will now be public and all information within it should be assumed to be public forever etc the rest of the project including other components will not be public | 0 |
449,864 | 31,865,780,301 | IssuesEvent | 2023-09-15 14:03:26 | akuity/terraform-provider-akp | https://api.github.com/repos/akuity/terraform-provider-akp | opened | Resource docs should start with a bare minimum example | documentation enhancement | Currently, the docs contain exhaustive examples demonstrating the use of every available argument. While this helps show their use, most users will want to start with the bare minimum resources using mainly defaults. Then tweaking it to their needs.
We should add an example of the resources that include only the required fields to be functional. | 1.0 | Resource docs should start with a bare minimum example - Currently, the docs contain exhaustive examples demonstrating the use of every available argument. While this helps show their use, most users will want to start with the bare minimum resources using mainly defaults. Then tweaking it to their needs.
We should add an example of the resources that include only the required fields to be functional. | non_test | resource docs should start with a bare minimum example currently the docs contain exhaustive examples demonstrating the use of every available argument while this helps show their use most users will want to start with the bare minimum resources using mainly defaults then tweaking it to their needs we should add an example of the resources that include only the required fields to be functional | 0 |
504,935 | 14,624,091,512 | IssuesEvent | 2020-12-23 05:24:26 | ucfopen/Obojobo | https://api.github.com/repos/ucfopen/Obojobo | closed | yarn install fails due to missing pinned commit in ims-lti dependency on v11.1.0 | bug dependencies high priority | Some time today, yarn install started failing:
> error Couldn’t find match for “d535b4c4aff8a43775d3d9c1f2069f0593b7779f” in “refs/heads/master,refs/tags/1.0.0,refs/tags/2.0.0,refs/tags/2.0.1,refs/tags/2.1.0,refs/tags/2.1.1,refs/tags/v2.1.2,refs/tags/v2.1.4,refs/tags/v2.1.5,refs/tags/v2.1.6,refs/tags/v3.0.0,refs/tags/v3.0.1,refs/tags/v3.0.2" for “https://github.com/ChristianMurphy/ims-lti.git”.
Github is displaying a warning message when one tries to view the commit here https://github.com/ChristianMurphy/ims-lti/commit/d535b4c4aff8a43775d3d9c1f2069f0593b7779f
| 1.0 | yarn install fails due to missing pinned commit in ims-lti dependency on v11.1.0 - Some time today, yarn install started failing:
> error Couldn’t find match for “d535b4c4aff8a43775d3d9c1f2069f0593b7779f” in “refs/heads/master,refs/tags/1.0.0,refs/tags/2.0.0,refs/tags/2.0.1,refs/tags/2.1.0,refs/tags/2.1.1,refs/tags/v2.1.2,refs/tags/v2.1.4,refs/tags/v2.1.5,refs/tags/v2.1.6,refs/tags/v3.0.0,refs/tags/v3.0.1,refs/tags/v3.0.2" for “https://github.com/ChristianMurphy/ims-lti.git”.
Github is displaying a warning message when one tries to view the commit here https://github.com/ChristianMurphy/ims-lti/commit/d535b4c4aff8a43775d3d9c1f2069f0593b7779f
| non_test | yarn install fails due to missing pinned commit in ims lti dependency on some time today yarn install started failing error couldn’t find match for “ ” in “refs heads master refs tags refs tags refs tags refs tags refs tags refs tags refs tags refs tags refs tags refs tags refs tags refs tags for “ github is displaying a warning message when one tries to view the commit here | 0 |
249,503 | 21,163,907,237 | IssuesEvent | 2022-04-07 11:57:50 | Uuvana-Studios/longvinter-windows-client | https://api.github.com/repos/Uuvana-Studios/longvinter-windows-client | closed | the range problem of a bullet | Bug Not Tested | **Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Symptoms that occur when pressed continuously
Can't use up 100 bullets at once.
**Expected behavior**
A clear and concise description of what you expected to happen.
Steps to reproduce the behavior:
the range problem of a bullet
The bullet seems to have a certain rangeten thousand
It doesn't go out exactly as far as that range, and when you use bullets, you get a stop.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. Windows] windows 10
- Game Version [e.g. 1.0]
- Steam Version [e.g. 1.0]
**Additional context**
Add any other context about the problem here.
| 1.0 | the range problem of a bullet - **Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Symptoms that occur when pressed continuously
Can't use up 100 bullets at once.
**Expected behavior**
A clear and concise description of what you expected to happen.
Steps to reproduce the behavior:
the range problem of a bullet
The bullet seems to have a certain rangeten thousand
It doesn't go out exactly as far as that range, and when you use bullets, you get a stop.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. Windows] windows 10
- Game Version [e.g. 1.0]
- Steam Version [e.g. 1.0]
**Additional context**
Add any other context about the problem here.
| test | the range problem of a bullet describe the bug a clear and concise description of what the bug is to reproduce symptoms that occur when pressed continuously can t use up bullets at once expected behavior a clear and concise description of what you expected to happen steps to reproduce the behavior the range problem of a bullet the bullet seems to have a certain rangeten thousand it doesn t go out exactly as far as that range and when you use bullets you get a stop screenshots if applicable add screenshots to help explain your problem desktop please complete the following information os windows game version steam version additional context add any other context about the problem here | 1 |
468,619 | 13,486,854,729 | IssuesEvent | 2020-09-11 10:03:17 | CamprGmbH/campr | https://api.github.com/repos/CamprGmbH/campr | closed | Email notification after creating a task | HIGH PRIORITY Prio 1 bug | After creating a task the corresponding email with the link 'Task Profile' is send out. The link itself is correct but there's an issue with showing the task details after clicking the link:
- showing the task details works only when
- the user is logged in into CAMPR **AND**
- the user is logged in into the workspace the project belongs to
- is the user **not** logged in and he passes the login procedure, he will end up in the workspace view instead seeing the task details
In any case, the user, whether online or offline, must land in the task details when clicking the link.
| 1.0 | Email notification after creating a task - After creating a task the corresponding email with the link 'Task Profile' is send out. The link itself is correct but there's an issue with showing the task details after clicking the link:
- showing the task details works only when
- the user is logged in into CAMPR **AND**
- the user is logged in into the workspace the project belongs to
- is the user **not** logged in and he passes the login procedure, he will end up in the workspace view instead seeing the task details
In any case, the user, whether online or offline, must land in the task details when clicking the link.
| non_test | email notification after creating a task after creating a task the corresponding email with the link task profile is send out the link itself is correct but there s an issue with showing the task details after clicking the link showing the task details works only when the user is logged in into campr and the user is logged in into the workspace the project belongs to is the user not logged in and he passes the login procedure he will end up in the workspace view instead seeing the task details in any case the user whether online or offline must land in the task details when clicking the link | 0 |
185,378 | 6,721,376,555 | IssuesEvent | 2017-10-16 11:28:53 | CS2103AUG2017-T13-B1/main | https://api.github.com/repos/CS2103AUG2017-T13-B1/main | opened | v1.2 Documentation | Priority: High Status: In Progress | - User Guide: Update as necessary.
- If a feature has been released in this version, replace the Coming in v2.0 annotation with a Since v1.2. Also replace UI mockups with actual screenshots.
- If a feature design has changed, update the descriptions accordingly.
Developer Guide:
- Each member should describe the implementation of at least one enhancement she has added (or planning to add).
- Expected length: ~1 page per person
- The description can contain things such as,
- How the feature is implemented.
- Why it is implemented that way.
- Alternatives considered.
- The stated objective is to explain the implementation to a future developer, but a hidden objective is to show evidence that you can document deeply-technical content using prose, examples, diagrams, code snippets, etc. appropriately. To that end, you may also describe features that you plan to implement in the future, even beyond v1.5 (hypothetically).
- For an example, see [the description of the undo/redo feature implementation in the AddressBook-Level4 developer guide](https://nus-cs2103-ay1718s1.github.io/addressbook-level4/DeveloperGuide.html#undo-redo-mechanism). | 1.0 | v1.2 Documentation - - User Guide: Update as necessary.
- If a feature has been released in this version, replace the Coming in v2.0 annotation with a Since v1.2. Also replace UI mockups with actual screenshots.
- If a feature design has changed, update the descriptions accordingly.
Developer Guide:
- Each member should describe the implementation of at least one enhancement she has added (or planning to add).
- Expected length: ~1 page per person
- The description can contain things such as,
- How the feature is implemented.
- Why it is implemented that way.
- Alternatives considered.
- The stated objective is to explain the implementation to a future developer, but a hidden objective is to show evidence that you can document deeply-technical content using prose, examples, diagrams, code snippets, etc. appropriately. To that end, you may also describe features that you plan to implement in the future, even beyond v1.5 (hypothetically).
- For an example, see [the description of the undo/redo feature implementation in the AddressBook-Level4 developer guide](https://nus-cs2103-ay1718s1.github.io/addressbook-level4/DeveloperGuide.html#undo-redo-mechanism). | non_test | documentation user guide update as necessary if a feature has been released in this version replace the coming in annotation with a since also replace ui mockups with actual screenshots if a feature design has changed update the descriptions accordingly developer guide each member should describe the implementation of at least one enhancement she has added or planning to add expected length page per person the description can contain things such as how the feature is implemented why it is implemented that way alternatives considered the stated objective is to explain the implementation to a future developer but a hidden objective is to show evidence that you can document deeply technical content using prose examples diagrams code snippets etc appropriately to that end you may also describe features that you plan to implement in the future even beyond hypothetically for an example see | 0 |
199,215 | 15,028,851,024 | IssuesEvent | 2021-02-02 04:06:17 | cloudflare/terraform-provider-cloudflare | https://api.github.com/repos/cloudflare/terraform-provider-cloudflare | closed | TestAccCloudflareOriginCACertificate_Basic is failing | kind/failing-test triage/accepted | `TestAccCloudflareOriginCACertificate_Basic` is failing with the following exception
```
=== RUN TestAccCloudflareOriginCACertificate_Basic
testing.go:705: Step 0 error: errors during apply:
Error: Error creating origin certificate: error from makeRequest: HTTP status 400: content "{\"success\":false,\"errors\":[{\"code\":10000,\"message\":\"Authentication error\"}]}\n"
on /tmp/tf-test901793942/main.tf line 2:
(source code not available)
```
Link to failure: https://github.com/cloudflare/terraform-provider-cloudflare/runs/1295364502?check_suite_focus=true#step:6:312 | 1.0 | TestAccCloudflareOriginCACertificate_Basic is failing - `TestAccCloudflareOriginCACertificate_Basic` is failing with the following exception
```
=== RUN TestAccCloudflareOriginCACertificate_Basic
testing.go:705: Step 0 error: errors during apply:
Error: Error creating origin certificate: error from makeRequest: HTTP status 400: content "{\"success\":false,\"errors\":[{\"code\":10000,\"message\":\"Authentication error\"}]}\n"
on /tmp/tf-test901793942/main.tf line 2:
(source code not available)
```
Link to failure: https://github.com/cloudflare/terraform-provider-cloudflare/runs/1295364502?check_suite_focus=true#step:6:312 | test | testacccloudflareorigincacertificate basic is failing testacccloudflareorigincacertificate basic is failing with the following exception run testacccloudflareorigincacertificate basic testing go step error errors during apply error error creating origin certificate error from makerequest http status content success false errors n on tmp tf main tf line source code not available link to failure | 1 |
221,874 | 7,398,389,011 | IssuesEvent | 2018-03-19 05:56:36 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.naukri.com - mobile site is not usable | browser-firefox-mobile-(tablet) priority-normal | <!-- @browser: Firefox Mobile (Tablet) 56.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.1.2; Tablet; rv:56.0) Gecko/56.0 Firefox/56.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.naukri.com/mnj/login?org=apply
**Browser / Version**: Firefox Mobile (Tablet) 56.0
**Operating System**: Android 7.1.2
**Problem type**: Mobile site is not usable
**Steps to Reproduce**
1. Navigate to: https://www.naukri.com/mnj/login?org=apply
2. …
Expected Behavior:
Site Should work. Login should work
Actual Behavior:
Asks to rotate screen on keyboard up. Can't login
[](https://webcompat.com/uploads/2017/6/8e2d3792-fd55-47d1-85fb-c2ecff69f443.jpg)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.naukri.com - mobile site is not usable - <!-- @browser: Firefox Mobile (Tablet) 56.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.1.2; Tablet; rv:56.0) Gecko/56.0 Firefox/56.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.naukri.com/mnj/login?org=apply
**Browser / Version**: Firefox Mobile (Tablet) 56.0
**Operating System**: Android 7.1.2
**Problem type**: Mobile site is not usable
**Steps to Reproduce**
1. Navigate to: https://www.naukri.com/mnj/login?org=apply
2. …
Expected Behavior:
Site Should work. Login should work
Actual Behavior:
Asks to rotate screen on keyboard up. Can't login
[](https://webcompat.com/uploads/2017/6/8e2d3792-fd55-47d1-85fb-c2ecff69f443.jpg)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | mobile site is not usable url browser version firefox mobile tablet operating system android problem type mobile site is not usable steps to reproduce navigate to … expected behavior site should work login should work actual behavior asks to rotate screen on keyboard up can t login from with ❤️ | 0 |
96,187 | 10,924,854,602 | IssuesEvent | 2019-11-22 11:04:03 | MarkusPaulsen/TheSpoon | https://api.github.com/repos/MarkusPaulsen/TheSpoon | closed | Upload meeting agendas | Documentation Task | **Description:**
**Acceptance criteria:**
- [x] Meeting agendas uploaded
| 1.0 | Upload meeting agendas - **Description:**
**Acceptance criteria:**
- [x] Meeting agendas uploaded
| non_test | upload meeting agendas description acceptance criteria meeting agendas uploaded | 0 |
43,544 | 5,543,743,661 | IssuesEvent | 2017-03-22 17:34:19 | e107inc/e107 | https://api.github.com/repos/e107inc/e107 | closed | NewForumPost_menu number of items | testing required | I can't set number of forum messages. I set 4 and after set jump back to 6. I make it again and problem same. | 1.0 | NewForumPost_menu number of items - I can't set number of forum messages. I set 4 and after set jump back to 6. I make it again and problem same. | test | newforumpost menu number of items i can t set number of forum messages i set and after set jump back to i make it again and problem same | 1 |
101,334 | 8,785,637,389 | IssuesEvent | 2018-12-20 13:36:55 | IBM-Blockchain/blockchain-vscode-extension | https://api.github.com/repos/IBM-Blockchain/blockchain-vscode-extension | closed | Split up system tests to make quicker | test | Split up the system tests into multiple travis functions to make them quicker as it now takes a long time for each build | 1.0 | Split up system tests to make quicker - Split up the system tests into multiple travis functions to make them quicker as it now takes a long time for each build | test | split up system tests to make quicker split up the system tests into multiple travis functions to make them quicker as it now takes a long time for each build | 1 |
52,829 | 27,796,099,130 | IssuesEvent | 2023-03-17 12:40:24 | qbittorrent/qBittorrent | https://api.github.com/repos/qbittorrent/qBittorrent | closed | 4.5.0.99~20221208* stops all activity after a few minutes | Performance WebUI | ### qBittorrent & operating system versions
qBittorrent-nox: 4.5.0.99\~202212080747-7855-65611cd3d\~ubuntu22.04.1
Operating system: Armbian 22.04
Qt: 5.15.3
libtorrent-rasterbar: 2.0.8
### What is the problem?
qbt stops all torrenting after a few minutes. CPU remains high, but **all network traffic has stopped** and the webui is partially responsive. I can still change screens and categories, but it no longer "updates" any info. It's like it's stopped updating everything, and won't refresh any information. qbittorrent.log doesn't show anything obvious.
Anything talking to qbt (sonarr, etc..) all start issuing qbt not responding errors.
This started with the newer 4.5.0 builds. Don't know which exactly(\*). Can't downgrade to test as older versions get removed from the PPA.
(\*) Update: digging through apt logs, these versions worked:
- 4.5.0.99\~202211271634-7849-480e3f02c\~ubuntu22.04.1
- 4.5.0.99\~202211302247-7852-18577d9cb\~ubuntu22.04.1
- 4.5.0.99\~202212040747-7854-6a4bb1356\~ubuntu22.04.1
Error starts here: 4.5.0.99\~202212080747-7855-65611cd3d\~ubuntu22.04.1
### Steps to reproduce
_No response_
### Additional context
Current screen. The values under Down Speed, Downloaded, etc.. have not changed in 10 minutes, and they never do. The only way to get things going is a kill -9 to the process, and restart. IT then starts all over again; runs for a few minutes, then hangs.
I can change to display a new category. Notice the Trackers tab is also not updating.
Again, change category.. but nothing else updates.
"Help -> About". Windows opens, but never populates.
### Log(s) & preferences file(s)
_No response_ | True | 4.5.0.99~20221208* stops all activity after a few minutes - ### qBittorrent & operating system versions
qBittorrent-nox: 4.5.0.99\~202212080747-7855-65611cd3d\~ubuntu22.04.1
Operating system: Armbian 22.04
Qt: 5.15.3
libtorrent-rasterbar: 2.0.8
### What is the problem?
qbt stops all torrenting after a few minutes. CPU remains high, but **all network traffic has stopped** and the webui is partially responsive. I can still change screens and categories, but it no longer "updates" any info. It's like it's stopped updating everything, and won't refresh any information. qbittorrent.log doesn't show anything obvious.
Anything talking to qbt (sonarr, etc..) all start issuing qbt not responding errors.
This started with the newer 4.5.0 builds. Don't know which exactly(\*). Can't downgrade to test as older versions get removed from the PPA.
(\*) Update: digging through apt logs, these versions worked:
- 4.5.0.99\~202211271634-7849-480e3f02c\~ubuntu22.04.1
- 4.5.0.99\~202211302247-7852-18577d9cb\~ubuntu22.04.1
- 4.5.0.99\~202212040747-7854-6a4bb1356\~ubuntu22.04.1
Error starts here: 4.5.0.99\~202212080747-7855-65611cd3d\~ubuntu22.04.1
### Steps to reproduce
_No response_
### Additional context
Current screen. The values under Down Speed, Downloaded, etc.. have not changed in 10 minutes, and they never do. The only way to get things going is a kill -9 to the process, and restart. IT then starts all over again; runs for a few minutes, then hangs.
I can change to display a new category. Notice the Trackers tab is also not updating.
Again, change category.. but nothing else updates.
"Help -> About". Windows opens, but never populates.
### Log(s) & preferences file(s)
_No response_ | non_test | stops all activity after a few minutes qbittorrent operating system versions qbittorrent nox operating system armbian qt libtorrent rasterbar what is the problem qbt stops all torrenting after a few minutes cpu remains high but all network traffic has stopped and the webui is partially responsive i can still change screens and categories but it no longer updates any info it s like it s stopped updating everything and won t refresh any information qbittorrent log doesn t show anything obvious anything talking to qbt sonarr etc all start issuing qbt not responding errors this started with the newer builds don t know which exactly can t downgrade to test as older versions get removed from the ppa update digging through apt logs these versions worked error starts here steps to reproduce no response additional context current screen the values under down speed downloaded etc have not changed in minutes and they never do the only way to get things going is a kill to the process and restart it then starts all over again runs for a few minutes then hangs i can change to display a new category notice the trackers tab is also not updating again change category but nothing else updates help about windows opens but never populates log s preferences file s no response | 0 |
51,019 | 13,188,043,425 | IssuesEvent | 2020-08-13 05:23:32 | icecube-trac/tix3 | https://api.github.com/repos/icecube-trac/tix3 | closed | Globus Tools in CVMFS (Trac #1836) | Migrated from Trac cmake defect | This is a ticket we received to our help@icecube queue that I'm passing over to you. This is from Thomas Kintscher, email address thomas.kintscher@desy.de , so if you could tie him in to any responses, that would be great!
-Nils
Dear helpdesk,
I noticed an issue with the version of the Globus tools in CVMFS (both
py2-v1 and py2-v2). The globus-url-copy tool always segfaults when
trying to list certain directories on the Zeuthen site, e.g. like this:
Show quoted text
gsiftp://gridftp.ifh.de/pnfs/ifh.de/acs/grid/icecube/data/sim/IceCube/2012/filtered/level2/CORSIKA-in-ice/11058/
zsh: segmentation fault globus-url-copy -list
Running the same command on cobalt outside of the CVMFS environment
works. I noticed that the version on CVMFS is 8.6, whereas the cobalts
already have 9.19.
Maybe updating the version on CVMFS would already be enough to resolve
this problem. For the time being, I can use the version installed on
cobalt, but it's somewhat inconvenient to switch if tools from CVMFS are
required.
Best,
Thomas
--
Thomas Kintscher
Deutsches Elektronen-Synchrotron (DESY)
Platanenallee 6, 15378 Zeuthen, Germany
Office: 2L/15, Phone: +49 33762-7-7312
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/ticket/1836">https://code.icecube.wisc.edu/ticket/1836</a>, reported by nirland and owned by </em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2016-08-26T18:24:01",
"description": "This is a ticket we received to our help@icecube queue that I'm passing over to you. This is from Thomas Kintscher, email address thomas.kintscher@desy.de , so if you could tie him in to any responses, that would be great!\n\n-Nils\n\n\n\nDear helpdesk,\n\nI noticed an issue with the version of the Globus tools in CVMFS (both\npy2-v1 and py2-v2). The globus-url-copy tool always segfaults when\ntrying to list certain directories on the Zeuthen site, e.g. like this:\n\n\nShow quoted text\n\ngsiftp://gridftp.ifh.de/pnfs/ifh.de/acs/grid/icecube/data/sim/IceCube/2012/filtered/level2/CORSIKA-in-ice/11058/\nzsh: segmentation fault globus-url-copy -list\n\n\nRunning the same command on cobalt outside of the CVMFS environment\nworks. I noticed that the version on CVMFS is 8.6, whereas the cobalts\nalready have 9.19.\nMaybe updating the version on CVMFS would already be enough to resolve\nthis problem. For the time being, I can use the version installed on\ncobalt, but it's somewhat inconvenient to switch if tools from CVMFS are\nrequired.\n\nBest,\nThomas\n\n-- \nThomas Kintscher\nDeutsches Elektronen-Synchrotron (DESY)\nPlatanenallee 6, 15378 Zeuthen, Germany\nOffice: 2L/15, Phone: +49 33762-7-7312",
"reporter": "nirland",
"cc": "",
"resolution": "wontfix",
"_ts": "1472235841289510",
"component": "cmake",
"summary": "Globus Tools in CVMFS",
"priority": "normal",
"keywords": "",
"time": "2016-08-26T17:24:29",
"milestone": "",
"owner": "",
"type": "defect"
}
```
</p>
</details>
| 1.0 | Globus Tools in CVMFS (Trac #1836) - This is a ticket we received to our help@icecube queue that I'm passing over to you. This is from Thomas Kintscher, email address thomas.kintscher@desy.de , so if you could tie him in to any responses, that would be great!
-Nils
Dear helpdesk,
I noticed an issue with the version of the Globus tools in CVMFS (both
py2-v1 and py2-v2). The globus-url-copy tool always segfaults when
trying to list certain directories on the Zeuthen site, e.g. like this:
Show quoted text
gsiftp://gridftp.ifh.de/pnfs/ifh.de/acs/grid/icecube/data/sim/IceCube/2012/filtered/level2/CORSIKA-in-ice/11058/
zsh: segmentation fault globus-url-copy -list
Running the same command on cobalt outside of the CVMFS environment
works. I noticed that the version on CVMFS is 8.6, whereas the cobalts
already have 9.19.
Maybe updating the version on CVMFS would already be enough to resolve
this problem. For the time being, I can use the version installed on
cobalt, but it's somewhat inconvenient to switch if tools from CVMFS are
required.
Best,
Thomas
--
Thomas Kintscher
Deutsches Elektronen-Synchrotron (DESY)
Platanenallee 6, 15378 Zeuthen, Germany
Office: 2L/15, Phone: +49 33762-7-7312
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/ticket/1836">https://code.icecube.wisc.edu/ticket/1836</a>, reported by nirland and owned by </em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2016-08-26T18:24:01",
"description": "This is a ticket we received to our help@icecube queue that I'm passing over to you. This is from Thomas Kintscher, email address thomas.kintscher@desy.de , so if you could tie him in to any responses, that would be great!\n\n-Nils\n\n\n\nDear helpdesk,\n\nI noticed an issue with the version of the Globus tools in CVMFS (both\npy2-v1 and py2-v2). The globus-url-copy tool always segfaults when\ntrying to list certain directories on the Zeuthen site, e.g. like this:\n\n\nShow quoted text\n\ngsiftp://gridftp.ifh.de/pnfs/ifh.de/acs/grid/icecube/data/sim/IceCube/2012/filtered/level2/CORSIKA-in-ice/11058/\nzsh: segmentation fault globus-url-copy -list\n\n\nRunning the same command on cobalt outside of the CVMFS environment\nworks. I noticed that the version on CVMFS is 8.6, whereas the cobalts\nalready have 9.19.\nMaybe updating the version on CVMFS would already be enough to resolve\nthis problem. For the time being, I can use the version installed on\ncobalt, but it's somewhat inconvenient to switch if tools from CVMFS are\nrequired.\n\nBest,\nThomas\n\n-- \nThomas Kintscher\nDeutsches Elektronen-Synchrotron (DESY)\nPlatanenallee 6, 15378 Zeuthen, Germany\nOffice: 2L/15, Phone: +49 33762-7-7312",
"reporter": "nirland",
"cc": "",
"resolution": "wontfix",
"_ts": "1472235841289510",
"component": "cmake",
"summary": "Globus Tools in CVMFS",
"priority": "normal",
"keywords": "",
"time": "2016-08-26T17:24:29",
"milestone": "",
"owner": "",
"type": "defect"
}
```
</p>
</details>
| non_test | globus tools in cvmfs trac this is a ticket we received to our help icecube queue that i m passing over to you this is from thomas kintscher email address thomas kintscher desy de so if you could tie him in to any responses that would be great nils dear helpdesk i noticed an issue with the version of the globus tools in cvmfs both and the globus url copy tool always segfaults when trying to list certain directories on the zeuthen site e g like this show quoted text gsiftp gridftp ifh de pnfs ifh de acs grid icecube data sim icecube filtered corsika in ice zsh segmentation fault globus url copy list running the same command on cobalt outside of the cvmfs environment works i noticed that the version on cvmfs is whereas the cobalts already have maybe updating the version on cvmfs would already be enough to resolve this problem for the time being i can use the version installed on cobalt but it s somewhat inconvenient to switch if tools from cvmfs are required best thomas thomas kintscher deutsches elektronen synchrotron desy platanenallee zeuthen germany office phone migrated from json status closed changetime description this is a ticket we received to our help icecube queue that i m passing over to you this is from thomas kintscher email address thomas kintscher desy de so if you could tie him in to any responses that would be great n n nils n n n ndear helpdesk n ni noticed an issue with the version of the globus tools in cvmfs both and the globus url copy tool always segfaults when ntrying to list certain directories on the zeuthen site e g like this n n nshow quoted text n ngsiftp gridftp ifh de pnfs ifh de acs grid icecube data sim icecube filtered corsika in ice nzsh segmentation fault globus url copy list n n nrunning the same command on cobalt outside of the cvmfs environment nworks i noticed that the version on cvmfs is whereas the cobalts nalready have nmaybe updating the version on cvmfs would already be enough to resolve nthis problem for the time being i can use the version installed on ncobalt but it s somewhat inconvenient to switch if tools from cvmfs are nrequired n nbest nthomas n n nthomas kintscher ndeutsches elektronen synchrotron desy nplatanenallee zeuthen germany noffice phone reporter nirland cc resolution wontfix ts component cmake summary globus tools in cvmfs priority normal keywords time milestone owner type defect | 0 |
749,372 | 26,161,255,866 | IssuesEvent | 2022-12-31 15:18:23 | RankyList/ranky-list | https://api.github.com/repos/RankyList/ranky-list | closed | [FEATURE] TierList Entities | api back feature priority 1 | ### Type of feature
Something new
### The name of the feature
Add basic TierList entities with fixtures
### Feature description
Add basic TierList entities with the following schema (adapt to MongoDB) :
We should also add fixtures for a better development experience. Make sure the API responds correctly with the appropriate data.
### Additional information
One thing we need to be careful of : a TierList item can belong to a Rank but also to a TierList (if it hasn't been assigned yet). It should **never** belong to both at the same time.
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | [FEATURE] TierList Entities - ### Type of feature
Something new
### The name of the feature
Add basic TierList entities with fixtures
### Feature description
Add basic TierList entities with the following schema (adapt to MongoDB) :
We should also add fixtures for a better development experience. Make sure the API responds correctly with the appropriate data.
### Additional information
One thing we need to be careful of : a TierList item can belong to a Rank but also to a TierList (if it hasn't been assigned yet). It should **never** belong to both at the same time.
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | non_test | tierlist entities type of feature something new the name of the feature add basic tierlist entities with fixtures feature description add basic tierlist entities with the following schema adapt to mongodb we should also add fixtures for a better development experience make sure the api responds correctly with the appropriate data additional information one thing we need to be careful of a tierlist item can belong to a rank but also to a tierlist if it hasn t been assigned yet it should never belong to both at the same time code of conduct i agree to follow this project s code of conduct | 0 |
343,265 | 30,653,593,008 | IssuesEvent | 2023-07-25 10:31:28 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix paddle_manipulation.test_paddle_concat | Sub Task Failing Test Paddle Frontend | | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix paddle_manipulation.test_paddle_concat - | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
| test | fix paddle manipulation test paddle concat torch a href src tensorflow a href src numpy a href src paddle a href src jax a href src | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.