Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 1
744
| labels
stringlengths 4
574
| body
stringlengths 9
211k
| index
stringclasses 10
values | text_combine
stringlengths 96
211k
| label
stringclasses 2
values | text
stringlengths 96
188k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
165,111
| 13,965,653,008
|
IssuesEvent
|
2020-10-25 23:27:29
|
janfic/useride
|
https://api.github.com/repos/janfic/useride
|
opened
|
USER Terminal Program: USER Documentation
|
documentation
|
Add documentation for each of the commands:
goto
print
+ others
as well as features such as Program Input + Output + piping
|
1.0
|
USER Terminal Program: USER Documentation - Add documentation for each of the commands:
goto
print
+ others
as well as features such as Program Input + Output + piping
|
non_process
|
user terminal program user documentation add documentation for each of the commands goto print others as well as features such as program input output piping
| 0
|
769,507
| 27,009,746,919
|
IssuesEvent
|
2023-02-10 14:32:12
|
aleksbobic/csx
|
https://api.github.com/repos/aleksbobic/csx
|
closed
|
Multiple bugs identified during evaluation
|
bug priority:high
|
The bugs:
- [x] Entering C in the filter for tabular data triggers the comment popup.
- [x] Detail graph to overview graph crashes CSX sometimes. The error is `Uncaught TypeError: e.connections is undefined`
- [x] Schema is sometimes out of focus when switching between graph types.
- [x] Search for something using the traditional search box . Then navigate to the workflow and just run it. It doesn't work.
- [x] No possibility of removing just one node from the graph.
|
1.0
|
Multiple bugs identified during evaluation - The bugs:
- [x] Entering C in the filter for tabular data triggers the comment popup.
- [x] Detail graph to overview graph crashes CSX sometimes. The error is `Uncaught TypeError: e.connections is undefined`
- [x] Schema is sometimes out of focus when switching between graph types.
- [x] Search for something using the traditional search box . Then navigate to the workflow and just run it. It doesn't work.
- [x] No possibility of removing just one node from the graph.
|
non_process
|
multiple bugs identified during evaluation the bugs entering c in the filter for tabular data triggers the comment popup detail graph to overview graph crashes csx sometimes the error is uncaught typeerror e connections is undefined schema is sometimes out of focus when switching between graph types search for something using the traditional search box then navigate to the workflow and just run it it doesn t work no possibility of removing just one node from the graph
| 0
|
296,269
| 22,293,470,872
|
IssuesEvent
|
2022-06-12 18:01:53
|
RoyalDonkey/put-se-sqc
|
https://api.github.com/repos/RoyalDonkey/put-se-sqc
|
closed
|
As a developer of analyst tools, I have access to a compact documentation of REST API requests available
|
documentation
|
- ship REST end-user documentation with the project
|
1.0
|
As a developer of analyst tools, I have access to a compact documentation of REST API requests available - - ship REST end-user documentation with the project
|
non_process
|
as a developer of analyst tools i have access to a compact documentation of rest api requests available ship rest end user documentation with the project
| 0
|
265,873
| 23,206,830,438
|
IssuesEvent
|
2022-08-02 06:29:40
|
Uuvana-Studios/longvinter-windows-client
|
https://api.github.com/repos/Uuvana-Studios/longvinter-windows-client
|
closed
|
์ง์ ์๋ ์์๊ฐ ์ด๋ฆฌ์ง ์์ต๋๋ค.
|
Bug Not Tested
|
**Describe the bug**
My box was locked up after my house was updated.
I can't clean it up or take it out.
It contains my precious things.
Please create a new box and move it.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See an error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
**Desktop (please complete the following information):**
- OS: [e.g. Windows]
- Game Version [e.g. 1.0]
- Steam Version [e.g. 1.0]
**Additional context**
Add any other context about the problem here.
|
1.0
|
์ง์ ์๋ ์์๊ฐ ์ด๋ฆฌ์ง ์์ต๋๋ค. - **Describe the bug**
My box was locked up after my house was updated.
I can't clean it up or take it out.
It contains my precious things.
Please create a new box and move it.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See an error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
**Desktop (please complete the following information):**
- OS: [e.g. Windows]
- Game Version [e.g. 1.0]
- Steam Version [e.g. 1.0]
**Additional context**
Add any other context about the problem here.
|
non_process
|
์ง์ ์๋ ์์๊ฐ ์ด๋ฆฌ์ง ์์ต๋๋ค describe the bug my box was locked up after my house was updated i can t clean it up or take it out it contains my precious things please create a new box and move it to reproduce steps to reproduce the behavior go to click on scroll down to see an error expected behavior a clear and concise description of what you expected to happen screenshots desktop please complete the following information os game version steam version additional context add any other context about the problem here
| 0
|
17,275
| 23,060,122,506
|
IssuesEvent
|
2022-07-25 09:10:34
|
MicrosoftDocs/azure-devops-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-devops-docs
|
closed
|
How to access a variable defined in matrix strategy in expression?
|
doc-enhancement devops/prod needs-more-info cba Pri2 devops-cicd-process/tech
|
I want to define a new variable based on values defined in matrix strategy. However it looks neither compile time nor runtime expression could get the value correctly.
The following snippet wants to define two booleans exp1/exp2 based on whether 'configuration' is 'Release'. 'configuration' is defined in the matrix strategy.
```
- job: WindowsSampleApp
displayName: 'Sample'
strategy:
matrix:
Release x64:
configuration: 'Release'
platform: 'x64'
maxParallel: 8
continueOnError: false
pool:
vmImage: "windows-2019"
workspace:
clean: all
timeoutInMinutes: 240
variables:
exp1: ${{ eq(variables.configuration, 'Release') }}
exp2: $[ eq(variables.configuration, 'Release') ]
raw1: ${{ variables.configuration }}
raw2: $[ variables.configuration ]
raw3: $(configuration)
steps:
- task: PowerShell@2
displayName: 'Dump variable'
inputs:
targetType: inline
script: |
Write-Host "exp1:" $env:exp1
Write-Host "exp2:" $env:exp2
Write-Host "raw1:" $env:raw1
Write-Host "raw2:" $env:raw2
Write-Host "raw3:" $env:raw3
errorActionPreference: 'stop'
failOnStderr: true
```
Output:
```
exp1: False
exp2: False
raw1:
raw2:
raw3: Release
```
Any idea what is the right way to do this except also defining exp1/exp2 in matrix strategy?
---
#### Document Details
โ *Do not edit this section. It is required for docs.microsoft.com โ GitHub issue linking.*
* ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
* Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
* Content: [Expressions - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops)
* Content Source: [docs/pipelines/process/expressions.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/expressions.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
1.0
|
How to access a variable defined in matrix strategy in expression? -
I want to define a new variable based on values defined in matrix strategy. However it looks neither compile time nor runtime expression could get the value correctly.
The following snippet wants to define two booleans exp1/exp2 based on whether 'configuration' is 'Release'. 'configuration' is defined in the matrix strategy.
```
- job: WindowsSampleApp
displayName: 'Sample'
strategy:
matrix:
Release x64:
configuration: 'Release'
platform: 'x64'
maxParallel: 8
continueOnError: false
pool:
vmImage: "windows-2019"
workspace:
clean: all
timeoutInMinutes: 240
variables:
exp1: ${{ eq(variables.configuration, 'Release') }}
exp2: $[ eq(variables.configuration, 'Release') ]
raw1: ${{ variables.configuration }}
raw2: $[ variables.configuration ]
raw3: $(configuration)
steps:
- task: PowerShell@2
displayName: 'Dump variable'
inputs:
targetType: inline
script: |
Write-Host "exp1:" $env:exp1
Write-Host "exp2:" $env:exp2
Write-Host "raw1:" $env:raw1
Write-Host "raw2:" $env:raw2
Write-Host "raw3:" $env:raw3
errorActionPreference: 'stop'
failOnStderr: true
```
Output:
```
exp1: False
exp2: False
raw1:
raw2:
raw3: Release
```
Any idea what is the right way to do this except also defining exp1/exp2 in matrix strategy?
---
#### Document Details
โ *Do not edit this section. It is required for docs.microsoft.com โ GitHub issue linking.*
* ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
* Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
* Content: [Expressions - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops)
* Content Source: [docs/pipelines/process/expressions.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/expressions.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
process
|
how to access a variable defined in matrix strategy in expression i want to define a new variable based on values defined in matrix strategy however it looks neither compile time nor runtime expression could get the value correctly the following snippet wants to define two booleans based on whether configuration is release configuration is defined in the matrix strategy job windowssampleapp displayname sample strategy matrix release configuration release platform maxparallel continueonerror false pool vmimage windows workspace clean all timeoutinminutes variables eq variables configuration release variables configuration configuration steps task powershell displayname dump variable inputs targettype inline script write host env write host env write host env write host env write host env erroractionpreference stop failonstderr true output false false release any idea what is the right way to do this except also defining in matrix strategy document details โ do not edit this section it is required for docs microsoft com โ github issue linking id version independent id content content source product devops technology devops cicd process github login juliakm microsoft alias jukullam
| 1
|
144,401
| 13,104,914,313
|
IssuesEvent
|
2020-08-04 11:11:14
|
kubeedge/kubeedge
|
https://api.github.com/repos/kubeedge/kubeedge
|
closed
|
docs: Add guidance for submitting changes to github and get accepted
|
kind/documentation lifecycle/stale
|
<!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Describe the workflow that we apply for checking-in changes.
**Why is this needed**:
Useful to new contributors.
ref: https://github.com/kubeedge/kubeedge/pull/506#issuecomment-492476244
|
1.0
|
docs: Add guidance for submitting changes to github and get accepted - <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Describe the workflow that we apply for checking-in changes.
**Why is this needed**:
Useful to new contributors.
ref: https://github.com/kubeedge/kubeedge/pull/506#issuecomment-492476244
|
non_process
|
docs add guidance for submitting changes to github and get accepted what would you like to be added describe the workflow that we apply for checking in changes why is this needed useful to new contributors ref
| 0
|
389,208
| 11,499,138,252
|
IssuesEvent
|
2020-02-12 13:25:14
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www.whatsapp.com - 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 -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/48099 -->
**URL**: https://www.whatsapp.com/
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Design is broken
**Description**: web page is not opening instead something other
**Steps to Reproduce**:
<details><summary>View the screenshot</summary><img alt='Screenshot' src='https://webcompat.com/uploads/2020/2/92efc6a8-63fb-4e81-8ceb-b9239cd9890e.jpeg'></details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200129152609</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/2/2f84c92c-0a53-4580-bd34-c8d3e51fa670)
_From [webcompat.com](https://webcompat.com/) with โค๏ธ_
|
1.0
|
www.whatsapp.com - 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 -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/48099 -->
**URL**: https://www.whatsapp.com/
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Design is broken
**Description**: web page is not opening instead something other
**Steps to Reproduce**:
<details><summary>View the screenshot</summary><img alt='Screenshot' src='https://webcompat.com/uploads/2020/2/92efc6a8-63fb-4e81-8ceb-b9239cd9890e.jpeg'></details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200129152609</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/2/2f84c92c-0a53-4580-bd34-c8d3e51fa670)
_From [webcompat.com](https://webcompat.com/) with โค๏ธ_
|
non_process
|
design is broken url browser version firefox mobile operating system android tested another browser yes problem type design is broken description web page is not opening instead something other steps to reproduce view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with โค๏ธ
| 0
|
5,544
| 3,238,264,461
|
IssuesEvent
|
2015-10-14 15:30:21
|
Alofoxx/club-websystem
|
https://api.github.com/repos/Alofoxx/club-websystem
|
closed
|
Add filtering hooks into the django-admin pages
|
improve existing code
|
Each club should only be able to see and edit its own stuff:
* No officer should be able to delete a user/member
* InfoSec officers should only be able to see/modify members who have a membership linking them to the InfoSec club
* Do the same for the other tables
|
1.0
|
Add filtering hooks into the django-admin pages - Each club should only be able to see and edit its own stuff:
* No officer should be able to delete a user/member
* InfoSec officers should only be able to see/modify members who have a membership linking them to the InfoSec club
* Do the same for the other tables
|
non_process
|
add filtering hooks into the django admin pages each club should only be able to see and edit its own stuff no officer should be able to delete a user member infosec officers should only be able to see modify members who have a membership linking them to the infosec club do the same for the other tables
| 0
|
269,834
| 23,470,525,230
|
IssuesEvent
|
2022-08-16 21:17:12
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: version/mixed/nodes=5 failed
|
C-test-failure O-robot O-roachtest release-blocker T-kv branch-release-22.1
|
roachtest.version/mixed/nodes=5 [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5921543&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5921543&tab=artifacts#/version/mixed/nodes=5) on release-22.1 @ [60293f9fdb49de3c0e0a7ad4bf49f92cec05b1a5](https://github.com/cockroachdb/cockroach/commits/60293f9fdb49de3c0e0a7ad4bf49f92cec05b1a5):
```
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (2) cluster.Stage
Wraps: (3) COMMAND_PROBLEM
Wraps: (4) Node 3. Command with error:
| ``````
|
| tmpdir="$(mktemp -d /tmp/cockroach-release.XXX)" && \
| dir=. && \
| curl -f -s -S -o- https://s3.amazonaws.com/binaries.cockroachdb.com/cockroach-v21.2.13.linux-amd64.tgz | tar xfz - -C "${tmpdir}" --strip-components 1 && \
| mv ${tmpdir}/cockroach ${dir}/cockroach && \
| mkdir -p ${dir}/lib && \
| if [ -d ${tmpdir}/lib ]; then mv ${tmpdir}/lib/* ${dir}/lib; fi && \
| chmod 755 ${dir}/cockroach
|
| ``````
Wraps: (5) exit status 2
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) errors.Cmd (4) *hintdetail.withDetail (5) *exec.ExitError
monitor.go:127,version.go:214,version.go:227,test_runner.go:883: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerVersion.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/version.go:214
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerVersion.func2
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/version.go:227
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:883
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| main/pkg/cmd/roachtest/monitor.go:80
| runtime.doInit
| GOROOT/src/runtime/proc.go:6498
| runtime.main
| GOROOT/src/runtime/proc.go:238
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*version/mixed/nodes=5.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-18216
|
2.0
|
roachtest: version/mixed/nodes=5 failed - roachtest.version/mixed/nodes=5 [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5921543&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5921543&tab=artifacts#/version/mixed/nodes=5) on release-22.1 @ [60293f9fdb49de3c0e0a7ad4bf49f92cec05b1a5](https://github.com/cockroachdb/cockroach/commits/60293f9fdb49de3c0e0a7ad4bf49f92cec05b1a5):
```
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (2) cluster.Stage
Wraps: (3) COMMAND_PROBLEM
Wraps: (4) Node 3. Command with error:
| ``````
|
| tmpdir="$(mktemp -d /tmp/cockroach-release.XXX)" && \
| dir=. && \
| curl -f -s -S -o- https://s3.amazonaws.com/binaries.cockroachdb.com/cockroach-v21.2.13.linux-amd64.tgz | tar xfz - -C "${tmpdir}" --strip-components 1 && \
| mv ${tmpdir}/cockroach ${dir}/cockroach && \
| mkdir -p ${dir}/lib && \
| if [ -d ${tmpdir}/lib ]; then mv ${tmpdir}/lib/* ${dir}/lib; fi && \
| chmod 755 ${dir}/cockroach
|
| ``````
Wraps: (5) exit status 2
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) errors.Cmd (4) *hintdetail.withDetail (5) *exec.ExitError
monitor.go:127,version.go:214,version.go:227,test_runner.go:883: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerVersion.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/version.go:214
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerVersion.func2
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/version.go:227
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:883
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| main/pkg/cmd/roachtest/monitor.go:80
| runtime.doInit
| GOROOT/src/runtime/proc.go:6498
| runtime.main
| GOROOT/src/runtime/proc.go:238
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*version/mixed/nodes=5.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-18216
|
non_process
|
roachtest version mixed nodes failed roachtest version mixed nodes with on release runtime goexit goroot src runtime asm s wraps cluster stage wraps command problem wraps node command with error tmpdir mktemp d tmp cockroach release xxx dir curl f s s o tar xfz c tmpdir strip components mv tmpdir cockroach dir cockroach mkdir p dir lib if then mv tmpdir lib dir lib fi chmod dir cockroach wraps exit status error types withstack withstack errutil withprefix errors cmd hintdetail withdetail exec exiterror monitor go version go version go test runner go monitor failure monitor task failed t fatal was called attached stack trace stack trace main monitorimpl waite main pkg cmd roachtest monitor go main monitorimpl wait main pkg cmd roachtest monitor go github com cockroachdb cockroach pkg cmd roachtest tests registerversion github com cockroachdb cockroach pkg cmd roachtest tests version go github com cockroachdb cockroach pkg cmd roachtest tests registerversion github com cockroachdb cockroach pkg cmd roachtest tests version go main testrunner runtest main pkg cmd roachtest test runner go wraps monitor failure wraps attached stack trace stack trace main monitorimpl wait main pkg cmd roachtest monitor go wraps monitor task failed wraps attached stack trace stack trace main init main pkg cmd roachtest monitor go runtime doinit goroot src runtime proc go runtime main goroot src runtime proc go runtime goexit goroot src runtime asm s wraps t fatal was called error types withstack withstack errutil withprefix withstack withstack errutil withprefix withstack withstack errutil leaferror help see see cc cockroachdb kv triage jira issue crdb
| 0
|
381,292
| 11,275,903,623
|
IssuesEvent
|
2020-01-14 21:50:14
|
googleapis/java-iot
|
https://api.github.com/repos/googleapis/java-iot
|
closed
|
Synthesis failed for java-iot
|
autosynth failure priority: p1 type: bug
|
Hello! Autosynth couldn't regenerate java-iot. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
main()
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
text=True,
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'
```
Google internal developers can see the full log [here](https://sponge/482a7766-2134-4c8a-887d-f6441089f633).
|
1.0
|
Synthesis failed for java-iot - Hello! Autosynth couldn't regenerate java-iot. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
main()
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
text=True,
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'
```
Google internal developers can see the full log [here](https://sponge/482a7766-2134-4c8a-887d-f6441089f633).
|
non_process
|
synthesis failed for java iot hello autosynth couldn t regenerate java iot broken heart here s the output from running synth py cloning into working repo switched to branch autosynth traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src git autosynth autosynth synth py line in main file tmpfs src git autosynth autosynth synth py line in main last synth commit hash get last metadata commit args metadata path file tmpfs src git autosynth autosynth synth py line in get last metadata commit text true file home kbuilder pyenv versions lib subprocess py line in run with popen popenargs kwargs as process typeerror init got an unexpected keyword argument text google internal developers can see the full log
| 0
|
344,715
| 30,754,729,431
|
IssuesEvent
|
2023-07-29 00:15:50
|
tendermint/tendermint
|
https://api.github.com/repos/tendermint/tendermint
|
closed
|
consensus: revise testing
|
C:consensus T:test stale
|
<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < โบ
v โฐ Thanks for opening an issue! โฐ
v Before smashing the submit button please review the template.
v Word of caution: poorly thought-out proposals may be rejected
v without deliberation
โบ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Summary
The consensus reactor is quite an unwieldy beast. In many ways it feels like a reactor within a reactor, with state having methods like `receiveRoutine` and `handleMsg`. It has 4 channels, a WAL, and an event bus all carefully interwoven with timeouts. If understanding the evidence reactor might be the equivalent of poking at the engine of a yamaha 125, then understanding the consensus reactor is like popping the hood on a boeing 747. It's a complex piece of machinery. This invariably makes is difficult to test. The predecessors who wrote most of the consensus test suite did a pretty good job but there is still quite a bit of work that needs to be done:
- The slashing test suite is commented out
- Some locking tests and the catchup test suite are missing
- Byzantine tests are scarce (and hard to write)
- Network partition tests and clock distorting (although perhaps this is outside of consensus)
We should look at fleshing out all these tests, review if any others could be improved on and perhaps better organise the tests (`state_test.go` is already 1900 lines)
Furthermore, the testing relies on the eventbus to ensure that the internal state machine processes occur as expected (which we can't be sure has the desired behavior when looking from the outside). This also has little control over the timing of events (i.e. it's hard to test how the locking mechanism may behave with timeouts) and requires a lot of overwriting of consensus logic to squeeze out the right situation. What I think might benefit the consensus tests is a complimentary vote-centric testing framework, which wraps around, one or possibly many consensus reactors, leaving them untouched and intact and merely focusing on their endpoints. The framework would be designed to fire specific permutations of votes (proposals, prevotes and precommits) and listen to how the reactor/s react/s. This could then more easily mock various network situations and could be thus considered more high level.
Would be happy to hear others input about how we can improve testing
____
#### For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged
- [ ] Contributor assigned/self-assigned
|
1.0
|
consensus: revise testing - <!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < โบ
v โฐ Thanks for opening an issue! โฐ
v Before smashing the submit button please review the template.
v Word of caution: poorly thought-out proposals may be rejected
v without deliberation
โบ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Summary
The consensus reactor is quite an unwieldy beast. In many ways it feels like a reactor within a reactor, with state having methods like `receiveRoutine` and `handleMsg`. It has 4 channels, a WAL, and an event bus all carefully interwoven with timeouts. If understanding the evidence reactor might be the equivalent of poking at the engine of a yamaha 125, then understanding the consensus reactor is like popping the hood on a boeing 747. It's a complex piece of machinery. This invariably makes is difficult to test. The predecessors who wrote most of the consensus test suite did a pretty good job but there is still quite a bit of work that needs to be done:
- The slashing test suite is commented out
- Some locking tests and the catchup test suite are missing
- Byzantine tests are scarce (and hard to write)
- Network partition tests and clock distorting (although perhaps this is outside of consensus)
We should look at fleshing out all these tests, review if any others could be improved on and perhaps better organise the tests (`state_test.go` is already 1900 lines)
Furthermore, the testing relies on the eventbus to ensure that the internal state machine processes occur as expected (which we can't be sure has the desired behavior when looking from the outside). This also has little control over the timing of events (i.e. it's hard to test how the locking mechanism may behave with timeouts) and requires a lot of overwriting of consensus logic to squeeze out the right situation. What I think might benefit the consensus tests is a complimentary vote-centric testing framework, which wraps around, one or possibly many consensus reactors, leaving them untouched and intact and merely focusing on their endpoints. The framework would be designed to fire specific permutations of votes (proposals, prevotes and precommits) and listen to how the reactor/s react/s. This could then more easily mock various network situations and could be thus considered more high level.
Would be happy to hear others input about how we can improve testing
____
#### For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged
- [ ] Contributor assigned/self-assigned
|
non_process
|
consensus revise testing โบ v โฐ thanks for opening an issue โฐ v before smashing the submit button please review the template v word of caution poorly thought out proposals may be rejected v without deliberation โบ summary the consensus reactor is quite an unwieldy beast in many ways it feels like a reactor within a reactor with state having methods like receiveroutine and handlemsg it has channels a wal and an event bus all carefully interwoven with timeouts if understanding the evidence reactor might be the equivalent of poking at the engine of a yamaha then understanding the consensus reactor is like popping the hood on a boeing it s a complex piece of machinery this invariably makes is difficult to test the predecessors who wrote most of the consensus test suite did a pretty good job but there is still quite a bit of work that needs to be done the slashing test suite is commented out some locking tests and the catchup test suite are missing byzantine tests are scarce and hard to write network partition tests and clock distorting although perhaps this is outside of consensus we should look at fleshing out all these tests review if any others could be improved on and perhaps better organise the tests state test go is already lines furthermore the testing relies on the eventbus to ensure that the internal state machine processes occur as expected which we can t be sure has the desired behavior when looking from the outside this also has little control over the timing of events i e it s hard to test how the locking mechanism may behave with timeouts and requires a lot of overwriting of consensus logic to squeeze out the right situation what i think might benefit the consensus tests is a complimentary vote centric testing framework which wraps around one or possibly many consensus reactors leaving them untouched and intact and merely focusing on their endpoints the framework would be designed to fire specific permutations of votes proposals prevotes and precommits and listen to how the reactor s react s this could then more easily mock various network situations and could be thus considered more high level would be happy to hear others input about how we can improve testing for admin use not duplicate issue appropriate labels applied appropriate contributors tagged contributor assigned self assigned
| 0
|
2,512
| 5,284,630,778
|
IssuesEvent
|
2017-02-08 01:04:16
|
jlm2017/jlm-video-subtitles
|
https://api.github.com/repos/jlm2017/jlm-video-subtitles
|
closed
|
#RDLS17 : THรO, MAYOTTE, HOLOGRAMME, YOUTUBE, ROUMANIE, CORRUPTION, FRANCE INSOUMISE
|
Language: French Process: [4] Ready for review (2)
|
# Video title
#RDLS17 : THรO, MAYOTTE, HOLOGRAMME, YOUTUBE, ROUMANIE, CORRUPTION, FRANCE INSOUMISE
# URL
https://www.youtube.com/watch?v=579gZ1fsLVY
# Youtube subtitles language
Franรงais
# Duration
28:55
# Subtitles URL
https://www.youtube.com/timedtext_editor?bl=vmp&v=579gZ1fsLVY&ui=hd&action_mde_edit_form=1&ref=player&tab=captions&lang=fr&captions-r=1
|
1.0
|
#RDLS17 : THรO, MAYOTTE, HOLOGRAMME, YOUTUBE, ROUMANIE, CORRUPTION, FRANCE INSOUMISE - # Video title
#RDLS17 : THรO, MAYOTTE, HOLOGRAMME, YOUTUBE, ROUMANIE, CORRUPTION, FRANCE INSOUMISE
# URL
https://www.youtube.com/watch?v=579gZ1fsLVY
# Youtube subtitles language
Franรงais
# Duration
28:55
# Subtitles URL
https://www.youtube.com/timedtext_editor?bl=vmp&v=579gZ1fsLVY&ui=hd&action_mde_edit_form=1&ref=player&tab=captions&lang=fr&captions-r=1
|
process
|
thรฉo mayotte hologramme youtube roumanie corruption france insoumise video title thรฉo mayotte hologramme youtube roumanie corruption france insoumise url youtube subtitles language franรงais duration subtitles url
| 1
|
19,704
| 26,053,068,959
|
IssuesEvent
|
2022-12-22 21:00:19
|
aolabNeuro/analyze
|
https://api.github.com/repos/aolabNeuro/analyze
|
closed
|
Return data and metadata in proc_() functions
|
enhancement preprocessing
|
See https://github.com/aolabNeuro/analyze/pull/227#pullrequestreview-854852350_
Similar return statements could be added to other preproc functions
|
1.0
|
Return data and metadata in proc_() functions - See https://github.com/aolabNeuro/analyze/pull/227#pullrequestreview-854852350_
Similar return statements could be added to other preproc functions
|
process
|
return data and metadata in proc functions see similar return statements could be added to other preproc functions
| 1
|
5,527
| 8,387,380,003
|
IssuesEvent
|
2018-10-09 00:03:03
|
nion-software/nionswift
|
https://api.github.com/repos/nion-software/nionswift
|
opened
|
Need ability to apply operations to sequences, collections, or non-display data.
|
f - computations f - processing level - difficult p2 - high type - enhancement w4 - ready
|
For instance, a collection of 256x256 x 256x256 should have option to calculate FFT based on display (produces a single 256x256 image) or on each datum (producing 256x256 x 256x256 data), etc.
|
1.0
|
Need ability to apply operations to sequences, collections, or non-display data. - For instance, a collection of 256x256 x 256x256 should have option to calculate FFT based on display (produces a single 256x256 image) or on each datum (producing 256x256 x 256x256 data), etc.
|
process
|
need ability to apply operations to sequences collections or non display data for instance a collection of x should have option to calculate fft based on display produces a single image or on each datum producing x data etc
| 1
|
2,233
| 5,082,330,923
|
IssuesEvent
|
2016-12-29 15:08:14
|
sysown/proxysql
|
https://api.github.com/repos/sysown/proxysql
|
closed
|
ProxySQL might writes on the slaves after `select @@....` query
|
bug QUERY PROCESSOR ROUTING
|
Hi,
Here are my rules:
```
INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight,max_replication_lag) VALUES ('x.x.x.55',600,3306,1000,60);
INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight,max_replication_lag) VALUES ('x.x.x.167',601,3306,1000,60);
INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight,max_replication_lag) VALUES ('x.x.x.175',601,3306,1000,0);
INSERT INTO mysql_replication_hostgroups VALUES (600,601,'');
LOAD MYSQL SERVERS TO RUNTIME; SAVE MYSQL SERVERS TO DISK;
insert into mysql_query_rules (username,destination_hostgroup,active) values('testuser_w',600,1);
insert into mysql_query_rules (username,destination_hostgroup,active) values('testuser_r',601,1);
insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest) values('testuser_rw',600,1,3,'^SELECT');
LOAD MYSQL QUERY RULES TO RUNTIME;SAVE MYSQL QUERY RULES TO DISK;
insert into mysql_users (username,password,active,default_hostgroup,default_schema,transaction_persistent) values ('testuser_w','XXXX.',1,600,'test',1);
insert into mysql_users (username,password,active,default_hostgroup,default_schema,transaction_persistent) values ('testuser_r','XXXX.',1,601,'test',1);
insert into mysql_users (username,password,active,default_hostgroup,default_schema,transaction_persistent) values ('testuser_rw','XXXX.',1,600,'test',1);
LOAD MYSQL USERS TO RUNTIME;SAVE MYSQL USERS TO DISK;
```
The slave servers are in read_only mode but the testuser_rw has ALL privileges.
After I connected the MySQL servers trough ProxySQL:
`mysql -h127.0.0.1 -utestuser_rw -pXXXX. -P6033`
I run `select @@hostname` to check where I am. ProxySQL redirected to me a slave server, which is in hostgroup 601. After this I run the following query:
`update test.sbtest1 set c='1' where id=1;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1 Changed: 1 Warnings: 0`
It was successful but when I checked the servers I was realised it was not executed on the master it was executed on the slave! I repeated the same steps multiple times and I was able to write the slaves!
But when I skipped the `select @@hostname` query the update was executed on the mater as we expected that.
So that means when you run a `select @@....` query after the writes executed on the slaves not on the master! If the user does not have ALL privileges the writes won't happen but still, ProxySQL tries to write on the slaves!
I think this is a serious bug! I already contacted with @renecannao.
|
1.0
|
ProxySQL might writes on the slaves after `select @@....` query - Hi,
Here are my rules:
```
INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight,max_replication_lag) VALUES ('x.x.x.55',600,3306,1000,60);
INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight,max_replication_lag) VALUES ('x.x.x.167',601,3306,1000,60);
INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight,max_replication_lag) VALUES ('x.x.x.175',601,3306,1000,0);
INSERT INTO mysql_replication_hostgroups VALUES (600,601,'');
LOAD MYSQL SERVERS TO RUNTIME; SAVE MYSQL SERVERS TO DISK;
insert into mysql_query_rules (username,destination_hostgroup,active) values('testuser_w',600,1);
insert into mysql_query_rules (username,destination_hostgroup,active) values('testuser_r',601,1);
insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest) values('testuser_rw',600,1,3,'^SELECT');
LOAD MYSQL QUERY RULES TO RUNTIME;SAVE MYSQL QUERY RULES TO DISK;
insert into mysql_users (username,password,active,default_hostgroup,default_schema,transaction_persistent) values ('testuser_w','XXXX.',1,600,'test',1);
insert into mysql_users (username,password,active,default_hostgroup,default_schema,transaction_persistent) values ('testuser_r','XXXX.',1,601,'test',1);
insert into mysql_users (username,password,active,default_hostgroup,default_schema,transaction_persistent) values ('testuser_rw','XXXX.',1,600,'test',1);
LOAD MYSQL USERS TO RUNTIME;SAVE MYSQL USERS TO DISK;
```
The slave servers are in read_only mode but the testuser_rw has ALL privileges.
After I connected the MySQL servers trough ProxySQL:
`mysql -h127.0.0.1 -utestuser_rw -pXXXX. -P6033`
I run `select @@hostname` to check where I am. ProxySQL redirected to me a slave server, which is in hostgroup 601. After this I run the following query:
`update test.sbtest1 set c='1' where id=1;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1 Changed: 1 Warnings: 0`
It was successful but when I checked the servers I was realised it was not executed on the master it was executed on the slave! I repeated the same steps multiple times and I was able to write the slaves!
But when I skipped the `select @@hostname` query the update was executed on the mater as we expected that.
So that means when you run a `select @@....` query after the writes executed on the slaves not on the master! If the user does not have ALL privileges the writes won't happen but still, ProxySQL tries to write on the slaves!
I think this is a serious bug! I already contacted with @renecannao.
|
process
|
proxysql might writes on the slaves after select query hi here are my rules insert into mysql servers hostname hostgroup id port weight max replication lag values x x x insert into mysql servers hostname hostgroup id port weight max replication lag values x x x insert into mysql servers hostname hostgroup id port weight max replication lag values x x x insert into mysql replication hostgroups values load mysql servers to runtime save mysql servers to disk insert into mysql query rules username destination hostgroup active values testuser w insert into mysql query rules username destination hostgroup active values testuser r insert into mysql query rules username destination hostgroup active retries match digest values testuser rw select load mysql query rules to runtime save mysql query rules to disk insert into mysql users username password active default hostgroup default schema transaction persistent values testuser w xxxx test insert into mysql users username password active default hostgroup default schema transaction persistent values testuser r xxxx test insert into mysql users username password active default hostgroup default schema transaction persistent values testuser rw xxxx test load mysql users to runtime save mysql users to disk the slave servers are in read only mode but the testuser rw has all privileges after i connected the mysql servers trough proxysql mysql utestuser rw pxxxx i run select hostname to check where i am proxysql redirected to me a slave server which is in hostgroup after this i run the following query update test set c where id query ok row affected sec rows matched changed warnings it was successful but when i checked the servers i was realised it was not executed on the master it was executed on the slave i repeated the same steps multiple times and i was able to write the slaves but when i skipped the select hostname query the update was executed on the mater as we expected that so that means when you run a select query after the writes executed on the slaves not on the master if the user does not have all privileges the writes won t happen but still proxysql tries to write on the slaves i think this is a serious bug i already contacted with renecannao
| 1
|
129,198
| 27,417,322,014
|
IssuesEvent
|
2023-03-01 14:35:53
|
Leafwing-Studios/Emergence
|
https://api.github.com/repos/Leafwing-Studios/Emergence
|
opened
|
`change_structure_material` is a mess of non-local data
|
code quality
|
Rather than relying on a global lookup, we should just store the material to use (or later, what effects to use) on the parent entity.
|
1.0
|
`change_structure_material` is a mess of non-local data - Rather than relying on a global lookup, we should just store the material to use (or later, what effects to use) on the parent entity.
|
non_process
|
change structure material is a mess of non local data rather than relying on a global lookup we should just store the material to use or later what effects to use on the parent entity
| 0
|
3,608
| 6,652,124,436
|
IssuesEvent
|
2017-09-28 23:09:39
|
IIIF/api
|
https://api.github.com/repos/IIIF/api
|
closed
|
Clarify release process for patch level updates
|
process
|
... that a community call is sufficient review for the "open meeting" requirement.
|
1.0
|
Clarify release process for patch level updates -
... that a community call is sufficient review for the "open meeting" requirement.
|
process
|
clarify release process for patch level updates that a community call is sufficient review for the open meeting requirement
| 1
|
194,378
| 15,421,807,854
|
IssuesEvent
|
2021-03-05 13:34:50
|
PyFE/FE-R
|
https://api.github.com/repos/PyFE/FE-R
|
closed
|
Black-Scholes for FX options
|
documentation enhancement
|
Add FX option (Garman-Kohlhagen model) documentation to `BlackScholesPrice`
`intr`: domestic interest rate
`divr`: domestic interest rate
https://en.wikipedia.org/wiki/Foreign_exchange_option
|
1.0
|
Black-Scholes for FX options - Add FX option (Garman-Kohlhagen model) documentation to `BlackScholesPrice`
`intr`: domestic interest rate
`divr`: domestic interest rate
https://en.wikipedia.org/wiki/Foreign_exchange_option
|
non_process
|
black scholes for fx options add fx option garman kohlhagen model documentation to blackscholesprice intr domestic interest rate divr domestic interest rate
| 0
|
15,356
| 19,579,826,025
|
IssuesEvent
|
2022-01-04 19:42:32
|
opensearch-project/OpenSearch-Dashboards
|
https://api.github.com/repos/opensearch-project/OpenSearch-Dashboards
|
opened
|
2.0 compatibility with OpenSearch 1.x
|
versioning backwards-compatibility v2.0.0
|
Our plan is to remain compatible with 1.x when we bump to 2.0.
|
True
|
2.0 compatibility with OpenSearch 1.x - Our plan is to remain compatible with 1.x when we bump to 2.0.
|
non_process
|
compatibility with opensearch x our plan is to remain compatible with x when we bump to
| 0
|
12,705
| 15,079,261,977
|
IssuesEvent
|
2021-02-05 09:54:54
|
e4exp/paper_manager_abstract
|
https://api.github.com/repos/e4exp/paper_manager_abstract
|
opened
|
Switch Transformers: Scaling to Trillion Parameter Models with Simple and Efficient Sparsity
|
2021 Mixture of Experts Natural Language Processing _read_later
|
* https://arxiv.org/abs/2101.03961
* 2021
ใใฃใผใใฉใผใใณใฐใงใฏใใขใใซใฏ้ๅธธใใในใฆใฎๅ
ฅๅใซๅฏพใใฆๅใใใฉใกใผใฟใๅๅฉ็จใใพใใ
Mixture of Experts (MoE)ใฏใใใ็ก่ฆใใฆใๅ
ฅๅใใใไพใใจใซ็ฐใชใใใฉใกใผใฟใ้ธๆใใพใใ
ใใฎ็ตๆใ้ๅธธใซๅคใใฎใใฉใกใผใฟใๆใคใใพใฐใใซๅไฝใใใขใใซใใงใใใใใพใใใ่จ็ฎใณในใใฏไธๅฎใงใใ
ใใใใMoEใฏใใใคใใฎๆณจ็ฎใในใๆๅใๅใใฆใใใซใใใใใใใๅบใๆฎๅใใใซใฏ่ค้ใใ้ไฟกใณในใใใใฌใผใใณใฐใฎไธๅฎๅฎใใๅฆจใใจใชใฃใฆใใพใใ
ๆใ
ใฏใMoEใซใผใใฃใณใฐใขใซใดใชใบใ ใๅ็ดๅใใ้ไฟกใจ่จ็ฎใณในใใๅๆธใใ็ดๆ็ใชๆน่ฏใขใใซใ่จญ่จใใพใใ
ๆๆกใใใใฌใผใใณใฐๆ่กใฏไธๅฎๅฎๆงใ่งฃๆถใใใฎใซๅฝน็ซใกใๅคง่ฆๆจกใชในใใผในใขใใซใๅใใฆไฝ็ฒพๅบฆ(bfloat16)ใใฉใผใใใใงใใฌใผใใณใฐใงใใใใจใ็คบใใพใใ
ๆใ
ใฏใT5-BaseใจT5-Largeใใใผในใซใใใขใใซใ่จญ่จใใๅใ่จ็ฎ่ณๆบใงๆๅคง7ๅใฎไบๅๅญฆ็ฟ้ๅบฆใๅพใใใจใใงใใพใใ
ใใใใฎๆนๅใฏๅค่จ่ช็ฐๅขใซใ้ฉ็จใใใ101ใฎๅ
จ่จ่ชใงmT5-Baseใใผใธใงใณใใใๅไธใใฆใใพใใ
ๆๅพใซใ"Colossal Clean Crawled Corpus "ไธใงๆๅคง1ๅ
ๅใฎใใฉใกใผใฟใขใใซใไบๅๅญฆ็ฟใใT5-XXLใขใใซใฎ4ๅใฎ้ๅบฆๅไธใ้ๆใใใใจใงใ็พๅจใฎ่จ่ชใขใใซใฎ่ฆๆจกใๅไธใใใฆใใพใใ
|
1.0
|
Switch Transformers: Scaling to Trillion Parameter Models with Simple and Efficient Sparsity - * https://arxiv.org/abs/2101.03961
* 2021
ใใฃใผใใฉใผใใณใฐใงใฏใใขใใซใฏ้ๅธธใใในใฆใฎๅ
ฅๅใซๅฏพใใฆๅใใใฉใกใผใฟใๅๅฉ็จใใพใใ
Mixture of Experts (MoE)ใฏใใใ็ก่ฆใใฆใๅ
ฅๅใใใไพใใจใซ็ฐใชใใใฉใกใผใฟใ้ธๆใใพใใ
ใใฎ็ตๆใ้ๅธธใซๅคใใฎใใฉใกใผใฟใๆใคใใพใฐใใซๅไฝใใใขใใซใใงใใใใใพใใใ่จ็ฎใณในใใฏไธๅฎใงใใ
ใใใใMoEใฏใใใคใใฎๆณจ็ฎใในใๆๅใๅใใฆใใใซใใใใใใใๅบใๆฎๅใใใซใฏ่ค้ใใ้ไฟกใณในใใใใฌใผใใณใฐใฎไธๅฎๅฎใใๅฆจใใจใชใฃใฆใใพใใ
ๆใ
ใฏใMoEใซใผใใฃใณใฐใขใซใดใชใบใ ใๅ็ดๅใใ้ไฟกใจ่จ็ฎใณในใใๅๆธใใ็ดๆ็ใชๆน่ฏใขใใซใ่จญ่จใใพใใ
ๆๆกใใใใฌใผใใณใฐๆ่กใฏไธๅฎๅฎๆงใ่งฃๆถใใใฎใซๅฝน็ซใกใๅคง่ฆๆจกใชในใใผในใขใใซใๅใใฆไฝ็ฒพๅบฆ(bfloat16)ใใฉใผใใใใงใใฌใผใใณใฐใงใใใใจใ็คบใใพใใ
ๆใ
ใฏใT5-BaseใจT5-Largeใใใผในใซใใใขใใซใ่จญ่จใใๅใ่จ็ฎ่ณๆบใงๆๅคง7ๅใฎไบๅๅญฆ็ฟ้ๅบฆใๅพใใใจใใงใใพใใ
ใใใใฎๆนๅใฏๅค่จ่ช็ฐๅขใซใ้ฉ็จใใใ101ใฎๅ
จ่จ่ชใงmT5-Baseใใผใธใงใณใใใๅไธใใฆใใพใใ
ๆๅพใซใ"Colossal Clean Crawled Corpus "ไธใงๆๅคง1ๅ
ๅใฎใใฉใกใผใฟใขใใซใไบๅๅญฆ็ฟใใT5-XXLใขใใซใฎ4ๅใฎ้ๅบฆๅไธใ้ๆใใใใจใงใ็พๅจใฎ่จ่ชใขใใซใฎ่ฆๆจกใๅไธใใใฆใใพใใ
|
process
|
switch transformers scaling to trillion parameter models with simple and efficient sparsity ใใฃใผใใฉใผใใณใฐใงใฏใใขใใซใฏ้ๅธธใใในใฆใฎๅ
ฅๅใซๅฏพใใฆๅใใใฉใกใผใฟใๅๅฉ็จใใพใใ mixture of experts moe ใฏใใใ็ก่ฆใใฆใๅ
ฅๅใใใไพใใจใซ็ฐใชใใใฉใกใผใฟใ้ธๆใใพใใ ใใฎ็ตๆใ้ๅธธใซๅคใใฎใใฉใกใผใฟใๆใคใใพใฐใใซๅไฝใใใขใใซใใงใใใใใพใใใ่จ็ฎใณในใใฏไธๅฎใงใใ ใใใใmoeใฏใใใคใใฎๆณจ็ฎใในใๆๅใๅใใฆใใใซใใใใใใใๅบใๆฎๅใใใซใฏ่ค้ใใ้ไฟกใณในใใใใฌใผใใณใฐใฎไธๅฎๅฎใใๅฆจใใจใชใฃใฆใใพใใ ๆใ
ใฏใmoeใซใผใใฃใณใฐใขใซใดใชใบใ ใๅ็ดๅใใ้ไฟกใจ่จ็ฎใณในใใๅๆธใใ็ดๆ็ใชๆน่ฏใขใใซใ่จญ่จใใพใใ ๆๆกใใใใฌใผใใณใฐๆ่กใฏไธๅฎๅฎๆงใ่งฃๆถใใใฎใซๅฝน็ซใกใๅคง่ฆๆจกใชในใใผในใขใใซใๅใใฆไฝ็ฒพๅบฆ ใใฉใผใใใใงใใฌใผใใณใฐใงใใใใจใ็คบใใพใใ ๆใ
ใฏใ largeใใใผในใซใใใขใใซใ่จญ่จใใ ใ ใใใใฎๆนๅใฏๅค่จ่ช็ฐๅขใซใ้ฉ็จใใใ baseใใผใธใงใณใใใๅไธใใฆใใพใใ ๆๅพใซใ colossal clean crawled corpus ใ ใ็พๅจใฎ่จ่ชใขใใซใฎ่ฆๆจกใๅไธใใใฆใใพใใ
| 1
|
785
| 3,266,542,868
|
IssuesEvent
|
2015-10-22 21:08:44
|
meteor/meteor
|
https://api.github.com/repos/meteor/meteor
|
opened
|
Streamline release process to avoid manual management of version numbers
|
feature Project:Release Process Project:Tool
|
I've been doing release management for 0.9.4, 1.1, and 1.2, and every single time we do a release we initially mess up some of the version number changes. I think this should be done automatically and should be easier to do correctly, with more checks in between. Some ideas:
1. Make sure a version number isn't decreased in a newer release (when you accidentally change `1.1.3` to `1.1.3-rc.0`, which should actually be `1.1.4-rc.0`)
2. Explicitly mark wrapper packages and make some sane strategy for them, since right now you can't combine wrapper versions and pre-release versions in the right way
3. Make the tool automatically increment numbers, with some way of indicating cases where a special version number change is necessary, for example for major version bumps
|
1.0
|
Streamline release process to avoid manual management of version numbers - I've been doing release management for 0.9.4, 1.1, and 1.2, and every single time we do a release we initially mess up some of the version number changes. I think this should be done automatically and should be easier to do correctly, with more checks in between. Some ideas:
1. Make sure a version number isn't decreased in a newer release (when you accidentally change `1.1.3` to `1.1.3-rc.0`, which should actually be `1.1.4-rc.0`)
2. Explicitly mark wrapper packages and make some sane strategy for them, since right now you can't combine wrapper versions and pre-release versions in the right way
3. Make the tool automatically increment numbers, with some way of indicating cases where a special version number change is necessary, for example for major version bumps
|
process
|
streamline release process to avoid manual management of version numbers i ve been doing release management for and and every single time we do a release we initially mess up some of the version number changes i think this should be done automatically and should be easier to do correctly with more checks in between some ideas make sure a version number isn t decreased in a newer release when you accidentally change to rc which should actually be rc explicitly mark wrapper packages and make some sane strategy for them since right now you can t combine wrapper versions and pre release versions in the right way make the tool automatically increment numbers with some way of indicating cases where a special version number change is necessary for example for major version bumps
| 1
|
203,126
| 15,350,209,421
|
IssuesEvent
|
2021-03-01 01:44:28
|
Azure/azure-sdk-for-net
|
https://api.github.com/repos/Azure/azure-sdk-for-net
|
closed
|
Azure.Communication.Common Readme issue
|
Client Communication Docs needs-team-triage test-manual-pass
|
1.
Section [link:](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/communication/Azure.Communication.Common#create-a-credential-with-a-static-token)
Suggestion: Update `clents` to `clients `
@jongio for notification.
|
1.0
|
Azure.Communication.Common Readme issue - 1.
Section [link:](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/communication/Azure.Communication.Common#create-a-credential-with-a-static-token)
Suggestion: Update `clents` to `clients `
@jongio for notification.
|
non_process
|
azure communication common readme issue section suggestion update clents to clients jongio for notification
| 0
|
17,945
| 3,653,606,188
|
IssuesEvent
|
2016-02-17 08:37:38
|
red/red
|
https://api.github.com/repos/red/red
|
closed
|
text not displayed in draw without font
|
Red status.built status.tested type.bug
|
`img` displays no text in either of these 2 examples:
```
img: draw make image! [100x100 255.255.255] [pen blue box 10x10 20x20 pen red text 20x20 "Hello, World!"]
```
```
img: draw make image! [100x100 0.0.0] [pen blue box 10x10 20x20 pen red text 20x20 "Hello, World!"]
```
|
1.0
|
text not displayed in draw without font - `img` displays no text in either of these 2 examples:
```
img: draw make image! [100x100 255.255.255] [pen blue box 10x10 20x20 pen red text 20x20 "Hello, World!"]
```
```
img: draw make image! [100x100 0.0.0] [pen blue box 10x10 20x20 pen red text 20x20 "Hello, World!"]
```
|
non_process
|
text not displayed in draw without font img displays no text in either of these examples img draw make image img draw make image
| 0
|
7,330
| 10,469,020,395
|
IssuesEvent
|
2019-09-22 17:45:17
|
produvia/ai-platform
|
https://api.github.com/repos/produvia/ai-platform
|
closed
|
Intent Classification
|
natural-language-processing task
|
# Goal(s)
- Describe how user messages should be categorized
# Input(s)
- Sentence
# Output(s)
- Category
# Objective Function(s)
- TBD
|
1.0
|
Intent Classification - # Goal(s)
- Describe how user messages should be categorized
# Input(s)
- Sentence
# Output(s)
- Category
# Objective Function(s)
- TBD
|
process
|
intent classification goal s describe how user messages should be categorized input s sentence output s category objective function s tbd
| 1
|
8,968
| 12,076,800,827
|
IssuesEvent
|
2020-04-17 08:19:30
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
v.drape - no 25D export with SpatiaLite format
|
Feedback Processing
|
hello everyone
I used v.drape for add the Z value to a SpatiaLite vector file using a raster DEM. If I use a SpatiaLite OUT format the file remaine 2D and not 25D. The issue there is not if I export a shp file or dxf too. Have you the same problem?
|
1.0
|
v.drape - no 25D export with SpatiaLite format - hello everyone
I used v.drape for add the Z value to a SpatiaLite vector file using a raster DEM. If I use a SpatiaLite OUT format the file remaine 2D and not 25D. The issue there is not if I export a shp file or dxf too. Have you the same problem?
|
process
|
v drape no export with spatialite format hello everyone i used v drape for add the z value to a spatialite vector file using a raster dem if i use a spatialite out format the file remaine and not the issue there is not if i export a shp file or dxf too have you the same problem
| 1
|
1,938
| 4,768,145,155
|
IssuesEvent
|
2016-10-26 08:09:41
|
paulkornikov/Pragonas
|
https://api.github.com/repos/paulkornikov/Pragonas
|
closed
|
Page d'accรจs aux processus
|
a-new feature processus workload I
|
pour:
- prolongation
- imputation
- rapprochement
- provision
- traces
|
1.0
|
Page d'accรจs aux processus - pour:
- prolongation
- imputation
- rapprochement
- provision
- traces
|
process
|
page d accรจs aux processus pour prolongation imputation rapprochement provision traces
| 1
|
22,026
| 30,542,078,111
|
IssuesEvent
|
2023-07-19 22:31:18
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
[MLv2] [Bug] Join `fields` generate unexpected field references
|
.metabase-lib .Team/QueryProcessor :hammer_and_wrench:
|
When selecting just a few columns from a join RHS table, MLv2 produces field references that can't be processed by the BE. For example, if we join the sample Orders table with the Products table, and only pick Products' ID and Title columns, here's how joins will look in MLv1 and MLv2:
### MLv1
```js
{
alias: "Products",
"source-table": 1,
condition: [ ... ],
fields: [
["field", 5, { "join-alias": "Products" } ],
["field", 1, { "join-alias": "Products" } ],
]
}
```
### MLv2
```js
{
alias: "Products",
"source-table": 1,
condition: [ ... ],
fields: [
["field", 5, { "base-type": "type/BigInteger" } ],
["field", 12, { "base-type": "type/Text" } ],
]
}
```
Notice the `join-alias` option is missing in MLv2, but has `base-type` options
As a result, the BE returns an error when trying to run a query with MLv2 join:
```
Cannot determine the source table or query for Field clause [:field 5 {:base-type :type/BigInteger}]
```
|
1.0
|
[MLv2] [Bug] Join `fields` generate unexpected field references - When selecting just a few columns from a join RHS table, MLv2 produces field references that can't be processed by the BE. For example, if we join the sample Orders table with the Products table, and only pick Products' ID and Title columns, here's how joins will look in MLv1 and MLv2:
### MLv1
```js
{
alias: "Products",
"source-table": 1,
condition: [ ... ],
fields: [
["field", 5, { "join-alias": "Products" } ],
["field", 1, { "join-alias": "Products" } ],
]
}
```
### MLv2
```js
{
alias: "Products",
"source-table": 1,
condition: [ ... ],
fields: [
["field", 5, { "base-type": "type/BigInteger" } ],
["field", 12, { "base-type": "type/Text" } ],
]
}
```
Notice the `join-alias` option is missing in MLv2, but has `base-type` options
As a result, the BE returns an error when trying to run a query with MLv2 join:
```
Cannot determine the source table or query for Field clause [:field 5 {:base-type :type/BigInteger}]
```
|
process
|
join fields generate unexpected field references when selecting just a few columns from a join rhs table produces field references that can t be processed by the be for example if we join the sample orders table with the products table and only pick products id and title columns here s how joins will look in and js alias products source table condition fields js alias products source table condition fields notice the join alias option is missing in but has base type options as a result the be returns an error when trying to run a query with join cannot determine the source table or query for field clause
| 1
|
203,236
| 15,358,477,398
|
IssuesEvent
|
2021-03-01 14:51:02
|
mlr-org/miesmuschel
|
https://api.github.com/repos/mlr-org/miesmuschel
|
closed
|
Autotest operators
|
Tests
|
test operate() with wrong cols, test operate() with data.table, with data.frame
|
1.0
|
Autotest operators - test operate() with wrong cols, test operate() with data.table, with data.frame
|
non_process
|
autotest operators test operate with wrong cols test operate with data table with data frame
| 0
|
16,023
| 20,188,229,519
|
IssuesEvent
|
2022-02-11 01:19:55
|
savitamittalmsft/WAS-SEC-TEST
|
https://api.github.com/repos/savitamittalmsft/WAS-SEC-TEST
|
opened
|
Design virtual networks for growth
|
WARP-Import WAF FEB 2021 Security Performance and Scalability Capacity Management Processes Security & Compliance Network Security
|
<a href="https://docs.microsoft.com/azure/architecture/framework/security/design-network-connectivity#connectivity-between-network-segments">Design virtual networks for growth</a>
<p><b>Why Consider This?</b></p>
Most organizations end up adding more resources to networks than initially planned. When this happens, IP addressing and subnetting schemes need to be refactored to accommodate the extra resources. This is a labor-intensive process. There is limited security value in creating a very large number of small subnets and then trying to map network access controls (such as security groups) to each of them.
<p><b>Context</b></p>
<p><span>A good Azure IP addressing schema provides flexibility, room for growth, and integration with on-premises networks. The schema ensures that communication works for deployed resources, minimizes public exposure of systems, and gives the organization flexibility in its network. If not properly designed, systems might not be able to communicate, and additional work will be required to remediate.</span></p>
<p><b>Suggested Actions</b></p>
<p><span>Design virtual networks and subnets for growth.</span><span><b> </b></span><span>It's</span><span><b> </b></span><span>recommend that to plan subnets based on common roles and functions that use common protocols for those roles and functions. This allows you to add resources to the subnet without needing to make changes to security groups that enforce network level access controls.</span><span /></p>
<p><b>Learn More</b></p>
<p><a href="https://docs.microsoft.com/en-us/azure/architecture/framework/Security/network-security-containment#design-virtual-network-subnet-security" target="_blank"><span>Design virtual network subnet security</span></a><span /></p><p><a href="https://docs.microsoft.com/en-us/learn/modules/design-ip-addressing-for-azure/" target="_blank"><span>Design an IP addressing schema for your Azure deployment</span></a><span /></p><p><span>"nbsp;</span></p>
|
1.0
|
Design virtual networks for growth - <a href="https://docs.microsoft.com/azure/architecture/framework/security/design-network-connectivity#connectivity-between-network-segments">Design virtual networks for growth</a>
<p><b>Why Consider This?</b></p>
Most organizations end up adding more resources to networks than initially planned. When this happens, IP addressing and subnetting schemes need to be refactored to accommodate the extra resources. This is a labor-intensive process. There is limited security value in creating a very large number of small subnets and then trying to map network access controls (such as security groups) to each of them.
<p><b>Context</b></p>
<p><span>A good Azure IP addressing schema provides flexibility, room for growth, and integration with on-premises networks. The schema ensures that communication works for deployed resources, minimizes public exposure of systems, and gives the organization flexibility in its network. If not properly designed, systems might not be able to communicate, and additional work will be required to remediate.</span></p>
<p><b>Suggested Actions</b></p>
<p><span>Design virtual networks and subnets for growth.</span><span><b> </b></span><span>It's</span><span><b> </b></span><span>recommend that to plan subnets based on common roles and functions that use common protocols for those roles and functions. This allows you to add resources to the subnet without needing to make changes to security groups that enforce network level access controls.</span><span /></p>
<p><b>Learn More</b></p>
<p><a href="https://docs.microsoft.com/en-us/azure/architecture/framework/Security/network-security-containment#design-virtual-network-subnet-security" target="_blank"><span>Design virtual network subnet security</span></a><span /></p><p><a href="https://docs.microsoft.com/en-us/learn/modules/design-ip-addressing-for-azure/" target="_blank"><span>Design an IP addressing schema for your Azure deployment</span></a><span /></p><p><span>"nbsp;</span></p>
|
process
|
design virtual networks for growth why consider this most organizations end up adding more resources to networks than initially planned when this happens ip addressing and subnetting schemes need to be refactored to accommodate the extra resources this is a labor intensive process there is limited security value in creating a very large number of small subnets and then trying to map network access controls such as security groups to each of them context a good azure ip addressing schema provides flexibility room for growth and integration with on premises networks the schema ensures that communication works for deployed resources minimizes public exposure of systems and gives the organization flexibility in its network if not properly designed systems might not be able to communicate and additional work will be required to remediate suggested actions design virtual networks and subnets for growth it s recommend that to plan subnets based on common roles and functions that use common protocols for those roles and functions this allows you to add resources to the subnet without needing to make changes to security groups that enforce network level access controls learn more design virtual network subnet security design an ip addressing schema for your azure deployment nbsp
| 1
|
632
| 3,092,114,338
|
IssuesEvent
|
2015-08-26 16:13:00
|
e-government-ua/iBP
|
https://api.github.com/repos/e-government-ua/iBP
|
opened
|
ะัะทะฝะตัะพะฒัะบ - ะะฒะตัะฝะตะฝะฝั ะณัะพะผะฐะดัะฝะธะฝะฐ ะดะพ ะผัััะบะพะณะพ ะณะพะปะพะฒะธ
|
in process of creating
|
ะะปะณะพัะธัะผ:
https://drive.google.com/file/d/0B1NO5RoNKst7NXFIanhIR0hFY2x0U0lxbGFRbFA5T1Y3RERZ/view?usp=sharing
ะะฐัะฒะฐ:
https://drive.google.com/file/d/0B1NO5RoNKst7MlZlOUNQbUE2eFZLcGxQbS1UWlpmYm1BcjhR/view?usp=sharing
ะัะพัั ะทะฒะตัะฝััะธ ะพัะพะฑะปะธะฒั ัะฒะฐะณั ะฝะฐ ัะฐะบั ัะฐะบัะพัะธ:
1. ะัะธะฟะธัะบะฐ ะฟัะพ "ะะฐั ะทะณะพะดั ะฝะฐ ะพะฑัะพะฑะบั ะฟะตััะพะฝะฐะปัะฝะธั
ะดะฐะฝะธั
...";
2. ะะพะถะปะธะฒัััั ะฟัะพะปะพะฝะณะฐััั ะฒัะดะฟะพะฒัะดั ะผัััะบะพะณะพ ะณะพะปะพะฒะธ ะท 15 ะดะพ 30 ะดะฝัะฒ. (ะผะพะถะปะธะฒะพ ะฐะฒัะพะผะฐัะธัะฝะต ะฟะพะฒัะดะพะผะปะตะฝะฝั ะบะพัะธัััะฒะฐัั ะฟัะพ ะฟัะพะปะพะฝะณะฐััั ั ัะฐะทั ะฒัะดัััะฝะพััั ะทะฐะบัะธััั ะฑัะทะฝะตั ะฟัะพัะตัั ะทะฐ 15 ะดะฝัะฒ ะฒัะด ะดะฐัะธ ะทะฐะฟััะบั ะฑัะทะฝะตั-ะฟัะพัะตัั ะบะพัะธัััะฒะฐัะตะผ);
3. ะัะปะพ ะฑ ะดะพะฑัะต ะฐะฑะธ ะดััะบะพะฒะฐะฝะฐ ัะพัะผะฐ ะฑัะปะฐ ะฐะฒัะตะฝัะธัะฝะฐ ัะฐะฑะปะพะฝั ัะบะธะน ั ะดะพะดะฐะฒ ะดะพ ะปะธััะฐ;
4. ะะธะฑัั ัะตะทัะปััะฐัั ะฟะพัะปัะณะธ: ัะบะฐะฝ ะฒ ะตะปะตะบััะพะฝะฝะพะผั ะฒะธะณะปัะดั ะฝะฐ ะฟะพััะฐะปั ะะะ "ะะฐะฑะตัั ัะฐะผ ั ะฆะะะ"
|
1.0
|
ะัะทะฝะตัะพะฒัะบ - ะะฒะตัะฝะตะฝะฝั ะณัะพะผะฐะดัะฝะธะฝะฐ ะดะพ ะผัััะบะพะณะพ ะณะพะปะพะฒะธ -
ะะปะณะพัะธัะผ:
https://drive.google.com/file/d/0B1NO5RoNKst7NXFIanhIR0hFY2x0U0lxbGFRbFA5T1Y3RERZ/view?usp=sharing
ะะฐัะฒะฐ:
https://drive.google.com/file/d/0B1NO5RoNKst7MlZlOUNQbUE2eFZLcGxQbS1UWlpmYm1BcjhR/view?usp=sharing
ะัะพัั ะทะฒะตัะฝััะธ ะพัะพะฑะปะธะฒั ัะฒะฐะณั ะฝะฐ ัะฐะบั ัะฐะบัะพัะธ:
1. ะัะธะฟะธัะบะฐ ะฟัะพ "ะะฐั ะทะณะพะดั ะฝะฐ ะพะฑัะพะฑะบั ะฟะตััะพะฝะฐะปัะฝะธั
ะดะฐะฝะธั
...";
2. ะะพะถะปะธะฒัััั ะฟัะพะปะพะฝะณะฐััั ะฒัะดะฟะพะฒัะดั ะผัััะบะพะณะพ ะณะพะปะพะฒะธ ะท 15 ะดะพ 30 ะดะฝัะฒ. (ะผะพะถะปะธะฒะพ ะฐะฒัะพะผะฐัะธัะฝะต ะฟะพะฒัะดะพะผะปะตะฝะฝั ะบะพัะธัััะฒะฐัั ะฟัะพ ะฟัะพะปะพะฝะณะฐััั ั ัะฐะทั ะฒัะดัััะฝะพััั ะทะฐะบัะธััั ะฑัะทะฝะตั ะฟัะพัะตัั ะทะฐ 15 ะดะฝัะฒ ะฒัะด ะดะฐัะธ ะทะฐะฟััะบั ะฑัะทะฝะตั-ะฟัะพัะตัั ะบะพัะธัััะฒะฐัะตะผ);
3. ะัะปะพ ะฑ ะดะพะฑัะต ะฐะฑะธ ะดััะบะพะฒะฐะฝะฐ ัะพัะผะฐ ะฑัะปะฐ ะฐะฒัะตะฝัะธัะฝะฐ ัะฐะฑะปะพะฝั ัะบะธะน ั ะดะพะดะฐะฒ ะดะพ ะปะธััะฐ;
4. ะะธะฑัั ัะตะทัะปััะฐัั ะฟะพัะปัะณะธ: ัะบะฐะฝ ะฒ ะตะปะตะบััะพะฝะฝะพะผั ะฒะธะณะปัะดั ะฝะฐ ะฟะพััะฐะปั ะะะ "ะะฐะฑะตัั ัะฐะผ ั ะฆะะะ"
|
process
|
ะบัะทะฝะตัะพะฒัะบ ะทะฒะตัะฝะตะฝะฝั ะณัะพะผะฐะดัะฝะธะฝะฐ ะดะพ ะผัััะบะพะณะพ ะณะพะปะพะฒะธ ะฐะปะณะพัะธัะผ ะทะฐัะฒะฐ ะฟัะพัั ะทะฒะตัะฝััะธ ะพัะพะฑะปะธะฒั ัะฒะฐะณั ะฝะฐ ัะฐะบั ัะฐะบัะพัะธ ะฟัะธะฟะธัะบะฐ ะฟัะพ ะดะฐั ะทะณะพะดั ะฝะฐ ะพะฑัะพะฑะบั ะฟะตััะพะฝะฐะปัะฝะธั
ะดะฐะฝะธั
ะผะพะถะปะธะฒัััั ะฟัะพะปะพะฝะณะฐััั ะฒัะดะฟะพะฒัะดั ะผัััะบะพะณะพ ะณะพะปะพะฒะธ ะท ะดะพ ะดะฝัะฒ ะผะพะถะปะธะฒะพ ะฐะฒัะพะผะฐัะธัะฝะต ะฟะพะฒัะดะพะผะปะตะฝะฝั ะบะพัะธัััะฒะฐัั ะฟัะพ ะฟัะพะปะพะฝะณะฐััั ั ัะฐะทั ะฒัะดัััะฝะพััั ะทะฐะบัะธััั ะฑัะทะฝะตั ะฟัะพัะตัั ะทะฐ ะดะฝัะฒ ะฒัะด ะดะฐัะธ ะทะฐะฟััะบั ะฑัะทะฝะตั ะฟัะพัะตัั ะบะพัะธัััะฒะฐัะตะผ ะฑัะปะพ ะฑ ะดะพะฑัะต ะฐะฑะธ ะดััะบะพะฒะฐะฝะฐ ัะพัะผะฐ ะฑัะปะฐ ะฐะฒัะตะฝัะธัะฝะฐ ัะฐะฑะปะพะฝั ัะบะธะน ั ะดะพะดะฐะฒ ะดะพ ะปะธััะฐ ะฒะธะฑัั ัะตะทัะปััะฐัั ะฟะพัะปัะณะธ ัะบะฐะฝ ะฒ ะตะปะตะบััะพะฝะฝะพะผั ะฒะธะณะปัะดั ะฝะฐ ะฟะพััะฐะปั ะฐะฑะพ ะทะฐะฑะตัั ัะฐะผ ั ัะฝะฐะฟ
| 1
|
81,535
| 3,592,065,872
|
IssuesEvent
|
2016-02-01 14:45:26
|
thesgc/chembiohub_helpdesk
|
https://api.github.com/repos/thesgc/chembiohub_helpdesk
|
closed
|
Test of iScienceSearch http://isciencesearch.com/iss. Passing through search terms likely to be use
|
app: ChemReg Dev Specific For Andy and Paul Review name: Karen priority: Medium status: New
|
Test of iScienceSearch http://isciencesearch.com/iss. Passing through search terms likely to be used in ChemReg to test results. Determine if there'd be any value in further testing / integration.
|
1.0
|
Test of iScienceSearch http://isciencesearch.com/iss. Passing through search terms likely to be use - Test of iScienceSearch http://isciencesearch.com/iss. Passing through search terms likely to be used in ChemReg to test results. Determine if there'd be any value in further testing / integration.
|
non_process
|
test of isciencesearch passing through search terms likely to be use test of isciencesearch passing through search terms likely to be used in chemreg to test results determine if there d be any value in further testing integration
| 0
|
19,741
| 26,096,711,087
|
IssuesEvent
|
2022-12-26 21:18:59
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
closed
|
Gradle release task always set image tag to the version property
|
bug process
|
### Description
The maven version replacer allows setting module version and docker tag version separately. The docker tag version is used to replace the hedera-mirror-* docker image version in `docker-compose.yml` and the Chart.appVersion in our charts. This provides the flexibility for our release automation to:
- Set the version in `docker-compose.yaml` and Chart.appVersion to the same non-snapshot versions
- Set the version in `docker-compose.yaml` and Chart.appVersion to `main` for snapshot versions
The Gradle task will set everything to the `version` property.
### Steps to reproduce
Run `./gradlew release -Pversion=$VERSION`
### Additional context
_No response_
### Hedera network
other
### Version
0.72.0-SNAPSHOT
### Operating system
None
|
1.0
|
Gradle release task always set image tag to the version property - ### Description
The maven version replacer allows setting module version and docker tag version separately. The docker tag version is used to replace the hedera-mirror-* docker image version in `docker-compose.yml` and the Chart.appVersion in our charts. This provides the flexibility for our release automation to:
- Set the version in `docker-compose.yaml` and Chart.appVersion to the same non-snapshot versions
- Set the version in `docker-compose.yaml` and Chart.appVersion to `main` for snapshot versions
The Gradle task will set everything to the `version` property.
### Steps to reproduce
Run `./gradlew release -Pversion=$VERSION`
### Additional context
_No response_
### Hedera network
other
### Version
0.72.0-SNAPSHOT
### Operating system
None
|
process
|
gradle release task always set image tag to the version property description the maven version replacer allows setting module version and docker tag version separately the docker tag version is used to replace the hedera mirror docker image version in docker compose yml and the chart appversion in our charts this provides the flexibility for our release automation to set the version in docker compose yaml and chart appversion to the same non snapshot versions set the version in docker compose yaml and chart appversion to main for snapshot versions the gradle task will set everything to the version property steps to reproduce run gradlew release pversion version additional context no response hedera network other version snapshot operating system none
| 1
|
15,241
| 19,179,101,599
|
IssuesEvent
|
2021-12-04 04:04:04
|
shirou/gopsutil
|
https://api.github.com/repos/shirou/gopsutil
|
closed
|
process.Name returns an empty string in Apple Silicon
|
os:darwin package:process
|
**Describe the bug**
Calling `process.Name()` returns an empty string in Apple Silicon. This happens with any process.
**To Reproduce**
```go
package main
import (
"log"
"os"
"github.com/shirou/gopsutil/v3/process"
)
func main() {
pid := os.Getpid()
proc, err := process.NewProcess(int32(pid))
if err != nil {
log.Fatalf("Could not create process %d, %s", pid, err)
}
log.Println(proc.Pid)
name, err := proc.Name()
if err != nil {
log.Fatalln("Could not read process name,", err)
}
if name == "" {
log.Fatalln("Could not parse process name")
}
}
```
**Expected behavior**
`process.Name()` returns an empty string.
**Environment (please complete the following information):**
- [ ] Windows: [paste the result of `ver`]
- [ ] Linux: [paste contents of `/etc/os-release` and the result of `uname -a`]
- [x] Mac OS: [paste the result of `sw_vers` and `uname -a`
- [ ] FreeBSD: [paste the result of `freebsd-version -k -r -u` and `uname -a`]
- [ ] OpenBSD: [paste the result of `uname -a`]
ProductName: macOS
ProductVersion: 11.2
BuildVersion: 20D64
Darwin ramiros-mini.lan 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101 arm64
**Additional context**
The same reproduces in `github.com/shirou/gopsutil/v3/process` and `github.com/shirou/gopsutil/process`
|
1.0
|
process.Name returns an empty string in Apple Silicon - **Describe the bug**
Calling `process.Name()` returns an empty string in Apple Silicon. This happens with any process.
**To Reproduce**
```go
package main
import (
"log"
"os"
"github.com/shirou/gopsutil/v3/process"
)
func main() {
pid := os.Getpid()
proc, err := process.NewProcess(int32(pid))
if err != nil {
log.Fatalf("Could not create process %d, %s", pid, err)
}
log.Println(proc.Pid)
name, err := proc.Name()
if err != nil {
log.Fatalln("Could not read process name,", err)
}
if name == "" {
log.Fatalln("Could not parse process name")
}
}
```
**Expected behavior**
`process.Name()` returns an empty string.
**Environment (please complete the following information):**
- [ ] Windows: [paste the result of `ver`]
- [ ] Linux: [paste contents of `/etc/os-release` and the result of `uname -a`]
- [x] Mac OS: [paste the result of `sw_vers` and `uname -a`
- [ ] FreeBSD: [paste the result of `freebsd-version -k -r -u` and `uname -a`]
- [ ] OpenBSD: [paste the result of `uname -a`]
ProductName: macOS
ProductVersion: 11.2
BuildVersion: 20D64
Darwin ramiros-mini.lan 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101 arm64
**Additional context**
The same reproduces in `github.com/shirou/gopsutil/v3/process` and `github.com/shirou/gopsutil/process`
|
process
|
process name returns an empty string in apple silicon describe the bug calling process name returns an empty string in apple silicon this happens with any process to reproduce go package main import log os github com shirou gopsutil process func main pid os getpid proc err process newprocess pid if err nil log fatalf could not create process d s pid err log println proc pid name err proc name if err nil log fatalln could not read process name err if name log fatalln could not parse process name expected behavior process name returns an empty string environment please complete the following information windows linux mac os paste the result of sw vers and uname a freebsd openbsd productname macos productversion buildversion darwin ramiros mini lan darwin kernel version thu jan pst root xnu release additional context the same reproduces in github com shirou gopsutil process and github com shirou gopsutil process
| 1
|
320,288
| 27,430,223,518
|
IssuesEvent
|
2023-03-02 00:20:06
|
MPMG-DCC-UFMG/F01
|
https://api.github.com/repos/MPMG-DCC-UFMG/F01
|
closed
|
Teste de generalizacao para a tag Receitas - Dados de Receitas - Sรฃo Vicente de Minas
|
generalization test development
|
DoD: Realizar o teste de Generalizaรงรฃo do validador da tag Receitas - Dados de Receitas para o Municรญpio de Sรฃo Vicente de Minas.
|
1.0
|
Teste de generalizacao para a tag Receitas - Dados de Receitas - Sรฃo Vicente de Minas - DoD: Realizar o teste de Generalizaรงรฃo do validador da tag Receitas - Dados de Receitas para o Municรญpio de Sรฃo Vicente de Minas.
|
non_process
|
teste de generalizacao para a tag receitas dados de receitas sรฃo vicente de minas dod realizar o teste de generalizaรงรฃo do validador da tag receitas dados de receitas para o municรญpio de sรฃo vicente de minas
| 0
|
325,298
| 24,042,152,651
|
IssuesEvent
|
2022-09-16 03:38:09
|
FoyiLabs/uncovr-python
|
https://api.github.com/repos/FoyiLabs/uncovr-python
|
closed
|
Add weblinks and labels
|
documentation In progress
|
Add the FOYI documentation page on the Repo and add appropriate meta data in labels
|
1.0
|
Add weblinks and labels - Add the FOYI documentation page on the Repo and add appropriate meta data in labels
|
non_process
|
add weblinks and labels add the foyi documentation page on the repo and add appropriate meta data in labels
| 0
|
9,702
| 11,755,320,845
|
IssuesEvent
|
2020-03-13 09:17:44
|
Tewr/BlazorFileReader
|
https://api.github.com/repos/Tewr/BlazorFileReader
|
closed
|
BlazorFileReader crashes since Blazor WebAssembly 3.2 Preview 2
|
Compatibility
|
After updating to Blazor WebAssembly 3.2 Preview 2, I keep getting the following error with Blazor File Reader:
```
WASM: ๏ปฟblazor:js:FileReaderComponent.js blazor.webassembly.js:1:35561
WASM: ๏ปฟUnhandled exception rendering component: blazor.webassembly.js:1:35609
WASM: System.Reflection.TargetException: Object does not match target type. blazor.webassembly.js:1:35609
WASM: at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x1f03f58 + 0x0004e> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) <0x1f038a0 + 0x00014> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.IJSRuntimeExtensions.InvokeUnmarshalled[TParam,TReturn] (Microsoft.JSInterop.IJSRuntime jsRuntime, System.String methodName, TParam parameter) <0x295bfa0 + 0x000b0> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop+<>c__DisplayClass21_0.<ReadFileUnmarshalledAsync>b__0 () <0x295bdc8 + 0x00068> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at (wrapper delegate-invoke) System.Func`1[System.Int32].invoke_TResult() blazor.webassembly.js:1:35609
WASM: at System.Threading.Tasks.Task`1[TResult].InnerInvoke () <0x295bb40 + 0x00020> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Threading.Tasks.Task.Execute () <0x26f3f98 + 0x00008> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: --- End of stack trace from previous location where exception was thrown --- blazor.webassembly.js:1:35609
WASM: blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop.ReadFileUnmarshalledAsync (System.Int32 fileRef, System.Byte[] buffer, System.Int64 position, System.Int64 bufferOffset, System.Int32 count, System.Threading.CancellationToken cancellationToken) <0x2951588 + 0x00116> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop.ReadFileAsync (System.Int32 fileRef, System.Byte[] buffer, System.Int64 position, System.Int64 bufferOffset, System.Int32 count, System.Threading.CancellationToken cancellationToken) <0x2950b30 + 0x00114> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop+InteropFileStream.ReadAsync (System.Byte[] buffer, System.Int32 offset, System.Int32 count, System.Threading.CancellationToken cancellationToken) <0x2950350 + 0x00110> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Threading.Tasks.ValueTask`1[TResult].get_Result () <0x28806c8 + 0x0002c> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.IO.Stream.CopyToAsyncInternal (System.IO.Stream destination, System.Int32 bufferSize, System.Threading.CancellationToken cancellationToken) <0x294f820 + 0x00134> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpContent.CopyToAsyncCore (System.Threading.Tasks.ValueTask copyTask) <0x2952c08 + 0x000be> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.MultipartContent.SerializeToStreamAsync (System.IO.Stream stream, System.Net.TransportContext context) <0x294d818 + 0x0043c> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpContent.LoadIntoBufferAsyncCore (System.Threading.Tasks.Task serializeToStreamTask, System.IO.MemoryStream tempBuffer) <0x2955c30 + 0x00112> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpContent.WaitAndReturnAsync[TState,TResult] (System.Threading.Tasks.Task waitTask, TState state, System.Func`2[T,TResult] returnFunc) <0x2956f60 + 0x000ce> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at WebAssembly.Net.Http.HttpClient.WasmHttpMessageHandler.doFetch (System.Threading.Tasks.TaskCompletionSource`1[TResult] tcs, System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) <0x2949808 + 0x002fe> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at WebAssembly.Net.Http.HttpClient.WasmHttpMessageHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) <0x2925ec8 + 0x00184> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpClient.FinishSendAsyncBuffered (System.Threading.Tasks.Task`1[TResult] sendTask, System.Net.Http.HttpRequestMessage request, System.Threading.CancellationTokenSource cts, System.Boolean disposeCts) <0x295afd0 + 0x00278> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at ImportTool.Client.Pages.Upload.AnalyseFile () <0x284fa70 + 0x00570> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion (System.Threading.Tasks.Task task) <0x25cf838 + 0x000e6> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask (System.Threading.Tasks.Task taskToHandle) <0x25d03b8 + 0x000c2> in <filename unknown>:0
```
**To Reproduce**
Steps to reproduce the behavior:
1. I used the following code in my Blazor Client Project:
```html
<input type="file" class="form-control" name="csv_file" @ref="importFile" id="fileToImport" accept=".csv" @onchange="onFileSelected" multiple />
```
```csharp
var files = await fileReaderService.CreateReference(importFile).EnumerateFilesAsync();
var formData = new MultipartFormDataContent();
foreach (var file in files)
{
var info = await file.ReadFileInfoAsync();
var stream = await file.OpenReadAsync();
formData.Add(new StreamContent(stream), info.Name, info.Name);
}
HttpResponseMessage httpResponse = null;
httpResponse = await http.PostAsync("api/import/validate", formData);
```
**Expected behavior**
No crash :)
**Project type**
CSB
**Environment**
- Firefox 74.0
- Blazor.FileReader 1.3.0.20049
- Version of .net sdk 3.1.200-preview-015002
Add any other context about the problem here.
|
True
|
BlazorFileReader crashes since Blazor WebAssembly 3.2 Preview 2 - After updating to Blazor WebAssembly 3.2 Preview 2, I keep getting the following error with Blazor File Reader:
```
WASM: ๏ปฟblazor:js:FileReaderComponent.js blazor.webassembly.js:1:35561
WASM: ๏ปฟUnhandled exception rendering component: blazor.webassembly.js:1:35609
WASM: System.Reflection.TargetException: Object does not match target type. blazor.webassembly.js:1:35609
WASM: at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x1f03f58 + 0x0004e> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) <0x1f038a0 + 0x00014> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.IJSRuntimeExtensions.InvokeUnmarshalled[TParam,TReturn] (Microsoft.JSInterop.IJSRuntime jsRuntime, System.String methodName, TParam parameter) <0x295bfa0 + 0x000b0> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop+<>c__DisplayClass21_0.<ReadFileUnmarshalledAsync>b__0 () <0x295bdc8 + 0x00068> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at (wrapper delegate-invoke) System.Func`1[System.Int32].invoke_TResult() blazor.webassembly.js:1:35609
WASM: at System.Threading.Tasks.Task`1[TResult].InnerInvoke () <0x295bb40 + 0x00020> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Threading.Tasks.Task.Execute () <0x26f3f98 + 0x00008> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: --- End of stack trace from previous location where exception was thrown --- blazor.webassembly.js:1:35609
WASM: blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop.ReadFileUnmarshalledAsync (System.Int32 fileRef, System.Byte[] buffer, System.Int64 position, System.Int64 bufferOffset, System.Int32 count, System.Threading.CancellationToken cancellationToken) <0x2951588 + 0x00116> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop.ReadFileAsync (System.Int32 fileRef, System.Byte[] buffer, System.Int64 position, System.Int64 bufferOffset, System.Int32 count, System.Threading.CancellationToken cancellationToken) <0x2950b30 + 0x00114> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Blazor.FileReader.FileReaderJsInterop+InteropFileStream.ReadAsync (System.Byte[] buffer, System.Int32 offset, System.Int32 count, System.Threading.CancellationToken cancellationToken) <0x2950350 + 0x00110> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Threading.Tasks.ValueTask`1[TResult].get_Result () <0x28806c8 + 0x0002c> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.IO.Stream.CopyToAsyncInternal (System.IO.Stream destination, System.Int32 bufferSize, System.Threading.CancellationToken cancellationToken) <0x294f820 + 0x00134> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpContent.CopyToAsyncCore (System.Threading.Tasks.ValueTask copyTask) <0x2952c08 + 0x000be> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.MultipartContent.SerializeToStreamAsync (System.IO.Stream stream, System.Net.TransportContext context) <0x294d818 + 0x0043c> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpContent.LoadIntoBufferAsyncCore (System.Threading.Tasks.Task serializeToStreamTask, System.IO.MemoryStream tempBuffer) <0x2955c30 + 0x00112> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpContent.WaitAndReturnAsync[TState,TResult] (System.Threading.Tasks.Task waitTask, TState state, System.Func`2[T,TResult] returnFunc) <0x2956f60 + 0x000ce> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at WebAssembly.Net.Http.HttpClient.WasmHttpMessageHandler.doFetch (System.Threading.Tasks.TaskCompletionSource`1[TResult] tcs, System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) <0x2949808 + 0x002fe> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at WebAssembly.Net.Http.HttpClient.WasmHttpMessageHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) <0x2925ec8 + 0x00184> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at System.Net.Http.HttpClient.FinishSendAsyncBuffered (System.Threading.Tasks.Task`1[TResult] sendTask, System.Net.Http.HttpRequestMessage request, System.Threading.CancellationTokenSource cts, System.Boolean disposeCts) <0x295afd0 + 0x00278> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at ImportTool.Client.Pages.Upload.AnalyseFile () <0x284fa70 + 0x00570> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion (System.Threading.Tasks.Task task) <0x25cf838 + 0x000e6> in <filename unknown>:0 blazor.webassembly.js:1:35609
WASM: at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask (System.Threading.Tasks.Task taskToHandle) <0x25d03b8 + 0x000c2> in <filename unknown>:0
```
**To Reproduce**
Steps to reproduce the behavior:
1. I used the following code in my Blazor Client Project:
```html
<input type="file" class="form-control" name="csv_file" @ref="importFile" id="fileToImport" accept=".csv" @onchange="onFileSelected" multiple />
```
```csharp
var files = await fileReaderService.CreateReference(importFile).EnumerateFilesAsync();
var formData = new MultipartFormDataContent();
foreach (var file in files)
{
var info = await file.ReadFileInfoAsync();
var stream = await file.OpenReadAsync();
formData.Add(new StreamContent(stream), info.Name, info.Name);
}
HttpResponseMessage httpResponse = null;
httpResponse = await http.PostAsync("api/import/validate", formData);
```
**Expected behavior**
No crash :)
**Project type**
CSB
**Environment**
- Firefox 74.0
- Blazor.FileReader 1.3.0.20049
- Version of .net sdk 3.1.200-preview-015002
Add any other context about the problem here.
|
non_process
|
blazorfilereader crashes since blazor webassembly preview after updating to blazor webassembly preview i keep getting the following error with blazor file reader wasm ๏ปฟblazor js filereadercomponent js blazor webassembly js wasm ๏ปฟunhandled exception rendering component blazor webassembly js wasm system reflection targetexception object does not match target type blazor webassembly js wasm at system reflection runtimemethodinfo invoke system object obj system reflection bindingflags invokeattr system reflection binder binder system object parameters system globalization cultureinfo culture in blazor webassembly js wasm at system reflection methodbase invoke system object obj system object parameters in blazor webassembly js wasm at blazor filereader ijsruntimeextensions invokeunmarshalled microsoft jsinterop ijsruntime jsruntime system string methodname tparam parameter in blazor webassembly js wasm at blazor filereader filereaderjsinterop c b in blazor webassembly js wasm at wrapper delegate invoke system func invoke tresult blazor webassembly js wasm at system threading tasks task innerinvoke in blazor webassembly js wasm at system threading tasks task execute in blazor webassembly js wasm end of stack trace from previous location where exception was thrown blazor webassembly js wasm blazor webassembly js wasm at blazor filereader filereaderjsinterop readfileunmarshalledasync system fileref system byte buffer system position system bufferoffset system count system threading cancellationtoken cancellationtoken in blazor webassembly js wasm at blazor filereader filereaderjsinterop readfileasync system fileref system byte buffer system position system bufferoffset system count system threading cancellationtoken cancellationtoken in blazor webassembly js wasm at blazor filereader filereaderjsinterop interopfilestream readasync system byte buffer system offset system count system threading cancellationtoken cancellationtoken in blazor webassembly js wasm at system threading tasks valuetask get result in blazor webassembly js wasm at system io stream copytoasyncinternal system io stream destination system buffersize system threading cancellationtoken cancellationtoken in blazor webassembly js wasm at system net http httpcontent copytoasynccore system threading tasks valuetask copytask in blazor webassembly js wasm at system net http multipartcontent serializetostreamasync system io stream stream system net transportcontext context in blazor webassembly js wasm at system net http httpcontent loadintobufferasynccore system threading tasks task serializetostreamtask system io memorystream tempbuffer in blazor webassembly js wasm at system net http httpcontent waitandreturnasync system threading tasks task waittask tstate state system func returnfunc in blazor webassembly js wasm at webassembly net http httpclient wasmhttpmessagehandler dofetch system threading tasks taskcompletionsource tcs system net http httprequestmessage request system threading cancellationtoken cancellationtoken in blazor webassembly js wasm at webassembly net http httpclient wasmhttpmessagehandler sendasync system net http httprequestmessage request system threading cancellationtoken cancellationtoken in blazor webassembly js wasm at system net http httpclient finishsendasyncbuffered system threading tasks task sendtask system net http httprequestmessage request system threading cancellationtokensource cts system boolean disposects in blazor webassembly js wasm at importtool client pages upload analysefile in blazor webassembly js wasm at microsoft aspnetcore components componentbase callstatehaschangedonasynccompletion system threading tasks task task in blazor webassembly js wasm at microsoft aspnetcore components rendertree renderer geterrorhandledtask system threading tasks task tasktohandle in to reproduce steps to reproduce the behavior i used the following code in my blazor client project html csharp var files await filereaderservice createreference importfile enumeratefilesasync var formdata new multipartformdatacontent foreach var file in files var info await file readfileinfoasync var stream await file openreadasync formdata add new streamcontent stream info name info name httpresponsemessage httpresponse null httpresponse await http postasync api import validate formdata expected behavior no crash project type csb environment firefox blazor filereader version of net sdk preview add any other context about the problem here
| 0
|
87,106
| 25,034,265,443
|
IssuesEvent
|
2022-11-04 14:48:15
|
Crocoblock/suggestions
|
https://api.github.com/repos/Crocoblock/suggestions
|
closed
|
Automatically align for to add to cart buttons / jet woobuilder
|
JetWooBuilder
|
In the product grid widget, if the items in this widget are not equal, the Add to Cart button in the product grid widget will not be aligned, and this will severely damage ux. So, please add the Automatically align feature for the buttons to add to cart product grid widget. This feature has been added in version elementor pro 3.7 and works great. https://prnt.sc/NDF88Znr4OFY
|
1.0
|
Automatically align for to add to cart buttons / jet woobuilder - In the product grid widget, if the items in this widget are not equal, the Add to Cart button in the product grid widget will not be aligned, and this will severely damage ux. So, please add the Automatically align feature for the buttons to add to cart product grid widget. This feature has been added in version elementor pro 3.7 and works great. https://prnt.sc/NDF88Znr4OFY
|
non_process
|
automatically align for to add to cart buttons jet woobuilder in the product grid widget if the items in this widget are not equal the add to cart button in the product grid widget will not be aligned and this will severely damage ux so please add the automatically align feature for the buttons to add to cart product grid widget this feature has been added in version elementor pro and works great
| 0
|
7,223
| 10,349,691,231
|
IssuesEvent
|
2019-09-04 23:30:41
|
AcademySoftwareFoundation/OpenCue
|
https://api.github.com/repos/AcademySoftwareFoundation/OpenCue
|
opened
|
Cleanup and remove testMode from rqd cuebot code
|
process
|
Look at `com.imageworks.spcue.rqd.RqsClientGrpc`, the `testMode` functionality should no longer be needed. Verify it is safe to remove and remove it along with all callers in the unittests.
|
1.0
|
Cleanup and remove testMode from rqd cuebot code - Look at `com.imageworks.spcue.rqd.RqsClientGrpc`, the `testMode` functionality should no longer be needed. Verify it is safe to remove and remove it along with all callers in the unittests.
|
process
|
cleanup and remove testmode from rqd cuebot code look at com imageworks spcue rqd rqsclientgrpc the testmode functionality should no longer be needed verify it is safe to remove and remove it along with all callers in the unittests
| 1
|
285,143
| 8,755,145,300
|
IssuesEvent
|
2018-12-14 14:01:50
|
estevez-dev/ha_client
|
https://api.github.com/repos/estevez-dev/ha_client
|
closed
|
device_class is not working for icons
|
bug priority: high
|
Hi
I have added to my HA by 1wire sensors of temp. I add it in lovelace in glance card. In HA web page show correct icon to temperature as termometer... but in app show icon EYE but should show termometer.
|
1.0
|
device_class is not working for icons - Hi
I have added to my HA by 1wire sensors of temp. I add it in lovelace in glance card. In HA web page show correct icon to temperature as termometer... but in app show icon EYE but should show termometer.
|
non_process
|
device class is not working for icons hi i have added to my ha by sensors of temp i add it in lovelace in glance card in ha web page show correct icon to temperature as termometer but in app show icon eye but should show termometer
| 0
|
254,509
| 19,249,420,358
|
IssuesEvent
|
2021-12-09 02:12:55
|
Alphasians/AinaBot
|
https://api.github.com/repos/Alphasians/AinaBot
|
closed
|
Adding Documentation of the BOT
|
documentation good first issue first-timers Hacktoberfest no issue activity
|
## Documenting The Project!
Based on the following the features:
- [x] Music Commands - Play, Skip, Stop, Resume, Queue.
- [x] Mod Commands - Kick, Ban.
- [ ] Level Commands
- [ ] Misc Commands
Once you have completed the documentation of the specific feature, we will mark it as complete!
|
1.0
|
Adding Documentation of the BOT - ## Documenting The Project!
Based on the following the features:
- [x] Music Commands - Play, Skip, Stop, Resume, Queue.
- [x] Mod Commands - Kick, Ban.
- [ ] Level Commands
- [ ] Misc Commands
Once you have completed the documentation of the specific feature, we will mark it as complete!
|
non_process
|
adding documentation of the bot documenting the project based on the following the features music commands play skip stop resume queue mod commands kick ban level commands misc commands once you have completed the documentation of the specific feature we will mark it as complete
| 0
|
8,202
| 11,396,232,096
|
IssuesEvent
|
2020-01-30 13:10:50
|
Open-EO/openeo-processes
|
https://api.github.com/repos/Open-EO/openeo-processes
|
closed
|
Filter by point process
|
accepted critical has PR new process
|
We discussed in the telco that it might make sense to have a process to filter by point, like we have a filter by polygon.
The use case we're thinking of is to quickly get all relevant data about a particular point in the world. What that entails is not entirely clear though and probably depends on what filtering by polygon does, so as to maintain consistency. Right now filtering by polygon effectively is defined as a `crop`/`clip` function, and the same could be done for filtering by point.
There are three more alternatives: to have it work as an `intersect`, so that dimensions of features or rasters are not changed but anything not touching (i.e. not relevant to) the point is discarded (that's how it works in GEE); to have it work as an `extract`, so that the space dimensions are collapsed (you get e.g. a time series); or to not have either of the filtering options altogether and just provide `clip`/`crop`, `intersect`, and `extract` as their own processes.
|
1.0
|
Filter by point process - We discussed in the telco that it might make sense to have a process to filter by point, like we have a filter by polygon.
The use case we're thinking of is to quickly get all relevant data about a particular point in the world. What that entails is not entirely clear though and probably depends on what filtering by polygon does, so as to maintain consistency. Right now filtering by polygon effectively is defined as a `crop`/`clip` function, and the same could be done for filtering by point.
There are three more alternatives: to have it work as an `intersect`, so that dimensions of features or rasters are not changed but anything not touching (i.e. not relevant to) the point is discarded (that's how it works in GEE); to have it work as an `extract`, so that the space dimensions are collapsed (you get e.g. a time series); or to not have either of the filtering options altogether and just provide `clip`/`crop`, `intersect`, and `extract` as their own processes.
|
process
|
filter by point process we discussed in the telco that it might make sense to have a process to filter by point like we have a filter by polygon the use case we re thinking of is to quickly get all relevant data about a particular point in the world what that entails is not entirely clear though and probably depends on what filtering by polygon does so as to maintain consistency right now filtering by polygon effectively is defined as a crop clip function and the same could be done for filtering by point there are three more alternatives to have it work as an intersect so that dimensions of features or rasters are not changed but anything not touching i e not relevant to the point is discarded that s how it works in gee to have it work as an extract so that the space dimensions are collapsed you get e g a time series or to not have either of the filtering options altogether and just provide clip crop intersect and extract as their own processes
| 1
|
11,133
| 13,957,691,642
|
IssuesEvent
|
2020-10-24 08:10:28
|
alexanderkotsev/geoportal
|
https://api.github.com/repos/alexanderkotsev/geoportal
|
opened
|
BE: Harvest
|
BE - Belgium Geoportal Harvesting process
|
Hi,
Is it possible to harvest Geopunt-Metadatacenter zoekdienst (Informatie Vlaanderen).
Thx
Bart
|
1.0
|
BE: Harvest - Hi,
Is it possible to harvest Geopunt-Metadatacenter zoekdienst (Informatie Vlaanderen).
Thx
Bart
|
process
|
be harvest hi is it possible to harvest geopunt metadatacenter zoekdienst informatie vlaanderen thx bart
| 1
|
215,779
| 16,617,103,024
|
IssuesEvent
|
2021-06-02 18:11:04
|
edgexfoundry/edgex-docs
|
https://api.github.com/repos/edgexfoundry/edgex-docs
|
closed
|
Add deployment best practices in security chapter
|
1-low documentation geneva
|
Some best practices:
1) Launch container as non-root user where possible
2) Close un-used ports:
a) source - in docker-compose only list ports that we use, cleaning up any cruft
b) some ports will still be open for on-host inter-service requests. The micro services are on the same network, so they shall be able to access these without issue.
c) In EdgeX secure-mode, add iptables rules to allow access only to the security proxy for all non-local accesses
|
1.0
|
Add deployment best practices in security chapter - Some best practices:
1) Launch container as non-root user where possible
2) Close un-used ports:
a) source - in docker-compose only list ports that we use, cleaning up any cruft
b) some ports will still be open for on-host inter-service requests. The micro services are on the same network, so they shall be able to access these without issue.
c) In EdgeX secure-mode, add iptables rules to allow access only to the security proxy for all non-local accesses
|
non_process
|
add deployment best practices in security chapter some best practices launch container as non root user where possible close un used ports a source in docker compose only list ports that we use cleaning up any cruft b some ports will still be open for on host inter service requests the micro services are on the same network so they shall be able to access these without issue c in edgex secure mode add iptables rules to allow access only to the security proxy for all non local accesses
| 0
|
15,167
| 18,924,972,373
|
IssuesEvent
|
2021-11-17 08:32:49
|
pystatgen/sgkit
|
https://api.github.com/repos/pystatgen/sgkit
|
closed
|
Release 0.4.0
|
process + tools
|
This is a coordinating issue for the release.
Issues for this release are listed here: https://github.com/pystatgen/sgkit/milestone/2
|
1.0
|
Release 0.4.0 - This is a coordinating issue for the release.
Issues for this release are listed here: https://github.com/pystatgen/sgkit/milestone/2
|
process
|
release this is a coordinating issue for the release issues for this release are listed here
| 1
|
18,452
| 24,547,364,913
|
IssuesEvent
|
2022-10-12 09:49:07
|
Altinn/app-template-dotnet
|
https://api.github.com/repos/Altinn/app-template-dotnet
|
closed
|
Develop API needed to support GUI for available BPMN tasks
|
area/process solution/app-backend
|
## Description
The frontend needs an endpoint that lists "allowed next tasks" to be available to navigate to.
Based on the authorization the list could only contain processes the user should be able to use from the given process/view.
## Spec
From an API for example `{org}/{app}/api/v2/instances/{instanceOwnerPartyId:int}/{instanceGuid:guid}/process/next`, the httpclient will get an object like thissimilar to this:
``` JSON
{
"tasks": {
"allowedTask": {
"weight": 9,
"otherAttributes": "may need to have more complexity later"
},
"nextTask": {
"weight": 5
},
"illegalTask": {
"illegal_reason": "invalid_role",
"weight": 0
}
},
"availableTasks": [ "nextTask", "allowedTask", "illegalTask" ]
}
```
In frontend the weight can be used to evaluate the importance of a button where weight 9 could indicate a "Submit" variant and and the highest weight below 9 would indicate a primary button.
## Requirements
- [x] decide how that API will look like
- [ ] update Altinn/app-frontend-react#432 with the correct endpoint to request from
|
1.0
|
Develop API needed to support GUI for available BPMN tasks -
## Description
The frontend needs an endpoint that lists "allowed next tasks" to be available to navigate to.
Based on the authorization the list could only contain processes the user should be able to use from the given process/view.
## Spec
From an API for example `{org}/{app}/api/v2/instances/{instanceOwnerPartyId:int}/{instanceGuid:guid}/process/next`, the httpclient will get an object like thissimilar to this:
``` JSON
{
"tasks": {
"allowedTask": {
"weight": 9,
"otherAttributes": "may need to have more complexity later"
},
"nextTask": {
"weight": 5
},
"illegalTask": {
"illegal_reason": "invalid_role",
"weight": 0
}
},
"availableTasks": [ "nextTask", "allowedTask", "illegalTask" ]
}
```
In frontend the weight can be used to evaluate the importance of a button where weight 9 could indicate a "Submit" variant and and the highest weight below 9 would indicate a primary button.
## Requirements
- [x] decide how that API will look like
- [ ] update Altinn/app-frontend-react#432 with the correct endpoint to request from
|
process
|
develop api needed to support gui for available bpmn tasks description the frontend needs an endpoint that lists allowed next tasks to be available to navigate to based on the authorization the list could only contain processes the user should be able to use from the given process view spec from an api for example org app api instances instanceownerpartyid int instanceguid guid process next the httpclient will get an object like thissimilar to this json tasks allowedtask weight otherattributes may need to have more complexity later nexttask weight illegaltask illegal reason invalid role weight availabletasks in frontend the weight can be used to evaluate the importance of a button where weight could indicate a submit variant and and the highest weight below would indicate a primary button requirements decide how that api will look like update altinn app frontend react with the correct endpoint to request from
| 1
|
337,770
| 10,220,160,534
|
IssuesEvent
|
2019-08-15 20:33:24
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www.novinky.cz - design is broken
|
browser-firefox-tablet engine-gecko priority-normal
|
<!-- @browser: Firefox Mobile (Tablet) 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 6.0.1; Tablet; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.novinky.cz/
**Browser / Version**: Firefox Mobile (Tablet) 68.0
**Operating System**: Android 6.0.1
**Tested Another Browser**: No
**Problem type**: Design is broken
**Description**: see picture
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2019/8/c2b0e05c-dd77-4234-b154-c715d44a6817.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190805070035</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>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "Naten prvku <script> ze zdroje data:text/javascript;base64, se nezdailo." {file: "https://www.novinky.cz/" line: 2}]', u'[JavaScript Error: "ReferenceError: ghdw is not defined" {file: "https://www.novinky.cz/" line: 2}]\n@https://www.novinky.cz/:2:1\n', u'[JavaScript Error: "Content Security Policy: The pages settings blocked the loading of a resource at data:text/javascript;base64, (script-src)."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with โค๏ธ_
|
1.0
|
www.novinky.cz - design is broken - <!-- @browser: Firefox Mobile (Tablet) 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 6.0.1; Tablet; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.novinky.cz/
**Browser / Version**: Firefox Mobile (Tablet) 68.0
**Operating System**: Android 6.0.1
**Tested Another Browser**: No
**Problem type**: Design is broken
**Description**: see picture
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2019/8/c2b0e05c-dd77-4234-b154-c715d44a6817.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190805070035</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>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "Naten prvku <script> ze zdroje data:text/javascript;base64, se nezdailo." {file: "https://www.novinky.cz/" line: 2}]', u'[JavaScript Error: "ReferenceError: ghdw is not defined" {file: "https://www.novinky.cz/" line: 2}]\n@https://www.novinky.cz/:2:1\n', u'[JavaScript Error: "Content Security Policy: The pages settings blocked the loading of a resource at data:text/javascript;base64, (script-src)."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]', u'[JavaScript Warning: "Content Security Policy: Ignoring x-frame-options because of frame-ancestors directive."]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with โค๏ธ_
|
non_process
|
design is broken url browser version firefox mobile tablet operating system android tested another browser no problem type design is broken description see picture steps to reproduce 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 console messages u n u u u u u u u from with โค๏ธ
| 0
|
162,330
| 6,151,078,281
|
IssuesEvent
|
2017-06-28 00:57:57
|
facelessuser/Rummage
|
https://api.github.com/repos/facelessuser/Rummage
|
closed
|
Make available on PyPi
|
Maintenance Priority - Medium
|
I don't know how people usually handle GUI modules as you can't really have wxPython has a dependency that auto installs. I am going to sit and think about this one.
|
1.0
|
Make available on PyPi - I don't know how people usually handle GUI modules as you can't really have wxPython has a dependency that auto installs. I am going to sit and think about this one.
|
non_process
|
make available on pypi i don t know how people usually handle gui modules as you can t really have wxpython has a dependency that auto installs i am going to sit and think about this one
| 0
|
2,795
| 5,723,573,733
|
IssuesEvent
|
2017-04-20 12:37:33
|
dita-ot/dita-ot
|
https://api.github.com/repos/dita-ot/dita-ot
|
closed
|
NPE in ForceUniqueFilter
|
enhancement P3 preprocess
|
Our QA team found this:
E:\KiTuri\qa\oxygen\frameworks\dita\DITA-OT2.x\plugins\org.dita.base\build_preprocess.xml:290:
java.lang.NullPointerException
at
org.dita.dost.writer.ForceUniqueFilter.generateCopyToTarget(ForceUniqueFilter.java:101)
at
org.dita.dost.writer.ForceUniqueFilter.startElement(ForceUniqueFilter.java:67)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
Source)
at
org.ditang.relaxng.defaults.RelaxNGDefaultsComponent.emptyElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.ditang.relaxng.defaults.RelaxDefaultsParserConfiguration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:451)
at net.sf.saxon.event.Sender.send(Sender.java:153)
at
net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:375)
at org.dita.dost.util.XMLUtils.transformFile(XMLUtils.java:391)
at org.dita.dost.util.XMLUtils.transform(XMLUtils.java:346)
at org.dita.dost.util.XMLUtils.transform(XMLUtils.java:335)
at org.dita.dost.module.CopyToModule.processMap(CopyToModule.java:91)
at org.dita.dost.module.CopyToModule.execute(CopyToModule.java:65)
at
org.dita.dost.pipeline.PipelineFacade.execute(PipelineFacade.java:70)
at
org.dita.dost.invoker.ExtensibleAntInvoker.execute(ExtensibleAntInvoker.java:222)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
If I find some samples to reproduce the problem I'll be back.
|
1.0
|
NPE in ForceUniqueFilter - Our QA team found this:
E:\KiTuri\qa\oxygen\frameworks\dita\DITA-OT2.x\plugins\org.dita.base\build_preprocess.xml:290:
java.lang.NullPointerException
at
org.dita.dost.writer.ForceUniqueFilter.generateCopyToTarget(ForceUniqueFilter.java:101)
at
org.dita.dost.writer.ForceUniqueFilter.startElement(ForceUniqueFilter.java:67)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
Source)
at
org.ditang.relaxng.defaults.RelaxNGDefaultsComponent.emptyElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.ditang.relaxng.defaults.RelaxDefaultsParserConfiguration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:451)
at net.sf.saxon.event.Sender.send(Sender.java:153)
at
net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:375)
at org.dita.dost.util.XMLUtils.transformFile(XMLUtils.java:391)
at org.dita.dost.util.XMLUtils.transform(XMLUtils.java:346)
at org.dita.dost.util.XMLUtils.transform(XMLUtils.java:335)
at org.dita.dost.module.CopyToModule.processMap(CopyToModule.java:91)
at org.dita.dost.module.CopyToModule.execute(CopyToModule.java:65)
at
org.dita.dost.pipeline.PipelineFacade.execute(PipelineFacade.java:70)
at
org.dita.dost.invoker.ExtensibleAntInvoker.execute(ExtensibleAntInvoker.java:222)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
If I find some samples to reproduce the problem I'll be back.
|
process
|
npe in forceuniquefilter our qa team found this e kituri qa oxygen frameworks dita dita x plugins org dita base build preprocess xml java lang nullpointerexception at org dita dost writer forceuniquefilter generatecopytotarget forceuniquefilter java at org dita dost writer forceuniquefilter startelement forceuniquefilter java at org apache xerces parsers abstractsaxparser startelement unknown source at org apache xerces parsers abstractxmldocumentparser emptyelement unknown source at org ditang relaxng defaults relaxngdefaultscomponent emptyelement unknown source at org apache xerces impl xmlnsdocumentscannerimpl scanstartelement unknown source at org apache xerces impl xmldocumentfragmentscannerimpl fragmentcontentdispatcher dispatch unknown source at org apache xerces impl xmldocumentfragmentscannerimpl scandocument unknown source at org apache xerces parsers parse unknown source at org ditang relaxng defaults relaxdefaultsparserconfiguration parse unknown source at org apache xerces parsers parse unknown source at org apache xerces parsers xmlparser parse unknown source at org apache xerces parsers abstractsaxparser parse unknown source at org xml sax helpers xmlfilterimpl parse unknown source at org xml sax helpers xmlfilterimpl parse unknown source at net sf saxon event sender sendsaxsource sender java at net sf saxon event sender send sender java at net sf saxon jaxp identitytransformer transform identitytransformer java at org dita dost util xmlutils transformfile xmlutils java at org dita dost util xmlutils transform xmlutils java at org dita dost util xmlutils transform xmlutils java at org dita dost module copytomodule processmap copytomodule java at org dita dost module copytomodule execute copytomodule java at org dita dost pipeline pipelinefacade execute pipelinefacade java at org dita dost invoker extensibleantinvoker execute extensibleantinvoker java at org apache tools ant unknownelement execute unknownelement java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke unknown source at java lang reflect method invoke unknown source at org apache tools ant dispatch dispatchutils execute dispatchutils java at org apache tools ant task perform task java at org apache tools ant target execute target java at org apache tools ant target performtasks target java at org apache tools ant project executesortedtargets project java if i find some samples to reproduce the problem i ll be back
| 1
|
75,631
| 15,437,980,721
|
IssuesEvent
|
2021-03-07 18:41:27
|
Pafipi/MDM-Web
|
https://api.github.com/repos/Pafipi/MDM-Web
|
closed
|
Implement basic JWT Authorization/Authentication functionality for the API
|
API backend feature security
|
The API should have a working JWT authentication and authorization process. The implementation should consist of:
-authentication scheme
-challenge scheme
-jwt bearer
-policy definitions
|
True
|
Implement basic JWT Authorization/Authentication functionality for the API - The API should have a working JWT authentication and authorization process. The implementation should consist of:
-authentication scheme
-challenge scheme
-jwt bearer
-policy definitions
|
non_process
|
implement basic jwt authorization authentication functionality for the api the api should have a working jwt authentication and authorization process the implementation should consist of authentication scheme challenge scheme jwt bearer policy definitions
| 0
|
5,115
| 7,888,188,982
|
IssuesEvent
|
2018-06-27 21:07:05
|
acstech/doppler-frontend
|
https://api.github.com/repos/acstech/doppler-frontend
|
closed
|
process clientID input
|
Exceeds frontend queries real time processing
|
basically taking in their client ID and first, finding any real time data associated with that ID and then second using it in query processing
|
1.0
|
process clientID input - basically taking in their client ID and first, finding any real time data associated with that ID and then second using it in query processing
|
process
|
process clientid input basically taking in their client id and first finding any real time data associated with that id and then second using it in query processing
| 1
|
107,212
| 9,204,331,973
|
IssuesEvent
|
2019-03-08 06:57:15
|
grpc/grpc
|
https://api.github.com/repos/grpc/grpc
|
closed
|
FLAKE: h2_http_proxy_nosec_test@max_connection_age@poller=poll-cv
|
infra/test env flake kind/bug lang/core priority/P1
|
https://source.cloud.google.com/results/invocations/ffdbbe38-dfb8-46ea-b300-bd87e2f8c23e/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_http_proxy_nosec_test@max_connection_age@poller%3Dpoll-cv/log
PR on 1.17.x branch: https://github.com/grpc/grpc/pull/17382
Seen on both ubsan and Debug c/C++ bazel suites
```
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //test/core/end2end:h2_http_proxy_nosec_test@max_connection_age@poller=poll-cv
-----------------------------------------------------------------------------
D1203 20:49:06.813697180 20 test_config.cc:391] test slowdown factor: sanitizer=1, fixture=1, poller=5, total=5
D1203 20:49:06.814248786 20 ev_posix.cc:169] Using polling engine: poll-cv
D1203 20:49:06.814381997 20 dns_resolver.cc:338] Using native dns resolver
I1203 20:49:06.814509824 20 http_proxy_fixture.cc:536] Proxy address: localhost:14643
D1203 20:49:06.815316304 20 dns_resolver.cc:279] Start resolving.
I1203 20:49:06.816352410 20 http_connect_handshaker.cc:300] Connecting to server localhost:14642 via HTTP proxy ipv6:[::1]:14643
D1203 20:49:06.816611664 24 http_proxy_fixture.cc:384] on_read_request_done: 0x7f5e14001620 "No Error"
I1203 20:49:06.817275162 20 subchannel.cc:841] New connected subchannel at 0x1018c80 for subchannel 0x7f5e08002c70
D1203 20:49:07.340445299 20 dns_resolver.cc:259] In cooldown from last resolution (from 525 ms ago). Will resolve again in 475 ms
D1203 20:49:07.340493604 20 dns_resolver.cc:279] Start resolving.
I1203 20:49:08.340386587 24 http_proxy_fixture.cc:162] HTTP proxy server read: {"created":"@1543870148.340362074","description":"Socket closed","fd":8,"file":"src/core/lib/iomgr/tcp_posix.cc","file_line":465,"grpc_status":14,"target_address":"ipv6:[::1]:14642"}
I1203 20:49:08.340454319 24 http_proxy_fixture.cc:162] HTTP proxy client read: {"created":"@1543870148.340432724","description":"FD shutdown","file":"src/core/lib/iomgr/ev_poll_posix.cc","file_line":532,"grpc_status":14,"referenced_errors":[{"created":"@1543870148.340362074","description":"Socket closed","fd":8,"file":"src/core/lib/iomgr/tcp_posix.cc","file_line":465,"grpc_status":14,"target_address":"ipv6:[::1]:14642"}]}
D1203 20:49:08.340543663 24 http_proxy_fixture.cc:130] endpoints: 0x7f5e14000fd0 0x7f5e14005ec0
I1203 20:49:09.340844280 20 http_proxy_fixture.cc:536] Proxy address: localhost:14645
D1203 20:49:09.341306856 20 dns_resolver.cc:279] Start resolving.
I1203 20:49:09.341781833 20 http_connect_handshaker.cc:300] Connecting to server localhost:14644 via HTTP proxy ipv6:[::1]:14645
I1203 20:49:29.341388363 23 subchannel.cc:878] Connect failed: {"created":"@1543870169.341286005","description":"FD shutdown","file":"src/core/lib/iomgr/ev_poll_posix.cc","file_line":532,"grpc_status":14,"referenced_errors":[{"created":"@1543870169.341196438","description":"Handshake timed out","file":"src/core/lib/channel/handshaker.cc","file_line":290}]}
I1203 20:49:29.341742915 20 http_connect_handshaker.cc:300] Connecting to server localhost:14644 via HTTP proxy ipv4:127.0.0.1:14645
I1203 20:49:49.341383661 28 subchannel.cc:878] Connect failed: {"created":"@1543870189.341292414","description":"FD shutdown","file":"src/core/lib/iomgr/ev_poll_posix.cc","file_line":532,"grpc_status":14,"referenced_errors":[{"created":"@1543870189.341193244","description":"Handshake timed out","file":"src/core/lib/channel/handshaker.cc","file_line":290}]}
I1203 20:49:49.341463939 28 subchannel.cc:758] Subchannel 0x7f5e08002c70: Retry immediately
I1203 20:49:49.341474264 28 subchannel.cc:719] Failed to connect to channel, retrying
D1203 20:49:49.341627337 28 dns_resolver.cc:279] Start resolving.
E1203 20:49:49.341784683 20 cq_verifier.cc:273] cq returned unexpected event: OP_COMPLETE: tag:0x1 OK
E1203 20:49:49.341803342 20 cq_verifier.cc:280] expected tags:
tag(101) GRPC_OP_COMPLETE success=1 test/core/end2end/tests/max_connection_age.cc:296
*******************************
Caught signal SIGABRT
test/core/end2end/h2_http_proxy_nosec_test[0x5a2018]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f5e1bb77390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f5e1af30428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5e1af3202a]
test/core/end2end/h2_http_proxy_nosec_test[0x474650]
test/core/end2end/h2_http_proxy_nosec_test[0x44a47e]
test/core/end2end/h2_http_proxy_nosec_test[0x449211]
test/core/end2end/h2_http_proxy_nosec_test[0x407ba2]
test/core/end2end/h2_http_proxy_nosec_test[0x405040]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f5e1af1b830]
test/core/end2end/h2_http_proxy_nosec_test[0x404c79]
Aborted (core dumped)
```
|
1.0
|
FLAKE: h2_http_proxy_nosec_test@max_connection_age@poller=poll-cv - https://source.cloud.google.com/results/invocations/ffdbbe38-dfb8-46ea-b300-bd87e2f8c23e/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_http_proxy_nosec_test@max_connection_age@poller%3Dpoll-cv/log
PR on 1.17.x branch: https://github.com/grpc/grpc/pull/17382
Seen on both ubsan and Debug c/C++ bazel suites
```
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //test/core/end2end:h2_http_proxy_nosec_test@max_connection_age@poller=poll-cv
-----------------------------------------------------------------------------
D1203 20:49:06.813697180 20 test_config.cc:391] test slowdown factor: sanitizer=1, fixture=1, poller=5, total=5
D1203 20:49:06.814248786 20 ev_posix.cc:169] Using polling engine: poll-cv
D1203 20:49:06.814381997 20 dns_resolver.cc:338] Using native dns resolver
I1203 20:49:06.814509824 20 http_proxy_fixture.cc:536] Proxy address: localhost:14643
D1203 20:49:06.815316304 20 dns_resolver.cc:279] Start resolving.
I1203 20:49:06.816352410 20 http_connect_handshaker.cc:300] Connecting to server localhost:14642 via HTTP proxy ipv6:[::1]:14643
D1203 20:49:06.816611664 24 http_proxy_fixture.cc:384] on_read_request_done: 0x7f5e14001620 "No Error"
I1203 20:49:06.817275162 20 subchannel.cc:841] New connected subchannel at 0x1018c80 for subchannel 0x7f5e08002c70
D1203 20:49:07.340445299 20 dns_resolver.cc:259] In cooldown from last resolution (from 525 ms ago). Will resolve again in 475 ms
D1203 20:49:07.340493604 20 dns_resolver.cc:279] Start resolving.
I1203 20:49:08.340386587 24 http_proxy_fixture.cc:162] HTTP proxy server read: {"created":"@1543870148.340362074","description":"Socket closed","fd":8,"file":"src/core/lib/iomgr/tcp_posix.cc","file_line":465,"grpc_status":14,"target_address":"ipv6:[::1]:14642"}
I1203 20:49:08.340454319 24 http_proxy_fixture.cc:162] HTTP proxy client read: {"created":"@1543870148.340432724","description":"FD shutdown","file":"src/core/lib/iomgr/ev_poll_posix.cc","file_line":532,"grpc_status":14,"referenced_errors":[{"created":"@1543870148.340362074","description":"Socket closed","fd":8,"file":"src/core/lib/iomgr/tcp_posix.cc","file_line":465,"grpc_status":14,"target_address":"ipv6:[::1]:14642"}]}
D1203 20:49:08.340543663 24 http_proxy_fixture.cc:130] endpoints: 0x7f5e14000fd0 0x7f5e14005ec0
I1203 20:49:09.340844280 20 http_proxy_fixture.cc:536] Proxy address: localhost:14645
D1203 20:49:09.341306856 20 dns_resolver.cc:279] Start resolving.
I1203 20:49:09.341781833 20 http_connect_handshaker.cc:300] Connecting to server localhost:14644 via HTTP proxy ipv6:[::1]:14645
I1203 20:49:29.341388363 23 subchannel.cc:878] Connect failed: {"created":"@1543870169.341286005","description":"FD shutdown","file":"src/core/lib/iomgr/ev_poll_posix.cc","file_line":532,"grpc_status":14,"referenced_errors":[{"created":"@1543870169.341196438","description":"Handshake timed out","file":"src/core/lib/channel/handshaker.cc","file_line":290}]}
I1203 20:49:29.341742915 20 http_connect_handshaker.cc:300] Connecting to server localhost:14644 via HTTP proxy ipv4:127.0.0.1:14645
I1203 20:49:49.341383661 28 subchannel.cc:878] Connect failed: {"created":"@1543870189.341292414","description":"FD shutdown","file":"src/core/lib/iomgr/ev_poll_posix.cc","file_line":532,"grpc_status":14,"referenced_errors":[{"created":"@1543870189.341193244","description":"Handshake timed out","file":"src/core/lib/channel/handshaker.cc","file_line":290}]}
I1203 20:49:49.341463939 28 subchannel.cc:758] Subchannel 0x7f5e08002c70: Retry immediately
I1203 20:49:49.341474264 28 subchannel.cc:719] Failed to connect to channel, retrying
D1203 20:49:49.341627337 28 dns_resolver.cc:279] Start resolving.
E1203 20:49:49.341784683 20 cq_verifier.cc:273] cq returned unexpected event: OP_COMPLETE: tag:0x1 OK
E1203 20:49:49.341803342 20 cq_verifier.cc:280] expected tags:
tag(101) GRPC_OP_COMPLETE success=1 test/core/end2end/tests/max_connection_age.cc:296
*******************************
Caught signal SIGABRT
test/core/end2end/h2_http_proxy_nosec_test[0x5a2018]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f5e1bb77390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f5e1af30428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5e1af3202a]
test/core/end2end/h2_http_proxy_nosec_test[0x474650]
test/core/end2end/h2_http_proxy_nosec_test[0x44a47e]
test/core/end2end/h2_http_proxy_nosec_test[0x449211]
test/core/end2end/h2_http_proxy_nosec_test[0x407ba2]
test/core/end2end/h2_http_proxy_nosec_test[0x405040]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f5e1af1b830]
test/core/end2end/h2_http_proxy_nosec_test[0x404c79]
Aborted (core dumped)
```
|
non_process
|
flake http proxy nosec test max connection age poller poll cv pr on x branch seen on both ubsan and debug c c bazel suites exec pager usr bin less exit executing tests from test core http proxy nosec test max connection age poller poll cv test config cc test slowdown factor sanitizer fixture poller total ev posix cc using polling engine poll cv dns resolver cc using native dns resolver http proxy fixture cc proxy address localhost dns resolver cc start resolving http connect handshaker cc connecting to server localhost via http proxy http proxy fixture cc on read request done no error subchannel cc new connected subchannel at for subchannel dns resolver cc in cooldown from last resolution from ms ago will resolve again in ms dns resolver cc start resolving http proxy fixture cc http proxy server read created description socket closed fd file src core lib iomgr tcp posix cc file line grpc status target address http proxy fixture cc http proxy client read created description fd shutdown file src core lib iomgr ev poll posix cc file line grpc status referenced errors http proxy fixture cc endpoints http proxy fixture cc proxy address localhost dns resolver cc start resolving http connect handshaker cc connecting to server localhost via http proxy subchannel cc connect failed created description fd shutdown file src core lib iomgr ev poll posix cc file line grpc status referenced errors http connect handshaker cc connecting to server localhost via http proxy subchannel cc connect failed created description fd shutdown file src core lib iomgr ev poll posix cc file line grpc status referenced errors subchannel cc subchannel retry immediately subchannel cc failed to connect to channel retrying dns resolver cc start resolving cq verifier cc cq returned unexpected event op complete tag ok cq verifier cc expected tags tag grpc op complete success test core tests max connection age cc caught signal sigabrt test core http proxy nosec test lib linux gnu libpthread so lib linux gnu libc so gsignal lib linux gnu libc so abort test core http proxy nosec test test core http proxy nosec test test core http proxy nosec test test core http proxy nosec test test core http proxy nosec test lib linux gnu libc so libc start main test core http proxy nosec test aborted core dumped
| 0
|
11,378
| 14,220,614,331
|
IssuesEvent
|
2020-11-17 14:45:04
|
bazelbuild/bazel
|
https://api.github.com/repos/bazelbuild/bazel
|
closed
|
Debugging grpc OUT_OF_RANGE (proto 2GB serialization limit?)
|
team-Remote-Exec type: support / not a bug (process) untriaged
|
bazel 3.1.0 is crashing with the following error:
`Caused by: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648`.
Here is the full stacktrace:
```
ERROR: /repo/BUILD:110:1: failed (Exit 34): com.google.devtools.build.lib.remote.BulkTransferException
--
ย | at com.google.devtools.build.lib.remote.RemoteCache.waitForBulkTransfer(RemoteCache.java:223)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.uploadMissing(RemoteExecutionCache.java:58)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.ensureInputsPresent(RemoteExecutionCache.java:110)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.lambda$exec$0(RemoteSpawnRunner.java:315)
ย | at com.google.devtools.build.lib.remote.Retrier.execute(Retrier.java:237)
ย | at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:116)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.exec(RemoteSpawnRunner.java:304)
ย | at com.google.devtools.build.lib.exec.SpawnRunner.execAsync(SpawnRunner.java:238)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:126)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:96)
ย | at com.google.devtools.build.lib.actions.SpawnStrategy.beginExecution(SpawnStrategy.java:39)
ย | at com.google.devtools.build.lib.exec.ProxySpawnActionContext.beginExecution(ProxySpawnActionContext.java:60)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.beginTestAttempt(StandaloneTestStrategy.java:308)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.access$100(StandaloneTestStrategy.java:68)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy$StandaloneTestRunnerSpawn.beginExecution(StandaloneTestStrategy.java:442)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginIfNotCancelled(TestRunnerAction.java:835)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginExecution(TestRunnerAction.java:804)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:860)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:851)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$4.execute(SkyframeActionExecutor.java:961)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.continueAction(SkyframeActionExecutor.java:1109)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.run(SkyframeActionExecutor.java:1080)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.runStateMachine(ActionExecutionState.java:137)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.getResultOrDependOnFuture(ActionExecutionState.java:80)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor.executeAction(SkyframeActionExecutor.java:601)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.checkCacheAndExecuteIfNeeded(ActionExecutionFunction.java:907)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.compute(ActionExecutionFunction.java:297)
ย | at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:438)
ย | at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:399)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ย | at java.base/java.lang.Thread.run(Unknown Source)
ย | Suppressed: java.io.IOException: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader.lambda$uploadBlobAsync$1(ByteStreamUploader.java:248)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:175)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:107)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$5$1.run(MoreExecutors.java:992)
ย | at io.grpc.Context$1.run(Context.java:595)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at io.grpc.Context$1FixedContextExecutor.execute(Context.java:634)
ย | at com.google.common.util.concurrent.MoreExecutors$5.execute(MoreExecutors.java:987)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.SettableFuture.setException(SettableFuture.java:54)
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader$AsyncUpload$1.onClose(ByteStreamUploader.java:505)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at com.google.devtools.build.lib.remote.util.NetworkTime$NetworkTimeCall$1.onClose(NetworkTime.java:93)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:398)
ย | at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459)
ย | at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:584)
ย | at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
ย | at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
ย | ... 3 more
ย | Caused by: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at io.grpc.Status.asRuntimeException(Status.java:523)
ย | ... 23 more
ย | . Note: Remote connection/protocol failed with: execution failed com.google.devtools.build.lib.remote.BulkTransferException
ย | at com.google.devtools.build.lib.remote.RemoteCache.waitForBulkTransfer(RemoteCache.java:223)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.uploadMissing(RemoteExecutionCache.java:58)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.ensureInputsPresent(RemoteExecutionCache.java:110)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.lambda$exec$0(RemoteSpawnRunner.java:315)
ย | at com.google.devtools.build.lib.remote.Retrier.execute(Retrier.java:237)
ย | at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:116)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.exec(RemoteSpawnRunner.java:304)
ย | at com.google.devtools.build.lib.exec.SpawnRunner.execAsync(SpawnRunner.java:238)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:126)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:96)
ย | at com.google.devtools.build.lib.actions.SpawnStrategy.beginExecution(SpawnStrategy.java:39)
ย | at com.google.devtools.build.lib.exec.ProxySpawnActionContext.beginExecution(ProxySpawnActionContext.java:60)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.beginTestAttempt(StandaloneTestStrategy.java:308)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.access$100(StandaloneTestStrategy.java:68)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy$StandaloneTestRunnerSpawn.beginExecution(StandaloneTestStrategy.java:442)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginIfNotCancelled(TestRunnerAction.java:835)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginExecution(TestRunnerAction.java:804)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:860)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:851)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$4.execute(SkyframeActionExecutor.java:961)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.continueAction(SkyframeActionExecutor.java:1109)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.run(SkyframeActionExecutor.java:1080)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.runStateMachine(ActionExecutionState.java:137)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.getResultOrDependOnFuture(ActionExecutionState.java:80)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor.executeAction(SkyframeActionExecutor.java:601)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.checkCacheAndExecuteIfNeeded(ActionExecutionFunction.java:907)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.compute(ActionExecutionFunction.java:297)
ย | at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:438)
ย | at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:399)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ย | at java.base/java.lang.Thread.run(Unknown Source)
ย | Suppressed: java.io.IOException: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader.lambda$uploadBlobAsync$1(ByteStreamUploader.java:248)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:175)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:107)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$5$1.run(MoreExecutors.java:992)
ย | at io.grpc.Context$1.run(Context.java:595)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at io.grpc.Context$1FixedContextExecutor.execute(Context.java:634)
ย | at com.google.common.util.concurrent.MoreExecutors$5.execute(MoreExecutors.java:987)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.SettableFuture.setException(SettableFuture.java:54)
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader$AsyncUpload$1.onClose(ByteStreamUploader.java:505)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at com.google.devtools.build.lib.remote.util.NetworkTime$NetworkTimeCall$1.onClose(NetworkTime.java:93)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:398)
ย | at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459)
ย | at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:584)
ย | at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
ย | at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
ย | ... 3 more
ย | Caused by: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at io.grpc.Status.asRuntimeException(Status.java:523)
ย | ... 23 more
```
I think I'm hitting the 2GB limit on protobuf serialization for remote execution. I didn't find any related issues that include this message. Are there any flags I could use to find the offending files?
|
1.0
|
Debugging grpc OUT_OF_RANGE (proto 2GB serialization limit?) - bazel 3.1.0 is crashing with the following error:
`Caused by: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648`.
Here is the full stacktrace:
```
ERROR: /repo/BUILD:110:1: failed (Exit 34): com.google.devtools.build.lib.remote.BulkTransferException
--
ย | at com.google.devtools.build.lib.remote.RemoteCache.waitForBulkTransfer(RemoteCache.java:223)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.uploadMissing(RemoteExecutionCache.java:58)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.ensureInputsPresent(RemoteExecutionCache.java:110)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.lambda$exec$0(RemoteSpawnRunner.java:315)
ย | at com.google.devtools.build.lib.remote.Retrier.execute(Retrier.java:237)
ย | at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:116)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.exec(RemoteSpawnRunner.java:304)
ย | at com.google.devtools.build.lib.exec.SpawnRunner.execAsync(SpawnRunner.java:238)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:126)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:96)
ย | at com.google.devtools.build.lib.actions.SpawnStrategy.beginExecution(SpawnStrategy.java:39)
ย | at com.google.devtools.build.lib.exec.ProxySpawnActionContext.beginExecution(ProxySpawnActionContext.java:60)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.beginTestAttempt(StandaloneTestStrategy.java:308)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.access$100(StandaloneTestStrategy.java:68)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy$StandaloneTestRunnerSpawn.beginExecution(StandaloneTestStrategy.java:442)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginIfNotCancelled(TestRunnerAction.java:835)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginExecution(TestRunnerAction.java:804)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:860)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:851)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$4.execute(SkyframeActionExecutor.java:961)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.continueAction(SkyframeActionExecutor.java:1109)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.run(SkyframeActionExecutor.java:1080)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.runStateMachine(ActionExecutionState.java:137)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.getResultOrDependOnFuture(ActionExecutionState.java:80)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor.executeAction(SkyframeActionExecutor.java:601)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.checkCacheAndExecuteIfNeeded(ActionExecutionFunction.java:907)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.compute(ActionExecutionFunction.java:297)
ย | at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:438)
ย | at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:399)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ย | at java.base/java.lang.Thread.run(Unknown Source)
ย | Suppressed: java.io.IOException: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader.lambda$uploadBlobAsync$1(ByteStreamUploader.java:248)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:175)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:107)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$5$1.run(MoreExecutors.java:992)
ย | at io.grpc.Context$1.run(Context.java:595)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at io.grpc.Context$1FixedContextExecutor.execute(Context.java:634)
ย | at com.google.common.util.concurrent.MoreExecutors$5.execute(MoreExecutors.java:987)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.SettableFuture.setException(SettableFuture.java:54)
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader$AsyncUpload$1.onClose(ByteStreamUploader.java:505)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at com.google.devtools.build.lib.remote.util.NetworkTime$NetworkTimeCall$1.onClose(NetworkTime.java:93)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:398)
ย | at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459)
ย | at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:584)
ย | at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
ย | at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
ย | ... 3 more
ย | Caused by: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at io.grpc.Status.asRuntimeException(Status.java:523)
ย | ... 23 more
ย | . Note: Remote connection/protocol failed with: execution failed com.google.devtools.build.lib.remote.BulkTransferException
ย | at com.google.devtools.build.lib.remote.RemoteCache.waitForBulkTransfer(RemoteCache.java:223)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.uploadMissing(RemoteExecutionCache.java:58)
ย | at com.google.devtools.build.lib.remote.RemoteExecutionCache.ensureInputsPresent(RemoteExecutionCache.java:110)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.lambda$exec$0(RemoteSpawnRunner.java:315)
ย | at com.google.devtools.build.lib.remote.Retrier.execute(Retrier.java:237)
ย | at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:116)
ย | at com.google.devtools.build.lib.remote.RemoteSpawnRunner.exec(RemoteSpawnRunner.java:304)
ย | at com.google.devtools.build.lib.exec.SpawnRunner.execAsync(SpawnRunner.java:238)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:126)
ย | at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:96)
ย | at com.google.devtools.build.lib.actions.SpawnStrategy.beginExecution(SpawnStrategy.java:39)
ย | at com.google.devtools.build.lib.exec.ProxySpawnActionContext.beginExecution(ProxySpawnActionContext.java:60)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.beginTestAttempt(StandaloneTestStrategy.java:308)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy.access$100(StandaloneTestStrategy.java:68)
ย | at com.google.devtools.build.lib.exec.StandaloneTestStrategy$StandaloneTestRunnerSpawn.beginExecution(StandaloneTestStrategy.java:442)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginIfNotCancelled(TestRunnerAction.java:835)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.beginExecution(TestRunnerAction.java:804)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:860)
ย | at com.google.devtools.build.lib.analysis.test.TestRunnerAction.execute(TestRunnerAction.java:851)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$4.execute(SkyframeActionExecutor.java:961)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.continueAction(SkyframeActionExecutor.java:1109)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.run(SkyframeActionExecutor.java:1080)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.runStateMachine(ActionExecutionState.java:137)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionState.getResultOrDependOnFuture(ActionExecutionState.java:80)
ย | at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor.executeAction(SkyframeActionExecutor.java:601)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.checkCacheAndExecuteIfNeeded(ActionExecutionFunction.java:907)
ย | at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.compute(ActionExecutionFunction.java:297)
ย | at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:438)
ย | at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:399)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ย | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ย | at java.base/java.lang.Thread.run(Unknown Source)
ย | Suppressed: java.io.IOException: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader.lambda$uploadBlobAsync$1(ByteStreamUploader.java:248)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:175)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.doFallback(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:107)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:93)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:752)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:185)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture$AsyncCatchingFuture.setResult(AbstractCatchingFuture.java:162)
ย | at com.google.common.util.concurrent.AbstractCatchingFuture.run(AbstractCatchingFuture.java:116)
ย | at com.google.common.util.concurrent.MoreExecutors$5$1.run(MoreExecutors.java:992)
ย | at io.grpc.Context$1.run(Context.java:595)
ย | at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:398)
ย | at io.grpc.Context$1FixedContextExecutor.execute(Context.java:634)
ย | at com.google.common.util.concurrent.MoreExecutors$5.execute(MoreExecutors.java:987)
ย | at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1024)
ย | at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:866)
ย | at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:711)
ย | at com.google.common.util.concurrent.SettableFuture.setException(SettableFuture.java:54)
ย | at com.google.devtools.build.lib.remote.ByteStreamUploader$AsyncUpload$1.onClose(ByteStreamUploader.java:505)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at com.google.devtools.build.lib.remote.util.NetworkTime$NetworkTimeCall$1.onClose(NetworkTime.java:93)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700)
ย | at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
ย | at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
ย | at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
ย | at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:398)
ย | at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459)
ย | at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467)
ย | at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:584)
ย | at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
ย | at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
ย | ... 3 more
ย | Caused by: io.grpc.StatusRuntimeException: OUT_OF_RANGE: size 2460924504 exceeds 2147483648
ย | at io.grpc.Status.asRuntimeException(Status.java:523)
ย | ... 23 more
```
I think I'm hitting the 2GB limit on protobuf serialization for remote execution. I didn't find any related issues that include this message. Are there any flags I could use to find the offending files?
|
process
|
debugging grpc out of range proto serialization limit bazel is crashing with the following error caused by io grpc statusruntimeexception out of range size exceeds here is the full stacktrace error repo build failed exit com google devtools build lib remote bulktransferexception ย at com google devtools build lib remote remotecache waitforbulktransfer remotecache java ย at com google devtools build lib remote remoteexecutioncache uploadmissing remoteexecutioncache java ย at com google devtools build lib remote remoteexecutioncache ensureinputspresent remoteexecutioncache java ย at com google devtools build lib remote remotespawnrunner lambda exec remotespawnrunner java ย at com google devtools build lib remote retrier execute retrier java ย at com google devtools build lib remote remoteretrier execute remoteretrier java ย at com google devtools build lib remote remotespawnrunner exec remotespawnrunner java ย at com google devtools build lib exec spawnrunner execasync spawnrunner java ย at com google devtools build lib exec abstractspawnstrategy exec abstractspawnstrategy java ย at com google devtools build lib exec abstractspawnstrategy exec abstractspawnstrategy java ย at com google devtools build lib actions spawnstrategy beginexecution spawnstrategy java ย at com google devtools build lib exec proxyspawnactioncontext beginexecution proxyspawnactioncontext java ย at com google devtools build lib exec standaloneteststrategy begintestattempt standaloneteststrategy java ย at com google devtools build lib exec standaloneteststrategy access standaloneteststrategy java ย at com google devtools build lib exec standaloneteststrategy standalonetestrunnerspawn beginexecution standaloneteststrategy java ย at com google devtools build lib analysis test testrunneraction beginifnotcancelled testrunneraction java ย at com google devtools build lib analysis test testrunneraction beginexecution testrunneraction java ย at com google devtools build lib analysis test testrunneraction execute testrunneraction java ย at com google devtools build lib analysis test testrunneraction execute testrunneraction java ย at com google devtools build lib skyframe skyframeactionexecutor execute skyframeactionexecutor java ย at com google devtools build lib skyframe skyframeactionexecutor actionrunner continueaction skyframeactionexecutor java ย at com google devtools build lib skyframe skyframeactionexecutor actionrunner run skyframeactionexecutor java ย at com google devtools build lib skyframe actionexecutionstate runstatemachine actionexecutionstate java ย at com google devtools build lib skyframe actionexecutionstate getresultordependonfuture actionexecutionstate java ย at com google devtools build lib skyframe skyframeactionexecutor executeaction skyframeactionexecutor java ย at com google devtools build lib skyframe actionexecutionfunction checkcacheandexecuteifneeded actionexecutionfunction java ย at com google devtools build lib skyframe actionexecutionfunction compute actionexecutionfunction java ย at com google devtools build skyframe abstractparallelevaluator evaluate run abstractparallelevaluator java ย at com google devtools build lib concurrent abstractqueuevisitor wrappedrunnable run abstractqueuevisitor java ย at java base java util concurrent threadpoolexecutor runworker unknown source ย at java base java util concurrent threadpoolexecutor worker run unknown source ย at java base java lang thread run unknown source ย suppressed java io ioexception io grpc statusruntimeexception out of range size exceeds ย at com google devtools build lib remote bytestreamuploader lambda uploadblobasync bytestreamuploader java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture dofallback abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture dofallback abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture run abstractcatchingfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setexception abstractfuture java ย at com google common util concurrent abstracttransformfuture run abstracttransformfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setexception abstractfuture java ย at com google common util concurrent abstracttransformfuture run abstracttransformfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setfuture abstractfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture run abstractcatchingfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setfuture abstractfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture run abstractcatchingfuture java ย at com google common util concurrent moreexecutors run moreexecutors java ย at io grpc context run context java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at io grpc context execute context java ย at com google common util concurrent moreexecutors execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setexception abstractfuture java ย at com google common util concurrent settablefuture setexception settablefuture java ย at com google devtools build lib remote bytestreamuploader asyncupload onclose bytestreamuploader java ย at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java ย at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java ย at com google devtools build lib remote util networktime networktimecall onclose networktime java ย at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java ย at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc internal censusstatsmodule statsclientinterceptor onclose censusstatsmodule java ย at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java ย at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc internal censustracingmodule tracingclientinterceptor onclose censustracingmodule java ย at io grpc internal clientcallimpl closeobserver clientcallimpl java ย at io grpc internal clientcallimpl access clientcallimpl java ย at io grpc internal clientcallimpl clientstreamlistenerimpl close clientcallimpl java ย at io grpc internal clientcallimpl clientstreamlistenerimpl access clientcallimpl java ย at io grpc internal clientcallimpl clientstreamlistenerimpl runincontext clientcallimpl java ย at io grpc internal contextrunnable run contextrunnable java ย at io grpc internal serializingexecutor run serializingexecutor java ย more ย caused by io grpc statusruntimeexception out of range size exceeds ย at io grpc status asruntimeexception status java ย more ย note remote connection protocol failed with execution failed com google devtools build lib remote bulktransferexception ย at com google devtools build lib remote remotecache waitforbulktransfer remotecache java ย at com google devtools build lib remote remoteexecutioncache uploadmissing remoteexecutioncache java ย at com google devtools build lib remote remoteexecutioncache ensureinputspresent remoteexecutioncache java ย at com google devtools build lib remote remotespawnrunner lambda exec remotespawnrunner java ย at com google devtools build lib remote retrier execute retrier java ย at com google devtools build lib remote remoteretrier execute remoteretrier java ย at com google devtools build lib remote remotespawnrunner exec remotespawnrunner java ย at com google devtools build lib exec spawnrunner execasync spawnrunner java ย at com google devtools build lib exec abstractspawnstrategy exec abstractspawnstrategy java ย at com google devtools build lib exec abstractspawnstrategy exec abstractspawnstrategy java ย at com google devtools build lib actions spawnstrategy beginexecution spawnstrategy java ย at com google devtools build lib exec proxyspawnactioncontext beginexecution proxyspawnactioncontext java ย at com google devtools build lib exec standaloneteststrategy begintestattempt standaloneteststrategy java ย at com google devtools build lib exec standaloneteststrategy access standaloneteststrategy java ย at com google devtools build lib exec standaloneteststrategy standalonetestrunnerspawn beginexecution standaloneteststrategy java ย at com google devtools build lib analysis test testrunneraction beginifnotcancelled testrunneraction java ย at com google devtools build lib analysis test testrunneraction beginexecution testrunneraction java ย at com google devtools build lib analysis test testrunneraction execute testrunneraction java ย at com google devtools build lib analysis test testrunneraction execute testrunneraction java ย at com google devtools build lib skyframe skyframeactionexecutor execute skyframeactionexecutor java ย at com google devtools build lib skyframe skyframeactionexecutor actionrunner continueaction skyframeactionexecutor java ย at com google devtools build lib skyframe skyframeactionexecutor actionrunner run skyframeactionexecutor java ย at com google devtools build lib skyframe actionexecutionstate runstatemachine actionexecutionstate java ย at com google devtools build lib skyframe actionexecutionstate getresultordependonfuture actionexecutionstate java ย at com google devtools build lib skyframe skyframeactionexecutor executeaction skyframeactionexecutor java ย at com google devtools build lib skyframe actionexecutionfunction checkcacheandexecuteifneeded actionexecutionfunction java ย at com google devtools build lib skyframe actionexecutionfunction compute actionexecutionfunction java ย at com google devtools build skyframe abstractparallelevaluator evaluate run abstractparallelevaluator java ย at com google devtools build lib concurrent abstractqueuevisitor wrappedrunnable run abstractqueuevisitor java ย at java base java util concurrent threadpoolexecutor runworker unknown source ย at java base java util concurrent threadpoolexecutor worker run unknown source ย at java base java lang thread run unknown source ย suppressed java io ioexception io grpc statusruntimeexception out of range size exceeds ย at com google devtools build lib remote bytestreamuploader lambda uploadblobasync bytestreamuploader java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture dofallback abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture dofallback abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture run abstractcatchingfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setexception abstractfuture java ย at com google common util concurrent abstracttransformfuture run abstracttransformfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setexception abstractfuture java ย at com google common util concurrent abstracttransformfuture run abstracttransformfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setfuture abstractfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture run abstractcatchingfuture java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setfuture abstractfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture asynccatchingfuture setresult abstractcatchingfuture java ย at com google common util concurrent abstractcatchingfuture run abstractcatchingfuture java ย at com google common util concurrent moreexecutors run moreexecutors java ย at io grpc context run context java ย at com google common util concurrent moreexecutors directexecutor execute moreexecutors java ย at io grpc context execute context java ย at com google common util concurrent moreexecutors execute moreexecutors java ย at com google common util concurrent abstractfuture executelistener abstractfuture java ย at com google common util concurrent abstractfuture complete abstractfuture java ย at com google common util concurrent abstractfuture setexception abstractfuture java ย at com google common util concurrent settablefuture setexception settablefuture java ย at com google devtools build lib remote bytestreamuploader asyncupload onclose bytestreamuploader java ย at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java ย at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java ย at com google devtools build lib remote util networktime networktimecall onclose networktime java ย at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java ย at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc internal censusstatsmodule statsclientinterceptor onclose censusstatsmodule java ย at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java ย at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java ย at io grpc internal censustracingmodule tracingclientinterceptor onclose censustracingmodule java ย at io grpc internal clientcallimpl closeobserver clientcallimpl java ย at io grpc internal clientcallimpl access clientcallimpl java ย at io grpc internal clientcallimpl clientstreamlistenerimpl close clientcallimpl java ย at io grpc internal clientcallimpl clientstreamlistenerimpl access clientcallimpl java ย at io grpc internal clientcallimpl clientstreamlistenerimpl runincontext clientcallimpl java ย at io grpc internal contextrunnable run contextrunnable java ย at io grpc internal serializingexecutor run serializingexecutor java ย more ย caused by io grpc statusruntimeexception out of range size exceeds ย at io grpc status asruntimeexception status java ย more i think i m hitting the limit on protobuf serialization for remote execution i didn t find any related issues that include this message are there any flags i could use to find the offending files
| 1
|
49,569
| 26,212,440,653
|
IssuesEvent
|
2023-01-04 08:03:44
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
torch.linalg.norm is greatly slower than numpy.linalg.norm
|
module: performance triaged module: linear algebra
|
### ๐ Describe the bug
`torch.linalg.norm` is greatly slower than `numpy.linalg.norm` with **double precision** float number.
```python
import numpy as np
import torch
print(torch.__version__)
p = np.random.rand(200000, 3)
%timeit np.linalg.norm(p, axis=1)
%timeit np.sqrt((p * p).sum(axis=1))
p_ts = torch.as_tensor(p)
%timeit torch.linalg.norm(p_ts, axis=1)
%timeit torch.sqrt((p_ts * p_ts).sum(axis=1))
```
In Jupyter cell, the output is:
```
1.13.1
3.88 ms ยฑ 141 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
4.14 ms ยฑ 227 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
21.5 ms ยฑ 395 ยตs per loop (mean ยฑ std. dev. of 7 runs, 10 loops each)
2.77 ms ยฑ 135 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
```
### Versions
PyTorch version: 1.13.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A
OS: Microsoft Windows 11 Pro for Workstations
GCC version: (Rev5, Built by MSYS2 project) 5.3.0
Python version: 3.10.8 | packaged by conda-forge | (main, Nov 22 2022, 08:16:33) [MSC v.1929 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22621-SP0
cc @ngimel @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
|
True
|
torch.linalg.norm is greatly slower than numpy.linalg.norm - ### ๐ Describe the bug
`torch.linalg.norm` is greatly slower than `numpy.linalg.norm` with **double precision** float number.
```python
import numpy as np
import torch
print(torch.__version__)
p = np.random.rand(200000, 3)
%timeit np.linalg.norm(p, axis=1)
%timeit np.sqrt((p * p).sum(axis=1))
p_ts = torch.as_tensor(p)
%timeit torch.linalg.norm(p_ts, axis=1)
%timeit torch.sqrt((p_ts * p_ts).sum(axis=1))
```
In Jupyter cell, the output is:
```
1.13.1
3.88 ms ยฑ 141 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
4.14 ms ยฑ 227 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
21.5 ms ยฑ 395 ยตs per loop (mean ยฑ std. dev. of 7 runs, 10 loops each)
2.77 ms ยฑ 135 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
```
### Versions
PyTorch version: 1.13.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A
OS: Microsoft Windows 11 Pro for Workstations
GCC version: (Rev5, Built by MSYS2 project) 5.3.0
Python version: 3.10.8 | packaged by conda-forge | (main, Nov 22 2022, 08:16:33) [MSC v.1929 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22621-SP0
cc @ngimel @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
|
non_process
|
torch linalg norm is greatly slower than numpy linalg norm ๐ describe the bug torch linalg norm is greatly slower than numpy linalg norm with double precision float number python import numpy as np import torch print torch version p np random rand timeit np linalg norm p axis timeit np sqrt p p sum axis p ts torch as tensor p timeit torch linalg norm p ts axis timeit torch sqrt p ts p ts sum axis in jupyter cell the output is ms ยฑ ยตs per loop mean ยฑ std dev of runs loops each ms ยฑ ยตs per loop mean ยฑ std dev of runs loops each ms ยฑ ยตs per loop mean ยฑ std dev of runs loops each ms ยฑ ยตs per loop mean ยฑ std dev of runs loops each versions pytorch version is debug build false cuda used to build pytorch none rocm used to build pytorch n a os microsoft windows pro for workstations gcc version built by project python version packaged by conda forge main nov bit runtime python platform windows cc ngimel jianyuh nikitaved pearu mruberry walterddr ivanyashchuk lezcano
| 0
|
21,002
| 27,871,572,928
|
IssuesEvent
|
2023-03-21 13:47:10
|
firebase/firebase-cpp-sdk
|
https://api.github.com/repos/firebase/firebase-cpp-sdk
|
reopened
|
[C++] Nightly Integration Testing Report
|
type: process nightly-testing
|
Note: This report excludes firestore. Please also check **[the report for firestore](https://github.com/firebase/firebase-cpp-sdk/issues/1178)**
***
<hidden value="integration-test-status-comment"></hidden>
### โ
[build against repo] Integration test succeeded!
Requested by @DellaBitta on commit fba10392802c8bd118730f3ea2659fa184391af5
Last updated: Tue Mar 21 03:56 PDT 2023
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/4477190996)**
<hidden value="integration-test-status-comment"></hidden>
***
### โ
[build against SDK] Integration test succeeded!
Requested by @firebase-workflow-trigger[bot] on commit fba10392802c8bd118730f3ea2659fa184391af5
Last updated: Mon Mar 20 06:26 PDT 2023
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/4467928973)**
<hidden value="integration-test-status-comment"></hidden>
|
1.0
|
[C++] Nightly Integration Testing Report - Note: This report excludes firestore. Please also check **[the report for firestore](https://github.com/firebase/firebase-cpp-sdk/issues/1178)**
***
<hidden value="integration-test-status-comment"></hidden>
### โ
[build against repo] Integration test succeeded!
Requested by @DellaBitta on commit fba10392802c8bd118730f3ea2659fa184391af5
Last updated: Tue Mar 21 03:56 PDT 2023
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/4477190996)**
<hidden value="integration-test-status-comment"></hidden>
***
### โ
[build against SDK] Integration test succeeded!
Requested by @firebase-workflow-trigger[bot] on commit fba10392802c8bd118730f3ea2659fa184391af5
Last updated: Mon Mar 20 06:26 PDT 2023
**[View integration test log & download artifacts](https://github.com/firebase/firebase-cpp-sdk/actions/runs/4467928973)**
<hidden value="integration-test-status-comment"></hidden>
|
process
|
nightly integration testing report note this report excludes firestore please also check โ
nbsp integration test succeeded requested by dellabitta on commit last updated tue mar pdt โ
nbsp integration test succeeded requested by firebase workflow trigger on commit last updated mon mar pdt
| 1
|
299
| 2,733,630,370
|
IssuesEvent
|
2015-04-17 15:02:18
|
hammerlab/pileup.js
|
https://api.github.com/repos/hammerlab/pileup.js
|
opened
|
Mocha failures are contagious
|
process
|
When one mocha async test fails, all subsequent async tests will fail. I usually work around this by adding a `?grep=` param to the `runner.html` URL, but this shouldn't be necessary. This also happens when running `grunt test` on the command line.
|
1.0
|
Mocha failures are contagious - When one mocha async test fails, all subsequent async tests will fail. I usually work around this by adding a `?grep=` param to the `runner.html` URL, but this shouldn't be necessary. This also happens when running `grunt test` on the command line.
|
process
|
mocha failures are contagious when one mocha async test fails all subsequent async tests will fail i usually work around this by adding a grep param to the runner html url but this shouldn t be necessary this also happens when running grunt test on the command line
| 1
|
370,425
| 10,931,966,559
|
IssuesEvent
|
2019-11-23 14:25:27
|
VioletVillain/CreativeCanvas
|
https://api.github.com/repos/VioletVillain/CreativeCanvas
|
closed
|
Provide a Parser Along With A Simple GUI for Configuring And Editing Different Settings.
|
Assigned Difficulty: EASY Enhancement Priority: MEDIUM
|
Refer To "Milestone: **Pre Alpha**."
|
1.0
|
Provide a Parser Along With A Simple GUI for Configuring And Editing Different Settings. - Refer To "Milestone: **Pre Alpha**."
|
non_process
|
provide a parser along with a simple gui for configuring and editing different settings refer to milestone pre alpha
| 0
|
160,465
| 6,098,001,075
|
IssuesEvent
|
2017-06-20 06:01:13
|
Gaspard--/Swords-Scrolls-and-Knuckles
|
https://api.github.com/repos/Gaspard--/Swords-Scrolls-and-Knuckles
|
closed
|
Player IA
|
priority the world is burning q33H5 required by subject
|
`On multiplayer Game, your program must at least handle two human players. Non
played characters must have the option to be AI controled. Think about allowing
a game only with AI`
|
1.0
|
Player IA - `On multiplayer Game, your program must at least handle two human players. Non
played characters must have the option to be AI controled. Think about allowing
a game only with AI`
|
non_process
|
player ia on multiplayer game your program must at least handle two human players non played characters must have the option to be ai controled think about allowing a game only with ai
| 0
|
464
| 2,903,438,723
|
IssuesEvent
|
2015-06-18 13:27:45
|
pwittchen/prefser
|
https://api.github.com/repos/pwittchen/prefser
|
closed
|
Create release notes for 1.0.5
|
release process
|
Done:
- Removed `final` keyword from `Prefser` class in order to allow class mocking
- Removed unused imports from `Prefser` class
- Added test coverage report generation
- Increased test coverage to 100%
- Added abstraction for `JsonConverter` and default `GsonConverter`
- Added `getAndObserve(...)` method
- Emiting current value right on subscription to `Observable` with `getAndObserve(...)` method
|
1.0
|
Create release notes for 1.0.5 - Done:
- Removed `final` keyword from `Prefser` class in order to allow class mocking
- Removed unused imports from `Prefser` class
- Added test coverage report generation
- Increased test coverage to 100%
- Added abstraction for `JsonConverter` and default `GsonConverter`
- Added `getAndObserve(...)` method
- Emiting current value right on subscription to `Observable` with `getAndObserve(...)` method
|
process
|
create release notes for done removed final keyword from prefser class in order to allow class mocking removed unused imports from prefser class added test coverage report generation increased test coverage to added abstraction for jsonconverter and default gsonconverter added getandobserve method emiting current value right on subscription to observable with getandobserve method
| 1
|
189,226
| 6,795,430,785
|
IssuesEvent
|
2017-11-01 15:41:10
|
OpenSourceBrain/geppetto-osb
|
https://api.github.com/repos/OpenSourceBrain/geppetto-osb
|
closed
|
Plot all recorded variables not working in live
|
bug Priority
|
For a completed simulation, the "Plot all recorded variables" option is not working in live. It seems to work after one variable has been plotted with the control panel.
|
1.0
|
Plot all recorded variables not working in live - For a completed simulation, the "Plot all recorded variables" option is not working in live. It seems to work after one variable has been plotted with the control panel.
|
non_process
|
plot all recorded variables not working in live for a completed simulation the plot all recorded variables option is not working in live it seems to work after one variable has been plotted with the control panel
| 0
|
20,555
| 27,211,588,447
|
IssuesEvent
|
2023-02-20 16:59:59
|
cse442-at-ub/project_s23-cinco
|
https://api.github.com/repos/cse442-at-ub/project_s23-cinco
|
closed
|
Design log in screen on Figma
|
Processing Task Sprint 1
|
Go to website login page: https://www.figma.com/file/8pMMrECO2YUx86OFXKaJLl/Untitled?t=NLfh2fBFdCM1SvqR-0
Test 1:
Check that there is a text field for username and password.
Check that there is a login button.
Check for a "forgot password" option and its button.
Check for a sign up or register option and its button.
Test 2:
Ensure that the login button takes you to the homepage of the website if successful, and won't if not successful.
Ensure that the forgot password button will take you to a screen that will help you change your password.
Ensure that the register button will take you to a screen where you can sign up for the website.
|
1.0
|
Design log in screen on Figma - Go to website login page: https://www.figma.com/file/8pMMrECO2YUx86OFXKaJLl/Untitled?t=NLfh2fBFdCM1SvqR-0
Test 1:
Check that there is a text field for username and password.
Check that there is a login button.
Check for a "forgot password" option and its button.
Check for a sign up or register option and its button.
Test 2:
Ensure that the login button takes you to the homepage of the website if successful, and won't if not successful.
Ensure that the forgot password button will take you to a screen that will help you change your password.
Ensure that the register button will take you to a screen where you can sign up for the website.
|
process
|
design log in screen on figma go to website login page test check that there is a text field for username and password check that there is a login button check for a forgot password option and its button check for a sign up or register option and its button test ensure that the login button takes you to the homepage of the website if successful and won t if not successful ensure that the forgot password button will take you to a screen that will help you change your password ensure that the register button will take you to a screen where you can sign up for the website
| 1
|
73,571
| 19,712,015,031
|
IssuesEvent
|
2022-01-13 06:56:40
|
google/mediapipe
|
https://api.github.com/repos/google/mediapipe
|
opened
|
Autoflip error when bazel build
|
type:build/install
|
**Describe the problem**
I have followed the installation tutorial of Mediapipe on windows10 platform. My bazel version is 4.2.2 currently. Most solutions in Mediapipe could be built and executed smoothly. Ex: FaceใObjectใIris module Demo.
But there was a confusing error when I wanted to build the Autoflip solution.
`bazel build -c opt --define MEDIAPIPE_DISABLE_GPU=1 --action_env PYTHON_BIN_PATH="C://Users//a004234//AppData//Local//Programs//Python//Python365//python.exe" mediapipe/examples/desktop/autoflip:run_autoflip`
For this problem, I have tried to clean the bazel file through "bazel clean --expunge", and updat latest Bazel version. This issue still happened. What detail am I missing?
Thanks!
**Bazel report via "--verbose_failures":**
ERROR: C:/users/a004234/_bazel_a004234/kwxb47zi/external/ceres_solver/BUILD:36:14: Compiling internal/ceres/dense_sparse_matrix.cc failed: (Exit 2): cl.exe failed: error executing command
cd C:/users/a004234/_bazel_a004234/kwxb47zi/execroot/mediapipe
SET INCLUDE=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29333\ATLMFC\include;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29333\include;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\cppwinrt
SET PATH=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\\Extensions\Microsoft\IntelliCode\CLI;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29333\bin\HostX64\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\bin\Roslyn;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Team Tools\Performance Tools;C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\\x64;C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64\;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\FSharp\;C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64;C:\Program Files (x86)\Windows Kits\10\bin\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\\MSBuild\Current\Bin;C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\Tools\;;C:\WINDOWS\system32;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\VC\Linux\bin\ConnectionManagerExe
SET PWD=/proc/self/cwd
SET PYTHON_BIN_PATH=C://Users//a004234//AppData//Local//Programs//Python//Python365//python.exe
SET RUNFILES_MANIFEST_ONLY=1
SET TEMP=C:\Users\a004234\AppData\Local\Temp
SET TMP=C:\Users\a004234\AppData\Local\Temp
C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29333/bin/HostX64/x64/cl.exe /nologo /DCOMPILER_MSVC /DNOMINMAX /D_WIN32_WINNT=0x0601 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_SECURE_NO_WARNINGS /bigobj /Zm500 /EHsc /wd4351 /wd4291 /wd4250 /wd4996 /Iexternal/ceres_solver /Ibazel-out/x64_windows-opt/bin/external/ceres_solver /Iexternal/eigen_archive /Ibazel-out/x64_windows-opt/bin/external/eigen_archive /Iexternal/com_github_glog_glog /Ibazel-out/x64_windows-opt/bin/external/com_github_glog_glog /Iexternal/com_github_gflags_gflags /Ibazel-out/x64_windows-opt/bin/external/com_github_gflags_gflags /Ibazel-out/x64_windows-opt/bin/external/com_github_glog_glog/_virtual_includes/windows_glog_headers /Ibazel-out/x64_windows-opt/bin/external/com_github_gflags_gflags/_virtual_includes/gflags /Iexternal/ceres_solver/config /Ibazel-out/x64_windows-opt/bin/external/ceres_solver/config /Iexternal/ceres_solver/include /Ibazel-out/x64_windows-opt/bin/external/ceres_solver/include /Iexternal/eigen_archive /Ibazel-out/x64_windows-opt/bin/external/eigen_archive /DEIGEN_MPL2_ONLY /DEIGEN_MAX_ALIGN_BYTES=64 /DGOOGLE_GLOG_DLL_DECL=__declspec(dllexport) /DCERES_NO_SUITESPARSE /DCERES_NO_CXSPARSE /DCERES_NO_ACCELERATE_SPARSE /DCERES_NO_LAPACK /DCERES_USE_EIGEN_SPARSE /DCERES_USE_CXX_THREADS /showIncludes /MD /O2 /Oy- /DNDEBUG /wd4117 -D__DATE__="redacted" -D__TIMESTAMP__="redacted" -D__TIME__="redacted" /Gy /Gw /w /D_USE_MATH_DEFINES /std:c++17 -Iexternal/ceres_solver/internal -Wno-sign-compare /Fobazel-out/x64_windows-opt/bin/external/ceres_solver/_objs/ceres/dense_sparse_matrix.obj /c external/ceres_solver/internal/ceres/dense_sparse_matrix.cc
Execution platform: @local_execution_config_platform//:platform
cl : Command line error D8021 : invalid numeric argument '/Wno-sign-compare'
Target //mediapipe/examples/desktop/autoflip:run_autoflip failed to build
INFO: Elapsed time: 71.979s, Critical Path: 68.58s
INFO: 171 processes: 129 internal, 42 local.
FAILED: Build did NOT complete successfully
**System information**
- MediaPipe version: on 14 Dec 2021
- Bazel version: 4.2.2
- OpenCV version: 3.4.10
- BAZEL_VS=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
- BAZEL_VC=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC
- BAZEL_VC_FULL_VERSION=14.28.29333
- BAZEL_WINSDK_FULL_VERSION=10.0.18362.0
|
1.0
|
Autoflip error when bazel build - **Describe the problem**
I have followed the installation tutorial of Mediapipe on windows10 platform. My bazel version is 4.2.2 currently. Most solutions in Mediapipe could be built and executed smoothly. Ex: FaceใObjectใIris module Demo.
But there was a confusing error when I wanted to build the Autoflip solution.
`bazel build -c opt --define MEDIAPIPE_DISABLE_GPU=1 --action_env PYTHON_BIN_PATH="C://Users//a004234//AppData//Local//Programs//Python//Python365//python.exe" mediapipe/examples/desktop/autoflip:run_autoflip`
For this problem, I have tried to clean the bazel file through "bazel clean --expunge", and updat latest Bazel version. This issue still happened. What detail am I missing?
Thanks!
**Bazel report via "--verbose_failures":**
ERROR: C:/users/a004234/_bazel_a004234/kwxb47zi/external/ceres_solver/BUILD:36:14: Compiling internal/ceres/dense_sparse_matrix.cc failed: (Exit 2): cl.exe failed: error executing command
cd C:/users/a004234/_bazel_a004234/kwxb47zi/execroot/mediapipe
SET INCLUDE=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29333\ATLMFC\include;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29333\include;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\cppwinrt
SET PATH=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\\Extensions\Microsoft\IntelliCode\CLI;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29333\bin\HostX64\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\bin\Roslyn;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Team Tools\Performance Tools;C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\\x64;C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64\;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\FSharp\;C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64;C:\Program Files (x86)\Windows Kits\10\bin\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\\MSBuild\Current\Bin;C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\Tools\;;C:\WINDOWS\system32;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja;C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\VC\Linux\bin\ConnectionManagerExe
SET PWD=/proc/self/cwd
SET PYTHON_BIN_PATH=C://Users//a004234//AppData//Local//Programs//Python//Python365//python.exe
SET RUNFILES_MANIFEST_ONLY=1
SET TEMP=C:\Users\a004234\AppData\Local\Temp
SET TMP=C:\Users\a004234\AppData\Local\Temp
C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29333/bin/HostX64/x64/cl.exe /nologo /DCOMPILER_MSVC /DNOMINMAX /D_WIN32_WINNT=0x0601 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_SECURE_NO_WARNINGS /bigobj /Zm500 /EHsc /wd4351 /wd4291 /wd4250 /wd4996 /Iexternal/ceres_solver /Ibazel-out/x64_windows-opt/bin/external/ceres_solver /Iexternal/eigen_archive /Ibazel-out/x64_windows-opt/bin/external/eigen_archive /Iexternal/com_github_glog_glog /Ibazel-out/x64_windows-opt/bin/external/com_github_glog_glog /Iexternal/com_github_gflags_gflags /Ibazel-out/x64_windows-opt/bin/external/com_github_gflags_gflags /Ibazel-out/x64_windows-opt/bin/external/com_github_glog_glog/_virtual_includes/windows_glog_headers /Ibazel-out/x64_windows-opt/bin/external/com_github_gflags_gflags/_virtual_includes/gflags /Iexternal/ceres_solver/config /Ibazel-out/x64_windows-opt/bin/external/ceres_solver/config /Iexternal/ceres_solver/include /Ibazel-out/x64_windows-opt/bin/external/ceres_solver/include /Iexternal/eigen_archive /Ibazel-out/x64_windows-opt/bin/external/eigen_archive /DEIGEN_MPL2_ONLY /DEIGEN_MAX_ALIGN_BYTES=64 /DGOOGLE_GLOG_DLL_DECL=__declspec(dllexport) /DCERES_NO_SUITESPARSE /DCERES_NO_CXSPARSE /DCERES_NO_ACCELERATE_SPARSE /DCERES_NO_LAPACK /DCERES_USE_EIGEN_SPARSE /DCERES_USE_CXX_THREADS /showIncludes /MD /O2 /Oy- /DNDEBUG /wd4117 -D__DATE__="redacted" -D__TIMESTAMP__="redacted" -D__TIME__="redacted" /Gy /Gw /w /D_USE_MATH_DEFINES /std:c++17 -Iexternal/ceres_solver/internal -Wno-sign-compare /Fobazel-out/x64_windows-opt/bin/external/ceres_solver/_objs/ceres/dense_sparse_matrix.obj /c external/ceres_solver/internal/ceres/dense_sparse_matrix.cc
Execution platform: @local_execution_config_platform//:platform
cl : Command line error D8021 : invalid numeric argument '/Wno-sign-compare'
Target //mediapipe/examples/desktop/autoflip:run_autoflip failed to build
INFO: Elapsed time: 71.979s, Critical Path: 68.58s
INFO: 171 processes: 129 internal, 42 local.
FAILED: Build did NOT complete successfully
**System information**
- MediaPipe version: on 14 Dec 2021
- Bazel version: 4.2.2
- OpenCV version: 3.4.10
- BAZEL_VS=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
- BAZEL_VC=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC
- BAZEL_VC_FULL_VERSION=14.28.29333
- BAZEL_WINSDK_FULL_VERSION=10.0.18362.0
|
non_process
|
autoflip error when bazel build describe the problem i have followed the installation tutorial of mediapipe on platform my bazel version is currently most solutions in mediapipe could be built and executed smoothly ex faceใobjectใiris module demo but there was a confusing error when i wanted to build the autoflip solution bazel build c opt define mediapipe disable gpu action env python bin path c users appdata local programs python python exe mediapipe examples desktop autoflip run autoflip for this problem i have tried to clean the bazel file through bazel clean expunge and updat latest bazel version this issue still happened what detail am i missing thanks bazel report via verbose failures error c users bazel external ceres solver build compiling internal ceres dense sparse matrix cc failed exit cl exe failed error executing command cd c users bazel execroot mediapipe set include c program files microsoft visual studio professional vc tools msvc atlmfc include c program files microsoft visual studio professional vc tools msvc include c program files windows kits netfxsdk include um c program files windows kits include ucrt c program files windows kits include shared c program files windows kits include um c program files windows kits include winrt c program files windows kits include cppwinrt set path c program files microsoft visual studio professional ide extensions microsoft intellicode cli c program files microsoft visual studio professional vc tools msvc bin c program files microsoft visual studio professional ide vc vcpackages c program files microsoft visual studio professional ide commonextensions microsoft testwindow c program files microsoft visual studio professional ide commonextensions microsoft teamfoundation team explorer c program files microsoft visual studio professional msbuild current bin roslyn c program files microsoft visual studio professional team tools performance tools c program files microsoft visual studio professional team tools performance tools c program files microsoft visual studio shared common vsperfcollectiontools c program files microsoft visual studio shared common vsperfcollectiontools c program files microsoft sdks windows bin netfx tools c program files html help workshop c program files microsoft visual studio professional ide commonextensions microsoft fsharp c program files windows kits bin c program files windows kits bin c program files microsoft visual studio professional msbuild current bin c windows microsoft net c program files microsoft visual studio professional ide c program files microsoft visual studio professional tools c windows c program files microsoft visual studio professional ide commonextensions microsoft cmake cmake bin c program files microsoft visual studio professional ide commonextensions microsoft cmake ninja c program files microsoft visual studio professional ide vc linux bin connectionmanagerexe set pwd proc self cwd set python bin path c users appdata local programs python python exe set runfiles manifest only set temp c users appdata local temp set tmp c users appdata local temp c program files microsoft visual studio professional vc tools msvc bin cl exe nologo dcompiler msvc dnominmax d winnt d crt secure no deprecate d crt secure no warnings bigobj ehsc iexternal ceres solver ibazel out windows opt bin external ceres solver iexternal eigen archive ibazel out windows opt bin external eigen archive iexternal com github glog glog ibazel out windows opt bin external com github glog glog iexternal com github gflags gflags ibazel out windows opt bin external com github gflags gflags ibazel out windows opt bin external com github glog glog virtual includes windows glog headers ibazel out windows opt bin external com github gflags gflags virtual includes gflags iexternal ceres solver config ibazel out windows opt bin external ceres solver config iexternal ceres solver include ibazel out windows opt bin external ceres solver include iexternal eigen archive ibazel out windows opt bin external eigen archive deigen only deigen max align bytes dgoogle glog dll decl declspec dllexport dceres no suitesparse dceres no cxsparse dceres no accelerate sparse dceres no lapack dceres use eigen sparse dceres use cxx threads showincludes md oy dndebug d date redacted d timestamp redacted d time redacted gy gw w d use math defines std c iexternal ceres solver internal wno sign compare fobazel out windows opt bin external ceres solver objs ceres dense sparse matrix obj c external ceres solver internal ceres dense sparse matrix cc execution platform local execution config platform platform cl command line error invalid numeric argument wno sign compare target mediapipe examples desktop autoflip run autoflip failed to build info elapsed time critical path info processes internal local failed build did not complete successfully system information mediapipe version on dec bazel version opencv version bazel vs c program files microsoft visual studio buildtools bazel vc c program files microsoft visual studio buildtools vc bazel vc full version bazel winsdk full version
| 0
|
138,322
| 20,387,624,858
|
IssuesEvent
|
2022-02-22 08:49:16
|
Regalis11/Barotrauma
|
https://api.github.com/repos/Regalis11/Barotrauma
|
closed
|
depleted fuel coilgun ammo is broken
|
Design Balance
|
- [yes] I have searched the issue tracker to check if the issue has already been reported.
**Description**
Depleted fuel coilgun ammo seems to be currently the most versatile combat item in the game, it's cheap (since fuel is not rare), it melts small monsters, medium and large targets die easily no matter if you hit the armor or not, abyss creatures eat half of a box and then start getting 300 damage per second because of the radiation, plus there's no monster armor in the game that protects against radiation. And it's a tier 1 talent item.
Some other ammunitions or weapons are better in certain situations but depleted fuel ammo is a cost efficient jack of all trades, i see a lot of people covering their subs with nothing but coilguns with depleted fuel ammo.
(I was gonna put it in discussions but it seems to be more of an issue than my own opinion)
**Version**
0.16.5
|
1.0
|
depleted fuel coilgun ammo is broken - - [yes] I have searched the issue tracker to check if the issue has already been reported.
**Description**
Depleted fuel coilgun ammo seems to be currently the most versatile combat item in the game, it's cheap (since fuel is not rare), it melts small monsters, medium and large targets die easily no matter if you hit the armor or not, abyss creatures eat half of a box and then start getting 300 damage per second because of the radiation, plus there's no monster armor in the game that protects against radiation. And it's a tier 1 talent item.
Some other ammunitions or weapons are better in certain situations but depleted fuel ammo is a cost efficient jack of all trades, i see a lot of people covering their subs with nothing but coilguns with depleted fuel ammo.
(I was gonna put it in discussions but it seems to be more of an issue than my own opinion)
**Version**
0.16.5
|
non_process
|
depleted fuel coilgun ammo is broken i have searched the issue tracker to check if the issue has already been reported description depleted fuel coilgun ammo seems to be currently the most versatile combat item in the game it s cheap since fuel is not rare it melts small monsters medium and large targets die easily no matter if you hit the armor or not abyss creatures eat half of a box and then start getting damage per second because of the radiation plus there s no monster armor in the game that protects against radiation and it s a tier talent item some other ammunitions or weapons are better in certain situations but depleted fuel ammo is a cost efficient jack of all trades i see a lot of people covering their subs with nothing but coilguns with depleted fuel ammo i was gonna put it in discussions but it seems to be more of an issue than my own opinion version
| 0
|
478,823
| 13,786,160,928
|
IssuesEvent
|
2020-10-09 00:58:32
|
zulip/zulip
|
https://api.github.com/repos/zulip/zulip
|
opened
|
Fix Tornado load issues with `peer_add` events when a large number of users join at once
|
area: api area: production priority: high
|
When many users join a large Zulip organization with thousands of users, many of whom are currently online, and dozens of default streams, we currently can generate a huge number of events that can cause load problems for the Tornado server->client events system. This is a common chain of events for a large event running on Zulip, which is increasingly common.
We had a recent partial outage related to this that was resolved by disabling `peer_add` events for the organization holding an event.
The main issue here is the `peer_add` events that we send when a user is subscribed to a stream are a fundamentally superlinear structure -- we send the event to all other clients, for each default stream, for each new user. So even a moderate rate of new user accounts can result in a very high volume.
Possibly solutions include:
* Deciding to stop sending `peer_add` events altogether in large enough organizations; they're mainly used for relatively low-value features and could be replaced with an extra RTT in cases where the data is not available. This would involve a decent amount of work and some regression in functionality.
* Including a `streams` field in the `realm_user/add` event for a new user being created, and having clients implement accessing that data. Since we have to send that event, it would eliminate the overhead of this feature. The only downside with this approach is that it could leak the set of integer IDs of private streams in the organization that the user was added to on joining to clients receiving that event. We'd need to think hard about whether that would violate Zulip's security model. One option would be to do that only for public streams, and send `peer_add` events for any private streams the user joins on account creation.
I think we should aim to do the latter approach if we can make it work, since it seems to not have major downsides.
If we're going that route, we'll need to carefully think about the interface of `do_create_user`, `process_new_human_user`, and `bulk_add_subscriptions`. It's easy enough to have `process_new_human_user` pass an option into `bulk_add_subscriptions` to make it return data on public stream subscriptions (or something) rather than sending `peer_add` events for them, but I think at present we send the `realm_user` events before even calling that function, and that's probably the right architecture, so we might want to just generalize the `peer_add` event format to support `(user_id, list_of_stream_ids)`.
|
1.0
|
Fix Tornado load issues with `peer_add` events when a large number of users join at once - When many users join a large Zulip organization with thousands of users, many of whom are currently online, and dozens of default streams, we currently can generate a huge number of events that can cause load problems for the Tornado server->client events system. This is a common chain of events for a large event running on Zulip, which is increasingly common.
We had a recent partial outage related to this that was resolved by disabling `peer_add` events for the organization holding an event.
The main issue here is the `peer_add` events that we send when a user is subscribed to a stream are a fundamentally superlinear structure -- we send the event to all other clients, for each default stream, for each new user. So even a moderate rate of new user accounts can result in a very high volume.
Possibly solutions include:
* Deciding to stop sending `peer_add` events altogether in large enough organizations; they're mainly used for relatively low-value features and could be replaced with an extra RTT in cases where the data is not available. This would involve a decent amount of work and some regression in functionality.
* Including a `streams` field in the `realm_user/add` event for a new user being created, and having clients implement accessing that data. Since we have to send that event, it would eliminate the overhead of this feature. The only downside with this approach is that it could leak the set of integer IDs of private streams in the organization that the user was added to on joining to clients receiving that event. We'd need to think hard about whether that would violate Zulip's security model. One option would be to do that only for public streams, and send `peer_add` events for any private streams the user joins on account creation.
I think we should aim to do the latter approach if we can make it work, since it seems to not have major downsides.
If we're going that route, we'll need to carefully think about the interface of `do_create_user`, `process_new_human_user`, and `bulk_add_subscriptions`. It's easy enough to have `process_new_human_user` pass an option into `bulk_add_subscriptions` to make it return data on public stream subscriptions (or something) rather than sending `peer_add` events for them, but I think at present we send the `realm_user` events before even calling that function, and that's probably the right architecture, so we might want to just generalize the `peer_add` event format to support `(user_id, list_of_stream_ids)`.
|
non_process
|
fix tornado load issues with peer add events when a large number of users join at once when many users join a large zulip organization with thousands of users many of whom are currently online and dozens of default streams we currently can generate a huge number of events that can cause load problems for the tornado server client events system this is a common chain of events for a large event running on zulip which is increasingly common we had a recent partial outage related to this that was resolved by disabling peer add events for the organization holding an event the main issue here is the peer add events that we send when a user is subscribed to a stream are a fundamentally superlinear structure we send the event to all other clients for each default stream for each new user so even a moderate rate of new user accounts can result in a very high volume possibly solutions include deciding to stop sending peer add events altogether in large enough organizations they re mainly used for relatively low value features and could be replaced with an extra rtt in cases where the data is not available this would involve a decent amount of work and some regression in functionality including a streams field in the realm user add event for a new user being created and having clients implement accessing that data since we have to send that event it would eliminate the overhead of this feature the only downside with this approach is that it could leak the set of integer ids of private streams in the organization that the user was added to on joining to clients receiving that event we d need to think hard about whether that would violate zulip s security model one option would be to do that only for public streams and send peer add events for any private streams the user joins on account creation i think we should aim to do the latter approach if we can make it work since it seems to not have major downsides if we re going that route we ll need to carefully think about the interface of do create user process new human user and bulk add subscriptions it s easy enough to have process new human user pass an option into bulk add subscriptions to make it return data on public stream subscriptions or something rather than sending peer add events for them but i think at present we send the realm user events before even calling that function and that s probably the right architecture so we might want to just generalize the peer add event format to support user id list of stream ids
| 0
|
502,242
| 14,542,916,376
|
IssuesEvent
|
2020-12-15 16:15:47
|
thehyve/omop-etl-wrapper
|
https://api.github.com/repos/thehyve/omop-etl-wrapper
|
opened
|
Add lookup functions to extract information from existing database records
|
enhancement medium priority
|
Can significantly speed up work on ETL transformations whenever a query to a standard CDM table is needed. Useful for example if you want to link a certain drug exposure with an existing `visit_occurrence_id`.
- [ ] enable caching of results?
- [ ] make part of wrapper or other module?
Examples from UKB:
```python
def lookup_visit_occurrence_id(self, **kwargs) -> Optional[int]:
return self.lookup_id(self.cdm.VisitOccurrence, 'visit_occurrence_id', **kwargs)
def lookup_visit_detail_id(self, **kwargs) -> Optional[int]:
return self.lookup_id(self.cdm.VisitDetail, 'visit_detail_id', **kwargs)
def lookup_person_id(self, person_source_value) -> Optional[int]:
return self.lookup_id(self.cdm.Person, 'person_id', person_source_value=person_source_value)
def lookup_id(self, model, id_to_lookup, **kwargs) -> Optional[int]:
query = self._session_for_lookups.query(model).filter_by(**kwargs)
try:
visit_record = query.one()
except NoResultFound:
return None
except MultipleResultsFound:
logger.warning(f'Multiple {id_to_lookup}\'s found for {kwargs}, returning first only')
visit_record = query.first()
return getattr(visit_record, id_to_lookup)
```
|
1.0
|
Add lookup functions to extract information from existing database records - Can significantly speed up work on ETL transformations whenever a query to a standard CDM table is needed. Useful for example if you want to link a certain drug exposure with an existing `visit_occurrence_id`.
- [ ] enable caching of results?
- [ ] make part of wrapper or other module?
Examples from UKB:
```python
def lookup_visit_occurrence_id(self, **kwargs) -> Optional[int]:
return self.lookup_id(self.cdm.VisitOccurrence, 'visit_occurrence_id', **kwargs)
def lookup_visit_detail_id(self, **kwargs) -> Optional[int]:
return self.lookup_id(self.cdm.VisitDetail, 'visit_detail_id', **kwargs)
def lookup_person_id(self, person_source_value) -> Optional[int]:
return self.lookup_id(self.cdm.Person, 'person_id', person_source_value=person_source_value)
def lookup_id(self, model, id_to_lookup, **kwargs) -> Optional[int]:
query = self._session_for_lookups.query(model).filter_by(**kwargs)
try:
visit_record = query.one()
except NoResultFound:
return None
except MultipleResultsFound:
logger.warning(f'Multiple {id_to_lookup}\'s found for {kwargs}, returning first only')
visit_record = query.first()
return getattr(visit_record, id_to_lookup)
```
|
non_process
|
add lookup functions to extract information from existing database records can significantly speed up work on etl transformations whenever a query to a standard cdm table is needed useful for example if you want to link a certain drug exposure with an existing visit occurrence id enable caching of results make part of wrapper or other module examples from ukb python def lookup visit occurrence id self kwargs optional return self lookup id self cdm visitoccurrence visit occurrence id kwargs def lookup visit detail id self kwargs optional return self lookup id self cdm visitdetail visit detail id kwargs def lookup person id self person source value optional return self lookup id self cdm person person id person source value person source value def lookup id self model id to lookup kwargs optional query self session for lookups query model filter by kwargs try visit record query one except noresultfound return none except multipleresultsfound logger warning f multiple id to lookup s found for kwargs returning first only visit record query first return getattr visit record id to lookup
| 0
|
215,579
| 24,183,902,059
|
IssuesEvent
|
2022-09-23 11:33:20
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
Best practices for rule executions
|
discuss Meta Team:APM Feature:Alerting Team:Observability Team:ResponseOps Team: SecuritySolution Theme: rac
|
Rules, like any other background process, can have a significant impact on Elasticsearch and Kibana performance:
- Many concurrent rules reading data from and writing data to Elasticsearch might overwhelm the cluster
- Users might configure a rule in a way that the rule execution runs for a very long time and/or consumes a lot of memory, causing issues with task distribution or even taking down Kibana
- Monitoring options are limited: we don't have all the data (yet), and rules are only accessible from one space, making it hard to get a good high-level overview.
For monitoring, the Security solution already has a great monitoring UI that hopefully other teams will adopt. We can also look into how APM will help.
I propose that we clearly document what good rule execution citizenship means, by defining best practices. I'll add a few suggestions to kick-start the discussion:
1. **Consider performance impact of unexpected user configurations or data characteristics**
Rule types that are free-form are powerful, but are also prone to misconfiguration by the user, creating a footgun. E.g., the user might configure a grouping key that is a high cardinality field, or a very short interval. These scenarios should be taken into account when designing and implementing a rule type, e.g. by limiting the amount of configurable options.
2. **Use circuit-breakers**
In some cases, misconfiguration cannot be avoided. In those scenarios we should use circuit-breakers, e.g. by limiting the amount of grouping values to 1000, or setting a timeout on an Elasticsearch query that is in proportion to the execution interval.
2. **Instrument rule with the APM agent and use it to analyse performance**
The task manager wraps a task execution (and thus, the rule execution) in an APM transaction, that can be visualised in the APM app. This is useful for local debugging, but will prove especially helpful once we enable APM for Kibana on Cloud. Rule type producers can leverage this transaction to add their own metrics. The trace waterfall provides a good overview of where rule execution time is being spent:
3. **Limit the amount of Elasticsearch requests.**
Every request to Elasticsearch will consume resources, e.g. a search thread, even if it is short. Additionally, depending on how you structure your Elasticsearch interactions, something that feels like one search, might actually become multiple requests. E.g., you're using a client to search, the client might do a privilege check, get a saved object, and only then do the search.
4. **Avoid unbound queries**
Ideally queries have a range query on a date field and / or a term query on a constant_keyword field. This allows Elasticsearch to skip indices and shards entirely, leading to faster search responses, but also to less search threads being used.
5. **Round the lower end of the time range**
Rounding the lower end of the time range, and preferably the upper end as well, means that ES caching can be leveraged better. This is especially useful when multiple rules execute around the same time. Date math expressions should be avoided if possible.
6. **Appropriately deal with delayed data**
Indexing of data might be delayed, for a handful of reasons (buffering, network latency, refresh interval, backpressure). This could mean that if you always query from `now - now-1m`, you might never see data. Rule executions should consider adding a configurable query delay option, similar to ML jobs.
7. **Handle scenarios where execution gets throttled**
If Kibana can't keep up with the amount of tasks that are being scheduled, it will start delaying task execution to prevent Kibana from falling over. Rule executions should take this into account, e.g. processing data relative to the last execution, to prevent gaps, or, explicitly allowing gaps and warning the user (this is what I think the Security Solution does). Probably not both.
|
True
|
Best practices for rule executions - Rules, like any other background process, can have a significant impact on Elasticsearch and Kibana performance:
- Many concurrent rules reading data from and writing data to Elasticsearch might overwhelm the cluster
- Users might configure a rule in a way that the rule execution runs for a very long time and/or consumes a lot of memory, causing issues with task distribution or even taking down Kibana
- Monitoring options are limited: we don't have all the data (yet), and rules are only accessible from one space, making it hard to get a good high-level overview.
For monitoring, the Security solution already has a great monitoring UI that hopefully other teams will adopt. We can also look into how APM will help.
I propose that we clearly document what good rule execution citizenship means, by defining best practices. I'll add a few suggestions to kick-start the discussion:
1. **Consider performance impact of unexpected user configurations or data characteristics**
Rule types that are free-form are powerful, but are also prone to misconfiguration by the user, creating a footgun. E.g., the user might configure a grouping key that is a high cardinality field, or a very short interval. These scenarios should be taken into account when designing and implementing a rule type, e.g. by limiting the amount of configurable options.
2. **Use circuit-breakers**
In some cases, misconfiguration cannot be avoided. In those scenarios we should use circuit-breakers, e.g. by limiting the amount of grouping values to 1000, or setting a timeout on an Elasticsearch query that is in proportion to the execution interval.
2. **Instrument rule with the APM agent and use it to analyse performance**
The task manager wraps a task execution (and thus, the rule execution) in an APM transaction, that can be visualised in the APM app. This is useful for local debugging, but will prove especially helpful once we enable APM for Kibana on Cloud. Rule type producers can leverage this transaction to add their own metrics. The trace waterfall provides a good overview of where rule execution time is being spent:
3. **Limit the amount of Elasticsearch requests.**
Every request to Elasticsearch will consume resources, e.g. a search thread, even if it is short. Additionally, depending on how you structure your Elasticsearch interactions, something that feels like one search, might actually become multiple requests. E.g., you're using a client to search, the client might do a privilege check, get a saved object, and only then do the search.
4. **Avoid unbound queries**
Ideally queries have a range query on a date field and / or a term query on a constant_keyword field. This allows Elasticsearch to skip indices and shards entirely, leading to faster search responses, but also to less search threads being used.
5. **Round the lower end of the time range**
Rounding the lower end of the time range, and preferably the upper end as well, means that ES caching can be leveraged better. This is especially useful when multiple rules execute around the same time. Date math expressions should be avoided if possible.
6. **Appropriately deal with delayed data**
Indexing of data might be delayed, for a handful of reasons (buffering, network latency, refresh interval, backpressure). This could mean that if you always query from `now - now-1m`, you might never see data. Rule executions should consider adding a configurable query delay option, similar to ML jobs.
7. **Handle scenarios where execution gets throttled**
If Kibana can't keep up with the amount of tasks that are being scheduled, it will start delaying task execution to prevent Kibana from falling over. Rule executions should take this into account, e.g. processing data relative to the last execution, to prevent gaps, or, explicitly allowing gaps and warning the user (this is what I think the Security Solution does). Probably not both.
|
non_process
|
best practices for rule executions rules like any other background process can have a significant impact on elasticsearch and kibana performance many concurrent rules reading data from and writing data to elasticsearch might overwhelm the cluster users might configure a rule in a way that the rule execution runs for a very long time and or consumes a lot of memory causing issues with task distribution or even taking down kibana monitoring options are limited we don t have all the data yet and rules are only accessible from one space making it hard to get a good high level overview for monitoring the security solution already has a great monitoring ui that hopefully other teams will adopt we can also look into how apm will help i propose that we clearly document what good rule execution citizenship means by defining best practices i ll add a few suggestions to kick start the discussion consider performance impact of unexpected user configurations or data characteristics rule types that are free form are powerful but are also prone to misconfiguration by the user creating a footgun e g the user might configure a grouping key that is a high cardinality field or a very short interval these scenarios should be taken into account when designing and implementing a rule type e g by limiting the amount of configurable options use circuit breakers in some cases misconfiguration cannot be avoided in those scenarios we should use circuit breakers e g by limiting the amount of grouping values to or setting a timeout on an elasticsearch query that is in proportion to the execution interval instrument rule with the apm agent and use it to analyse performance the task manager wraps a task execution and thus the rule execution in an apm transaction that can be visualised in the apm app this is useful for local debugging but will prove especially helpful once we enable apm for kibana on cloud rule type producers can leverage this transaction to add their own metrics the trace waterfall provides a good overview of where rule execution time is being spent limit the amount of elasticsearch requests every request to elasticsearch will consume resources e g a search thread even if it is short additionally depending on how you structure your elasticsearch interactions something that feels like one search might actually become multiple requests e g you re using a client to search the client might do a privilege check get a saved object and only then do the search avoid unbound queries ideally queries have a range query on a date field and or a term query on a constant keyword field this allows elasticsearch to skip indices and shards entirely leading to faster search responses but also to less search threads being used round the lower end of the time range rounding the lower end of the time range and preferably the upper end as well means that es caching can be leveraged better this is especially useful when multiple rules execute around the same time date math expressions should be avoided if possible appropriately deal with delayed data indexing of data might be delayed for a handful of reasons buffering network latency refresh interval backpressure this could mean that if you always query from now now you might never see data rule executions should consider adding a configurable query delay option similar to ml jobs handle scenarios where execution gets throttled if kibana can t keep up with the amount of tasks that are being scheduled it will start delaying task execution to prevent kibana from falling over rule executions should take this into account e g processing data relative to the last execution to prevent gaps or explicitly allowing gaps and warning the user this is what i think the security solution does probably not both
| 0
|
13,592
| 16,163,270,660
|
IssuesEvent
|
2021-05-01 02:58:24
|
tdwg/chrono
|
https://api.github.com/repos/tdwg/chrono
|
closed
|
Change term - ChronometricAge
|
Process - prepare for Executive review Term - change
|
## Change term
* Submitter: Stephen Richard
* Justification: Definition given on the term chrono:ChronometricAge "The age of a specimen or related materials that is generated from a dating assay." is not a definition unless 'age' is defined. In the abstract we have this: "chronometric ages - the processes and results of an assay or other analysis used to determine the age of a sample." If a thing is a process and a result, it must be the result of a process or event. These are perduants, temporal things. Interpreting probable intention, the statement reduces to "an age is a result used to determine an age". This is circular.
Specimens are endurants, they only have temporal position indirectly through their participation in events; only the events can be located in time.
*
* Proponents: anyone trying to understand what you mean.
Proposed new attributes of the term:
* Organized in Class: ChronometricAge
* Term name: chronometric age:
* Definition of the term: A temporal position assigned to an event in the history of a specimen.
* Usage comments :
The age assignment is the result of some procedure that might involve analysis of the specimen as well as observed or inferred relationships to other analyzed materials. Typically the event of interest is when the sampled object originated, but what constitutes 'origin' will depend on the kind of sample. For a fossil, the origin event might be considered the life of the organism that was fossilized, for an archeological artifact when the item was manufactured, for a sedimentary rock when the sediment was deposited, for a metamorphic rock when it was metamorphosed. Other events in the history of a specimen might also be of interest and assigned chronometric ages.
##### Necessary properties:
-- the event that is assigned a temporal position
-- the temporal reference system used to assert temporal position
-- the assigned age value (instant or interval)
##### other important properties
-- method used to assign age
-- uncertainty
* Examples:
* Refines (identifier of the broader term this term refines, if applicable):
* Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG, if applicable):
|
1.0
|
Change term - ChronometricAge - ## Change term
* Submitter: Stephen Richard
* Justification: Definition given on the term chrono:ChronometricAge "The age of a specimen or related materials that is generated from a dating assay." is not a definition unless 'age' is defined. In the abstract we have this: "chronometric ages - the processes and results of an assay or other analysis used to determine the age of a sample." If a thing is a process and a result, it must be the result of a process or event. These are perduants, temporal things. Interpreting probable intention, the statement reduces to "an age is a result used to determine an age". This is circular.
Specimens are endurants, they only have temporal position indirectly through their participation in events; only the events can be located in time.
*
* Proponents: anyone trying to understand what you mean.
Proposed new attributes of the term:
* Organized in Class: ChronometricAge
* Term name: chronometric age:
* Definition of the term: A temporal position assigned to an event in the history of a specimen.
* Usage comments :
The age assignment is the result of some procedure that might involve analysis of the specimen as well as observed or inferred relationships to other analyzed materials. Typically the event of interest is when the sampled object originated, but what constitutes 'origin' will depend on the kind of sample. For a fossil, the origin event might be considered the life of the organism that was fossilized, for an archeological artifact when the item was manufactured, for a sedimentary rock when the sediment was deposited, for a metamorphic rock when it was metamorphosed. Other events in the history of a specimen might also be of interest and assigned chronometric ages.
##### Necessary properties:
-- the event that is assigned a temporal position
-- the temporal reference system used to assert temporal position
-- the assigned age value (instant or interval)
##### other important properties
-- method used to assign age
-- uncertainty
* Examples:
* Refines (identifier of the broader term this term refines, if applicable):
* Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG, if applicable):
|
process
|
change term chronometricage change term submitter stephen richard justification definition given on the term chrono chronometricage the age of a specimen or related materials that is generated from a dating assay is not a definition unless age is defined in the abstract we have this chronometric ages the processes and results of an assay or other analysis used to determine the age of a sample if a thing is a process and a result it must be the result of a process or event these are perduants temporal things interpreting probable intention the statement reduces to an age is a result used to determine an age this is circular specimens are endurants they only have temporal position indirectly through their participation in events only the events can be located in time proponents anyone trying to understand what you mean proposed new attributes of the term organized in class chronometricage term name chronometric age definition of the term a temporal position assigned to an event in the history of a specimen usage comments the age assignment is the result of some procedure that might involve analysis of the specimen as well as observed or inferred relationships to other analyzed materials typically the event of interest is when the sampled object originated but what constitutes origin will depend on the kind of sample for a fossil the origin event might be considered the life of the organism that was fossilized for an archeological artifact when the item was manufactured for a sedimentary rock when the sediment was deposited for a metamorphic rock when it was metamorphosed other events in the history of a specimen might also be of interest and assigned chronometric ages necessary properties the event that is assigned a temporal position the temporal reference system used to assert temporal position the assigned age value instant or interval other important properties method used to assign age uncertainty examples refines identifier of the broader term this term refines if applicable replaces identifier of the existing term that would be deprecated and replaced by this term if applicable abcd xpath of the equivalent term in abcd or efg if applicable
| 1
|
337,494
| 24,542,621,845
|
IssuesEvent
|
2022-10-12 05:59:24
|
metamelb-repliCATS/aggreCAT
|
https://api.github.com/repos/metamelb-repliCATS/aggreCAT
|
opened
|
Clean up Bibliography, format according to JSS guidelines
|
documentation
|
# JSS quarto template BiBTeX guide
Cleaning up bibtex files is a somewhat tedious task โ especially when acquiring the entries automatically from mixed online sources. However, it is important that informations are complete and presented in a consistent style to avoid confusions. JSS requires the following format.
- [ ] JSS-specific markup (\proglang, \pkg, \code) should be used in the references.
- [ ] Titles should be in title case.
- [ ] Journal titles should not be abbreviated and in title case.
- [ ] DOIs should be included where available.
- [ ] Software should be properly cited as well. For R packages citation("pkgname") typically provides a good starting point.
|
1.0
|
Clean up Bibliography, format according to JSS guidelines - # JSS quarto template BiBTeX guide
Cleaning up bibtex files is a somewhat tedious task โ especially when acquiring the entries automatically from mixed online sources. However, it is important that informations are complete and presented in a consistent style to avoid confusions. JSS requires the following format.
- [ ] JSS-specific markup (\proglang, \pkg, \code) should be used in the references.
- [ ] Titles should be in title case.
- [ ] Journal titles should not be abbreviated and in title case.
- [ ] DOIs should be included where available.
- [ ] Software should be properly cited as well. For R packages citation("pkgname") typically provides a good starting point.
|
non_process
|
clean up bibliography format according to jss guidelines jss quarto template bibtex guide cleaning up bibtex files is a somewhat tedious task โ especially when acquiring the entries automatically from mixed online sources however it is important that informations are complete and presented in a consistent style to avoid confusions jss requires the following format jss specific markup proglang pkg code should be used in the references titles should be in title case journal titles should not be abbreviated and in title case dois should be included where available software should be properly cited as well for r packages citation pkgname typically provides a good starting point
| 0
|
22,687
| 31,990,439,391
|
IssuesEvent
|
2023-09-21 05:13:37
|
OpenImageIO/oiio
|
https://api.github.com/repos/OpenImageIO/oiio
|
closed
|
[FEATURE REQUEST] Add `ImageBufAlgo::normalize` implementation
|
image processing feature request good intermediate project
|
A relatively common step when dealing with interchange of 3D file formats is normalizing certain data such as vertex normal vectors.
A parallel use-case in the 2D world would be normalizing non-standard normal map textures for compatibility with a given render engine, which provides a solid case for the addition of an `ImageBufAlgo::normalize` function.
Ideally, the implementation should be general enough to support images with different center values and value ranges.
Suggested interface from @lgritz :
```c++
IBA::normalize(ImageBuf& dst, const ImageBuf& src, float center = 0.0f, scale = 1.0f, ROI roi = {}, int nthreads = 0);
```
|
1.0
|
[FEATURE REQUEST] Add `ImageBufAlgo::normalize` implementation - A relatively common step when dealing with interchange of 3D file formats is normalizing certain data such as vertex normal vectors.
A parallel use-case in the 2D world would be normalizing non-standard normal map textures for compatibility with a given render engine, which provides a solid case for the addition of an `ImageBufAlgo::normalize` function.
Ideally, the implementation should be general enough to support images with different center values and value ranges.
Suggested interface from @lgritz :
```c++
IBA::normalize(ImageBuf& dst, const ImageBuf& src, float center = 0.0f, scale = 1.0f, ROI roi = {}, int nthreads = 0);
```
|
process
|
add imagebufalgo normalize implementation a relatively common step when dealing with interchange of file formats is normalizing certain data such as vertex normal vectors a parallel use case in the world would be normalizing non standard normal map textures for compatibility with a given render engine which provides a solid case for the addition of an imagebufalgo normalize function ideally the implementation should be general enough to support images with different center values and value ranges suggested interface from lgritz c iba normalize imagebuf dst const imagebuf src float center scale roi roi int nthreads
| 1
|
192,134
| 14,600,160,974
|
IssuesEvent
|
2020-12-21 06:13:01
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
kelseyhightower/dns01-exec-plugins: googledns/vendor/cloud.google.com/go/spanner/session_test.go; 119 LoC
|
fresh large test
|
Found a possible issue in [kelseyhightower/dns01-exec-plugins](https://www.github.com/kelseyhightower/dns01-exec-plugins) at [googledns/vendor/cloud.google.com/go/spanner/session_test.go](https://github.com/kelseyhightower/dns01-exec-plugins/blob/2039e3b983b29d5ab1107e666379a42dc5dac731/googledns/vendor/cloud.google.com/go/spanner/session_test.go#L716-L834)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable ti used in defer or goroutine at line 759
[Click here to see the code in its original context.](https://github.com/kelseyhightower/dns01-exec-plugins/blob/2039e3b983b29d5ab1107e666379a42dc5dac731/googledns/vendor/cloud.google.com/go/spanner/session_test.go#L716-L834)
<details>
<summary>Click here to show the 119 line(s) of Go which triggered the analyzer.</summary>
```go
for ti, cfg := range []SessionPoolConfig{
SessionPoolConfig{},
SessionPoolConfig{maxSessionAge: 20 * time.Millisecond},
SessionPoolConfig{MinOpened: 10, MaxOpened: 100},
SessionPoolConfig{MaxBurst: 50},
SessionPoolConfig{maxSessionAge: 20 * time.Millisecond, MinOpened: 10, MaxOpened: 200, MaxBurst: 5},
SessionPoolConfig{maxSessionAge: 20 * time.Millisecond, MinOpened: 10, MaxOpened: 200, MaxBurst: 5, WriteSessions: 0.2},
} {
var wg sync.WaitGroup
// Create a more aggressive session healthchecker to increase test concurrency.
cfg.HealthCheckInterval = 50 * time.Millisecond
cfg.healthCheckSampleInterval = 10 * time.Millisecond
cfg.HealthCheckWorkers = 50
sc := testutil.NewMockCloudSpannerClient(t)
sc.MakeNice()
cfg.getRPCClient = func() (sppb.SpannerClient, error) {
return sc, nil
}
sp, _ := newSessionPool("mockdb", cfg, nil)
for i := 0; i < 100; i++ {
wg.Add(1)
// Schedule a test worker.
go func(idx int, pool *sessionPool, client sppb.SpannerClient) {
defer wg.Done()
// Test worker iterates 1K times and tries different session / session pool operations.
for j := 0; j < 1000; j++ {
if idx%10 == 0 && j >= 900 {
// Close the pool in selected set of workers during the middle of the test.
pool.close()
}
// Take a write sessions ~ 20% of the times.
takeWrite := rand.Intn(5) == 4
var (
sh *sessionHandle
gotErr error
)
if takeWrite {
sh, gotErr = pool.takeWriteSession(context.Background())
} else {
sh, gotErr = pool.take(context.Background())
}
if gotErr != nil {
if pool.isValid() {
t.Errorf("%v.%v: pool.take returns error when pool is still valid: %v", ti, idx, gotErr)
}
if wantErr := errInvalidSessionPool(); !reflect.DeepEqual(gotErr, wantErr) {
t.Errorf("%v.%v: got error when pool is closed: %v, want %v", ti, idx, gotErr, wantErr)
}
continue
}
// Verify if session is valid when session pool is valid. Note that if session pool is invalid after sh is taken,
// then sh might be invalidated by healthcheck workers.
if (sh.getID() == "" || sh.session == nil || !sh.session.isValid()) && pool.isValid() {
t.Errorf("%v.%v.%v: pool.take returns invalid session %v", ti, idx, takeWrite, sh.session)
}
if takeWrite && sh.getTransactionID() == nil {
t.Errorf("%v.%v: pool.takeWriteSession returns session %v without transaction", ti, idx, sh.session)
}
if int64(cfg.maxSessionAge) > 0 && rand.Intn(100) < idx {
// Random sleep before destroying/recycling the session, to give healthcheck worker a chance to step in.
<-time.After(time.Duration(rand.Int63n(int64(cfg.maxSessionAge))))
}
if rand.Intn(100) < idx {
// destroy the session.
sh.destroy()
continue
}
// recycle the session.
sh.recycle()
}
}(i, sp, sc)
}
wg.Wait()
sp.hc.close()
// Here the states of healthchecker, session pool and mockclient are stable.
idleSessions := map[string]bool{}
hcSessions := map[string]bool{}
mockSessions := sc.DumpSessions()
// Dump session pool's idle list.
for sl := sp.idleList.Front(); sl != nil; sl = sl.Next() {
s := sl.Value.(*session)
if idleSessions[s.getID()] {
t.Errorf("%v: found duplicated session in idle list: %v", ti, s.getID())
}
idleSessions[s.getID()] = true
}
for sl := sp.idleWriteList.Front(); sl != nil; sl = sl.Next() {
s := sl.Value.(*session)
if idleSessions[s.getID()] {
t.Errorf("%v: found duplicated session in idle write list: %v", ti, s.getID())
}
idleSessions[s.getID()] = true
}
if int(sp.numOpened) != len(idleSessions) {
t.Errorf("%v: number of opened sessions (%v) != number of idle sessions (%v)", ti, sp.numOpened, len(idleSessions))
}
if sp.createReqs != 0 {
t.Errorf("%v: number of pending session creations = %v, want 0", ti, sp.createReqs)
}
// Dump healthcheck queue.
for _, s := range sp.hc.queue.sessions {
if hcSessions[s.getID()] {
t.Errorf("%v: found duplicated session in healthcheck queue: %v", ti, s.getID())
}
hcSessions[s.getID()] = true
}
// Verify that idleSessions == hcSessions == mockSessions.
if !reflect.DeepEqual(idleSessions, hcSessions) {
t.Errorf("%v: sessions in idle list (%v) != sessions in healthcheck queue (%v)", ti, idleSessions, hcSessions)
}
if !reflect.DeepEqual(hcSessions, mockSessions) {
t.Errorf("%v: sessions in healthcheck queue (%v) != sessions in mockclient (%v)", ti, hcSessions, mockSessions)
}
sp.close()
mockSessions = sc.DumpSessions()
if len(mockSessions) != 0 {
t.Errorf("Found live sessions: %v", mockSessions)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 2039e3b983b29d5ab1107e666379a42dc5dac731
|
1.0
|
kelseyhightower/dns01-exec-plugins: googledns/vendor/cloud.google.com/go/spanner/session_test.go; 119 LoC -
Found a possible issue in [kelseyhightower/dns01-exec-plugins](https://www.github.com/kelseyhightower/dns01-exec-plugins) at [googledns/vendor/cloud.google.com/go/spanner/session_test.go](https://github.com/kelseyhightower/dns01-exec-plugins/blob/2039e3b983b29d5ab1107e666379a42dc5dac731/googledns/vendor/cloud.google.com/go/spanner/session_test.go#L716-L834)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable ti used in defer or goroutine at line 759
[Click here to see the code in its original context.](https://github.com/kelseyhightower/dns01-exec-plugins/blob/2039e3b983b29d5ab1107e666379a42dc5dac731/googledns/vendor/cloud.google.com/go/spanner/session_test.go#L716-L834)
<details>
<summary>Click here to show the 119 line(s) of Go which triggered the analyzer.</summary>
```go
for ti, cfg := range []SessionPoolConfig{
SessionPoolConfig{},
SessionPoolConfig{maxSessionAge: 20 * time.Millisecond},
SessionPoolConfig{MinOpened: 10, MaxOpened: 100},
SessionPoolConfig{MaxBurst: 50},
SessionPoolConfig{maxSessionAge: 20 * time.Millisecond, MinOpened: 10, MaxOpened: 200, MaxBurst: 5},
SessionPoolConfig{maxSessionAge: 20 * time.Millisecond, MinOpened: 10, MaxOpened: 200, MaxBurst: 5, WriteSessions: 0.2},
} {
var wg sync.WaitGroup
// Create a more aggressive session healthchecker to increase test concurrency.
cfg.HealthCheckInterval = 50 * time.Millisecond
cfg.healthCheckSampleInterval = 10 * time.Millisecond
cfg.HealthCheckWorkers = 50
sc := testutil.NewMockCloudSpannerClient(t)
sc.MakeNice()
cfg.getRPCClient = func() (sppb.SpannerClient, error) {
return sc, nil
}
sp, _ := newSessionPool("mockdb", cfg, nil)
for i := 0; i < 100; i++ {
wg.Add(1)
// Schedule a test worker.
go func(idx int, pool *sessionPool, client sppb.SpannerClient) {
defer wg.Done()
// Test worker iterates 1K times and tries different session / session pool operations.
for j := 0; j < 1000; j++ {
if idx%10 == 0 && j >= 900 {
// Close the pool in selected set of workers during the middle of the test.
pool.close()
}
// Take a write sessions ~ 20% of the times.
takeWrite := rand.Intn(5) == 4
var (
sh *sessionHandle
gotErr error
)
if takeWrite {
sh, gotErr = pool.takeWriteSession(context.Background())
} else {
sh, gotErr = pool.take(context.Background())
}
if gotErr != nil {
if pool.isValid() {
t.Errorf("%v.%v: pool.take returns error when pool is still valid: %v", ti, idx, gotErr)
}
if wantErr := errInvalidSessionPool(); !reflect.DeepEqual(gotErr, wantErr) {
t.Errorf("%v.%v: got error when pool is closed: %v, want %v", ti, idx, gotErr, wantErr)
}
continue
}
// Verify if session is valid when session pool is valid. Note that if session pool is invalid after sh is taken,
// then sh might be invalidated by healthcheck workers.
if (sh.getID() == "" || sh.session == nil || !sh.session.isValid()) && pool.isValid() {
t.Errorf("%v.%v.%v: pool.take returns invalid session %v", ti, idx, takeWrite, sh.session)
}
if takeWrite && sh.getTransactionID() == nil {
t.Errorf("%v.%v: pool.takeWriteSession returns session %v without transaction", ti, idx, sh.session)
}
if int64(cfg.maxSessionAge) > 0 && rand.Intn(100) < idx {
// Random sleep before destroying/recycling the session, to give healthcheck worker a chance to step in.
<-time.After(time.Duration(rand.Int63n(int64(cfg.maxSessionAge))))
}
if rand.Intn(100) < idx {
// destroy the session.
sh.destroy()
continue
}
// recycle the session.
sh.recycle()
}
}(i, sp, sc)
}
wg.Wait()
sp.hc.close()
// Here the states of healthchecker, session pool and mockclient are stable.
idleSessions := map[string]bool{}
hcSessions := map[string]bool{}
mockSessions := sc.DumpSessions()
// Dump session pool's idle list.
for sl := sp.idleList.Front(); sl != nil; sl = sl.Next() {
s := sl.Value.(*session)
if idleSessions[s.getID()] {
t.Errorf("%v: found duplicated session in idle list: %v", ti, s.getID())
}
idleSessions[s.getID()] = true
}
for sl := sp.idleWriteList.Front(); sl != nil; sl = sl.Next() {
s := sl.Value.(*session)
if idleSessions[s.getID()] {
t.Errorf("%v: found duplicated session in idle write list: %v", ti, s.getID())
}
idleSessions[s.getID()] = true
}
if int(sp.numOpened) != len(idleSessions) {
t.Errorf("%v: number of opened sessions (%v) != number of idle sessions (%v)", ti, sp.numOpened, len(idleSessions))
}
if sp.createReqs != 0 {
t.Errorf("%v: number of pending session creations = %v, want 0", ti, sp.createReqs)
}
// Dump healthcheck queue.
for _, s := range sp.hc.queue.sessions {
if hcSessions[s.getID()] {
t.Errorf("%v: found duplicated session in healthcheck queue: %v", ti, s.getID())
}
hcSessions[s.getID()] = true
}
// Verify that idleSessions == hcSessions == mockSessions.
if !reflect.DeepEqual(idleSessions, hcSessions) {
t.Errorf("%v: sessions in idle list (%v) != sessions in healthcheck queue (%v)", ti, idleSessions, hcSessions)
}
if !reflect.DeepEqual(hcSessions, mockSessions) {
t.Errorf("%v: sessions in healthcheck queue (%v) != sessions in mockclient (%v)", ti, hcSessions, mockSessions)
}
sp.close()
mockSessions = sc.DumpSessions()
if len(mockSessions) != 0 {
t.Errorf("Found live sessions: %v", mockSessions)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 2039e3b983b29d5ab1107e666379a42dc5dac731
|
non_process
|
kelseyhightower exec plugins googledns vendor cloud google com go spanner session test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable ti used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for ti cfg range sessionpoolconfig sessionpoolconfig sessionpoolconfig maxsessionage time millisecond sessionpoolconfig minopened maxopened sessionpoolconfig maxburst sessionpoolconfig maxsessionage time millisecond minopened maxopened maxburst sessionpoolconfig maxsessionage time millisecond minopened maxopened maxburst writesessions var wg sync waitgroup create a more aggressive session healthchecker to increase test concurrency cfg healthcheckinterval time millisecond cfg healthchecksampleinterval time millisecond cfg healthcheckworkers sc testutil newmockcloudspannerclient t sc makenice cfg getrpcclient func sppb spannerclient error return sc nil sp newsessionpool mockdb cfg nil for i i i wg add schedule a test worker go func idx int pool sessionpool client sppb spannerclient defer wg done test worker iterates times and tries different session session pool operations for j j j if idx j close the pool in selected set of workers during the middle of the test pool close take a write sessions of the times takewrite rand intn var sh sessionhandle goterr error if takewrite sh goterr pool takewritesession context background else sh goterr pool take context background if goterr nil if pool isvalid t errorf v v pool take returns error when pool is still valid v ti idx goterr if wanterr errinvalidsessionpool reflect deepequal goterr wanterr t errorf v v got error when pool is closed v want v ti idx goterr wanterr continue verify if session is valid when session pool is valid note that if session pool is invalid after sh is taken then sh might be invalidated by healthcheck workers if sh getid sh session nil sh session isvalid pool isvalid t errorf v v v pool take returns invalid session v ti idx takewrite sh session if takewrite sh gettransactionid nil t errorf v v pool takewritesession returns session v without transaction ti idx sh session if cfg maxsessionage rand intn idx random sleep before destroying recycling the session to give healthcheck worker a chance to step in time after time duration rand cfg maxsessionage if rand intn idx destroy the session sh destroy continue recycle the session sh recycle i sp sc wg wait sp hc close here the states of healthchecker session pool and mockclient are stable idlesessions map bool hcsessions map bool mocksessions sc dumpsessions dump session pool s idle list for sl sp idlelist front sl nil sl sl next s sl value session if idlesessions t errorf v found duplicated session in idle list v ti s getid idlesessions true for sl sp idlewritelist front sl nil sl sl next s sl value session if idlesessions t errorf v found duplicated session in idle write list v ti s getid idlesessions true if int sp numopened len idlesessions t errorf v number of opened sessions v number of idle sessions v ti sp numopened len idlesessions if sp createreqs t errorf v number of pending session creations v want ti sp createreqs dump healthcheck queue for s range sp hc queue sessions if hcsessions t errorf v found duplicated session in healthcheck queue v ti s getid hcsessions true verify that idlesessions hcsessions mocksessions if reflect deepequal idlesessions hcsessions t errorf v sessions in idle list v sessions in healthcheck queue v ti idlesessions hcsessions if reflect deepequal hcsessions mocksessions t errorf v sessions in healthcheck queue v sessions in mockclient v ti hcsessions mocksessions sp close mocksessions sc dumpsessions if len mocksessions t errorf found live sessions v mocksessions leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 0
|
117,618
| 9,948,279,787
|
IssuesEvent
|
2019-07-04 08:33:39
|
LIBCAS/INDIHU-Exhibition
|
https://api.github.com/repos/LIBCAS/INDIHU-Exhibition
|
closed
|
Ikonka koลก - maลพe bez dalลกรญho varovรกnรญ
|
waiting for test
|
Kliknu-li na koลก, ลรกdek se bez dalลกรญho varovรกnรญ smaลพe (zdรก se mi, ลพe takto nastaveno vลกude); moลพnรก bych vyลพadoval jeลกtฤ jedno potvrzenรญ, jinak hrozรญ, ลพe se nฤkdo uklikne.
|
1.0
|
Ikonka koลก - maลพe bez dalลกรญho varovรกnรญ - 
Kliknu-li na koลก, ลรกdek se bez dalลกรญho varovรกnรญ smaลพe (zdรก se mi, ลพe takto nastaveno vลกude); moลพnรก bych vyลพadoval jeลกtฤ jedno potvrzenรญ, jinak hrozรญ, ลพe se nฤkdo uklikne.
|
non_process
|
ikonka koลก maลพe bez dalลกรญho varovรกnรญ kliknu li na koลก ลรกdek se bez dalลกรญho varovรกnรญ smaลพe zdรก se mi ลพe takto nastaveno vลกude moลพnรก bych vyลพadoval jeลกtฤ jedno potvrzenรญ jinak hrozรญ ลพe se nฤkdo uklikne
| 0
|
7,416
| 10,540,588,983
|
IssuesEvent
|
2019-10-02 08:46:33
|
threefoldtech/jumpscaleX_threebot
|
https://api.github.com/repos/threefoldtech/jumpscaleX_threebot
|
closed
|
navigation sidebar in wikis doesn't work correctly
|
process_wontfix
|
## Steps
- Click on any element from sidebar
- try to collapse it
## Issue
it will not collapse and can't go to any element from sidebar again
|
1.0
|
navigation sidebar in wikis doesn't work correctly - ## Steps
- Click on any element from sidebar
- try to collapse it
## Issue
it will not collapse and can't go to any element from sidebar again
|
process
|
navigation sidebar in wikis doesn t work correctly steps click on any element from sidebar try to collapse it issue it will not collapse and can t go to any element from sidebar again
| 1
|
71,337
| 23,548,100,936
|
IssuesEvent
|
2022-08-21 12:27:12
|
SeleniumHQ/selenium
|
https://api.github.com/repos/SeleniumHQ/selenium
|
closed
|
selenium.common.exceptions.InvalidArgumentException: Message: invalid argument
|
I-defect needs-triaging
|
### What happened?
Hi,
I was running a script on Selenium 4.2 with Webdriver Manager and encountered an issue.
### How can we reproduce the issue?
```shell
from selenium import webdriver
from selenium.webdriver.chrome.service import Service as ChromeService
from selenium.webdriver.common.by import By
from webdriver_manager.chrome import ChromeDriverManager
import time
driver = webdriver.Chrome(service=ChromeService(ChromeDriverManager().install()))
driver.get("//https:www.google.com")
time.sleep(100)
driver.find_element(By.ID, "input").click()
driver.quit()
Python 3.10
Selenium 4.2
Chrome Version 104.0.5112.102 (Official Build) (64-bit)
```
### Relevant log output
```shell
------------------------------------------------------------------------- Captured stderr --------------------------------------------------------------------------
[WDM] - ====== WebDriver manager ======
[WDM] - Current google-chrome version is 104.0.5112
[WDM] - Get LATEST chromedriver version for 104.0.5112 google-chrome
[WDM] - Driver [C:\Users\Preety Gupta\.wdm\drivers\chromedriver\win32\104.0.5112.79\chromedriver.exe] found in cache
===================================================================== short test summary info ======================================================================
ERROR test_sel.py - selenium.common.exceptions.InvalidArgumentException: Message: invalid argument
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
========================================================================= 1 error in 6.67s =========================================================================
```
### Operating System
Windows 10
### Selenium version
Selenium 4.2
### What are the browser(s) and version(s) where you see this issue?
Chrome Version 104.0.5112.102 (Official Build) (64-bit)
### What are the browser driver(s) and version(s) where you see this issue?
Chrome Version 104.0.5112.102
### Are you using Selenium Grid?
No
|
1.0
|
selenium.common.exceptions.InvalidArgumentException: Message: invalid argument - ### What happened?
Hi,
I was running a script on Selenium 4.2 with Webdriver Manager and encountered an issue.
### How can we reproduce the issue?
```shell
from selenium import webdriver
from selenium.webdriver.chrome.service import Service as ChromeService
from selenium.webdriver.common.by import By
from webdriver_manager.chrome import ChromeDriverManager
import time
driver = webdriver.Chrome(service=ChromeService(ChromeDriverManager().install()))
driver.get("//https:www.google.com")
time.sleep(100)
driver.find_element(By.ID, "input").click()
driver.quit()
Python 3.10
Selenium 4.2
Chrome Version 104.0.5112.102 (Official Build) (64-bit)
```
### Relevant log output
```shell
------------------------------------------------------------------------- Captured stderr --------------------------------------------------------------------------
[WDM] - ====== WebDriver manager ======
[WDM] - Current google-chrome version is 104.0.5112
[WDM] - Get LATEST chromedriver version for 104.0.5112 google-chrome
[WDM] - Driver [C:\Users\Preety Gupta\.wdm\drivers\chromedriver\win32\104.0.5112.79\chromedriver.exe] found in cache
===================================================================== short test summary info ======================================================================
ERROR test_sel.py - selenium.common.exceptions.InvalidArgumentException: Message: invalid argument
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
========================================================================= 1 error in 6.67s =========================================================================
```
### Operating System
Windows 10
### Selenium version
Selenium 4.2
### What are the browser(s) and version(s) where you see this issue?
Chrome Version 104.0.5112.102 (Official Build) (64-bit)
### What are the browser driver(s) and version(s) where you see this issue?
Chrome Version 104.0.5112.102
### Are you using Selenium Grid?
No
|
non_process
|
selenium common exceptions invalidargumentexception message invalid argument what happened hi i was running a script on selenium with webdriver manager and encountered an issue how can we reproduce the issue shell from selenium import webdriver from selenium webdriver chrome service import service as chromeservice from selenium webdriver common by import by from webdriver manager chrome import chromedrivermanager import time driver webdriver chrome service chromeservice chromedrivermanager install driver get https time sleep driver find element by id input click driver quit python selenium chrome version official build bit relevant log output shell captured stderr webdriver manager current google chrome version is get latest chromedriver version for google chrome driver found in cache short test summary info error test sel py selenium common exceptions invalidargumentexception message invalid argument interrupted error during collection error in operating system windows selenium version selenium what are the browser s and version s where you see this issue chrome version official build bit what are the browser driver s and version s where you see this issue chrome version are you using selenium grid no
| 0
|
3,444
| 6,538,268,755
|
IssuesEvent
|
2017-09-01 04:51:52
|
amaster507/ifbmt
|
https://api.github.com/repos/amaster507/ifbmt
|
opened
|
Ideas and Vision - Jeremy Bingham
|
idea process
|
I am thinking of a missionary making calls for meetings and being able to tap the phone number to call from a phone, while having it open on a tablet or PC and with the ability to type notes on the call or create a calendar item for a scheduled meeting.
|
1.0
|
Ideas and Vision - Jeremy Bingham - I am thinking of a missionary making calls for meetings and being able to tap the phone number to call from a phone, while having it open on a tablet or PC and with the ability to type notes on the call or create a calendar item for a scheduled meeting.
|
process
|
ideas and vision jeremy bingham i am thinking of a missionary making calls for meetings and being able to tap the phone number to call from a phone while having it open on a tablet or pc and with the ability to type notes on the call or create a calendar item for a scheduled meeting
| 1
|
6,909
| 10,059,846,747
|
IssuesEvent
|
2019-07-22 17:23:59
|
googleapis/google-cloud-java
|
https://api.github.com/repos/googleapis/google-cloud-java
|
closed
|
Outdated PMD config
|
type: process
|
The packaged PMD configuration file produces tons of Warnings on the latest versions of PMD and will cause outright failures in the upcoming PMD 7.0 release.
I have produced an updated version of the PMD config file.
See also: https://github.com/google/styleguide/issues/321#issuecomment-476400843
|
1.0
|
Outdated PMD config - The packaged PMD configuration file produces tons of Warnings on the latest versions of PMD and will cause outright failures in the upcoming PMD 7.0 release.
I have produced an updated version of the PMD config file.
See also: https://github.com/google/styleguide/issues/321#issuecomment-476400843
|
process
|
outdated pmd config the packaged pmd configuration file produces tons of warnings on the latest versions of pmd and will cause outright failures in the upcoming pmd release i have produced an updated version of the pmd config file see also
| 1
|
123,163
| 17,772,181,452
|
IssuesEvent
|
2021-08-30 14:49:45
|
kapseliboi/zotero
|
https://api.github.com/repos/kapseliboi/zotero
|
opened
|
CVE-2021-23337 (High) detected in lodash-4.17.20.tgz
|
security vulnerability
|
## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.20.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: zotero/package.json</p>
<p>Path to vulnerable library: zotero/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- cli-7.12.1.tgz (Root Library)
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/zotero/commit/3cf45924442ab2512d5d382270f6e567cbbf4be9">3cf45924442ab2512d5d382270f6e567cbbf4be9</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</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-23337 (High) detected in lodash-4.17.20.tgz - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.20.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: zotero/package.json</p>
<p>Path to vulnerable library: zotero/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- cli-7.12.1.tgz (Root Library)
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/zotero/commit/3cf45924442ab2512d5d382270f6e567cbbf4be9">3cf45924442ab2512d5d382270f6e567cbbf4be9</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in lodash tgz cve high severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file zotero package json path to vulnerable library zotero node modules lodash package json dependency hierarchy cli tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash step up your open source security game with whitesource
| 0
|
15,792
| 19,982,856,733
|
IssuesEvent
|
2022-01-30 06:53:51
|
CATcher-org/CATcher
|
https://api.github.com/repos/CATcher-org/CATcher
|
opened
|
Create Issue Templates for Users / Developers
|
aspect-Process p.Low
|
# Summary
As an Open Source Project, it becomes painful to see developers writing bug reports
which do not clarify what the bug is about. (Which was one of the purposes of CATcher
as well) ๐
## Description
We can aim to come up with a few issue templates for Bug Reports / Feature Requests such that
issue reporters are guided to give good features / clarify their issues before submitting
Can refer to an example from [NUSMods](https://github.com/nusmodifications/nusmods/tree/master/.github/ISSUE_TEMPLATE) to see how it is done and their respective [PR](https://github.com/nusmodifications/nusmods/commit/6b4b8720caab05f2b3d1bc032aecb93851265427#diff-3afc0895c6bbf0cf8777294fd7c3a51a6023cc78fd51bf2e29679553b63196c7)
|
1.0
|
Create Issue Templates for Users / Developers - # Summary
As an Open Source Project, it becomes painful to see developers writing bug reports
which do not clarify what the bug is about. (Which was one of the purposes of CATcher
as well) ๐
## Description
We can aim to come up with a few issue templates for Bug Reports / Feature Requests such that
issue reporters are guided to give good features / clarify their issues before submitting
Can refer to an example from [NUSMods](https://github.com/nusmodifications/nusmods/tree/master/.github/ISSUE_TEMPLATE) to see how it is done and their respective [PR](https://github.com/nusmodifications/nusmods/commit/6b4b8720caab05f2b3d1bc032aecb93851265427#diff-3afc0895c6bbf0cf8777294fd7c3a51a6023cc78fd51bf2e29679553b63196c7)
|
process
|
create issue templates for users developers summary as an open source project it becomes painful to see developers writing bug reports which do not clarify what the bug is about which was one of the purposes of catcher as well ๐ description we can aim to come up with a few issue templates for bug reports feature requests such that issue reporters are guided to give good features clarify their issues before submitting can refer to an example from to see how it is done and their respective
| 1
|
22,493
| 31,467,854,352
|
IssuesEvent
|
2023-08-30 04:33:34
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Save features to files overwrites whole GeoPackage
|
Processing Bug Crash/Data Corruption
|
### What is the bug or the crash?
A pre-existing GeoPackage gets overwritten by QGIS โSave features to filesโ
### Steps to reproduce the issue
Save a vector layer to a GeoPackage using QGIS โSave vector features to fileโ
### Versions
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body>
QGIS version | 3.28.9-Firenze | QGIS code branch | Release 3.28
-- | -- | -- | --
Qt version | 5.15.10
Python version | 3.11.4
GDAL/OGR version | 3.7.1
PROJ version | 9.2.1
EPSG Registry database version | v10.088 (2023-05-13)
GEOS version | 3.12.0-CAPI-1.18.0
SQLite version | 3.42.0
PDAL version | 2.5.5
PostgreSQL client version | unknown
SpatiaLite version | 5.1.0
QWT version | 6.1.6
QScintilla2 version | 2.13.3
OS version | macOS 13.4
ย | ย | ย | ย
Active Python plugins
QuickOSM | 2.2.3
profiletool | 4.2.6
processing_saga_nextgen | 0.0.7
Serval | 3.10.5
valuetool | 3.0.17
processing | 2.12.99
sagaprovider | 2.12.99
grassprovider | 2.12.99
db_manager | 0.1.20
MetaSearch | 0.3.6
</body></html>QGIS version
3.28.9-Firenze
QGIS code branch
[Release 3.28](https://github.com/qgis/QGIS/tree/release-3_28)
Qt version
5.15.10
Python version
3.11.4
GDAL/OGR version
3.7.1
PROJ version
9.2.1
EPSG Registry database version
v10.088 (2023-05-13)
GEOS version
3.12.0-CAPI-1.18.0
SQLite version
3.42.0
PDAL version
2.5.5
PostgreSQL client version
unknown
SpatiaLite version
5.1.0
QWT version
6.1.6
QScintilla2 version
2.13.3
OS version
macOS 13.4
Active Python plugins
QuickOSM
2.2.3
profiletool
4.2.6
processing_saga_nextgen
0.0.7
Serval
3.10.5
valuetool
3.0.17
processing
2.12.99
sagaprovider
2.12.99
grassprovider
2.12.99
db_manager
0.1.20
MetaSearch
0.3.6
### Supported QGIS version
- [X] I'm running a supported QGIS version according to [the roadmap](https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule).
### New profile
- [X] I tried with a new [QGIS profile](https://docs.qgis.org/latest/en/docs/user_manual/introduction/qgis_configuration.html#working-with-user-profiles)
### Additional context
The main issue here is that on macOS, when dealing with GeoPackages, one is _always_ asked if one wants to fully replace the pre-existing GeoPackage.
Some tools will do that, some other tools will add the layers to the GeoPackageโฏ; but it's impossible to know in advance.
And it's not clear from the description of โSave vector features to filesโ that it is intended to overwrite.
The โPackage layersโ tool for examples has a different behaviour.
|
1.0
|
Save features to files overwrites whole GeoPackage - ### What is the bug or the crash?
A pre-existing GeoPackage gets overwritten by QGIS โSave features to filesโ
### Steps to reproduce the issue
Save a vector layer to a GeoPackage using QGIS โSave vector features to fileโ
### Versions
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body>
QGIS version | 3.28.9-Firenze | QGIS code branch | Release 3.28
-- | -- | -- | --
Qt version | 5.15.10
Python version | 3.11.4
GDAL/OGR version | 3.7.1
PROJ version | 9.2.1
EPSG Registry database version | v10.088 (2023-05-13)
GEOS version | 3.12.0-CAPI-1.18.0
SQLite version | 3.42.0
PDAL version | 2.5.5
PostgreSQL client version | unknown
SpatiaLite version | 5.1.0
QWT version | 6.1.6
QScintilla2 version | 2.13.3
OS version | macOS 13.4
ย | ย | ย | ย
Active Python plugins
QuickOSM | 2.2.3
profiletool | 4.2.6
processing_saga_nextgen | 0.0.7
Serval | 3.10.5
valuetool | 3.0.17
processing | 2.12.99
sagaprovider | 2.12.99
grassprovider | 2.12.99
db_manager | 0.1.20
MetaSearch | 0.3.6
</body></html>QGIS version
3.28.9-Firenze
QGIS code branch
[Release 3.28](https://github.com/qgis/QGIS/tree/release-3_28)
Qt version
5.15.10
Python version
3.11.4
GDAL/OGR version
3.7.1
PROJ version
9.2.1
EPSG Registry database version
v10.088 (2023-05-13)
GEOS version
3.12.0-CAPI-1.18.0
SQLite version
3.42.0
PDAL version
2.5.5
PostgreSQL client version
unknown
SpatiaLite version
5.1.0
QWT version
6.1.6
QScintilla2 version
2.13.3
OS version
macOS 13.4
Active Python plugins
QuickOSM
2.2.3
profiletool
4.2.6
processing_saga_nextgen
0.0.7
Serval
3.10.5
valuetool
3.0.17
processing
2.12.99
sagaprovider
2.12.99
grassprovider
2.12.99
db_manager
0.1.20
MetaSearch
0.3.6
### Supported QGIS version
- [X] I'm running a supported QGIS version according to [the roadmap](https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule).
### New profile
- [X] I tried with a new [QGIS profile](https://docs.qgis.org/latest/en/docs/user_manual/introduction/qgis_configuration.html#working-with-user-profiles)
### Additional context
The main issue here is that on macOS, when dealing with GeoPackages, one is _always_ asked if one wants to fully replace the pre-existing GeoPackage.
Some tools will do that, some other tools will add the layers to the GeoPackageโฏ; but it's impossible to know in advance.
And it's not clear from the description of โSave vector features to filesโ that it is intended to overwrite.
The โPackage layersโ tool for examples has a different behaviour.
|
process
|
save features to files overwrites whole geopackage what is the bug or the crash a pre existing geopackage gets overwritten by qgis โsave features to filesโ steps to reproduce the issue save a vector layer to a geopackage using qgis โsave vector features to fileโ versions doctype html public dtd html en p li white space pre wrap qgis version firenze qgis code branch release qt version python version gdal ogr version proj version epsg registry database version geos version capi sqlite version pdal version postgresql client version unknown spatialite version qwt version version os version macos ย ย ย ย active python plugins quickosm profiletool processing saga nextgen serval valuetool processing sagaprovider grassprovider db manager metasearch qgis version firenze qgis code branch qt version python version gdal ogr version proj version epsg registry database version geos version capi sqlite version pdal version postgresql client version unknown spatialite version qwt version version os version macos active python plugins quickosm profiletool processing saga nextgen serval valuetool processing sagaprovider grassprovider db manager metasearch supported qgis version i m running a supported qgis version according to new profile i tried with a new additional context the main issue here is that on macos when dealing with geopackages one is always asked if one wants to fully replace the pre existing geopackage some tools will do that some other tools will add the layers to the geopackageโฏ but it s impossible to know in advance and it s not clear from the description of โsave vector features to filesโ that it is intended to overwrite the โpackage layersโ tool for examples has a different behaviour
| 1
|
296,198
| 22,292,273,194
|
IssuesEvent
|
2022-06-12 14:40:45
|
seawee1/driver-dojo
|
https://api.github.com/repos/seawee1/driver-dojo
|
opened
|
Sphinx documentation
|
documentation
|
Besides code documentation, we would like to provide a [Sphinx](https://www.sphinx-doc.org/en/master/) for Driver Dojo
|
1.0
|
Sphinx documentation - Besides code documentation, we would like to provide a [Sphinx](https://www.sphinx-doc.org/en/master/) for Driver Dojo
|
non_process
|
sphinx documentation besides code documentation we would like to provide a for driver dojo
| 0
|
44,277
| 12,101,435,548
|
IssuesEvent
|
2020-04-20 15:12:40
|
codesmithtools/Templates
|
https://api.github.com/repos/codesmithtools/Templates
|
closed
|
EnumList does not match full table name expressions
|
Framework-PLINQO Type-Defect auto-migrated
|
```
Both the IncludeList and IgnoreList match full table name expressions to
precisely identify table names to include or ignore as mapped entities. For
example:
^dbo.Customer$
^dbo.Order$
But a full table name expression in the EnumList does NOT result in an enum
being generated from that table. For example:
^dbo.Product$
Changing the expression in the EnumList to a sub-string match results in an
enum being generated from that table:
Product
I would expect expression parsing to have similarly predictable results for
EnumList as for IncludeList and IgnoreList.
```
Original issue reported on code.google.com by `dustin.w...@imaginelearning.com` on 19 Jan 2012 at 6:06
|
1.0
|
EnumList does not match full table name expressions - ```
Both the IncludeList and IgnoreList match full table name expressions to
precisely identify table names to include or ignore as mapped entities. For
example:
^dbo.Customer$
^dbo.Order$
But a full table name expression in the EnumList does NOT result in an enum
being generated from that table. For example:
^dbo.Product$
Changing the expression in the EnumList to a sub-string match results in an
enum being generated from that table:
Product
I would expect expression parsing to have similarly predictable results for
EnumList as for IncludeList and IgnoreList.
```
Original issue reported on code.google.com by `dustin.w...@imaginelearning.com` on 19 Jan 2012 at 6:06
|
non_process
|
enumlist does not match full table name expressions both the includelist and ignorelist match full table name expressions to precisely identify table names to include or ignore as mapped entities for example dbo customer dbo order but a full table name expression in the enumlist does not result in an enum being generated from that table for example dbo product changing the expression in the enumlist to a sub string match results in an enum being generated from that table product i would expect expression parsing to have similarly predictable results for enumlist as for includelist and ignorelist original issue reported on code google com by dustin w imaginelearning com on jan at
| 0
|
17,757
| 23,671,490,357
|
IssuesEvent
|
2022-08-27 12:29:25
|
OpenDataScotland/the_od_bods
|
https://api.github.com/repos/OpenDataScotland/the_od_bods
|
closed
|
create collection of keywords relevant to categories
|
data processing
|
a task emerging from #35 and a question of if we can use keywords to identify what category(s) a dataset should belong to. See https://github.com/OpenDataScotland/the_od_bods/files/7613702/TagsToCategories.csv in particular
|
1.0
|
create collection of keywords relevant to categories - a task emerging from #35 and a question of if we can use keywords to identify what category(s) a dataset should belong to. See https://github.com/OpenDataScotland/the_od_bods/files/7613702/TagsToCategories.csv in particular
|
process
|
create collection of keywords relevant to categories a task emerging from and a question of if we can use keywords to identify what category s a dataset should belong to see in particular
| 1
|
7,003
| 10,146,102,606
|
IssuesEvent
|
2019-08-05 07:12:10
|
raxod502/straight.el
|
https://api.github.com/repos/raxod502/straight.el
|
closed
|
How to work around 'could not read Username'
|
fork https process buffer ssh support ux waiting on response
|
Hi. I've been using the command line git all the time, and today I want to see if straight.el can help me contributing my code to Emacs packages easier. I set up `:fork` in the recipe, and the "origin" and "fork" remotes are set correctly by straight.el. But when I finished my change and using `straight-push-package`, but there's the error
```
fatal: could not read Username for 'https://github.com': No such file or directory
```
I hope straight.el ask me for username/password and push my change, but it didn't. I assume if I use ssh remote URL, these problems will be solved since username/password are not needed. However, set `straight-vc-git-default-protocol` to `'ssh` makes me cannot clone other people's packages, and seems there's no way to use ssh URL only for my packages/forks using straight.el.
Am I doing it right? If not, what's the correct way to develop other people's packages with straight.el?
Thanks!
|
1.0
|
How to work around 'could not read Username' - Hi. I've been using the command line git all the time, and today I want to see if straight.el can help me contributing my code to Emacs packages easier. I set up `:fork` in the recipe, and the "origin" and "fork" remotes are set correctly by straight.el. But when I finished my change and using `straight-push-package`, but there's the error
```
fatal: could not read Username for 'https://github.com': No such file or directory
```
I hope straight.el ask me for username/password and push my change, but it didn't. I assume if I use ssh remote URL, these problems will be solved since username/password are not needed. However, set `straight-vc-git-default-protocol` to `'ssh` makes me cannot clone other people's packages, and seems there's no way to use ssh URL only for my packages/forks using straight.el.
Am I doing it right? If not, what's the correct way to develop other people's packages with straight.el?
Thanks!
|
process
|
how to work around could not read username hi i ve been using the command line git all the time and today i want to see if straight el can help me contributing my code to emacs packages easier i set up fork in the recipe and the origin and fork remotes are set correctly by straight el but when i finished my change and using straight push package but there s the error fatal could not read username for no such file or directory i hope straight el ask me for username password and push my change but it didn t i assume if i use ssh remote url these problems will be solved since username password are not needed however set straight vc git default protocol to ssh makes me cannot clone other people s packages and seems there s no way to use ssh url only for my packages forks using straight el am i doing it right if not what s the correct way to develop other people s packages with straight el thanks
| 1
|
18,075
| 12,529,147,683
|
IssuesEvent
|
2020-06-04 10:48:20
|
the-tale/the-tale
|
https://api.github.com/repos/the-tale/the-tale
|
opened
|
Discord: ัะฒะฝะพ ัะพะพะฑัะฐัั ะธะณัะพะบั, ััะพ ะฝะฐัะฐะปะฐัั ะพะฑัะฐะฑะพัะบะฐ ะตะณะพ ะบะพะผะฐะฝะดั ะธ ััะพ ะพะฝะฐ ะทะฐะฒะตััะธะปะฐัั
|
comp_discord cont_usability est_medium good first issue type_improvement
|
ะกะตะนัะฐั ะฝะตะบะพัะพััะต ะบะพะผะฐะฝะดั ะฒะพะทะฒัะฐัะฐัั ัะฟัะฐะฒะปะตะฝะธะต ัะฐะฝััะต, ัะตะผ ะฑัะดัั ะทะฐะฒะตััะตะฝั ะธะฝะธัะธะธัะพะฒะฐะฝะฝัะต ะธะผะธ ะดะตะนััะฒะธั.
ะกะฐะผะพ ะฟะพ ัะตะฑะต ััะพ ะฟัะฐะฒะธะปัะฝะพ, ั ัะพัะบะธ ะทัะตะฝะธั ัะตะบััะตะน ะฐัั
ะธัะตะบัััั, ะฝะพ ะฝะตัะดะพะฑะฝะพ ั ัะพัะบะธ ะทัะตะฝะธั ะฟะพะปัะทะพะฒะฐัะตะปะตะน.
ะะฐะดะพ ััะพ-ะฝะธะฑัะดั ะฟัะธะดัะผะฐัั.
ะะฐัะธะฐะฝัั:
- ะกะปะฐัั ัะพะพะฑัะตะฝะธะต ะพ ะฝะฐัะฐะปะต ะพะฟะตัะฐัะธะน ะดะปั ะบะฐะถะดะพะน (?) ะบะพะผะฐะฝะดั.
- ะกะบะพััะตะบัะธัะพะฒะฐัั ัะพะพะฑัะตะฝะธั ะฑะพัะฐ ัะฐะบ, ััะพะฑั ะตะณะพ ะฟะพะฒะตะดะตะฝะธะต ััะฐะปะพ ะฟะพะฝััะฝัะผ.
- ะฏะฒะฝะพ ะดะพะถะธะดะฐัััั ะทะฐะฒะตััะตะฝะธั ะฒัะตั
ะพะฟะตัะฐัะธะน ะธ ัะปะฐัั ะพัะดะตะปัะฝะพะต ัะพะพะฑัะตะฝะธะต ะฟะพ ะธั
ะพะบะพะฝัะฐะฝะธะธ. ะญัะพั ะฒะฐัะธะฐะฝั ั ััะธัะฐั ะฟะปะพั
ะธะผ, ัะฐะบ ะบะฐะบ ะพะฝ ััะตะทะผะตัะฝะพ ัะฒะตะปะธัะธั ัะฒัะทะฐะฝะฝะพััั ะปะพะณะธะบะธ.
- ะะพะผะตะฝััั ะฐัั
ะธัะตะบัััั ัะฐะบ, ััะพะฑั ะฟัะพะฑะปะตะผะฐ ะธััะตะทะปะฐ. ะกะปะธัะบะพะผ ะผะฝะพะณะพ ัะฐะฑะพัั ั ะฝะตััะฝัะผ ะธัะพะณะพะผ (ะฐัั
ะธัะตะบัััะฐ ัะตะนัะฐั ะฝะพัะผะฐะปัะฝะฐั, ะผะตะฝััั ะตั ัะฐะดะธ ะผะตะปะพัะธ ะฝะตั ัะผััะปะฐ).
- ะงัะพ-ัะพ ะตัั.
|
True
|
Discord: ัะฒะฝะพ ัะพะพะฑัะฐัั ะธะณัะพะบั, ััะพ ะฝะฐัะฐะปะฐัั ะพะฑัะฐะฑะพัะบะฐ ะตะณะพ ะบะพะผะฐะฝะดั ะธ ััะพ ะพะฝะฐ ะทะฐะฒะตััะธะปะฐัั - ะกะตะนัะฐั ะฝะตะบะพัะพััะต ะบะพะผะฐะฝะดั ะฒะพะทะฒัะฐัะฐัั ัะฟัะฐะฒะปะตะฝะธะต ัะฐะฝััะต, ัะตะผ ะฑัะดัั ะทะฐะฒะตััะตะฝั ะธะฝะธัะธะธัะพะฒะฐะฝะฝัะต ะธะผะธ ะดะตะนััะฒะธั.
ะกะฐะผะพ ะฟะพ ัะตะฑะต ััะพ ะฟัะฐะฒะธะปัะฝะพ, ั ัะพัะบะธ ะทัะตะฝะธั ัะตะบััะตะน ะฐัั
ะธัะตะบัััั, ะฝะพ ะฝะตัะดะพะฑะฝะพ ั ัะพัะบะธ ะทัะตะฝะธั ะฟะพะปัะทะพะฒะฐัะตะปะตะน.
ะะฐะดะพ ััะพ-ะฝะธะฑัะดั ะฟัะธะดัะผะฐัั.
ะะฐัะธะฐะฝัั:
- ะกะปะฐัั ัะพะพะฑัะตะฝะธะต ะพ ะฝะฐัะฐะปะต ะพะฟะตัะฐัะธะน ะดะปั ะบะฐะถะดะพะน (?) ะบะพะผะฐะฝะดั.
- ะกะบะพััะตะบัะธัะพะฒะฐัั ัะพะพะฑัะตะฝะธั ะฑะพัะฐ ัะฐะบ, ััะพะฑั ะตะณะพ ะฟะพะฒะตะดะตะฝะธะต ััะฐะปะพ ะฟะพะฝััะฝัะผ.
- ะฏะฒะฝะพ ะดะพะถะธะดะฐัััั ะทะฐะฒะตััะตะฝะธั ะฒัะตั
ะพะฟะตัะฐัะธะน ะธ ัะปะฐัั ะพัะดะตะปัะฝะพะต ัะพะพะฑัะตะฝะธะต ะฟะพ ะธั
ะพะบะพะฝัะฐะฝะธะธ. ะญัะพั ะฒะฐัะธะฐะฝั ั ััะธัะฐั ะฟะปะพั
ะธะผ, ัะฐะบ ะบะฐะบ ะพะฝ ััะตะทะผะตัะฝะพ ัะฒะตะปะธัะธั ัะฒัะทะฐะฝะฝะพััั ะปะพะณะธะบะธ.
- ะะพะผะตะฝััั ะฐัั
ะธัะตะบัััั ัะฐะบ, ััะพะฑั ะฟัะพะฑะปะตะผะฐ ะธััะตะทะปะฐ. ะกะปะธัะบะพะผ ะผะฝะพะณะพ ัะฐะฑะพัั ั ะฝะตััะฝัะผ ะธัะพะณะพะผ (ะฐัั
ะธัะตะบัััะฐ ัะตะนัะฐั ะฝะพัะผะฐะปัะฝะฐั, ะผะตะฝััั ะตั ัะฐะดะธ ะผะตะปะพัะธ ะฝะตั ัะผััะปะฐ).
- ะงัะพ-ัะพ ะตัั.
|
non_process
|
discord ัะฒะฝะพ ัะพะพะฑัะฐัั ะธะณัะพะบั ััะพ ะฝะฐัะฐะปะฐัั ะพะฑัะฐะฑะพัะบะฐ ะตะณะพ ะบะพะผะฐะฝะดั ะธ ััะพ ะพะฝะฐ ะทะฐะฒะตััะธะปะฐัั ัะตะนัะฐั ะฝะตะบะพัะพััะต ะบะพะผะฐะฝะดั ะฒะพะทะฒัะฐัะฐัั ัะฟัะฐะฒะปะตะฝะธะต ัะฐะฝััะต ัะตะผ ะฑัะดัั ะทะฐะฒะตััะตะฝั ะธะฝะธัะธะธัะพะฒะฐะฝะฝัะต ะธะผะธ ะดะตะนััะฒะธั ัะฐะผะพ ะฟะพ ัะตะฑะต ััะพ ะฟัะฐะฒะธะปัะฝะพ ั ัะพัะบะธ ะทัะตะฝะธั ัะตะบััะตะน ะฐัั
ะธัะตะบัััั ะฝะพ ะฝะตัะดะพะฑะฝะพ ั ัะพัะบะธ ะทัะตะฝะธั ะฟะพะปัะทะพะฒะฐัะตะปะตะน ะฝะฐะดะพ ััะพ ะฝะธะฑัะดั ะฟัะธะดัะผะฐัั ะฒะฐัะธะฐะฝัั ัะปะฐัั ัะพะพะฑัะตะฝะธะต ะพ ะฝะฐัะฐะปะต ะพะฟะตัะฐัะธะน ะดะปั ะบะฐะถะดะพะน ะบะพะผะฐะฝะดั ัะบะพััะตะบัะธัะพะฒะฐัั ัะพะพะฑัะตะฝะธั ะฑะพัะฐ ัะฐะบ ััะพะฑั ะตะณะพ ะฟะพะฒะตะดะตะฝะธะต ััะฐะปะพ ะฟะพะฝััะฝัะผ ัะฒะฝะพ ะดะพะถะธะดะฐัััั ะทะฐะฒะตััะตะฝะธั ะฒัะตั
ะพะฟะตัะฐัะธะน ะธ ัะปะฐัั ะพัะดะตะปัะฝะพะต ัะพะพะฑัะตะฝะธะต ะฟะพ ะธั
ะพะบะพะฝัะฐะฝะธะธ ััะพั ะฒะฐัะธะฐะฝั ั ััะธัะฐั ะฟะปะพั
ะธะผ ัะฐะบ ะบะฐะบ ะพะฝ ััะตะทะผะตัะฝะพ ัะฒะตะปะธัะธั ัะฒัะทะฐะฝะฝะพััั ะปะพะณะธะบะธ ะฟะพะผะตะฝััั ะฐัั
ะธัะตะบัััั ัะฐะบ ััะพะฑั ะฟัะพะฑะปะตะผะฐ ะธััะตะทะปะฐ ัะปะธัะบะพะผ ะผะฝะพะณะพ ัะฐะฑะพัั ั ะฝะตััะฝัะผ ะธัะพะณะพะผ ะฐัั
ะธัะตะบัััะฐ ัะตะนัะฐั ะฝะพัะผะฐะปัะฝะฐั ะผะตะฝััั ะตั ัะฐะดะธ ะผะตะปะพัะธ ะฝะตั ัะผััะปะฐ ััะพ ัะพ ะตัั
| 0
|
57,474
| 14,163,297,542
|
IssuesEvent
|
2020-11-12 02:01:11
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
Microsoft Security Advisory CVE-2020-1597 | ASP.NET Core Denial of Service Vulnerability
|
Security
|
# Microsoft Security Advisory CVE-2020-1597 | ASP.NET Core Denial of Service Vulnerability
## <a name="executive-summary"></a>Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.
A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application.
The update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests.
## Original Announcement
The original announcement for this issue can be found at https://github.com/dotnet/announcements/issues/162
## <a name="mitigation-factors"></a>Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
## <a name="affected-software"></a>Affected software
* Any .NET Core 3.1 application running on .NET Core 3.1.6 or lower
Please note that .NET Core 3.0 is now out of support and all applications should be updated to 3.1.
### <a name="how-affected"></a>How do I know if I am affected?
If you have a runtime or SDK with a version listed in [affected software](#affected-software) you are exposed to the vulnerability.
### <a name="how-fix"></a>How do I fix the issue?
To fix the issue please install the latest version of .NET Core 3.1. If you have installed one or more .NET Core SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio which will also update your .NET Core SDKs.
You can list the versions you have installed by running the `dotnet --info` command. You will see output like the following;
```txt
.NET Core SDK (reflecting any global.json):
Version: 3.1.100
Commit: cd82f021f4
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.100\
Host (useful for support):
Version: 3.1.0
Commit: 65f04fb6db
.NET Core SDKs installed:
3.1.100 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
```
* You should download and install Runtime 3.1.7 or SDK 3.1.107 (for Visual Studio 2019 v16.4) or 3.1.401 (for Visual Studio 2019 v16.5 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
## Other Information
### Reporting Security Issues
If you have found a potential security issue in .NET Core, please email details to secure@microsoft.com. Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at [https://aka.ms/corebounty](https://aka.ms/corebounty).
### Support
You can ask questions about this issue on GitHub in the .NET Core GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
### Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
### External Links
[CVE-2020-1597](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1597)
### Revisions
V1.0 (August 11, 2020): Advisory published.
_Version 1.0_
_Last Updated 2020-08-11_
|
True
|
Microsoft Security Advisory CVE-2020-1597 | ASP.NET Core Denial of Service Vulnerability - # Microsoft Security Advisory CVE-2020-1597 | ASP.NET Core Denial of Service Vulnerability
## <a name="executive-summary"></a>Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.
A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application.
The update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests.
## Original Announcement
The original announcement for this issue can be found at https://github.com/dotnet/announcements/issues/162
## <a name="mitigation-factors"></a>Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
## <a name="affected-software"></a>Affected software
* Any .NET Core 3.1 application running on .NET Core 3.1.6 or lower
Please note that .NET Core 3.0 is now out of support and all applications should be updated to 3.1.
### <a name="how-affected"></a>How do I know if I am affected?
If you have a runtime or SDK with a version listed in [affected software](#affected-software) you are exposed to the vulnerability.
### <a name="how-fix"></a>How do I fix the issue?
To fix the issue please install the latest version of .NET Core 3.1. If you have installed one or more .NET Core SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio which will also update your .NET Core SDKs.
You can list the versions you have installed by running the `dotnet --info` command. You will see output like the following;
```txt
.NET Core SDK (reflecting any global.json):
Version: 3.1.100
Commit: cd82f021f4
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.100\
Host (useful for support):
Version: 3.1.0
Commit: 65f04fb6db
.NET Core SDKs installed:
3.1.100 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
```
* You should download and install Runtime 3.1.7 or SDK 3.1.107 (for Visual Studio 2019 v16.4) or 3.1.401 (for Visual Studio 2019 v16.5 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
## Other Information
### Reporting Security Issues
If you have found a potential security issue in .NET Core, please email details to secure@microsoft.com. Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at [https://aka.ms/corebounty](https://aka.ms/corebounty).
### Support
You can ask questions about this issue on GitHub in the .NET Core GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
### Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
### External Links
[CVE-2020-1597](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1597)
### Revisions
V1.0 (August 11, 2020): Advisory published.
_Version 1.0_
_Last Updated 2020-08-11_
|
non_process
|
microsoft security advisory cve asp net core denial of service vulnerability microsoft security advisory cve asp net core denial of service vulnerability executive summary microsoft is releasing this security advisory to provide information about a vulnerability in asp net core this advisory also provides guidance on what developers can do to update their applications to remove this vulnerability a denial of service vulnerability exists when asp net core improperly handles web requests an attacker who successfully exploited this vulnerability could cause a denial of service against an asp net core web application the vulnerability can be exploited remotely without authentication a remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the asp net core application the update addresses the vulnerability by correcting how the asp net core web application handles web requests original announcement the original announcement for this issue can be found at mitigation factors microsoft has not identified any mitigating factors for this vulnerability affected software any net core application running on net core or lower please note that net core is now out of support and all applications should be updated to how do i know if i am affected if you have a runtime or sdk with a version listed in affected software you are exposed to the vulnerability how do i fix the issue to fix the issue please install the latest version of net core if you have installed one or more net core sdks through visual studio visual studio will prompt you to update visual studio which will also update your net core sdks you can list the versions you have installed by running the dotnet info command you will see output like the following txt net core sdk reflecting any global json version commit runtime environment os name windows os version os platform windows rid base path c program files dotnet sdk host useful for support version commit net core sdks installed net core runtimes installed microsoft aspnetcore app microsoft netcore app microsoft windowsdesktop app to install additional net core runtimes or sdks you should download and install runtime or sdk for visual studio or for visual studio or later from once you have installed the updated runtime or sdk restart your apps for the update to take effect additionally if you ve deployed targeting any of the impacted versions these applications are also vulnerable and must be recompiled and redeployed other information reporting security issues if you have found a potential security issue in net core please email details to secure microsoft com reports may qualify for the net core bug bounty details of the net core bug bounty including terms and conditions are at support you can ask questions about this issue on github in the net core github organization the main repos are located at and the announcements repo will contain this bulletin as an issue and will include a link to a discussion issue you can ask questions in the linked discussion issue disclaimer the information provided in this advisory is provided as is without warranty of any kind microsoft disclaims all warranties either express or implied including the warranties of merchantability and fitness for a particular purpose in no event shall microsoft corporation or its suppliers be liable for any damages whatsoever including direct indirect incidental consequential loss of business profits or special damages even if microsoft corporation or its suppliers have been advised of the possibility of such damages some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply external links revisions august advisory published version last updated
| 0
|
722,419
| 24,861,357,893
|
IssuesEvent
|
2022-10-27 08:32:13
|
AY2223S1-CS2103T-T12-2/tp
|
https://api.github.com/repos/AY2223S1-CS2103T-T12-2/tp
|
closed
|
As a user, I can assign a task to a contact
|
type.Story priority.High
|
...so that I can modify the relation between tasks and contacts
|
1.0
|
As a user, I can assign a task to a contact - ...so that I can modify the relation between tasks and contacts
|
non_process
|
as a user i can assign a task to a contact so that i can modify the relation between tasks and contacts
| 0
|
465,285
| 13,369,877,593
|
IssuesEvent
|
2020-09-01 09:28:10
|
CamprGmbH/campr
|
https://api.github.com/repos/CamprGmbH/campr
|
closed
|
Able to create new projects with regular "user" role
|
HIGH PRIORITY Prio 1 bug
|
Currently, when clicking on projects (dashboard) I'm able to create new project as a user with role "user" in a workspace. This should not be possible! Only admins (incl. super admin) shall be able to do so!
|
1.0
|
Able to create new projects with regular "user" role - Currently, when clicking on projects (dashboard) I'm able to create new project as a user with role "user" in a workspace. This should not be possible! Only admins (incl. super admin) shall be able to do so!
|
non_process
|
able to create new projects with regular user role currently when clicking on projects dashboard i m able to create new project as a user with role user in a workspace this should not be possible only admins incl super admin shall be able to do so
| 0
|
10,269
| 13,125,115,899
|
IssuesEvent
|
2020-08-06 05:53:44
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
closed
|
Flaky internal test: 8_error_ui "number of passes should equal the number of failures: expected 61 to equal 63"
|
browser: firefox process: flaky test stage: needs investigating type: chore
|
### Current behavior:
I have to rerun this test *constantly* to get it to pass. Only in Firefox.
**Failing CircleCI Run:** https://circleci.com/gh/cypress-io/cypress/368931
**Failing Test:** https://github.com/cypress-io/cypress/blob/issue-7280/packages/server/test/e2e/8_error_ui_spec.ts#L34:L34
<img width="1045" alt="Screen Shot 2020-06-18 at 12 23 02 PM" src="https://user-images.githubusercontent.com/1271364/84983438-cd710600-b15e-11ea-89f0-4979895d0da0.png">
```
1) e2e error ui displays correct UI for errors [firefox]:
number of passes should equal the number of failures
+ expected - actual
-61
+63
at /root/cypress/packages/server/test/e2e/8_error_ui_spec.ts:31:96
at /root/cypress/node_modules/graceful-fs/polyfills.js:243:20
at FSReqCallback.oncomplete (fs.js:146:23)
From previous event:
at Object.onRun (test/e2e/8_error_ui_spec.ts:45:27)
at Context.<anonymous> (test/support/helpers/e2e.ts:330:28)
```
### Versions
`develop`
|
1.0
|
Flaky internal test: 8_error_ui "number of passes should equal the number of failures: expected 61 to equal 63" - ### Current behavior:
I have to rerun this test *constantly* to get it to pass. Only in Firefox.
**Failing CircleCI Run:** https://circleci.com/gh/cypress-io/cypress/368931
**Failing Test:** https://github.com/cypress-io/cypress/blob/issue-7280/packages/server/test/e2e/8_error_ui_spec.ts#L34:L34
<img width="1045" alt="Screen Shot 2020-06-18 at 12 23 02 PM" src="https://user-images.githubusercontent.com/1271364/84983438-cd710600-b15e-11ea-89f0-4979895d0da0.png">
```
1) e2e error ui displays correct UI for errors [firefox]:
number of passes should equal the number of failures
+ expected - actual
-61
+63
at /root/cypress/packages/server/test/e2e/8_error_ui_spec.ts:31:96
at /root/cypress/node_modules/graceful-fs/polyfills.js:243:20
at FSReqCallback.oncomplete (fs.js:146:23)
From previous event:
at Object.onRun (test/e2e/8_error_ui_spec.ts:45:27)
at Context.<anonymous> (test/support/helpers/e2e.ts:330:28)
```
### Versions
`develop`
|
process
|
flaky internal test error ui number of passes should equal the number of failures expected to equal current behavior i have to rerun this test constantly to get it to pass only in firefox failing circleci run failing test img width alt screen shot at pm src error ui displays correct ui for errors number of passes should equal the number of failures expected actual at root cypress packages server test error ui spec ts at root cypress node modules graceful fs polyfills js at fsreqcallback oncomplete fs js from previous event at object onrun test error ui spec ts at context test support helpers ts versions develop
| 1
|
7,369
| 9,608,472,696
|
IssuesEvent
|
2019-05-12 06:43:24
|
Zowayix/Meow-Launcher
|
https://api.github.com/repos/Zowayix/Meow-Launcher
|
closed
|
Get Commodore PET machine metadata from filename
|
compatibility enhancement
|
It is noted in emulator_info that there are incompatibilities with different Commodore PET models. For lack of a better source of information, should set Machine specific_info based on filename tags, and then generate a command line accordingly for VICE to use the right model when needed.
|
True
|
Get Commodore PET machine metadata from filename - It is noted in emulator_info that there are incompatibilities with different Commodore PET models. For lack of a better source of information, should set Machine specific_info based on filename tags, and then generate a command line accordingly for VICE to use the right model when needed.
|
non_process
|
get commodore pet machine metadata from filename it is noted in emulator info that there are incompatibilities with different commodore pet models for lack of a better source of information should set machine specific info based on filename tags and then generate a command line accordingly for vice to use the right model when needed
| 0
|
11,677
| 14,536,429,850
|
IssuesEvent
|
2020-12-15 07:36:47
|
CGAL/cgal
|
https://api.github.com/repos/CGAL/cgal
|
opened
|
[Testsuite] Add OpenGR/libpointmatcher to some platforms
|
Pkg::Point_set_processing_3 TODO Testsuite
|
## Issue Details
We've had several issues (https://github.com/CGAL/cgal/issues/5167, https://github.com/CGAL/cgal/issues/5262) about difficulties to compile the CGAL examples using OpenGR and libpointmatcher. It seems these are not tested at all by our testsuite (or at least I couldn't find a platform with the examples compiled by randomly clicking on the PSP3 line).
OpenGR and libpointmatcher should be installed at least on one Linux + one Windows platform in my opinion.
|
1.0
|
[Testsuite] Add OpenGR/libpointmatcher to some platforms - ## Issue Details
We've had several issues (https://github.com/CGAL/cgal/issues/5167, https://github.com/CGAL/cgal/issues/5262) about difficulties to compile the CGAL examples using OpenGR and libpointmatcher. It seems these are not tested at all by our testsuite (or at least I couldn't find a platform with the examples compiled by randomly clicking on the PSP3 line).
OpenGR and libpointmatcher should be installed at least on one Linux + one Windows platform in my opinion.
|
process
|
add opengr libpointmatcher to some platforms issue details we ve had several issues about difficulties to compile the cgal examples using opengr and libpointmatcher it seems these are not tested at all by our testsuite or at least i couldn t find a platform with the examples compiled by randomly clicking on the line opengr and libpointmatcher should be installed at least on one linux one windows platform in my opinion
| 1
|
31,103
| 8,652,525,000
|
IssuesEvent
|
2018-11-27 08:20:37
|
OpenFLUID/openfluid
|
https://api.github.com/repos/OpenFLUID/openfluid
|
closed
|
Crash when two observers enabled for aw6 domain project
|
builder duplicate-invalid-not reproduced framework unconfirmed bug
|
Openfluid crashes when observer kml anim and kml plot are enabled for the aw6 project example. No problem when just on observer is enabled
|
1.0
|
Crash when two observers enabled for aw6 domain project - Openfluid crashes when observer kml anim and kml plot are enabled for the aw6 project example. No problem when just on observer is enabled
|
non_process
|
crash when two observers enabled for domain project openfluid crashes when observer kml anim and kml plot are enabled for the project example no problem when just on observer is enabled
| 0
|
82,650
| 7,846,317,147
|
IssuesEvent
|
2018-06-19 15:10:50
|
metafizzy/packery
|
https://api.github.com/repos/metafizzy/packery
|
closed
|
packery tile is distorted in firefox browser
|
test case required
|
<!-- Thanks for submitting an issue! All bug reports and problem issues require a **reduced test case**. Create one by forking any one of the CodePen examples from the docs. See guidelines link above. -->
**Test case:** http://codepen.io/desandro/pen/QyrEgX
I have coded packery to build complex tile system with showing map and visualizations in rest of the tiles. Its working as expected in Chrome, IE and Safari but first tile having map with different shape not working in firefox. Please let me know if there is fix for it?
|
1.0
|
packery tile is distorted in firefox browser - <!-- Thanks for submitting an issue! All bug reports and problem issues require a **reduced test case**. Create one by forking any one of the CodePen examples from the docs. See guidelines link above. -->
**Test case:** http://codepen.io/desandro/pen/QyrEgX
I have coded packery to build complex tile system with showing map and visualizations in rest of the tiles. Its working as expected in Chrome, IE and Safari but first tile having map with different shape not working in firefox. Please let me know if there is fix for it?
|
non_process
|
packery tile is distorted in firefox browser test case i have coded packery to build complex tile system with showing map and visualizations in rest of the tiles its working as expected in chrome ie and safari but first tile having map with different shape not working in firefox please let me know if there is fix for it
| 0
|
5,816
| 3,288,293,919
|
IssuesEvent
|
2015-10-29 14:39:56
|
Yoast/google-analytics-for-wordpress
|
https://api.github.com/repos/Yoast/google-analytics-for-wordpress
|
closed
|
Add missing translator comments to strings with variables
|
enhancement needs-code-review
|
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-google-analytics.php#L323
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-google-analytics.php#L336
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-google-analytics.php#L349
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L43
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L52
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L65
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L82
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L91
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L111
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-admin.php#L322
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L101
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L110
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L118 (translator comment is not on the line before the gettext function)
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L124
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L138
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L140
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L144
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L145
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L146
|
1.0
|
Add missing translator comments to strings with variables - * [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-google-analytics.php#L323
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-google-analytics.php#L336
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-google-analytics.php#L349
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L43
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L52
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L65
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L82
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L91
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/dashboard.php#L111
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/class-admin.php#L322
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L101
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L110
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L118 (translator comment is not on the line before the gettext function)
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L124
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L138
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L140
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L144
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L145
* [x] https://github.com/Yoast/google-analytics-for-wordpress/blob/trunk/admin/pages/settings.php#L146
|
non_process
|
add missing translator comments to strings with variables translator comment is not on the line before the gettext function
| 0
|
8,139
| 11,340,395,611
|
IssuesEvent
|
2020-01-23 06:17:01
|
material-components/material-components-ios
|
https://api.github.com/repos/material-components/material-components-ios
|
closed
|
[FlexibleHeader] Internal issue: b/142322977
|
[FlexibleHeader] type:Process
|
This was filed as an internal issue. If you are a Googler, please visit [b/142322977](http://b/142322977) for more details.
<!-- Auto-generated content below, do not modify -->
---
#### Internal data
- Associated internal bug: [b/142322977](http://b/142322977)
- Blocked by: https://github.com/material-components/material-components-ios/issues/8722
- Blocked by: https://github.com/material-components/material-components-ios/issues/8723
- Blocked by: https://github.com/material-components/material-components-ios/issues/8621
- Blocked by: https://github.com/material-components/material-components-ios/issues/8603
|
1.0
|
[FlexibleHeader] Internal issue: b/142322977 - This was filed as an internal issue. If you are a Googler, please visit [b/142322977](http://b/142322977) for more details.
<!-- Auto-generated content below, do not modify -->
---
#### Internal data
- Associated internal bug: [b/142322977](http://b/142322977)
- Blocked by: https://github.com/material-components/material-components-ios/issues/8722
- Blocked by: https://github.com/material-components/material-components-ios/issues/8723
- Blocked by: https://github.com/material-components/material-components-ios/issues/8621
- Blocked by: https://github.com/material-components/material-components-ios/issues/8603
|
process
|
internal issue b this was filed as an internal issue if you are a googler please visit for more details internal data associated internal bug blocked by blocked by blocked by blocked by
| 1
|
68,312
| 8,248,619,492
|
IssuesEvent
|
2018-09-11 18:59:22
|
Opentrons/opentrons
|
https://api.github.com/repos/Opentrons/opentrons
|
closed
|
PD Analytics: Fullstory Opt-In
|
feature large protocol designer
|
As a protocol designer, I would like to be able to opt-in to share my usage data with Opentrons via Fullstory.
## Acceptance Criteria
- Add FullStory tracking to Protocol Designer
- Users prompted to opt in to share session data with Opentrons the first time they open the web app
- User able to turn session tracking on or off in the app
-- Add a new "Settings" tab to the bottom of our top level nav. The privacy list item will open a privacy card in the page.
## Implementation Notes
- [Link to code snippet and guide](https://app.fullstory.com/ui/B4RHZ/settings/general)
- [Discussion of FullStory and SPA](https://help.fullstory.com/using/does-fullstory-work-with-my-complex-site) (actually seems like a non-issue):
- Get account info from Alfie
## Design
Initial card upon opening session: https://zpl.io/aX4wR0X
I thought it made more sense as a card. We use modals when UI needs to go on top of something. If you don't have a protocol open yet there's no need for a modal.
Settings tab: https://zpl.io/25rGl4o
|
1.0
|
PD Analytics: Fullstory Opt-In - As a protocol designer, I would like to be able to opt-in to share my usage data with Opentrons via Fullstory.
## Acceptance Criteria
- Add FullStory tracking to Protocol Designer
- Users prompted to opt in to share session data with Opentrons the first time they open the web app
- User able to turn session tracking on or off in the app
-- Add a new "Settings" tab to the bottom of our top level nav. The privacy list item will open a privacy card in the page.
## Implementation Notes
- [Link to code snippet and guide](https://app.fullstory.com/ui/B4RHZ/settings/general)
- [Discussion of FullStory and SPA](https://help.fullstory.com/using/does-fullstory-work-with-my-complex-site) (actually seems like a non-issue):
- Get account info from Alfie
## Design
Initial card upon opening session: https://zpl.io/aX4wR0X
I thought it made more sense as a card. We use modals when UI needs to go on top of something. If you don't have a protocol open yet there's no need for a modal.
Settings tab: https://zpl.io/25rGl4o
|
non_process
|
pd analytics fullstory opt in as a protocol designer i would like to be able to opt in to share my usage data with opentrons via fullstory acceptance criteria add fullstory tracking to protocol designer users prompted to opt in to share session data with opentrons the first time they open the web app user able to turn session tracking on or off in the app add a new settings tab to the bottom of our top level nav the privacy list item will open a privacy card in the page implementation notes actually seems like a non issue get account info from alfie design initial card upon opening session i thought it made more sense as a card we use modals when ui needs to go on top of something if you don t have a protocol open yet there s no need for a modal settings tab
| 0
|
157,934
| 19,988,933,342
|
IssuesEvent
|
2022-01-31 02:05:25
|
sureng-ws-ibm/sg-x-nodegoat
|
https://api.github.com/repos/sureng-ws-ibm/sg-x-nodegoat
|
closed
|
CVE-2021-23383 (High) detected in handlebars-4.0.5.tgz - autoclosed
|
security vulnerability
|
## CVE-2021-23383 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.5.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/nyc/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- grunt-if-0.2.0.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- nyc-7.1.0.tgz
- istanbul-reports-1.0.0-alpha.8.tgz
- :x: **handlebars-4.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sureng-ws-ibm/sg-x-nodegoat/commit/81cd799c64e09f7670559bce715f20a9ec7821d5">81cd799c64e09f7670559bce715f20a9ec7821d5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383>CVE-2021-23383</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: handlebars - 4.7.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"handlebars","packageVersion":"4.0.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-if:0.2.0;grunt-contrib-nodeunit:1.0.0;nodeunit:0.9.5;tap:7.1.2;nyc:7.1.0;istanbul-reports:1.0.0-alpha.8;handlebars:4.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"handlebars - 4.7.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23383","vulnerabilityDetails":"The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-23383 (High) detected in handlebars-4.0.5.tgz - autoclosed - ## CVE-2021-23383 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.5.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/nyc/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- grunt-if-0.2.0.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- nyc-7.1.0.tgz
- istanbul-reports-1.0.0-alpha.8.tgz
- :x: **handlebars-4.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sureng-ws-ibm/sg-x-nodegoat/commit/81cd799c64e09f7670559bce715f20a9ec7821d5">81cd799c64e09f7670559bce715f20a9ec7821d5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383>CVE-2021-23383</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: handlebars - 4.7.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"handlebars","packageVersion":"4.0.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-if:0.2.0;grunt-contrib-nodeunit:1.0.0;nodeunit:0.9.5;tap:7.1.2;nyc:7.1.0;istanbul-reports:1.0.0-alpha.8;handlebars:4.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"handlebars - 4.7.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23383","vulnerabilityDetails":"The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_process
|
cve high detected in handlebars tgz autoclosed cve high severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file package json path to vulnerable library node modules nyc node modules handlebars package json dependency hierarchy grunt if tgz root library grunt contrib nodeunit tgz nodeunit tgz tap tgz nyc tgz istanbul reports alpha tgz x handlebars tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package handlebars before are vulnerable to prototype pollution when selecting certain compiling options to compile templates coming from an untrusted source publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution handlebars isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree grunt if grunt contrib nodeunit nodeunit tap nyc istanbul reports alpha handlebars isminimumfixversionavailable true minimumfixversion handlebars isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the package handlebars before are vulnerable to prototype pollution when selecting certain compiling options to compile templates coming from an untrusted source vulnerabilityurl
| 0
|
199,069
| 15,022,643,865
|
IssuesEvent
|
2021-02-01 17:11:55
|
OpenLiberty/open-liberty
|
https://api.github.com/repos/OpenLiberty/open-liberty
|
closed
|
FAT Summary for Support MicroProfile JWT 1.2
|
Feature Test Summary
|
Several FAT projects were updated or added in support of the MicroProfile JWT 1.2 Feature.
All testing for this feature is automated.
The existing mpJwt-1.1 FAT tests are now also run with the mpJwt-1.2 enabled to ensure that all 1.1 function still works.
Test developement included addressing servicibility. All messages were reviewed for each error encountered and analyzed for detail available to end user, admin, ... to ensure that we have valid information to each audience.
Confidence in the testing definitely 4, but, more likely a 5.
### Tests were added to support:
1. New signature algorigthms of: RS384, RS512, ES256, ES384, ES512, HS384 and HS512
1. Encrypting/Decrypting JWT tokens
1. Supporting placement of the JWT Token in either the **Authorization** or **Cookie** Header (and if Cookie allow the token to be named)
1. All new config and mp config attributes to support new function (addressed specifically below) (including configuration of the signature algorithm and audience in mp config properties (when they had only been supported via server.xml in the past)
### FAT projects updated:
1. com.ibm.ws.security.jwt_fat.builder
- (Signing) Tests were updated to sign using all of the supported Algorithms
Tests were added to use valid and invalid alias', keystores, matches and mis-matches between between the algorithm config attribute and the alias used
Tests were added to use updated server.xml config attributes with the new signature algorithms
Tests were added to use the builder **signWith** api with the new signature algorithms
Tests were added to use tokens with the new algorithms with the **claimsFrom** apis
- (Encrypting) Tests were updated to encrypt tokens/create JWE's instead of JWS'
Tests were added to encrypt using keys for each of the supported encryption algorithms (RS256, RS384 and RS512)
Tests were added to attempt to encrypt using keys for algorithms that are NOT supported
Tests were added to encrypt using new attributes from server.xml
Tests were added to encrypt using the new **encryptWith** api (both valid and invalid values were used) (these tests included some that would set **keyManagementKeyAlgorithm** and **contentEncryptionAlgorithm** values that our config doesn't support)
Tests were added to test the **claimsFrom** apis using JWE's and JWS' in various forms
Tests added included both valid and invalid values in the config
Tests were added to get the public key from either the builder config's trust store or the server's truststore (tests were created to use non-existant keys too)
Tests were added to use new server.xml config attributes.
**List of test cases added:**
```
JwkEndpointValidationUrlTests_encrypt_RS256
JwkEndpointValidationUrlTests_encrypt_RS384
JwkEndpointValidationUrlTests_encrypt_RS512
JwkEndpointValidationUrlTests_sigAlg_ES256
JwkEndpointValidationUrlTests_sigAlg_ES384
JwkEndpointValidationUrlTests_sigAlg_ES512
JwkEndpointValidationUrlTests_sigAlg_HS384
JwkEndpointValidationUrlTests_sigAlg_HS512
JwkEndpointValidationUrlTests_sigAlg_PS256
JwkEndpointValidationUrlTests_sigAlg_PS384
JwkEndpointValidationUrlTests_sigAlg_PS512
JwkEndpointValidationUrlTests_sigAlg_RS384
JwkEndpointValidationUrlTests_sigAlg_RS512
JwtBuilderAPIBasicTests_claimsFrom_jweString_decodedPayload_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweString_encodedPayload_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweString_to_jwtToken_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweTokenRS256_to_jweTokenRS384_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweToken_to_jwtToken_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jwtString_to_jweToken_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jwtToken_to_jweToken_allClaims
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_256_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_256_RS384_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_256_RS512_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_privateKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A192GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM_signWith_ES384
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM_signWith_HS512
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM_signWith_RS256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_invalidContentEncryptAlg
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_nullContentEncryptAlg
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_shortPublicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_privateKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM_signWith_ES512
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM_signWith_HS256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM_signWith_RS384
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_shortPublicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_privateKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM_signWith_ES256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM_signWith_HS256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM_signWith_RS512
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_shortPublicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_null_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_invalidKeyMgmtKeyAlg_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_nullContentEncryptAlg_goodBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_nullKeyMgmtKeyAlg_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_nullKeyMgmtKeyAlg_goodBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_null_publicKey_goodBuidlerConfig
JwtBuilderAPIBasicTests_encryptWith_useDifferentContentEncryptAlgThanBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_useDifferentKeyMgmtKeyAlgThanBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_useDifferentPublicKeyThanBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_useSameSettingsAsBuilderConfig
JwtBuilderAPIBasicTests_signWith_sigAlg_ES256_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_ES384_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_ES512_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_HS384_key_string
JwtBuilderAPIBasicTests_signWith_sigAlg_HS512_key_string
JwtBuilderAPIBasicTests_signWith_sigAlg_PS256_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_PS384_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_PS512_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_RS384_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_RS512_key_privKey
JwtBuilderAPIConfigTests_amrValue_empty
JwtBuilderAPIConfigTests_amrValue_invalid
JwtBuilderAPIConfigTests_amrValue_valid
JwtBuilderAPIConfigTests_encryption_RSAOAEP256KeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_badKeyManagementKeyAlias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodES256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodKeyManagementKeyAlias_goodContentEncryptAlg_trustStoreRefInvalid
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodKeyManagementKeyAlias_goodContentEncryptAlg_trustStoreRefMissing
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg_SigAlgES384
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_invalidContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_missingContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS384Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS512Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodServerWideKeyManagementKeyAlias_goodContentEncryptAlg_trustStoreRefMissing
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_missingKeyManagementKeyAlias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_invalidKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_missingKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
wtBuilderAPIConfigTests_sigAlg_HS384_with_sharedKey
JwtBuilderAPIConfigTests_sigAlg_HS512_with_sharedKey
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_RS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_RS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_RS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
```
1. com.ibm.ws.security.jwt_fat.consumer
- (Signing) Tests were updated to consume tokens using all of the supported Algorithms
Tests were added to use valid and invalid alias', keystores, matches and mis-matches between between the algorithm config attribute and the token contents
Tests were added to use updated server.xml config attributes with the new signature algorithms
- (Decrypting) Tests were updated to decrypt tokens JWE's instead of JWS'
Tests were added to decrypt using keys for each of the supported encryption algorithms (RS256, RS384 and RS512)
Tests were added to attempt to decrypt using keys for algorithms that are NOT supported
Tests were added to decrypt using new attributes from server.xml
Tests were added to decrypt tokens that contain **keyManagementKeyAlgorithm** and **contentEncryptionAlgorithm** values that our builder config doesn't support, but, we'll allow to be consumed
Tests added included both valid and invalid values in the config
Tests were added to get the private key from either the consumers config's trust store or the server's truststore (tests were created to use non-existant keys too)
Tests were added to use new server.xml config attributes.
Tests were added to have mis-matches between token being encrypted, but config doesn't decrypt and vice-versa
Tests were added to test non-default values for typ and cty in the JWE Header
**List of test cases added:**
```
JwtConsumerApiConfigTests_SigAlgES256
JwtConsumerApiConfigTests_SigAlgES256_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgES256_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgES256_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgES384
JwtConsumerApiConfigTests_SigAlgES384_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgES384_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgES384_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgES512
JwtConsumerApiConfigTests_SigAlgES512_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgES512_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgES512_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgHS256
JwtConsumerApiConfigTests_SigAlgHS384
JwtConsumerApiConfigTests_SigAlgHS512
JwtConsumerApiConfigTests_SigAlgRS256
JwtConsumerApiConfigTests_SigAlgRS256_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgRS256_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgRS256_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgRS384
JwtConsumerApiConfigTests_SigAlgRS384_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgRS384_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgRS384_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgRS512
JwtConsumerApiConfigTests_SigAlgRS512_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgRS512_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgRS512_trustAliasMisMatchRS
JwtConsumerApiConfigTests_badKeyManagementKeyAlias_goodSslRef
JwtConsumerApiConfigTests_decryptWithUnsupportedAlg
JwtConsumerApiConfigTests_encryptOtherContentEncryptionAlg
JwtConsumerApiConfigTests_encryptOtherJWEHeader_cty
JwtConsumerApiConfigTests_encryptOtherJWEHeader_typ
JwtConsumerApiConfigTests_encryptOtherKeyManagementKeyAlg
JwtConsumerApiConfigTests_encryptRS256_decryptRS256
JwtConsumerApiConfigTests_encryptRS256_decryptRS384
JwtConsumerApiConfigTests_encryptRS256_decryptRS512
JwtConsumerApiConfigTests_encryptRS384_decryptRS256
JwtConsumerApiConfigTests_encryptRS384_decryptRS384
JwtConsumerApiConfigTests_encryptRS384_decryptRS512
JwtConsumerApiConfigTests_encryptRS512_decryptRS256
JwtConsumerApiConfigTests_encryptRS512_decryptRS384
JwtConsumerApiConfigTests_encryptRS512_decryptRS512
JwtConsumerApiConfigTests_encryptSimpleJsonPayload
JwtConsumerApiConfigTests_encryptedToken_consumerDoesNotDecrypt
JwtConsumerApiConfigTests_goodKeyManagementKeyAlias_baddSslRef
JwtConsumerApiConfigTests_goodKeyManagementKeyAlias_missingSslRef_refMissingFromServerwideSSL
JwtConsumerApiConfigTests_tokenNotEncrypted_consumerDecrypts
```
2. com.ibm.ws.security.mp.jwt.1.1_fat
- (Signing) Tests were added to consume tokens using all of the supported Algorithms
Tests were added to use valid and invalid alias', keystores, matches and mis-matches between between the algorithm config attribute and the token contents
Tests were added to use updated server.xml config and mp config properties attributes for the new signature algorithms
**List of test cases added:**
```
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocES256RelativeFile_test
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocES512JwksUri_test
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocRS256Url_test
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocRS256Url_test
MPJwtGoodMPConfigAsEnvVars_UseES384PublicKey_NoKeyLoc_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocES2564Url_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocES384File_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocES512RelativeFile_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocRS512JwksUri_test
MPJwtGoodMPConfigAsSystemProperties_UseRS384PublicKey_NoKeyLoc_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES256PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES384PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES384PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES512PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES512PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodFileES512PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodFileRS256PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodJwksUriES384PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodJwksUriRS512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS256PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS384PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS384PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS512PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS512PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRelativeES512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRelativeRS256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodUrlES256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodUrlPublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodUrlRS384PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenES384_ES512PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenES384_PS256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenES384_RS384PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenRS512_ES384PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenRS512_PS512PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenRS512_RS256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES256_BadUrlRS384PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES384_BadJwksUriPS256PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES384_BadJwksUriRS512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadFilePS384PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadFileRS256PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadRelativePS384PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadRelativeRS256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS256_BadJwksUriES384PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadFileES512PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadRelativeES512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadUrlES256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadUrlPublicKeyLocationInMPConfigUnderWebInf_test
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingES256_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingES384_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingES512_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingHS256_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingHS384_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingHS512_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingRS256_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingRS384_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingRS512_tokenWithMatchAndMisMatchSigAlgs
```
### FAT projects created:
1. com.ibm.ws.security.mp.jwt.1.2_fat
- (Signing) All of the signing tests are included in the **com.ibm.ws.security.mp.jwt.1.1_fat** project
- (Specifying Audience) Tests were added to specify the audience value via mp config propertes (in addition to server.xml support that was part of 1.1)
The existing mpJwt FAT (1.1) tests supported specifying the audience value through the server.xml
Tests were added to specify the audience via the **mp.jwt.verify.audiences** attribute in any of the following locations/ways: microprofile-config.properties in META-INF or WEB-INF/classes/META-INF within the app, as Environment variables, or as System properties. Good/bad values were tested as well as testing that the correct precedence order is honored. (server.xml values override those found within the app)
- (Specifying signature Algorithm) Tests were added to specify the signature algorithm value via mp config propertes (in addition to server.xml support that was part of 1.1)
The existing mpJwt FAT (1.1) tests supported specifying the signature algorithm value through the server.xml
Tests were added to specify the audience via the **mp.jwt.verify.publickey.algorithm** attribute in any of the following locations/ways: microprofile-config.properties in META-INF or WEB-INF/classes/META-INF within the app, as Environment variables, or as System properties. Good/bad values were tested as well as testing that the correct precedence order is honored. (server.xml values override those found within the app)
- (Specifying how token will be passed) Tests were added to specify where/how the JWT token would be passed on a request to a protected app.
The existing mpJwt (1.1) tests always passed the JWT in the **Authorization** header using the name **Bearer**. This feature now allows the user to pass the JWT in the **Cookie** Header and specify the name to pass it with.
Tests have been added to specifying and omitting the token header and cookie name values. All good/bad combinations were included. We tested passing the token how the config expected it and did not expect it.
- (Decrypting) Tests were added to decrypt tokens JWE's instead of JWS'
Tests were added to decrypt using keys for each of the supported encryption algorithms (RS256, RS384 and RS512)
Tests were added to attempt to decrypt using keys for algorithms that are NOT supported
Tests were added to decrypt using new attributes from server.xml
Tests were added to decrypt tokens that contain **keyManagementKeyAlgorithm** and **contentEncryptionAlgorithm** values that our builder config doesn't support, but, we'll allow to be consumed
Tests added included both valid and invalid values in the config
Tests were added to get the private key from either the mpJwt config's trust store or the server's truststore (tests were created to use non-existant keys too)
Tests were added to use new server.xml config attributes.
Tests were added to use mp config properties from any of the following locations/ways: microprofile-config.properties in META-INF or WEB-INF/classes/META-INF within the app, as Environment variables, or as System properties.
Tests were added to ensure the correct precedence when using mp config properties and config attributes from server.xml
Tests were added to have mis-matches between token being encrypted, but config doesn't decrypt and vice-versa
Tests were added to test non-default values for typ and cty in the JWE Header
Tests were added to ensure that mpJwt-1.2 function will not work when only mpJwt-1.1 is enabled.
**List of test cases added:**
```
Feature11Enabled_ConfigInAppTests_DecryptKeyLocRelativeForRS256InMPConfig_InMetaInf_JWEToken_test
Feature11Enabled_ConfigInAppTests_DecryptKeyLocRelativeForRS256InMPConfig_InMetaInf_JWSToken_test
Feature11Enabled_ConfigInAppTests_GoodAudiencesInServerXml_BadAudiencesInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_GoodAudiencesInServerXml_BadAudiencesInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsAuthorizationInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsAuthorizationInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsCookieInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsCookieInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_MatchingNonDefaultKeyAndAlgorithmInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_MatchingNonDefaultKeyAndAlgorithmInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_NoAudiencesInServerXml_GoodAudiencesInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_NoAudiencesInServerXml_GoodAudiencesInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInServerXmlTests_Header_Authorization_passTokenInAuthHeaderUsingBearer
Feature11Enabled_ConfigInServerXmlTests_Header_Cookie_doNotSetCookieName_passTokenAsCookie
Feature11Enabled_ConfigInServerXmlTests_Header_Cookie_setCookieName_passTokenAsCookie
Feature11Enabled_ConfigInServerXmlTests_KeyManagementKeyAliasKeyRS256_JWEToken_test
Feature11Enabled_ConfigInServerXmlTests_KeyManagementKeyAliasKeyRS256_JWSToken_test
Feature11Enabled_ConfigInServerXmlTests_NoKeyManagementKeyAliasKey_JWEToken_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_Algorithm_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_Audience_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_HeaderCookie_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_overridAll_test
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderAndCookie_HeaderBad
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderAndCookie_HeaderGood
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderNotUsingBearer
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderUsingBearer
MPJwt12ConfigUsingBuilderTests_Header_Authorization_setCookieName_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Cookie_doNotSetCookieName_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Cookie_passTokenInAuthHeaderAndCookie_CookieBad
MPJwt12ConfigUsingBuilderTests_Header_Cookie_passTokenInAuthHeaderAndCookie_CookieGood
MPJwt12ConfigUsingBuilderTests_Header_Cookie_setCookieName_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Cookie_setCookieName_passTokenAsCookieUsingDefaultName
MPJwt12ConfigUsingBuilderTests_Header_Cookie_setCookieName_passTokenAsCookieUsingDifferentName
MPJwt12ConfigUsingBuilderTests_encrypt_mpJWtRS256_signUsingRS384
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtES384_tokenRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtNoEncryption_tokenEncrypted
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_JWEContentTypeNotjwt
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_JWETypeNotJose
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_simpleJsonPayload
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_tokenNotEncrypted
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_tokenRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_token_RSA_OAEP_256_RS256_publicKey_A256GCM
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_token_RSA_OAEP_RS256_publicKey_A192GCM
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS384_tokenRS384
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS384_tokenRS512
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS512_tokenRS512
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtShortPrivateKey_signUsingRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtinvalid_signUsingRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtpublicKey_signUsingRS256
MPJwt12MPConfigInApp_GoodAlgorithmInServerXml_BadAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_GoodAlgorithmInServerXml_BadAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_GoodAudiencesInServerXml_BadAudiencesInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_GoodAudiencesInServerXml_BadAudiencesInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_GoodNonDefaultKeyAndAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_GoodNonDefaultKeyAndAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_HeaderIsAuthorizationInServerXml_HeaderIsCookieInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_HeaderIsAuthorizationInServerXml_HeaderIsCookieInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_HeaderIsCookieCookieNameSetConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_HeaderIsCookieCookieNameSetInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_HeaderIsCookieInServerXml_HeaderIsAuthorizationInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_HeaderIsCookieInServerXml_HeaderIsAuthorizationInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_MPJwt12ConfigInServerXmlOverrides_BadDecryptInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAudiencesInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAudiencesInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocES256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocES256InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocFileForRS256InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocFileForRS512InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocJwksUriInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocPlainTextInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocRelativeForRS256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocRelativeForRS384InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocUrlForRS384InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocUrlForRS512InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptPublicKeyInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_JweContentTypeNotJwt_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_JweTypeNotJose_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_TokenNotEncrypted_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_simpleJsonPayload_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptShortKeyInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptStringKeyInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS2564DecryptRS384InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS2564DecryptRS512InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS3844DecryptRS512InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS384DecryptRS256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS5124DecryptRS256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS5124DecryptRS384InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAudiencesInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAudiencesInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsAuthorizationInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsAuthorizationInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsBadInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsBadInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithCookieNameInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithCookieNameInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_InMetaInf_PassCookieWithNameBearer_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_UnderWebInf_PassCookieWithNameBearer_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_NoDecryptInMPConfig_InMetaInf_TokenEncrypted_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_encrypt_mpJwtRS256_token_RSA_OAEP_256_RS256_publicKey_A256GCM
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_encrypt_mpJwtRS256_token_RSA_OAEP_RS256_publicKey_A192GCM
MPJwtGoodMP12ConfigAsEnvVars_Algorithm_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_Algorithm_test
MPJwtGoodMP12ConfigAsEnvVars_Audiences_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_Audiences_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderAuthorization_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderAuthorization_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_withCookieName_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_withCookieName_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_AlternateDecryptSettings_contentEncryptAlg192
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_AlternateDecryptSettings_keyMgmtKeyAlg256
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256File_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256File_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256PlainText_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256PlainText_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS512Url_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS512Url_test
MPJwtGoodMP12ConfigAsSystemProperties_Algorithm_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_Algorithm_test
MPJwtGoodMP12ConfigAsSystemProperties_Audiences_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_Audiences_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderAuthorization_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderAuthorization_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_withCookieName_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_withCookieName_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_AlternateDecryptSettings_contentEncryptAlg192
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_AlternateDecryptSettings_keyMgmtKeyAlg256
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS256Jwk_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS256Jwk_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS384RelativeFile_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS384RelativeFile_test
```
2. io.openliberty.microprofile.jwt.1.2.internal_fat_tck
These are the TCK test for MP JWT 1.2 and are currently at the latest 1.2-RC2 level available from Eclipse Microprofile.
As of 11/18/20, the EmptyTokenTest is the only TCK test that remains disabled. We can technically pass all of the tests in the class, but the server would have to be reconfigured in between tests in the EmptyTokenTest class in order to get them all to pass, which we donโt have the power to do so with the way the TCK tests run -- all tests in a class run against the same server configuration. We are looking at what we can do about this.
|
1.0
|
FAT Summary for Support MicroProfile JWT 1.2 - Several FAT projects were updated or added in support of the MicroProfile JWT 1.2 Feature.
All testing for this feature is automated.
The existing mpJwt-1.1 FAT tests are now also run with the mpJwt-1.2 enabled to ensure that all 1.1 function still works.
Test developement included addressing servicibility. All messages were reviewed for each error encountered and analyzed for detail available to end user, admin, ... to ensure that we have valid information to each audience.
Confidence in the testing definitely 4, but, more likely a 5.
### Tests were added to support:
1. New signature algorigthms of: RS384, RS512, ES256, ES384, ES512, HS384 and HS512
1. Encrypting/Decrypting JWT tokens
1. Supporting placement of the JWT Token in either the **Authorization** or **Cookie** Header (and if Cookie allow the token to be named)
1. All new config and mp config attributes to support new function (addressed specifically below) (including configuration of the signature algorithm and audience in mp config properties (when they had only been supported via server.xml in the past)
### FAT projects updated:
1. com.ibm.ws.security.jwt_fat.builder
- (Signing) Tests were updated to sign using all of the supported Algorithms
Tests were added to use valid and invalid alias', keystores, matches and mis-matches between between the algorithm config attribute and the alias used
Tests were added to use updated server.xml config attributes with the new signature algorithms
Tests were added to use the builder **signWith** api with the new signature algorithms
Tests were added to use tokens with the new algorithms with the **claimsFrom** apis
- (Encrypting) Tests were updated to encrypt tokens/create JWE's instead of JWS'
Tests were added to encrypt using keys for each of the supported encryption algorithms (RS256, RS384 and RS512)
Tests were added to attempt to encrypt using keys for algorithms that are NOT supported
Tests were added to encrypt using new attributes from server.xml
Tests were added to encrypt using the new **encryptWith** api (both valid and invalid values were used) (these tests included some that would set **keyManagementKeyAlgorithm** and **contentEncryptionAlgorithm** values that our config doesn't support)
Tests were added to test the **claimsFrom** apis using JWE's and JWS' in various forms
Tests added included both valid and invalid values in the config
Tests were added to get the public key from either the builder config's trust store or the server's truststore (tests were created to use non-existant keys too)
Tests were added to use new server.xml config attributes.
**List of test cases added:**
```
JwkEndpointValidationUrlTests_encrypt_RS256
JwkEndpointValidationUrlTests_encrypt_RS384
JwkEndpointValidationUrlTests_encrypt_RS512
JwkEndpointValidationUrlTests_sigAlg_ES256
JwkEndpointValidationUrlTests_sigAlg_ES384
JwkEndpointValidationUrlTests_sigAlg_ES512
JwkEndpointValidationUrlTests_sigAlg_HS384
JwkEndpointValidationUrlTests_sigAlg_HS512
JwkEndpointValidationUrlTests_sigAlg_PS256
JwkEndpointValidationUrlTests_sigAlg_PS384
JwkEndpointValidationUrlTests_sigAlg_PS512
JwkEndpointValidationUrlTests_sigAlg_RS384
JwkEndpointValidationUrlTests_sigAlg_RS512
JwtBuilderAPIBasicTests_claimsFrom_jweString_decodedPayload_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweString_encodedPayload_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweString_to_jwtToken_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweTokenRS256_to_jweTokenRS384_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jweToken_to_jwtToken_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jwtString_to_jweToken_allClaims
JwtBuilderAPIBasicTests_claimsFrom_jwtToken_to_jweToken_allClaims
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_256_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_256_RS384_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_256_RS512_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_privateKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A192GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM_signWith_ES384
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM_signWith_HS512
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_A256GCM_signWith_RS256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_invalidContentEncryptAlg
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_publicKey_nullContentEncryptAlg
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS256_shortPublicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_privateKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM_signWith_ES512
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM_signWith_HS256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_publicKey_A256GCM_signWith_RS384
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS384_shortPublicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_privateKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM_signWith_ES256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM_signWith_HS256
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_publicKey_A256GCM_signWith_RS512
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_RS512_shortPublicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_RSA_OAEP_null_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_invalidKeyMgmtKeyAlg_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_nullContentEncryptAlg_goodBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_nullKeyMgmtKeyAlg_RS256_publicKey_A256GCM
JwtBuilderAPIBasicTests_encryptWith_nullKeyMgmtKeyAlg_goodBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_null_publicKey_goodBuidlerConfig
JwtBuilderAPIBasicTests_encryptWith_useDifferentContentEncryptAlgThanBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_useDifferentKeyMgmtKeyAlgThanBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_useDifferentPublicKeyThanBuilderConfig
JwtBuilderAPIBasicTests_encryptWith_useSameSettingsAsBuilderConfig
JwtBuilderAPIBasicTests_signWith_sigAlg_ES256_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_ES384_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_ES512_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_HS384_key_string
JwtBuilderAPIBasicTests_signWith_sigAlg_HS512_key_string
JwtBuilderAPIBasicTests_signWith_sigAlg_PS256_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_PS384_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_PS512_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_RS384_key_privKey
JwtBuilderAPIBasicTests_signWith_sigAlg_RS512_key_privKey
JwtBuilderAPIConfigTests_amrValue_empty
JwtBuilderAPIConfigTests_amrValue_invalid
JwtBuilderAPIConfigTests_amrValue_valid
JwtBuilderAPIConfigTests_encryption_RSAOAEP256KeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_badKeyManagementKeyAlias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodES256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodKeyManagementKeyAlias_goodContentEncryptAlg_trustStoreRefInvalid
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodKeyManagementKeyAlias_goodContentEncryptAlg_trustStoreRefMissing
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg_SigAlgES384
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_invalidContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS256Alias_missingContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS384Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodRS512Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_goodServerWideKeyManagementKeyAlias_goodContentEncryptAlg_trustStoreRefMissing
JwtBuilderAPIConfigTests_encryption_goodKeyMgmtKeyAlg_missingKeyManagementKeyAlias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_invalidKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_encryption_missingKeyMgmtKeyAlg_goodRS256Alias_goodContentEncryptAlg
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_ES256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_ES384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_ES512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
wtBuilderAPIConfigTests_sigAlg_HS384_with_sharedKey
JwtBuilderAPIConfigTests_sigAlg_HS512_with_sharedKey
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_PS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_PS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_PS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_RS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_RS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_RS256_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_RS384_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_goodKeyAlias
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchES
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchPS
JwtBuilderAPIConfigTests_sigAlg_RS512_goodGlobalKeyStore_goodKeyStoreRef_keyAliasMisMatchRS
```
1. com.ibm.ws.security.jwt_fat.consumer
- (Signing) Tests were updated to consume tokens using all of the supported Algorithms
Tests were added to use valid and invalid alias', keystores, matches and mis-matches between between the algorithm config attribute and the token contents
Tests were added to use updated server.xml config attributes with the new signature algorithms
- (Decrypting) Tests were updated to decrypt tokens JWE's instead of JWS'
Tests were added to decrypt using keys for each of the supported encryption algorithms (RS256, RS384 and RS512)
Tests were added to attempt to decrypt using keys for algorithms that are NOT supported
Tests were added to decrypt using new attributes from server.xml
Tests were added to decrypt tokens that contain **keyManagementKeyAlgorithm** and **contentEncryptionAlgorithm** values that our builder config doesn't support, but, we'll allow to be consumed
Tests added included both valid and invalid values in the config
Tests were added to get the private key from either the consumers config's trust store or the server's truststore (tests were created to use non-existant keys too)
Tests were added to use new server.xml config attributes.
Tests were added to have mis-matches between token being encrypted, but config doesn't decrypt and vice-versa
Tests were added to test non-default values for typ and cty in the JWE Header
**List of test cases added:**
```
JwtConsumerApiConfigTests_SigAlgES256
JwtConsumerApiConfigTests_SigAlgES256_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgES256_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgES256_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgES384
JwtConsumerApiConfigTests_SigAlgES384_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgES384_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgES384_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgES512
JwtConsumerApiConfigTests_SigAlgES512_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgES512_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgES512_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgHS256
JwtConsumerApiConfigTests_SigAlgHS384
JwtConsumerApiConfigTests_SigAlgHS512
JwtConsumerApiConfigTests_SigAlgRS256
JwtConsumerApiConfigTests_SigAlgRS256_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgRS256_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgRS256_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgRS384
JwtConsumerApiConfigTests_SigAlgRS384_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgRS384_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgRS384_trustAliasMisMatchRS
JwtConsumerApiConfigTests_SigAlgRS512
JwtConsumerApiConfigTests_SigAlgRS512_trustAliasMisMatchES
JwtConsumerApiConfigTests_SigAlgRS512_trustAliasMisMatchPS
JwtConsumerApiConfigTests_SigAlgRS512_trustAliasMisMatchRS
JwtConsumerApiConfigTests_badKeyManagementKeyAlias_goodSslRef
JwtConsumerApiConfigTests_decryptWithUnsupportedAlg
JwtConsumerApiConfigTests_encryptOtherContentEncryptionAlg
JwtConsumerApiConfigTests_encryptOtherJWEHeader_cty
JwtConsumerApiConfigTests_encryptOtherJWEHeader_typ
JwtConsumerApiConfigTests_encryptOtherKeyManagementKeyAlg
JwtConsumerApiConfigTests_encryptRS256_decryptRS256
JwtConsumerApiConfigTests_encryptRS256_decryptRS384
JwtConsumerApiConfigTests_encryptRS256_decryptRS512
JwtConsumerApiConfigTests_encryptRS384_decryptRS256
JwtConsumerApiConfigTests_encryptRS384_decryptRS384
JwtConsumerApiConfigTests_encryptRS384_decryptRS512
JwtConsumerApiConfigTests_encryptRS512_decryptRS256
JwtConsumerApiConfigTests_encryptRS512_decryptRS384
JwtConsumerApiConfigTests_encryptRS512_decryptRS512
JwtConsumerApiConfigTests_encryptSimpleJsonPayload
JwtConsumerApiConfigTests_encryptedToken_consumerDoesNotDecrypt
JwtConsumerApiConfigTests_goodKeyManagementKeyAlias_baddSslRef
JwtConsumerApiConfigTests_goodKeyManagementKeyAlias_missingSslRef_refMissingFromServerwideSSL
JwtConsumerApiConfigTests_tokenNotEncrypted_consumerDecrypts
```
2. com.ibm.ws.security.mp.jwt.1.1_fat
- (Signing) Tests were added to consume tokens using all of the supported Algorithms
Tests were added to use valid and invalid alias', keystores, matches and mis-matches between between the algorithm config attribute and the token contents
Tests were added to use updated server.xml config and mp config properties attributes for the new signature algorithms
**List of test cases added:**
```
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocES256RelativeFile_test
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocES512JwksUri_test
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocRS256Url_test
MPJwtGoodMPConfigAsEnvVars_NoPublicKey_UseKeyLocRS256Url_test
MPJwtGoodMPConfigAsEnvVars_UseES384PublicKey_NoKeyLoc_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocES2564Url_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocES384File_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocES512RelativeFile_test
MPJwtGoodMPConfigAsSystemProperties_NoPublicKey_UseKeyLocRS512JwksUri_test
MPJwtGoodMPConfigAsSystemProperties_UseRS384PublicKey_NoKeyLoc_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES256PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES384PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES384PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES512PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodES512PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodFileES512PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodFileRS256PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodJwksUriES384PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodJwksUriRS512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS256PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS384PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS384PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS512PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRS512PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRelativeES512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodRelativeRS256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodUrlES256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodUrlPublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_GoodUrlRS384PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenES384_ES512PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenES384_PS256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenES384_RS384PublicKeyInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenRS512_ES384PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenRS512_PS512PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_MisMatch_tokenRS512_RS256PublicKeyInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES256_BadUrlRS384PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES384_BadJwksUriPS256PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES384_BadJwksUriRS512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadFilePS384PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadFileRS256PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadRelativePS384PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgES512_BadRelativeRS256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS256_BadJwksUriES384PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadFileES512PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadRelativeES512PublicKeyLocationInMPConfigInMetaInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadUrlES256PublicKeyLocationInMPConfigUnderWebInf_test
MPJwtMPOtherSigAlgConfigInApp_SigAlgOnlyMPJwtConfigInServerXml_cfgRS384_BadUrlPublicKeyLocationInMPConfigUnderWebInf_test
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingES256_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingES384_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingES512_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingHS256_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingHS384_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingHS512_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingRS256_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingRS384_tokenWithMatchAndMisMatchSigAlgs
MpJwtConfigUsingBuilderTests_sigAlg_mpJWTusingRS512_tokenWithMatchAndMisMatchSigAlgs
```
### FAT projects created:
1. com.ibm.ws.security.mp.jwt.1.2_fat
- (Signing) All of the signing tests are included in the **com.ibm.ws.security.mp.jwt.1.1_fat** project
- (Specifying Audience) Tests were added to specify the audience value via mp config propertes (in addition to server.xml support that was part of 1.1)
The existing mpJwt FAT (1.1) tests supported specifying the audience value through the server.xml
Tests were added to specify the audience via the **mp.jwt.verify.audiences** attribute in any of the following locations/ways: microprofile-config.properties in META-INF or WEB-INF/classes/META-INF within the app, as Environment variables, or as System properties. Good/bad values were tested as well as testing that the correct precedence order is honored. (server.xml values override those found within the app)
- (Specifying signature Algorithm) Tests were added to specify the signature algorithm value via mp config propertes (in addition to server.xml support that was part of 1.1)
The existing mpJwt FAT (1.1) tests supported specifying the signature algorithm value through the server.xml
Tests were added to specify the audience via the **mp.jwt.verify.publickey.algorithm** attribute in any of the following locations/ways: microprofile-config.properties in META-INF or WEB-INF/classes/META-INF within the app, as Environment variables, or as System properties. Good/bad values were tested as well as testing that the correct precedence order is honored. (server.xml values override those found within the app)
- (Specifying how token will be passed) Tests were added to specify where/how the JWT token would be passed on a request to a protected app.
The existing mpJwt (1.1) tests always passed the JWT in the **Authorization** header using the name **Bearer**. This feature now allows the user to pass the JWT in the **Cookie** Header and specify the name to pass it with.
Tests have been added to specifying and omitting the token header and cookie name values. All good/bad combinations were included. We tested passing the token how the config expected it and did not expect it.
- (Decrypting) Tests were added to decrypt tokens JWE's instead of JWS'
Tests were added to decrypt using keys for each of the supported encryption algorithms (RS256, RS384 and RS512)
Tests were added to attempt to decrypt using keys for algorithms that are NOT supported
Tests were added to decrypt using new attributes from server.xml
Tests were added to decrypt tokens that contain **keyManagementKeyAlgorithm** and **contentEncryptionAlgorithm** values that our builder config doesn't support, but, we'll allow to be consumed
Tests added included both valid and invalid values in the config
Tests were added to get the private key from either the mpJwt config's trust store or the server's truststore (tests were created to use non-existant keys too)
Tests were added to use new server.xml config attributes.
Tests were added to use mp config properties from any of the following locations/ways: microprofile-config.properties in META-INF or WEB-INF/classes/META-INF within the app, as Environment variables, or as System properties.
Tests were added to ensure the correct precedence when using mp config properties and config attributes from server.xml
Tests were added to have mis-matches between token being encrypted, but config doesn't decrypt and vice-versa
Tests were added to test non-default values for typ and cty in the JWE Header
Tests were added to ensure that mpJwt-1.2 function will not work when only mpJwt-1.1 is enabled.
**List of test cases added:**
```
Feature11Enabled_ConfigInAppTests_DecryptKeyLocRelativeForRS256InMPConfig_InMetaInf_JWEToken_test
Feature11Enabled_ConfigInAppTests_DecryptKeyLocRelativeForRS256InMPConfig_InMetaInf_JWSToken_test
Feature11Enabled_ConfigInAppTests_GoodAudiencesInServerXml_BadAudiencesInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_GoodAudiencesInServerXml_BadAudiencesInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsAuthorizationInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsAuthorizationInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsCookieInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_HeaderIsCookieInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_MatchingNonDefaultKeyAndAlgorithmInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_MatchingNonDefaultKeyAndAlgorithmInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInAppTests_NoAudiencesInServerXml_GoodAudiencesInMPConfig_InMetaInf_test
Feature11Enabled_ConfigInAppTests_NoAudiencesInServerXml_GoodAudiencesInMPConfig_UnderWebInf_test
Feature11Enabled_ConfigInServerXmlTests_Header_Authorization_passTokenInAuthHeaderUsingBearer
Feature11Enabled_ConfigInServerXmlTests_Header_Cookie_doNotSetCookieName_passTokenAsCookie
Feature11Enabled_ConfigInServerXmlTests_Header_Cookie_setCookieName_passTokenAsCookie
Feature11Enabled_ConfigInServerXmlTests_KeyManagementKeyAliasKeyRS256_JWEToken_test
Feature11Enabled_ConfigInServerXmlTests_KeyManagementKeyAliasKeyRS256_JWSToken_test
Feature11Enabled_ConfigInServerXmlTests_NoKeyManagementKeyAliasKey_JWEToken_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_Algorithm_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_Audience_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_HeaderCookie_test
Feature11Enabled_GenericEnvVarsAndSystemPropertiesTests_overridAll_test
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderAndCookie_HeaderBad
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderAndCookie_HeaderGood
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderNotUsingBearer
MPJwt12ConfigUsingBuilderTests_Header_Authorization_passTokenInAuthHeaderUsingBearer
MPJwt12ConfigUsingBuilderTests_Header_Authorization_setCookieName_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Cookie_doNotSetCookieName_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Cookie_passTokenInAuthHeaderAndCookie_CookieBad
MPJwt12ConfigUsingBuilderTests_Header_Cookie_passTokenInAuthHeaderAndCookie_CookieGood
MPJwt12ConfigUsingBuilderTests_Header_Cookie_setCookieName_passTokenAsCookie
MPJwt12ConfigUsingBuilderTests_Header_Cookie_setCookieName_passTokenAsCookieUsingDefaultName
MPJwt12ConfigUsingBuilderTests_Header_Cookie_setCookieName_passTokenAsCookieUsingDifferentName
MPJwt12ConfigUsingBuilderTests_encrypt_mpJWtRS256_signUsingRS384
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtES384_tokenRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtNoEncryption_tokenEncrypted
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_JWEContentTypeNotjwt
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_JWETypeNotJose
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_simpleJsonPayload
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_tokenNotEncrypted
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_tokenRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_token_RSA_OAEP_256_RS256_publicKey_A256GCM
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS256_token_RSA_OAEP_RS256_publicKey_A192GCM
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS384_tokenRS384
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS384_tokenRS512
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtRS512_tokenRS512
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtShortPrivateKey_signUsingRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtinvalid_signUsingRS256
MPJwt12ConfigUsingBuilderTests_encrypt_mpJwtpublicKey_signUsingRS256
MPJwt12MPConfigInApp_GoodAlgorithmInServerXml_BadAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_GoodAlgorithmInServerXml_BadAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_GoodAudiencesInServerXml_BadAudiencesInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_GoodAudiencesInServerXml_BadAudiencesInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_GoodNonDefaultKeyAndAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_GoodNonDefaultKeyAndAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_HeaderIsAuthorizationInServerXml_HeaderIsCookieInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_HeaderIsAuthorizationInServerXml_HeaderIsCookieInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_HeaderIsCookieCookieNameSetConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_HeaderIsCookieCookieNameSetInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_HeaderIsCookieInServerXml_HeaderIsAuthorizationInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_HeaderIsCookieInServerXml_HeaderIsAuthorizationInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_MPJwt12ConfigInServerXmlOverrides_BadDecryptInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAudiencesInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_BadAudiencesInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocES256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocES256InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocFileForRS256InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocFileForRS512InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocJwksUriInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocPlainTextInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocRelativeForRS256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocRelativeForRS384InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocUrlForRS384InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptKeyLocUrlForRS512InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptPublicKeyInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_JweContentTypeNotJwt_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_JweTypeNotJose_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_TokenNotEncrypted_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptRS256InMPConfig_InMetaInf_simpleJsonPayload_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptShortKeyInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_DecryptStringKeyInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS2564DecryptRS384InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS2564DecryptRS512InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS3844DecryptRS512InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS384DecryptRS256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS5124DecryptRS256InMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_EncryptRS5124DecryptRS384InMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAlgorithmInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAlgorithmInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAudiencesInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_GoodAudiencesInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsAuthorizationInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsAuthorizationInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsBadInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsBadInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithCookieNameInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithCookieNameInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_InMetaInf_PassCookieWithNameBearer_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_InMetaInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_UnderWebInf_PassCookieWithNameBearer_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_HeaderIsCookieWithOtherCookieNameInMPConfig_UnderWebInf_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_NoDecryptInMPConfig_InMetaInf_TokenEncrypted_test
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_encrypt_mpJwtRS256_token_RSA_OAEP_256_RS256_publicKey_A256GCM
MPJwt12MPConfigInApp_NoMPJwt12ConfigInServerXml_encrypt_mpJwtRS256_token_RSA_OAEP_RS256_publicKey_A192GCM
MPJwtGoodMP12ConfigAsEnvVars_Algorithm_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_Algorithm_test
MPJwtGoodMP12ConfigAsEnvVars_Audiences_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_Audiences_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderAuthorization_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderAuthorization_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_withCookieName_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_HeaderCookie_withCookieName_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_AlternateDecryptSettings_contentEncryptAlg192
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_AlternateDecryptSettings_keyMgmtKeyAlg256
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256File_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256File_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256PlainText_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS256PlainText_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS512Url_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsEnvVars_decryptKeyLoc_RS512Url_test
MPJwtGoodMP12ConfigAsSystemProperties_Algorithm_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_Algorithm_test
MPJwtGoodMP12ConfigAsSystemProperties_Audiences_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_Audiences_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderAuthorization_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderAuthorization_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_withCookieName_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_HeaderCookie_withCookieName_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_AlternateDecryptSettings_contentEncryptAlg192
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_AlternateDecryptSettings_keyMgmtKeyAlg256
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS256Jwk_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS256Jwk_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS384RelativeFile_overriddenByServerXml_test
MPJwtGoodMP12ConfigAsSystemProperties_decryptKeyLoc_RS384RelativeFile_test
```
2. io.openliberty.microprofile.jwt.1.2.internal_fat_tck
These are the TCK test for MP JWT 1.2 and are currently at the latest 1.2-RC2 level available from Eclipse Microprofile.
As of 11/18/20, the EmptyTokenTest is the only TCK test that remains disabled. We can technically pass all of the tests in the class, but the server would have to be reconfigured in between tests in the EmptyTokenTest class in order to get them all to pass, which we donโt have the power to do so with the way the TCK tests run -- all tests in a class run against the same server configuration. We are looking at what we can do about this.
|
non_process
|
fat summary for support microprofile jwt several fat projects were updated or added in support of the microprofile jwt feature all testing for this feature is automated the existing mpjwt fat tests are now also run with the mpjwt enabled to ensure that all function still works test developement included addressing servicibility all messages were reviewed for each error encountered and analyzed for detail available to end user admin to ensure that we have valid information to each audience confidence in the testing definitely but more likely a tests were added to support new signature algorigthms of and encrypting decrypting jwt tokens supporting placement of the jwt token in either the authorization or cookie header and if cookie allow the token to be named all new config and mp config attributes to support new function addressed specifically below including configuration of the signature algorithm and audience in mp config properties when they had only been supported via server xml in the past fat projects updated com ibm ws security jwt fat builder signing tests were updated to sign using all of the supported algorithms tests were added to use valid and invalid alias keystores matches and mis matches between between the algorithm config attribute and the alias used tests were added to use updated server xml config attributes with the new signature algorithms tests were added to use the builder signwith api with the new signature algorithms tests were added to use tokens with the new algorithms with the claimsfrom apis encrypting tests were updated to encrypt tokens create jwe s instead of jws tests were added to encrypt using keys for each of the supported encryption algorithms and tests were added to attempt to encrypt using keys for algorithms that are not supported tests were added to encrypt using new attributes from server xml tests were added to encrypt using the new encryptwith api both valid and invalid values were used these tests included some that would set keymanagementkeyalgorithm and contentencryptionalgorithm values that our config doesn t support tests were added to test the claimsfrom apis using jwe s and jws in various forms tests added included both valid and invalid values in the config tests were added to get the public key from either the builder config s trust store or the server s truststore tests were created to use non existant keys too tests were added to use new server xml config attributes list of test cases added jwkendpointvalidationurltests encrypt jwkendpointvalidationurltests encrypt jwkendpointvalidationurltests encrypt jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwkendpointvalidationurltests sigalg jwtbuilderapibasictests claimsfrom jwestring decodedpayload allclaims jwtbuilderapibasictests claimsfrom jwestring encodedpayload allclaims jwtbuilderapibasictests claimsfrom jwestring to jwttoken allclaims jwtbuilderapibasictests claimsfrom to allclaims jwtbuilderapibasictests claimsfrom jwetoken to jwttoken allclaims jwtbuilderapibasictests claimsfrom jwtstring to jwetoken allclaims jwtbuilderapibasictests claimsfrom jwttoken to jwetoken allclaims jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep privatekey jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey invalidcontentencryptalg jwtbuilderapibasictests encryptwith rsa oaep publickey nullcontentencryptalg jwtbuilderapibasictests encryptwith rsa oaep shortpublickey jwtbuilderapibasictests encryptwith rsa oaep privatekey jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep shortpublickey jwtbuilderapibasictests encryptwith rsa oaep privatekey jwtbuilderapibasictests encryptwith rsa oaep publickey jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep publickey signwith jwtbuilderapibasictests encryptwith rsa oaep shortpublickey jwtbuilderapibasictests encryptwith rsa oaep null publickey jwtbuilderapibasictests encryptwith invalidkeymgmtkeyalg publickey jwtbuilderapibasictests encryptwith nullcontentencryptalg goodbuilderconfig jwtbuilderapibasictests encryptwith nullkeymgmtkeyalg publickey jwtbuilderapibasictests encryptwith nullkeymgmtkeyalg goodbuilderconfig jwtbuilderapibasictests encryptwith null publickey goodbuidlerconfig jwtbuilderapibasictests encryptwith usedifferentcontentencryptalgthanbuilderconfig jwtbuilderapibasictests encryptwith usedifferentkeymgmtkeyalgthanbuilderconfig jwtbuilderapibasictests encryptwith usedifferentpublickeythanbuilderconfig jwtbuilderapibasictests encryptwith usesamesettingsasbuilderconfig jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key string jwtbuilderapibasictests signwith sigalg key string jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapibasictests signwith sigalg key privkey jwtbuilderapiconfigtests amrvalue empty jwtbuilderapiconfigtests amrvalue invalid jwtbuilderapiconfigtests amrvalue valid jwtbuilderapiconfigtests encryption goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg badkeymanagementkeyalias goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodkeymanagementkeyalias goodcontentencryptalg truststorerefinvalid jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodkeymanagementkeyalias goodcontentencryptalg truststorerefmissing jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg invalidcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg missingcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg goodserverwidekeymanagementkeyalias goodcontentencryptalg truststorerefmissing jwtbuilderapiconfigtests encryption goodkeymgmtkeyalg missingkeymanagementkeyalias goodcontentencryptalg jwtbuilderapiconfigtests encryption invalidkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests encryption missingkeymgmtkeyalg goodcontentencryptalg jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs wtbuilderapiconfigtests sigalg with sharedkey jwtbuilderapiconfigtests sigalg with sharedkey jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref goodkeyalias jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatches jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchps jwtbuilderapiconfigtests sigalg goodglobalkeystore goodkeystoreref keyaliasmismatchrs com ibm ws security jwt fat consumer signing tests were updated to consume tokens using all of the supported algorithms tests were added to use valid and invalid alias keystores matches and mis matches between between the algorithm config attribute and the token contents tests were added to use updated server xml config attributes with the new signature algorithms decrypting tests were updated to decrypt tokens jwe s instead of jws tests were added to decrypt using keys for each of the supported encryption algorithms and tests were added to attempt to decrypt using keys for algorithms that are not supported tests were added to decrypt using new attributes from server xml tests were added to decrypt tokens that contain keymanagementkeyalgorithm and contentencryptionalgorithm values that our builder config doesn t support but we ll allow to be consumed tests added included both valid and invalid values in the config tests were added to get the private key from either the consumers config s trust store or the server s truststore tests were created to use non existant keys too tests were added to use new server xml config attributes tests were added to have mis matches between token being encrypted but config doesn t decrypt and vice versa tests were added to test non default values for typ and cty in the jwe header list of test cases added jwtconsumerapiconfigtests jwtconsumerapiconfigtests trustaliasmismatches jwtconsumerapiconfigtests trustaliasmismatchps jwtconsumerapiconfigtests trustaliasmismatchrs jwtconsumerapiconfigtests jwtconsumerapiconfigtests trustaliasmismatches jwtconsumerapiconfigtests trustaliasmismatchps jwtconsumerapiconfigtests trustaliasmismatchrs jwtconsumerapiconfigtests jwtconsumerapiconfigtests trustaliasmismatches jwtconsumerapiconfigtests trustaliasmismatchps jwtconsumerapiconfigtests trustaliasmismatchrs jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests trustaliasmismatches jwtconsumerapiconfigtests trustaliasmismatchps jwtconsumerapiconfigtests trustaliasmismatchrs jwtconsumerapiconfigtests jwtconsumerapiconfigtests trustaliasmismatches jwtconsumerapiconfigtests trustaliasmismatchps jwtconsumerapiconfigtests trustaliasmismatchrs jwtconsumerapiconfigtests jwtconsumerapiconfigtests trustaliasmismatches jwtconsumerapiconfigtests trustaliasmismatchps jwtconsumerapiconfigtests trustaliasmismatchrs jwtconsumerapiconfigtests badkeymanagementkeyalias goodsslref jwtconsumerapiconfigtests decryptwithunsupportedalg jwtconsumerapiconfigtests encryptothercontentencryptionalg jwtconsumerapiconfigtests encryptotherjweheader cty jwtconsumerapiconfigtests encryptotherjweheader typ jwtconsumerapiconfigtests encryptotherkeymanagementkeyalg jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests jwtconsumerapiconfigtests encryptsimplejsonpayload jwtconsumerapiconfigtests encryptedtoken consumerdoesnotdecrypt jwtconsumerapiconfigtests goodkeymanagementkeyalias baddsslref jwtconsumerapiconfigtests goodkeymanagementkeyalias missingsslref refmissingfromserverwidessl jwtconsumerapiconfigtests tokennotencrypted consumerdecrypts com ibm ws security mp jwt fat signing tests were added to consume tokens using all of the supported algorithms tests were added to use valid and invalid alias keystores matches and mis matches between between the algorithm config attribute and the token contents tests were added to use updated server xml config and mp config properties attributes for the new signature algorithms list of test cases added mpjwtgoodmpconfigasenvvars nopublickey test mpjwtgoodmpconfigasenvvars nopublickey test mpjwtgoodmpconfigasenvvars nopublickey test mpjwtgoodmpconfigasenvvars nopublickey test mpjwtgoodmpconfigasenvvars nokeyloc test mpjwtgoodmpconfigassystemproperties nopublickey test mpjwtgoodmpconfigassystemproperties nopublickey test mpjwtgoodmpconfigassystemproperties nopublickey test mpjwtgoodmpconfigassystemproperties nopublickey test mpjwtgoodmpconfigassystemproperties nokeyloc test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml goodurlpublickeylocationinmpconfigunderwebinf test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml mismatch test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml mismatch test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml mismatch test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml mismatch test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml mismatch test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml mismatch test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml test mpjwtmpothersigalgconfiginapp sigalgonlympjwtconfiginserverxml badurlpublickeylocationinmpconfigunderwebinf test mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs mpjwtconfigusingbuildertests sigalg tokenwithmatchandmismatchsigalgs fat projects created com ibm ws security mp jwt fat signing all of the signing tests are included in the com ibm ws security mp jwt fat project specifying audience tests were added to specify the audience value via mp config propertes in addition to server xml support that was part of the existing mpjwt fat tests supported specifying the audience value through the server xml tests were added to specify the audience via the mp jwt verify audiences attribute in any of the following locations ways microprofile config properties in meta inf or web inf classes meta inf within the app as environment variables or as system properties good bad values were tested as well as testing that the correct precedence order is honored server xml values override those found within the app specifying signature algorithm tests were added to specify the signature algorithm value via mp config propertes in addition to server xml support that was part of the existing mpjwt fat tests supported specifying the signature algorithm value through the server xml tests were added to specify the audience via the mp jwt verify publickey algorithm attribute in any of the following locations ways microprofile config properties in meta inf or web inf classes meta inf within the app as environment variables or as system properties good bad values were tested as well as testing that the correct precedence order is honored server xml values override those found within the app specifying how token will be passed tests were added to specify where how the jwt token would be passed on a request to a protected app the existing mpjwt tests always passed the jwt in the authorization header using the name bearer this feature now allows the user to pass the jwt in the cookie header and specify the name to pass it with tests have been added to specifying and omitting the token header and cookie name values all good bad combinations were included we tested passing the token how the config expected it and did not expect it decrypting tests were added to decrypt tokens jwe s instead of jws tests were added to decrypt using keys for each of the supported encryption algorithms and tests were added to attempt to decrypt using keys for algorithms that are not supported tests were added to decrypt using new attributes from server xml tests were added to decrypt tokens that contain keymanagementkeyalgorithm and contentencryptionalgorithm values that our builder config doesn t support but we ll allow to be consumed tests added included both valid and invalid values in the config tests were added to get the private key from either the mpjwt config s trust store or the server s truststore tests were created to use non existant keys too tests were added to use new server xml config attributes tests were added to use mp config properties from any of the following locations ways microprofile config properties in meta inf or web inf classes meta inf within the app as environment variables or as system properties tests were added to ensure the correct precedence when using mp config properties and config attributes from server xml tests were added to have mis matches between token being encrypted but config doesn t decrypt and vice versa tests were added to test non default values for typ and cty in the jwe header tests were added to ensure that mpjwt function will not work when only mpjwt is enabled list of test cases added configinapptests inmetainf jwetoken test configinapptests inmetainf jwstoken test configinapptests goodaudiencesinserverxml badaudiencesinmpconfig inmetainf test configinapptests goodaudiencesinserverxml badaudiencesinmpconfig underwebinf test configinapptests headerisauthorizationinmpconfig inmetainf test configinapptests headerisauthorizationinmpconfig underwebinf test configinapptests headeriscookieinmpconfig inmetainf test configinapptests headeriscookieinmpconfig underwebinf test configinapptests matchingnondefaultkeyandalgorithminmpconfig inmetainf test configinapptests matchingnondefaultkeyandalgorithminmpconfig underwebinf test configinapptests noaudiencesinserverxml goodaudiencesinmpconfig inmetainf test configinapptests noaudiencesinserverxml goodaudiencesinmpconfig underwebinf test configinserverxmltests header authorization passtokeninauthheaderusingbearer configinserverxmltests header cookie donotsetcookiename passtokenascookie configinserverxmltests header cookie setcookiename passtokenascookie configinserverxmltests jwetoken test configinserverxmltests jwstoken test configinserverxmltests nokeymanagementkeyaliaskey jwetoken test genericenvvarsandsystempropertiestests algorithm test genericenvvarsandsystempropertiestests audience test genericenvvarsandsystempropertiestests headercookie test genericenvvarsandsystempropertiestests overridall test header authorization passtokenascookie header authorization passtokeninauthheaderandcookie headerbad header authorization passtokeninauthheaderandcookie headergood header authorization passtokeninauthheadernotusingbearer header authorization passtokeninauthheaderusingbearer header authorization setcookiename passtokenascookie header cookie donotsetcookiename passtokenascookie header cookie passtokeninauthheaderandcookie cookiebad header cookie passtokeninauthheaderandcookie cookiegood header cookie setcookiename passtokenascookie header cookie setcookiename passtokenascookieusingdefaultname header cookie setcookiename passtokenascookieusingdifferentname encrypt encrypt encrypt mpjwtnoencryption tokenencrypted encrypt jwecontenttypenotjwt encrypt jwetypenotjose encrypt simplejsonpayload encrypt tokennotencrypted encrypt encrypt token rsa oaep publickey encrypt token rsa oaep publickey encrypt encrypt encrypt encrypt mpjwtshortprivatekey encrypt mpjwtinvalid encrypt mpjwtpublickey goodalgorithminserverxml badalgorithminmpconfig inmetainf test goodalgorithminserverxml badalgorithminmpconfig underwebinf test goodaudiencesinserverxml badaudiencesinmpconfig inmetainf test goodaudiencesinserverxml badaudiencesinmpconfig underwebinf test goodnondefaultkeyandalgorithminmpconfig inmetainf test goodnondefaultkeyandalgorithminmpconfig underwebinf test headerisauthorizationinserverxml headeriscookieinmpconfig inmetainf test headerisauthorizationinserverxml headeriscookieinmpconfig underwebinf test headeriscookiecookienamesetconfiginserverxml headeriscookiewithothercookienameinmpconfig underwebinf test headeriscookiecookienamesetinserverxml headeriscookiewithothercookienameinmpconfig inmetainf test headeriscookieinserverxml headerisauthorizationinmpconfig inmetainf test headeriscookieinserverxml headerisauthorizationinmpconfig underwebinf test baddecryptinmpconfig inmetainf test badalgorithminmpconfig inmetainf test badalgorithminmpconfig underwebinf test badaudiencesinmpconfig inmetainf test badaudiencesinmpconfig underwebinf test inmetainf test underwebinf test underwebinf test inmetainf test decryptkeylocjwksuriinmpconfig underwebinf test decryptkeylocplaintextinmpconfig inmetainf test inmetainf test underwebinf test inmetainf test underwebinf test decryptpublickeyinmpconfig inmetainf test inmetainf jwecontenttypenotjwt test inmetainf jwetypenotjose test inmetainf tokennotencrypted test inmetainf simplejsonpayload test decryptshortkeyinmpconfig inmetainf test decryptstringkeyinmpconfig inmetainf test underwebinf test inmetainf test inmetainf test inmetainf test inmetainf test underwebinf test goodalgorithminmpconfig inmetainf test goodalgorithminmpconfig underwebinf test goodaudiencesinmpconfig inmetainf test goodaudiencesinmpconfig underwebinf test headerisauthorizationinmpconfig inmetainf test headerisauthorizationinmpconfig underwebinf test headerisbadinmpconfig inmetainf test headerisbadinmpconfig underwebinf test headeriscookieinmpconfig inmetainf test headeriscookieinmpconfig underwebinf test headeriscookiewithcookienameinmpconfig inmetainf test headeriscookiewithcookienameinmpconfig underwebinf test headeriscookiewithothercookienameinmpconfig inmetainf passcookiewithnamebearer test headeriscookiewithothercookienameinmpconfig inmetainf test headeriscookiewithothercookienameinmpconfig underwebinf passcookiewithnamebearer test headeriscookiewithothercookienameinmpconfig underwebinf test nodecryptinmpconfig inmetainf tokenencrypted test encrypt token rsa oaep publickey encrypt token rsa oaep publickey algorithm overriddenbyserverxml test algorithm test audiences overriddenbyserverxml test audiences test headerauthorization overriddenbyserverxml test headerauthorization test headercookie overriddenbyserverxml test headercookie test headercookie withcookiename overriddenbyserverxml test headercookie withcookiename test decryptkeyloc alternatedecryptsettings decryptkeyloc alternatedecryptsettings decryptkeyloc overriddenbyserverxml test decryptkeyloc test decryptkeyloc overriddenbyserverxml test decryptkeyloc test decryptkeyloc overriddenbyserverxml test decryptkeyloc test algorithm overriddenbyserverxml test algorithm test audiences overriddenbyserverxml test audiences test headerauthorization overriddenbyserverxml test headerauthorization test headercookie overriddenbyserverxml test headercookie test headercookie withcookiename overriddenbyserverxml test headercookie withcookiename test decryptkeyloc alternatedecryptsettings decryptkeyloc alternatedecryptsettings decryptkeyloc overriddenbyserverxml test decryptkeyloc test decryptkeyloc overriddenbyserverxml test decryptkeyloc test io openliberty microprofile jwt internal fat tck these are the tck test for mp jwt and are currently at the latest level available from eclipse microprofile as of the emptytokentest is the only tck test that remains disabled we can technically pass all of the tests in the class but the server would have to be reconfigured in between tests in the emptytokentest class in order to get them all to pass which we donโt have the power to do so with the way the tck tests run all tests in a class run against the same server configuration we are looking at what we can do about this
| 0
|
7,937
| 11,136,080,101
|
IssuesEvent
|
2019-12-20 15:47:44
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
closed
|
Testing on Win10
|
duplicate process question
|
Hi, We tried to set up on a Mirror Node Win10 - where we have done all our dev work so far (our Power Transition, Energy Microgrid Platform). Obviously we ran into trouble straight away and realized that we need to set up on OSX/Linux. Will there be a port onto Win10 in the near future? We'd like to keep things operating on the same OS.
|
1.0
|
Testing on Win10 - Hi, We tried to set up on a Mirror Node Win10 - where we have done all our dev work so far (our Power Transition, Energy Microgrid Platform). Obviously we ran into trouble straight away and realized that we need to set up on OSX/Linux. Will there be a port onto Win10 in the near future? We'd like to keep things operating on the same OS.
|
process
|
testing on hi we tried to set up on a mirror node where we have done all our dev work so far our power transition energy microgrid platform obviously we ran into trouble straight away and realized that we need to set up on osx linux will there be a port onto in the near future we d like to keep things operating on the same os
| 1
|
218,316
| 16,983,627,281
|
IssuesEvent
|
2021-06-30 12:01:51
|
spacemeshos/go-spacemesh
|
https://api.github.com/repos/spacemeshos/go-spacemesh
|
opened
|
Decouple node deployment and resource managment from test running in CI
|
Automation Epic devex devops tests
|
## Motivation
Our testing infrastructure in `tests` is coupled deeply with deploying on K8S, I'm not suggesting removing K8S (for now), but I do think we should split the code and make the tests modular to be able to "drop-in" tests or "play scenarios" inside an existing running network or just get network information essential to development and debugging easily.
## Action plan
- Create a simple API (first code and maybe evolve to RESTful) to perform changes in network structure and querying nodes
- Network management API
- Node client API to perform actions or checks
- "Plug" tests into the API or pass network info by params to run the wanted changes and checks on the network
- Test results reported back to some central or temporary central (for a temporary network) server, GH should able to consume results.
- Reports about important information about network during run (nice to have for now)
the above will probably be broken into smaller issues
|
1.0
|
Decouple node deployment and resource managment from test running in CI - ## Motivation
Our testing infrastructure in `tests` is coupled deeply with deploying on K8S, I'm not suggesting removing K8S (for now), but I do think we should split the code and make the tests modular to be able to "drop-in" tests or "play scenarios" inside an existing running network or just get network information essential to development and debugging easily.
## Action plan
- Create a simple API (first code and maybe evolve to RESTful) to perform changes in network structure and querying nodes
- Network management API
- Node client API to perform actions or checks
- "Plug" tests into the API or pass network info by params to run the wanted changes and checks on the network
- Test results reported back to some central or temporary central (for a temporary network) server, GH should able to consume results.
- Reports about important information about network during run (nice to have for now)
the above will probably be broken into smaller issues
|
non_process
|
decouple node deployment and resource managment from test running in ci motivation our testing infrastructure in tests is coupled deeply with deploying on i m not suggesting removing for now but i do think we should split the code and make the tests modular to be able to drop in tests or play scenarios inside an existing running network or just get network information essential to development and debugging easily action plan create a simple api first code and maybe evolve to restful to perform changes in network structure and querying nodes network management api node client api to perform actions or checks plug tests into the api or pass network info by params to run the wanted changes and checks on the network test results reported back to some central or temporary central for a temporary network server gh should able to consume results reports about important information about network during run nice to have for now the above will probably be broken into smaller issues
| 0
|
3,058
| 6,047,210,862
|
IssuesEvent
|
2017-06-12 13:59:27
|
eranhd/Anti-Drug-Jerusalem
|
https://api.github.com/repos/eranhd/Anti-Drug-Jerusalem
|
closed
|
ืืืขืื ืืช ืืืืืืช ืฉื "ืืื ืื" ืฉื ืืืชื ืืฉืชืืฉ
|
in process
|
ืืื ืืฉืชืืฉ ืืฉ ืื ืื, ืฆืจืื ืฉืขืืืจ ืื ืื ื ืืขื ืื ืืช ืืืืืืช ืฉืื ืื ืืืื
|
1.0
|
ืืืขืื ืืช ืืืืืืช ืฉื "ืืื ืื" ืฉื ืืืชื ืืฉืชืืฉ - ืืื ืืฉืชืืฉ ืืฉ ืื ืื, ืฆืจืื ืฉืขืืืจ ืื ืื ื ืืขื ืื ืืช ืืืืืืช ืฉืื ืื ืืืื
|
process
|
ืืืขืื ืืช ืืืืืืช ืฉื ืืื ืื ืฉื ืืืชื ืืฉืชืืฉ ืืื ืืฉืชืืฉ ืืฉ ืื ืื ืฆืจืื ืฉืขืืืจ ืื ืื ื ืืขื ืื ืืช ืืืืืืช ืฉืื ืื ืืืื
| 1
|
331,685
| 24,320,574,968
|
IssuesEvent
|
2022-09-30 10:20:26
|
opsd-io/terraform-github
|
https://api.github.com/repos/opsd-io/terraform-github
|
closed
|
Prepare (customize) newly created reposiotory
|
documentation
|
To do:
- [x] update basic project information
- [x] review asdf settings to ensure that proper tools will be used
|
1.0
|
Prepare (customize) newly created reposiotory - To do:
- [x] update basic project information
- [x] review asdf settings to ensure that proper tools will be used
|
non_process
|
prepare customize newly created reposiotory to do update basic project information review asdf settings to ensure that proper tools will be used
| 0
|
59,422
| 17,023,123,315
|
IssuesEvent
|
2021-07-03 00:28:38
|
tomhughes/trac-tickets
|
https://api.github.com/repos/tomhughes/trac-tickets
|
closed
|
editing key:val in JOSM should let me edit the key name too
|
Component: josm Priority: minor Resolution: invalid Type: defect
|
**[Submitted to the original trac issue database at 8.59am, Friday, 21st July 2006]**
I want to change all the 'Name' keys to 'name' but this means re-creating the keyval as you can only edit the value?
|
1.0
|
editing key:val in JOSM should let me edit the key name too - **[Submitted to the original trac issue database at 8.59am, Friday, 21st July 2006]**
I want to change all the 'Name' keys to 'name' but this means re-creating the keyval as you can only edit the value?
|
non_process
|
editing key val in josm should let me edit the key name too i want to change all the name keys to name but this means re creating the keyval as you can only edit the value
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.