Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 4 112 | repo_url stringlengths 33 141 | action stringclasses 3 values | title stringlengths 1 957 | labels stringlengths 4 1.11k | body stringlengths 1 261k | index stringclasses 11 values | text_combine stringlengths 95 261k | label stringclasses 2 values | text stringlengths 96 250k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
166,625 | 26,389,162,556 | IssuesEvent | 2023-01-12 14:31:10 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Nav offcanvas remove "Browse All" from inserter block picker | Accessibility (a11y) [Status] In Progress Needs Design Feedback Needs Technical Feedback [Block] Navigation [a11y] Keyboard & Focus | As reported in https://github.com/WordPress/gutenberg/issues/46939#issuecomment-1374652632, when picking blocks from the Navigation offcanvas using the inserter there is a `Browse All` button. However, when clicked this breaks focus away from the offcanvas and should be removed. | 1.0 | Nav offcanvas remove "Browse All" from inserter block picker - As reported in https://github.com/WordPress/gutenberg/issues/46939#issuecomment-1374652632, when picking blocks from the Navigation offcanvas using the inserter there is a `Browse All` button. However, when clicked this breaks focus away from the offcanvas and should be removed. | design | nav offcanvas remove browse all from inserter block picker as reported in when picking blocks from the navigation offcanvas using the inserter there is a browse all button however when clicked this breaks focus away from the offcanvas and should be removed | 1 |
187,635 | 15,103,718,385 | IssuesEvent | 2021-02-08 10:40:20 | openintegrationhub/openintegrationhub | https://api.github.com/repos/openintegrationhub/openintegrationhub | closed | Update GCP Installation Documents for Healthcheck Behavior | bug documentation | When deploying to Google Cloud Platform, following the [GCP Installation Guide](https://openintegrationhub.github.io/docs/Getting%20Started/GCPInstallationGuide.html) from the Help Documentation will lead to an inability for the Kubernetes control plane and kubelet to mark services as healthy and route traffic to them.
### To Reproduce
1. Following the steps in the Installation guide, the Ingress description is applied to the cluster early in the process (https://openintegrationhub.github.io/docs/Getting%20Started/GCPInstallationGuide.html#basic-open-integration-hub-infrastructure-setup)
2. Later, when IAM is deployed (https://openintegrationhub.github.io/docs/Getting%20Started/GCPInstallationGuide.html#identity-and-access-management-deployment), it is not possible to proceed to the next step because traffic will not be routed to the IAM Pod
3. This situation repeats when deploying any other services to the cluster which have already been defined in the Ingress
### Expected behavior
It was expected that the Pods would become addressable upon launch.
### Context
The root cause of this issue comes down to the actions performed by Google Kubernetes Engine when you create an Ingress. It additionally creates a Load Balancer and its related Backend Services. Each Backend Service also has a Healthcheck created and assigned, which pings the root endpoint `/` of Pods to see if they are alive. This Healthcheck is used to determine if a pod is in a Healthy state and can have traffic sent to it.
When applying the Deployment configuration for each Service, Readiness and Liveness probes are described at the endpoint `/healthcheck`. The OIH Services do not reply to the root endpoint `/`, but return a 404 error.
When a Healthcheck is created, it will use the Readiness and Liveness probes from applicable Deployments, but only if they have already been applied to the Cluster. After creation, the Healthcheck does not track any changes to Deployments, so will not pick up the probe values later.
### Proposed Solution
Once an Ingress has been created for a Service, the only way to change its healthcheck is by one of three methods:
- Delete and recreate the Ingress
- Apply the Ingress configuration without the Service, and then Apply the configuration again with the Service re-added
- Manually change the Healthcheck parameters
Therefore, it is proposed to handle this situation via education, and update the Help Documentation to apply the Ingress for each Service only after the Service and Deployment configurations have already been applied.
An alternate solution would be to use a [Backend Config CRD](https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#health_checks) to declaratively describe the Healthcheck values for each Service. | 1.0 | Update GCP Installation Documents for Healthcheck Behavior - When deploying to Google Cloud Platform, following the [GCP Installation Guide](https://openintegrationhub.github.io/docs/Getting%20Started/GCPInstallationGuide.html) from the Help Documentation will lead to an inability for the Kubernetes control plane and kubelet to mark services as healthy and route traffic to them.
### To Reproduce
1. Following the steps in the Installation guide, the Ingress description is applied to the cluster early in the process (https://openintegrationhub.github.io/docs/Getting%20Started/GCPInstallationGuide.html#basic-open-integration-hub-infrastructure-setup)
2. Later, when IAM is deployed (https://openintegrationhub.github.io/docs/Getting%20Started/GCPInstallationGuide.html#identity-and-access-management-deployment), it is not possible to proceed to the next step because traffic will not be routed to the IAM Pod
3. This situation repeats when deploying any other services to the cluster which have already been defined in the Ingress
### Expected behavior
It was expected that the Pods would become addressable upon launch.
### Context
The root cause of this issue comes down to the actions performed by Google Kubernetes Engine when you create an Ingress. It additionally creates a Load Balancer and its related Backend Services. Each Backend Service also has a Healthcheck created and assigned, which pings the root endpoint `/` of Pods to see if they are alive. This Healthcheck is used to determine if a pod is in a Healthy state and can have traffic sent to it.
When applying the Deployment configuration for each Service, Readiness and Liveness probes are described at the endpoint `/healthcheck`. The OIH Services do not reply to the root endpoint `/`, but return a 404 error.
When a Healthcheck is created, it will use the Readiness and Liveness probes from applicable Deployments, but only if they have already been applied to the Cluster. After creation, the Healthcheck does not track any changes to Deployments, so will not pick up the probe values later.
### Proposed Solution
Once an Ingress has been created for a Service, the only way to change its healthcheck is by one of three methods:
- Delete and recreate the Ingress
- Apply the Ingress configuration without the Service, and then Apply the configuration again with the Service re-added
- Manually change the Healthcheck parameters
Therefore, it is proposed to handle this situation via education, and update the Help Documentation to apply the Ingress for each Service only after the Service and Deployment configurations have already been applied.
An alternate solution would be to use a [Backend Config CRD](https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#health_checks) to declaratively describe the Healthcheck values for each Service. | non_design | update gcp installation documents for healthcheck behavior when deploying to google cloud platform following the from the help documentation will lead to an inability for the kubernetes control plane and kubelet to mark services as healthy and route traffic to them to reproduce following the steps in the installation guide the ingress description is applied to the cluster early in the process later when iam is deployed it is not possible to proceed to the next step because traffic will not be routed to the iam pod this situation repeats when deploying any other services to the cluster which have already been defined in the ingress expected behavior it was expected that the pods would become addressable upon launch context the root cause of this issue comes down to the actions performed by google kubernetes engine when you create an ingress it additionally creates a load balancer and its related backend services each backend service also has a healthcheck created and assigned which pings the root endpoint of pods to see if they are alive this healthcheck is used to determine if a pod is in a healthy state and can have traffic sent to it when applying the deployment configuration for each service readiness and liveness probes are described at the endpoint healthcheck the oih services do not reply to the root endpoint but return a error when a healthcheck is created it will use the readiness and liveness probes from applicable deployments but only if they have already been applied to the cluster after creation the healthcheck does not track any changes to deployments so will not pick up the probe values later proposed solution once an ingress has been created for a service the only way to change its healthcheck is by one of three methods delete and recreate the ingress apply the ingress configuration without the service and then apply the configuration again with the service re added manually change the healthcheck parameters therefore it is proposed to handle this situation via education and update the help documentation to apply the ingress for each service only after the service and deployment configurations have already been applied an alternate solution would be to use a to declaratively describe the healthcheck values for each service | 0 |
272,380 | 23,669,527,569 | IssuesEvent | 2022-08-27 05:43:47 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: sqlsmith/setup=tpcc/setting=no-ddl failed | C-test-failure O-robot O-roachtest branch-master | roachtest.sqlsmith/setup=tpcc/setting=no-ddl [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6260325?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6260325?buildTab=artifacts#/sqlsmith/setup=tpcc/setting=no-ddl) on master @ [770ff3c545a51752490403da64d56fb397f49c5e](https://github.com/cockroachdb/cockroach/commits/770ff3c545a51752490403da64d56fb397f49c5e):
```
test artifacts and logs in: /artifacts/sqlsmith/setup=tpcc/setting=no-ddl/run_1
sqlsmith.go:267,sqlsmith.go:327,test_runner.go:897: error: pq: internal error: unexpected error from the vectorized engine: runtime error: index out of range [2012] with length 2012
stmt:
SELECT
tab_105.o_carrier_id AS col_223,
(-6454220902618163273):::INT8 AS col_224,
tab_105.crdb_internal_mvcc_timestamp AS col_225,
tab_105.o_carrier_id AS col_226,
tab_105.o_entry_d AS col_227,
tab_105.o_w_id AS col_228
FROM
defaultdb.public."order"@order_idx AS tab_105
ORDER BY
tab_105.crdb_internal_mvcc_timestamp;
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=tpcc/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: sqlsmith/setup=tpcc/setting=no-ddl failed - roachtest.sqlsmith/setup=tpcc/setting=no-ddl [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6260325?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6260325?buildTab=artifacts#/sqlsmith/setup=tpcc/setting=no-ddl) on master @ [770ff3c545a51752490403da64d56fb397f49c5e](https://github.com/cockroachdb/cockroach/commits/770ff3c545a51752490403da64d56fb397f49c5e):
```
test artifacts and logs in: /artifacts/sqlsmith/setup=tpcc/setting=no-ddl/run_1
sqlsmith.go:267,sqlsmith.go:327,test_runner.go:897: error: pq: internal error: unexpected error from the vectorized engine: runtime error: index out of range [2012] with length 2012
stmt:
SELECT
tab_105.o_carrier_id AS col_223,
(-6454220902618163273):::INT8 AS col_224,
tab_105.crdb_internal_mvcc_timestamp AS col_225,
tab_105.o_carrier_id AS col_226,
tab_105.o_entry_d AS col_227,
tab_105.o_w_id AS col_228
FROM
defaultdb.public."order"@order_idx AS tab_105
ORDER BY
tab_105.crdb_internal_mvcc_timestamp;
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=tpcc/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_design | roachtest sqlsmith setup tpcc setting no ddl failed roachtest sqlsmith setup tpcc setting no ddl with on master test artifacts and logs in artifacts sqlsmith setup tpcc setting no ddl run sqlsmith go sqlsmith go test runner go error pq internal error unexpected error from the vectorized engine runtime error index out of range with length stmt select tab o carrier id as col as col tab crdb internal mvcc timestamp as col tab o carrier id as col tab o entry d as col tab o w id as col from defaultdb public order order idx as tab order by tab crdb internal mvcc timestamp parameters roachtest cloud gce roachtest cpu roachtest ssd help see see cc cockroachdb sql queries | 0 |
49,811 | 6,041,002,116 | IssuesEvent | 2017-06-10 19:44:20 | unknown-horizons/unknown-horizons | https://api.github.com/repos/unknown-horizons/unknown-horizons | closed | Run multiplayer tests on travis by providing enet bindings | A-internals tests | ~~For example here: https://travis-ci.org/unknown-horizons/unknown-horizons/builds/234343626~~
~~The tests apparantly won't continue to run until Travis decides to abort the build due to inactivity.~~
See https://github.com/unknown-horizons/unknown-horizons/issues/2691#issuecomment-307438696 | 1.0 | Run multiplayer tests on travis by providing enet bindings - ~~For example here: https://travis-ci.org/unknown-horizons/unknown-horizons/builds/234343626~~
~~The tests apparantly won't continue to run until Travis decides to abort the build due to inactivity.~~
See https://github.com/unknown-horizons/unknown-horizons/issues/2691#issuecomment-307438696 | non_design | run multiplayer tests on travis by providing enet bindings for example here the tests apparantly won t continue to run until travis decides to abort the build due to inactivity see | 0 |
37,721 | 4,835,882,812 | IssuesEvent | 2016-11-08 18:00:18 | owncloud/client | https://api.github.com/repos/owncloud/client | closed | Folder Sync Connections - Please order alphabetically | Design & UX Enhancement ReadyToTest | This is on the Mac OSX client app.
### Expected behaviour
After adding several "Folder Sync Connections" I should have those be organized alphabetically in the settings tab and on the top menu for the "Open folder ...".
### Actual behaviour
When adding several "Folder Sync Connections". Those are displayed in the order they were added but not alphabetically which is a bit of a burden. I have currently 8 folders and would love to have those ordered in an ascending manner.
### Steps to reproduce
1. Install the mac client app
2. Add a new server without specifying which folder
3. Then in the settings click on "Folder Sync Connection" and create several
4. You will see that those are not listed alphabetically
### Server configuration
Operating system:
OSX | 1.0 | Folder Sync Connections - Please order alphabetically - This is on the Mac OSX client app.
### Expected behaviour
After adding several "Folder Sync Connections" I should have those be organized alphabetically in the settings tab and on the top menu for the "Open folder ...".
### Actual behaviour
When adding several "Folder Sync Connections". Those are displayed in the order they were added but not alphabetically which is a bit of a burden. I have currently 8 folders and would love to have those ordered in an ascending manner.
### Steps to reproduce
1. Install the mac client app
2. Add a new server without specifying which folder
3. Then in the settings click on "Folder Sync Connection" and create several
4. You will see that those are not listed alphabetically
### Server configuration
Operating system:
OSX | design | folder sync connections please order alphabetically this is on the mac osx client app expected behaviour after adding several folder sync connections i should have those be organized alphabetically in the settings tab and on the top menu for the open folder actual behaviour when adding several folder sync connections those are displayed in the order they were added but not alphabetically which is a bit of a burden i have currently folders and would love to have those ordered in an ascending manner steps to reproduce install the mac client app add a new server without specifying which folder then in the settings click on folder sync connection and create several you will see that those are not listed alphabetically server configuration operating system osx | 1 |
17,528 | 6,469,634,855 | IssuesEvent | 2017-08-17 06:43:26 | gimli-org/gimli | https://api.github.com/repos/gimli-org/gimli | closed | Binary Installers for Windows | building and distribution | I guess typical Windows users (who use an IDE like Spyder) will look for a Download button and should find this under Installation just before we explain how to build pyGIMLi (which is really not necessary).
We are testing Windows installers and consider what (e.g. Examples and Tutorials as Python files or Jupyter notebooks?, what else?) should be shipped.
After making the version 1.0 (C&G paper) installers for both Python 3.5 and 3.6 will be available and updated regularly. | 1.0 | Binary Installers for Windows - I guess typical Windows users (who use an IDE like Spyder) will look for a Download button and should find this under Installation just before we explain how to build pyGIMLi (which is really not necessary).
We are testing Windows installers and consider what (e.g. Examples and Tutorials as Python files or Jupyter notebooks?, what else?) should be shipped.
After making the version 1.0 (C&G paper) installers for both Python 3.5 and 3.6 will be available and updated regularly. | non_design | binary installers for windows i guess typical windows users who use an ide like spyder will look for a download button and should find this under installation just before we explain how to build pygimli which is really not necessary we are testing windows installers and consider what e g examples and tutorials as python files or jupyter notebooks what else should be shipped after making the version c g paper installers for both python and will be available and updated regularly | 0 |
171,729 | 27,169,434,508 | IssuesEvent | 2023-02-17 17:59:44 | USAJOBS/ATP-Support | https://api.github.com/repos/USAJOBS/ATP-Support | closed | ATP new user and login process - login.gov | Design ATP Epic | **Collecting all the issues for the new ATP login process.**
-----
Most recent diagram from Brody (2/15):
| 1.0 | ATP new user and login process - login.gov - **Collecting all the issues for the new ATP login process.**
-----
Most recent diagram from Brody (2/15):
| design | atp new user and login process login gov collecting all the issues for the new atp login process most recent diagram from brody | 1 |
178,285 | 29,582,405,165 | IssuesEvent | 2023-06-07 07:01:34 | TryGhost/Ghost | https://api.github.com/repos/TryGhost/Ghost | closed | Mobile keyboard doesn't appear in the same time with the search modal | bug design | ### Issue Summary
When you use the default search on the mobile device, the keyboard doesn't appear in the same time when appears search input. Only after click on the search input the keyboard appears.
<img src="https://github.com/TryGhost/Ghost/assets/42737958/4a4a1acf-57cb-4d00-8d56-2a3ea895344d.png" width=40% height=40%>
<img src="https://github.com/TryGhost/Ghost/assets/42737958/4d6588b9-55ba-4386-9d23-afa17f486b7d.png" width=40% height=40%>
### Steps to Reproduce
1. Click on the search button with data-ghost-search
2. The search modal with the input appears
3. Click on the input
4. The keyboard appears
### Ghost Version
5.40.1
### Node.js Version
18.16.0
### How did you install Ghost?
Ubuntu
### Database type
MySQL 8
### Browser & OS version
Chrome 113.0.5672.76 & Android 12
### Relevant log / error output
_No response_
### Code of Conduct
- [X] I agree to be friendly and polite to people in this repository | 1.0 | Mobile keyboard doesn't appear in the same time with the search modal - ### Issue Summary
When you use the default search on the mobile device, the keyboard doesn't appear in the same time when appears search input. Only after click on the search input the keyboard appears.
<img src="https://github.com/TryGhost/Ghost/assets/42737958/4a4a1acf-57cb-4d00-8d56-2a3ea895344d.png" width=40% height=40%>
<img src="https://github.com/TryGhost/Ghost/assets/42737958/4d6588b9-55ba-4386-9d23-afa17f486b7d.png" width=40% height=40%>
### Steps to Reproduce
1. Click on the search button with data-ghost-search
2. The search modal with the input appears
3. Click on the input
4. The keyboard appears
### Ghost Version
5.40.1
### Node.js Version
18.16.0
### How did you install Ghost?
Ubuntu
### Database type
MySQL 8
### Browser & OS version
Chrome 113.0.5672.76 & Android 12
### Relevant log / error output
_No response_
### Code of Conduct
- [X] I agree to be friendly and polite to people in this repository | design | mobile keyboard doesn t appear in the same time with the search modal issue summary when you use the default search on the mobile device the keyboard doesn t appear in the same time when appears search input only after click on the search input the keyboard appears steps to reproduce click on the search button with data ghost search the search modal with the input appears click on the input the keyboard appears ghost version node js version how did you install ghost ubuntu database type mysql browser os version chrome android relevant log error output no response code of conduct i agree to be friendly and polite to people in this repository | 1 |
103,940 | 13,002,320,775 | IssuesEvent | 2020-07-24 02:52:02 | Digi-Shirt/digi-shirt-app | https://api.github.com/repos/Digi-Shirt/digi-shirt-app | closed | Display profile pic in nav drawer when logged in. | design | Image should probably be a cool round avatar. | 1.0 | Display profile pic in nav drawer when logged in. - Image should probably be a cool round avatar. | design | display profile pic in nav drawer when logged in image should probably be a cool round avatar | 1 |
135,910 | 19,682,020,762 | IssuesEvent | 2022-01-11 17:41:42 | vector-im/element-ios | https://api.github.com/repos/vector-im/element-ios | opened | Update Files component | T-Enhancement X-Needs-Design A-Message-Bubbles | ### Your use case
Update the "File" message type component to be the same as Web.
This issue is related to the Android issue: https://github.com/vector-im/element-android/issues/4897
| Files today | Web today |
|----|----|
|  | <img width="292" alt="Screenshot 2022-01-10 at 18 21 42" src="https://user-images.githubusercontent.com/89144281/148818495-d9edf8a6-4653-4636-a318-2946fd2134ca.png"> |
This was raised as part of the Bubbles work, and will be completed inside of the Bubbles project but should apply to all Appearance layouts
### Have you considered any alternatives?
_No response_
### Additional context
_No response_ | 1.0 | Update Files component - ### Your use case
Update the "File" message type component to be the same as Web.
This issue is related to the Android issue: https://github.com/vector-im/element-android/issues/4897
| Files today | Web today |
|----|----|
|  | <img width="292" alt="Screenshot 2022-01-10 at 18 21 42" src="https://user-images.githubusercontent.com/89144281/148818495-d9edf8a6-4653-4636-a318-2946fd2134ca.png"> |
This was raised as part of the Bubbles work, and will be completed inside of the Bubbles project but should apply to all Appearance layouts
### Have you considered any alternatives?
_No response_
### Additional context
_No response_ | design | update files component your use case update the file message type component to be the same as web this issue is related to the android issue files today web today img width alt screenshot at src this was raised as part of the bubbles work and will be completed inside of the bubbles project but should apply to all appearance layouts have you considered any alternatives no response additional context no response | 1 |
2,078 | 2,587,315,592 | IssuesEvent | 2015-02-17 17:40:59 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | opened | Interactive Design Meeting Notes - 2/13/15 | Area-Design Notes Area-Interactive Design Interactive-REPL | Interactive Design Meeting Notes - 2/13/15
==========================================
Definitions
-------------
- **REPL:** a read-eval-print-loop is a tool that allows developers to execute code snippets in a user-supplied context
- **Scripting:** a light-weight solution for writing simple and small programs. Includes an API for users to execute scripts in host-supplied applications
- **Interactive Window:** the Visual Studio component that will host the interactive modes of languages
- **Design-time**, also referred to as "standalone," includes scenarios that are not attached to a debugger process
- **Debug-time**, also referred to as the "immediate window," includes scenarios that are attached to a debugger process
Design Team
-------------
The following individuals are members of the dream team:
[Anthony D. Green](https://github.com/AnthonyDGreen)
[Chuck Stoner](https://github.com/CharlesStoner)
[Dustin Campbell](https://github.com/DustinCampbell)
[Kasey Uhlenhuth](https://github.com/kuhlenh)
[Kevin Halverson](https://github.com/KevinH-MS)
[Kevin Pilch-Bisson](https://github.com/Pilchie)
[Lincoln Atkinson](https://github.com/latkin)
[Manish Jayaswal](https://github.com/ManishJayaswal)
[Matt Warren](https://github.com/mattwar)
[Tomas Matousek](https://github.com/tmat)
*Special Guests:*
[Dino Viehland](https://github.com/dinov)
[Neal Gafter](https://github.com/gafter)
About the Design Process
------------------------
We meet for 2 hours a week to sketch final designs and experiences for Interactive. It is usually up to Kasey to determine the topic for discussion.
Meeting notes will be shared publicly on the dotnet/roslyn GitHub so that the community can respond and give input on our thoughts. Notes will be posted as *issues* thus allowing the community to comment on the thread. We will take comments into consideration for the next meeting.
Ultimately, the Interactive Design team is still in charge of the interactive intiative. This is not a democratic process; the team will make the final decisions. That said, we will look at UserVoice, comments on notes, and feature requests.
----------
Agenda: Interactive Window API Review
--------------------------------------
Quotes of the Day
> "Poli-check probably loves AbortExecution()"
> "Did I add value?"
We met with Dino from the Python Tools for Visual Studio team to review his changes to the Interactive Window API. With the API, language teams will only have to implement the evaluator for their interactive language in order to host their REPL in VS via the Interactive Window.
Follow along [here](https://github.com/dotnet/roslyn/tree/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor).
#### SUGGESTIONS
- **Rename "text" to "code" for consistency.** Some methods have names with "text" ([IInteractiveEvaluator.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveEvaluator.cs): <code> bool CanExecuteText(string text)</code>) and others have names with "code" ([IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs): <code>void InsertCode(string text)</code>). Use "code" only to be consistent in naming.
- **[IInteractiveEvaluator.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveEvaluator.cs): <code>bool CanExecuteText(string text)</code>**: Verify that this method does something special, otherwise remove it.
- **[IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>void Submit(IEnumerable<string> inputs)<code>:** Should this method be async?
- **[IInteractiveEvaluator.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveEvaluator.cs#L63) <code>void AbortCommand()</code>:** Verify that this method is necessary. We could just cancel the ExecuteCodeAsync Task to stop the code from running.
- **Both "Writes" should return spans:** [IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>Span WriteLine(string text = null)</code> and <code> int Write(string text)</code>
- **Rename Flush method to make it more intuitive:** [IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>void Flush()</code> to <code> void FlushOutput()</code>
- **[IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>string ReadStandardInput()</code>:** Make this method async. Also, any language that wants to support Standard Input will have to do extra work. Perhaps instead, we can modify this method so that it returns a Reader. This would also provide a means to support partial reading and more flexibility going forward.
- **[IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>bool IsResetting</code>:** Possibly rename to <code>bool IsInitializing</code>. Also, this method is transient. It can only be used on the UI Thread otherwise the return is invaluable. Add documentation that <code>bool IsResetting</code> and <code>bool IsRunning</code> can only be used on the UI Thread.
- **Rename [IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>void AddLogicalInput(string input)</code> to anything else**
- **Animation at prompt:** we thought about supporting the ability to have an animating prompt (for example to illustrate async methods running), but decided this wasn't a top priority.
| 2.0 | Interactive Design Meeting Notes - 2/13/15 - Interactive Design Meeting Notes - 2/13/15
==========================================
Definitions
-------------
- **REPL:** a read-eval-print-loop is a tool that allows developers to execute code snippets in a user-supplied context
- **Scripting:** a light-weight solution for writing simple and small programs. Includes an API for users to execute scripts in host-supplied applications
- **Interactive Window:** the Visual Studio component that will host the interactive modes of languages
- **Design-time**, also referred to as "standalone," includes scenarios that are not attached to a debugger process
- **Debug-time**, also referred to as the "immediate window," includes scenarios that are attached to a debugger process
Design Team
-------------
The following individuals are members of the dream team:
[Anthony D. Green](https://github.com/AnthonyDGreen)
[Chuck Stoner](https://github.com/CharlesStoner)
[Dustin Campbell](https://github.com/DustinCampbell)
[Kasey Uhlenhuth](https://github.com/kuhlenh)
[Kevin Halverson](https://github.com/KevinH-MS)
[Kevin Pilch-Bisson](https://github.com/Pilchie)
[Lincoln Atkinson](https://github.com/latkin)
[Manish Jayaswal](https://github.com/ManishJayaswal)
[Matt Warren](https://github.com/mattwar)
[Tomas Matousek](https://github.com/tmat)
*Special Guests:*
[Dino Viehland](https://github.com/dinov)
[Neal Gafter](https://github.com/gafter)
About the Design Process
------------------------
We meet for 2 hours a week to sketch final designs and experiences for Interactive. It is usually up to Kasey to determine the topic for discussion.
Meeting notes will be shared publicly on the dotnet/roslyn GitHub so that the community can respond and give input on our thoughts. Notes will be posted as *issues* thus allowing the community to comment on the thread. We will take comments into consideration for the next meeting.
Ultimately, the Interactive Design team is still in charge of the interactive intiative. This is not a democratic process; the team will make the final decisions. That said, we will look at UserVoice, comments on notes, and feature requests.
----------
Agenda: Interactive Window API Review
--------------------------------------
Quotes of the Day
> "Poli-check probably loves AbortExecution()"
> "Did I add value?"
We met with Dino from the Python Tools for Visual Studio team to review his changes to the Interactive Window API. With the API, language teams will only have to implement the evaluator for their interactive language in order to host their REPL in VS via the Interactive Window.
Follow along [here](https://github.com/dotnet/roslyn/tree/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor).
#### SUGGESTIONS
- **Rename "text" to "code" for consistency.** Some methods have names with "text" ([IInteractiveEvaluator.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveEvaluator.cs): <code> bool CanExecuteText(string text)</code>) and others have names with "code" ([IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs): <code>void InsertCode(string text)</code>). Use "code" only to be consistent in naming.
- **[IInteractiveEvaluator.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveEvaluator.cs): <code>bool CanExecuteText(string text)</code>**: Verify that this method does something special, otherwise remove it.
- **[IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>void Submit(IEnumerable<string> inputs)<code>:** Should this method be async?
- **[IInteractiveEvaluator.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveEvaluator.cs#L63) <code>void AbortCommand()</code>:** Verify that this method is necessary. We could just cancel the ExecuteCodeAsync Task to stop the code from running.
- **Both "Writes" should return spans:** [IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>Span WriteLine(string text = null)</code> and <code> int Write(string text)</code>
- **Rename Flush method to make it more intuitive:** [IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>void Flush()</code> to <code> void FlushOutput()</code>
- **[IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>string ReadStandardInput()</code>:** Make this method async. Also, any language that wants to support Standard Input will have to do extra work. Perhaps instead, we can modify this method so that it returns a Reader. This would also provide a means to support partial reading and more flexibility going forward.
- **[IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>bool IsResetting</code>:** Possibly rename to <code>bool IsInitializing</code>. Also, this method is transient. It can only be used on the UI Thread otherwise the return is invaluable. Add documentation that <code>bool IsResetting</code> and <code>bool IsRunning</code> can only be used on the UI Thread.
- **Rename [IInteractiveWindow.cs](https://github.com/dotnet/roslyn/blob/6f35e33694ac042a93195200bf0a317826c0388f/src/InteractiveWindow/Editor/IInteractiveWindow.cs) <code>void AddLogicalInput(string input)</code> to anything else**
- **Animation at prompt:** we thought about supporting the ability to have an animating prompt (for example to illustrate async methods running), but decided this wasn't a top priority.
| design | interactive design meeting notes interactive design meeting notes definitions repl a read eval print loop is a tool that allows developers to execute code snippets in a user supplied context scripting a light weight solution for writing simple and small programs includes an api for users to execute scripts in host supplied applications interactive window the visual studio component that will host the interactive modes of languages design time also referred to as standalone includes scenarios that are not attached to a debugger process debug time also referred to as the immediate window includes scenarios that are attached to a debugger process design team the following individuals are members of the dream team special guests about the design process we meet for hours a week to sketch final designs and experiences for interactive it is usually up to kasey to determine the topic for discussion meeting notes will be shared publicly on the dotnet roslyn github so that the community can respond and give input on our thoughts notes will be posted as issues thus allowing the community to comment on the thread we will take comments into consideration for the next meeting ultimately the interactive design team is still in charge of the interactive intiative this is not a democratic process the team will make the final decisions that said we will look at uservoice comments on notes and feature requests agenda interactive window api review quotes of the day poli check probably loves abortexecution did i add value we met with dino from the python tools for visual studio team to review his changes to the interactive window api with the api language teams will only have to implement the evaluator for their interactive language in order to host their repl in vs via the interactive window follow along suggestions rename text to code for consistency some methods have names with text bool canexecutetext string text and others have names with code void insertcode string text use code only to be consistent in naming bool canexecutetext string text verify that this method does something special otherwise remove it void submit ienumerable inputs should this method be async void abortcommand verify that this method is necessary we could just cancel the executecodeasync task to stop the code from running both writes should return spans span writeline string text null and int write string text rename flush method to make it more intuitive void flush to void flushoutput string readstandardinput make this method async also any language that wants to support standard input will have to do extra work perhaps instead we can modify this method so that it returns a reader this would also provide a means to support partial reading and more flexibility going forward bool isresetting possibly rename to bool isinitializing also this method is transient it can only be used on the ui thread otherwise the return is invaluable add documentation that bool isresetting and bool isrunning can only be used on the ui thread rename void addlogicalinput string input to anything else animation at prompt we thought about supporting the ability to have an animating prompt for example to illustrate async methods running but decided this wasn t a top priority | 1 |
126,458 | 17,034,417,774 | IssuesEvent | 2021-07-05 04:01:53 | MatrixAI/js-polykey | https://api.github.com/repos/MatrixAI/js-polykey | opened | Vault Tagging for Classification and Filtering/Sorting | design enhancement | Vault tagging is the ability to tag vaults to have a taxonomy/folksonomy of vaults.
This allows user to create classification levels of secrets which is useful for certain workflows: https://en.wikipedia.org/wiki/Classified_information
Users should be able create tags arbitrarily, and then assign these tags in a many-to-many relationship to vaults.
Then users can search for vaults with a specific tag or a set of tags.
When searching for a set of tags, the logic can be a conjunction of tags, or a disjunction of tags.
By default it should be a conjunction.
Previous issue: https://gitlab.com/MatrixAI/Engineering/Polykey/js-polykey/-/issues/159 | 1.0 | Vault Tagging for Classification and Filtering/Sorting - Vault tagging is the ability to tag vaults to have a taxonomy/folksonomy of vaults.
This allows user to create classification levels of secrets which is useful for certain workflows: https://en.wikipedia.org/wiki/Classified_information
Users should be able create tags arbitrarily, and then assign these tags in a many-to-many relationship to vaults.
Then users can search for vaults with a specific tag or a set of tags.
When searching for a set of tags, the logic can be a conjunction of tags, or a disjunction of tags.
By default it should be a conjunction.
Previous issue: https://gitlab.com/MatrixAI/Engineering/Polykey/js-polykey/-/issues/159 | design | vault tagging for classification and filtering sorting vault tagging is the ability to tag vaults to have a taxonomy folksonomy of vaults this allows user to create classification levels of secrets which is useful for certain workflows users should be able create tags arbitrarily and then assign these tags in a many to many relationship to vaults then users can search for vaults with a specific tag or a set of tags when searching for a set of tags the logic can be a conjunction of tags or a disjunction of tags by default it should be a conjunction previous issue | 1 |
391,829 | 11,579,132,786 | IssuesEvent | 2020-02-21 17:15:45 | ngageoint/hootenanny | https://api.github.com/repos/ngageoint/hootenanny | closed | Create test cases to help reduce DC streets reviews for things that should review | Category: Algorithms Priority: Medium Status: Defined Type: Task | Similar to #1328. There are several areas in the DC streets conflation that should have reviews, but they should return one review and no more. Some of the areas that should review are returning ten or more reviews for a small section of road. Create test cases for those areas and then create separate issues to fix the tests.
Probably best to finish out fixing the conflicts test cases through 31 before working this. Doing that first may render this OBE. | 1.0 | Create test cases to help reduce DC streets reviews for things that should review - Similar to #1328. There are several areas in the DC streets conflation that should have reviews, but they should return one review and no more. Some of the areas that should review are returning ten or more reviews for a small section of road. Create test cases for those areas and then create separate issues to fix the tests.
Probably best to finish out fixing the conflicts test cases through 31 before working this. Doing that first may render this OBE. | non_design | create test cases to help reduce dc streets reviews for things that should review similar to there are several areas in the dc streets conflation that should have reviews but they should return one review and no more some of the areas that should review are returning ten or more reviews for a small section of road create test cases for those areas and then create separate issues to fix the tests probably best to finish out fixing the conflicts test cases through before working this doing that first may render this obe | 0 |
50,688 | 6,426,132,769 | IssuesEvent | 2017-08-09 16:46:54 | phetsims/circuit-construction-kit-dc | https://api.github.com/repos/phetsims/circuit-construction-kit-dc | reopened | Keep value text centered over a component | design:general dev:enhancement status:ready-to-test | @samreid, I spoke with @arouinfar and we think it would be nice to have values always centered over their component. This should also support dynamic changes of value width, so going from 9.5 V to 10.0 V (an extra character is added here) should stay centered around the same point. Can we see how this would look? Hopefully there aren't too many design challenges with this.
For phetsims/QA/issues/33. | 1.0 | Keep value text centered over a component - @samreid, I spoke with @arouinfar and we think it would be nice to have values always centered over their component. This should also support dynamic changes of value width, so going from 9.5 V to 10.0 V (an extra character is added here) should stay centered around the same point. Can we see how this would look? Hopefully there aren't too many design challenges with this.
For phetsims/QA/issues/33. | design | keep value text centered over a component samreid i spoke with arouinfar and we think it would be nice to have values always centered over their component this should also support dynamic changes of value width so going from v to v an extra character is added here should stay centered around the same point can we see how this would look hopefully there aren t too many design challenges with this for phetsims qa issues | 1 |
1,693 | 2,659,877,474 | IssuesEvent | 2015-03-19 00:09:21 | brunobuzzi/OrbeonBridgeForGemStone | https://api.github.com/repos/brunobuzzi/OrbeonBridgeForGemStone | closed | Make all components send #answer: before calling other component | code improvement GUI | In order to close all rendered components make the component send "answer: true" before calling other component. This is to avoid unclosed component in the Web Server. | 1.0 | Make all components send #answer: before calling other component - In order to close all rendered components make the component send "answer: true" before calling other component. This is to avoid unclosed component in the Web Server. | non_design | make all components send answer before calling other component in order to close all rendered components make the component send answer true before calling other component this is to avoid unclosed component in the web server | 0 |
281,300 | 24,380,922,205 | IssuesEvent | 2022-10-04 07:45:38 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | opened | Choose other server in Profile 2 throws `Can't connect to server` error | QA/Yes QA/Test-Plan-Specified OS/Desktop feature/vpn | <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Choose other server in Profile 2 throws `Can't connect to server` error
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
Pre-requisites: Enable sku and vpn flags via brave://flags and purchase a vpn
1. Clean profile 1.45.x
2. Follow the prerequisites
3. Enable VPN on profile 1 (Confirmed VPN is cconnected to default/nearest server `Singapore`)
4. Create a profile 2 via hamburger menu
5. Ensure that VPN is connected in profile 2 (Confirmed VPN is connected to `Singapore`
6. In profile 2, click on VPN and choose another server
7. `Can't connect to server` error is shown
## Actual result:
<!--Please add screenshots if needed-->
Choose other server in Profile 2 throws `Can't connect to server` error
## Expected result:
Should not throw any error
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.45.78 Chromium: 106.0.5249.65 (Official Build) beta (64-bit)
-- | --
Revision | 3269dc3633cdd2ab94546fdbe54962e45b17a6e0-refs/branch-heads/5249@{#580}
OS | Windows 10 Version 21H2 (Build 19044.2006)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/qa-team @bsclifton @spylogsster @mattmcalister | 1.0 | Choose other server in Profile 2 throws `Can't connect to server` error - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Choose other server in Profile 2 throws `Can't connect to server` error
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
Pre-requisites: Enable sku and vpn flags via brave://flags and purchase a vpn
1. Clean profile 1.45.x
2. Follow the prerequisites
3. Enable VPN on profile 1 (Confirmed VPN is cconnected to default/nearest server `Singapore`)
4. Create a profile 2 via hamburger menu
5. Ensure that VPN is connected in profile 2 (Confirmed VPN is connected to `Singapore`
6. In profile 2, click on VPN and choose another server
7. `Can't connect to server` error is shown
## Actual result:
<!--Please add screenshots if needed-->
Choose other server in Profile 2 throws `Can't connect to server` error
## Expected result:
Should not throw any error
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.45.78 Chromium: 106.0.5249.65 (Official Build) beta (64-bit)
-- | --
Revision | 3269dc3633cdd2ab94546fdbe54962e45b17a6e0-refs/branch-heads/5249@{#580}
OS | Windows 10 Version 21H2 (Build 19044.2006)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/qa-team @bsclifton @spylogsster @mattmcalister | non_design | choose other server in profile throws can t connect to server error have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description choose other server in profile throws can t connect to server error steps to reproduce pre requisites enable sku and vpn flags via brave flags and purchase a vpn clean profile x follow the prerequisites enable vpn on profile confirmed vpn is cconnected to default nearest server singapore create a profile via hamburger menu ensure that vpn is connected in profile confirmed vpn is connected to singapore in profile click on vpn and choose another server can t connect to server error is shown actual result choose other server in profile throws can t connect to server error expected result should not throw any error reproduces how often easy brave version brave version info brave chromium official build beta bit revision refs branch heads os windows version build version channel information can you reproduce this issue with the current release na can you reproduce this issue with the beta channel yes can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields na does the issue resolve itself when disabling brave rewards na is the issue reproducible on the latest version of chrome na miscellaneous information cc brave qa team bsclifton spylogsster mattmcalister | 0 |
870 | 11,201,344,757 | IssuesEvent | 2020-01-04 02:30:29 | SynBioHub/synbiohub | https://api.github.com/repos/SynBioHub/synbiohub | closed | Errors not reported in status code | reliability | In some places, errors are caught without sending an appropriate error code. If it sent a code, the test suite would be able to catch more errors. | True | Errors not reported in status code - In some places, errors are caught without sending an appropriate error code. If it sent a code, the test suite would be able to catch more errors. | non_design | errors not reported in status code in some places errors are caught without sending an appropriate error code if it sent a code the test suite would be able to catch more errors | 0 |
180,177 | 30,456,414,878 | IssuesEvent | 2023-07-16 23:37:44 | TheOdinProject/theodinproject | https://api.github.com/repos/TheOdinProject/theodinproject | closed | Acessibility improvements | Status: On Hold Type: Design Status: Stale Type: Accessibility Type: CSS | Lighthouse points to those improvements on several pages of the site:
- [ ] Background and foreground colors do not have a sufficient contrast ratio.
- [x] Image elements do not have [alt] attributes.
- [ ] Links do not have a discernible name.
- [ ] [aria-hidden="true"] elements contain focusable descendants.
- [ ] Lists do not contain only `<li>` elements and script supporting elements (`<script> `and `<template>`).
| 1.0 | Acessibility improvements - Lighthouse points to those improvements on several pages of the site:
- [ ] Background and foreground colors do not have a sufficient contrast ratio.
- [x] Image elements do not have [alt] attributes.
- [ ] Links do not have a discernible name.
- [ ] [aria-hidden="true"] elements contain focusable descendants.
- [ ] Lists do not contain only `<li>` elements and script supporting elements (`<script> `and `<template>`).
| design | acessibility improvements lighthouse points to those improvements on several pages of the site background and foreground colors do not have a sufficient contrast ratio image elements do not have attributes links do not have a discernible name elements contain focusable descendants lists do not contain only elements and script supporting elements and | 1 |
107,392 | 13,456,475,658 | IssuesEvent | 2020-09-09 07:54:15 | litmuschaos/litmus | https://api.github.com/repos/litmuschaos/litmus | closed | Add Basic Authorization for GQL Operations | area/litmus-portal state/design-complete state/dev-complete state/docs-skip | - Create Middleware to validate JWT token
- Integrate Authorization with User Specific Operations | 1.0 | Add Basic Authorization for GQL Operations - - Create Middleware to validate JWT token
- Integrate Authorization with User Specific Operations | design | add basic authorization for gql operations create middleware to validate jwt token integrate authorization with user specific operations | 1 |
1,275 | 2,536,887,811 | IssuesEvent | 2015-01-26 16:56:07 | podiobooks/podiobooks | https://api.github.com/repos/podiobooks/podiobooks | opened | Search Box Styling | Design | Looks like Google changed the CSS and/or markup delivered with the search box... needs to be restyled.
| 1.0 | Search Box Styling - Looks like Google changed the CSS and/or markup delivered with the search box... needs to be restyled.
| design | search box styling looks like google changed the css and or markup delivered with the search box needs to be restyled | 1 |
189,350 | 6,796,860,391 | IssuesEvent | 2017-11-01 20:31:33 | xcodeswift/xclint | https://api.github.com/repos/xcodeswift/xclint | opened | Add CocoaPods support | difficulty:easy priority:medium status:ready-development type:feature | ## Context 🕵️♀️
Support installing the tool with CocoaPods. Other tools like SwiftLint supports CocoaPods, https://github.com/realm/SwiftLint/blob/master/SwiftLint.podspec
## What 🌱
The binary gets installed by CocoaPods and developers can easily use the binary from a project build phase.
## Proposal 🎉
Add a `.podspec` and update the release process to generate the CocoaPods binary.
| 1.0 | Add CocoaPods support - ## Context 🕵️♀️
Support installing the tool with CocoaPods. Other tools like SwiftLint supports CocoaPods, https://github.com/realm/SwiftLint/blob/master/SwiftLint.podspec
## What 🌱
The binary gets installed by CocoaPods and developers can easily use the binary from a project build phase.
## Proposal 🎉
Add a `.podspec` and update the release process to generate the CocoaPods binary.
| non_design | add cocoapods support context 🕵️♀️ support installing the tool with cocoapods other tools like swiftlint supports cocoapods what 🌱 the binary gets installed by cocoapods and developers can easily use the binary from a project build phase proposal 🎉 add a podspec and update the release process to generate the cocoapods binary | 0 |
145,313 | 22,640,564,378 | IssuesEvent | 2022-07-01 01:15:48 | urbit/developers.urbit.org | https://api.github.com/repos/urbit/developers.urbit.org | closed | additional guides are not listed on landing page | design | on https://developers.urbit.org/guides there's no additional guides button/card/whatever so you have to open another guide & then click additional guides in the sidebar. There should be a list of the additional guides at the bottom of the landing page | 1.0 | additional guides are not listed on landing page - on https://developers.urbit.org/guides there's no additional guides button/card/whatever so you have to open another guide & then click additional guides in the sidebar. There should be a list of the additional guides at the bottom of the landing page | design | additional guides are not listed on landing page on there s no additional guides button card whatever so you have to open another guide then click additional guides in the sidebar there should be a list of the additional guides at the bottom of the landing page | 1 |
163,709 | 25,861,762,772 | IssuesEvent | 2022-12-13 17:27:28 | decidim/decidim | https://api.github.com/repos/decidim/decidim | opened | Redesign: Scopes, categories and filters | contract: redesign | We would like to point out that the usability of the filters is confusing, largely due to the use of icons instead of radio buttons or checkboxes. Futhermore, the introduction of all these icons brings up more complexity, specially in the case of big implementations where a lot of categories are used.
- [ ] Implement radio buttons and checkboxes instead of icons
- [ ] The "All" selector remains selected after I unselect one category.
| 1.0 | Redesign: Scopes, categories and filters - We would like to point out that the usability of the filters is confusing, largely due to the use of icons instead of radio buttons or checkboxes. Futhermore, the introduction of all these icons brings up more complexity, specially in the case of big implementations where a lot of categories are used.
- [ ] Implement radio buttons and checkboxes instead of icons
- [ ] The "All" selector remains selected after I unselect one category.
| design | redesign scopes categories and filters we would like to point out that the usability of the filters is confusing largely due to the use of icons instead of radio buttons or checkboxes futhermore the introduction of all these icons brings up more complexity specially in the case of big implementations where a lot of categories are used implement radio buttons and checkboxes instead of icons the all selector remains selected after i unselect one category | 1 |
28,978 | 4,460,796,631 | IssuesEvent | 2016-08-24 01:24:20 | czlee/tabbycat | https://api.github.com/repos/czlee/tabbycat | closed | Fix travis view tests | bug in progress tests | The tests that resolve views now throw errors on travis as the static file serving can't locate particular files. I've tried using `.travis.yml` to emulate the normal asset compilation state with out any luck; maybe the travis VM doesn't resolve its filesystem as normal. Options/ideas:
- Add some sort of travis-specific configuration that reverts to django's default asset compilation pipeline
- Rewrite view tests to suppress asset compilation errors (difficult as they are ValueError)
- Rewrite view tests to check the template variables that set the JSON files rather than the template's resolution
- Remove the view tests as they haven't actually been that useful | 1.0 | Fix travis view tests - The tests that resolve views now throw errors on travis as the static file serving can't locate particular files. I've tried using `.travis.yml` to emulate the normal asset compilation state with out any luck; maybe the travis VM doesn't resolve its filesystem as normal. Options/ideas:
- Add some sort of travis-specific configuration that reverts to django's default asset compilation pipeline
- Rewrite view tests to suppress asset compilation errors (difficult as they are ValueError)
- Rewrite view tests to check the template variables that set the JSON files rather than the template's resolution
- Remove the view tests as they haven't actually been that useful | non_design | fix travis view tests the tests that resolve views now throw errors on travis as the static file serving can t locate particular files i ve tried using travis yml to emulate the normal asset compilation state with out any luck maybe the travis vm doesn t resolve its filesystem as normal options ideas add some sort of travis specific configuration that reverts to django s default asset compilation pipeline rewrite view tests to suppress asset compilation errors difficult as they are valueerror rewrite view tests to check the template variables that set the json files rather than the template s resolution remove the view tests as they haven t actually been that useful | 0 |
22,985 | 3,812,953,111 | IssuesEvent | 2016-03-27 23:37:53 | pkulchenko/ZeroBraneStudio | https://api.github.com/repos/pkulchenko/ZeroBraneStudio | reopened | Replace with regular expression doesn't replace on the first attempt | By design | Example:
Replace in regular, from `{a,b,c,d}` with pattern `(\w)` replace to `[\1] = true`.
Expect result is `{[a] = true, ..}`.
Actual result, just work like search, will select each matched char and next, but won't replace any. | 1.0 | Replace with regular expression doesn't replace on the first attempt - Example:
Replace in regular, from `{a,b,c,d}` with pattern `(\w)` replace to `[\1] = true`.
Expect result is `{[a] = true, ..}`.
Actual result, just work like search, will select each matched char and next, but won't replace any. | design | replace with regular expression doesn t replace on the first attempt example replace in regular from a b c d with pattern w replace to true expect result is true actual result just work like search will select each matched char and next but won t replace any | 1 |
182,075 | 30,790,554,882 | IssuesEvent | 2023-07-31 15:52:36 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | Include discussion settings / detail for pages in site editor | [Type] Enhancement Needs Design Feedback [Feature] Site Editor | In the _post editor_ Inspector it's possible to enable/disable discussion (comments) on a per-page basis:
<img width="1206" alt="Screenshot 2023-07-31 at 16 35 45" src="https://github.com/WordPress/gutenberg/assets/846565/80d6cbad-fad7-45dd-9260-22d1e858e113">
This feature is altogether missing in the _site editor_.
### Details panel
<img width="1069" alt="Screenshot 2023-07-31 at 16 39 04" src="https://github.com/WordPress/gutenberg/assets/846565/89140ff8-5b9d-4f97-ac9a-9f703d228636">
The list of details here can easily accommodate a row about discussion. The label / value are initial suggestions.
### Inspector
<img width="1069" alt="Screenshot 2023-07-31 at 16 51 34" src="https://github.com/WordPress/gutenberg/assets/846565/a02b2b0d-0374-45db-b1cc-714ef8010f1e">
Initially we can mimic the same panel from the post editor Inspector. | 1.0 | Include discussion settings / detail for pages in site editor - In the _post editor_ Inspector it's possible to enable/disable discussion (comments) on a per-page basis:
<img width="1206" alt="Screenshot 2023-07-31 at 16 35 45" src="https://github.com/WordPress/gutenberg/assets/846565/80d6cbad-fad7-45dd-9260-22d1e858e113">
This feature is altogether missing in the _site editor_.
### Details panel
<img width="1069" alt="Screenshot 2023-07-31 at 16 39 04" src="https://github.com/WordPress/gutenberg/assets/846565/89140ff8-5b9d-4f97-ac9a-9f703d228636">
The list of details here can easily accommodate a row about discussion. The label / value are initial suggestions.
### Inspector
<img width="1069" alt="Screenshot 2023-07-31 at 16 51 34" src="https://github.com/WordPress/gutenberg/assets/846565/a02b2b0d-0374-45db-b1cc-714ef8010f1e">
Initially we can mimic the same panel from the post editor Inspector. | design | include discussion settings detail for pages in site editor in the post editor inspector it s possible to enable disable discussion comments on a per page basis img width alt screenshot at src this feature is altogether missing in the site editor details panel img width alt screenshot at src the list of details here can easily accommodate a row about discussion the label value are initial suggestions inspector img width alt screenshot at src initially we can mimic the same panel from the post editor inspector | 1 |
131,284 | 18,265,254,201 | IssuesEvent | 2021-10-04 07:41:15 | Facepunch/sbox-issues | https://api.github.com/repos/Facepunch/sbox-issues | opened | VFX shader struct includes should not have header guards | api design | **What it is**
Currently `pixelinput.hlsl` & `vertexinput.hlsl` have include guards. This prohibits reusing the includes when you're wanting to pass the same data to other shader stages, example: Vertex -> Geometry -> Pixel where vertex and geometry share the same data.
**What it should be**
```hlsl
#ifndef COMMON_VERTEXINPUT_H
#define COMMON_VERTEXINPUT_H
// ...
#endif
```
should be omitted so it's possible to do:
```hlsl
struct VertexInput
{
#include "common/vertexinput.hlsl"
};
struct HullInput
{
#include "common/vertexinput.hlsl"
};
struct HullOutput
{
#include "common/vertexinput.hlsl"
};
```
| 1.0 | VFX shader struct includes should not have header guards - **What it is**
Currently `pixelinput.hlsl` & `vertexinput.hlsl` have include guards. This prohibits reusing the includes when you're wanting to pass the same data to other shader stages, example: Vertex -> Geometry -> Pixel where vertex and geometry share the same data.
**What it should be**
```hlsl
#ifndef COMMON_VERTEXINPUT_H
#define COMMON_VERTEXINPUT_H
// ...
#endif
```
should be omitted so it's possible to do:
```hlsl
struct VertexInput
{
#include "common/vertexinput.hlsl"
};
struct HullInput
{
#include "common/vertexinput.hlsl"
};
struct HullOutput
{
#include "common/vertexinput.hlsl"
};
```
| design | vfx shader struct includes should not have header guards what it is currently pixelinput hlsl vertexinput hlsl have include guards this prohibits reusing the includes when you re wanting to pass the same data to other shader stages example vertex geometry pixel where vertex and geometry share the same data what it should be hlsl ifndef common vertexinput h define common vertexinput h endif should be omitted so it s possible to do hlsl struct vertexinput include common vertexinput hlsl struct hullinput include common vertexinput hlsl struct hulloutput include common vertexinput hlsl | 1 |
75,920 | 14,536,500,733 | IssuesEvent | 2020-12-15 07:44:22 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | [Feature Request] Rename "signal_store" input of memory component to "set_write" | Code Feature request | The `signal_store` input on the memory component is often confusing to new players as it does not actually store the signal. Instead, the `signal_in` stores received signals while `signal_store` works more like a write enable, working as a set state input that allows new signals to be stored if true.
Renaming the pin to `set_write` (or alternatively `enable_write` ) may clear up that confusion. | 1.0 | [Feature Request] Rename "signal_store" input of memory component to "set_write" - The `signal_store` input on the memory component is often confusing to new players as it does not actually store the signal. Instead, the `signal_in` stores received signals while `signal_store` works more like a write enable, working as a set state input that allows new signals to be stored if true.
Renaming the pin to `set_write` (or alternatively `enable_write` ) may clear up that confusion. | non_design | rename signal store input of memory component to set write the signal store input on the memory component is often confusing to new players as it does not actually store the signal instead the signal in stores received signals while signal store works more like a write enable working as a set state input that allows new signals to be stored if true renaming the pin to set write or alternatively enable write may clear up that confusion | 0 |
218,685 | 24,390,735,348 | IssuesEvent | 2022-10-04 15:02:39 | MidnightBSD/midnightbsd-app-store | https://api.github.com/repos/MidnightBSD/midnightbsd-app-store | closed | CVE-2022-40150 (High) detected in jettison-1.4.0.jar - autoclosed | security vulnerability | ## CVE-2022-40150 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jettison-1.4.0.jar</b></p></summary>
<p>A StAX implementation for JSON.</p>
<p>Library home page: <a href="https://github.com/jettison-json/jettison">https://github.com/jettison-json/jettison</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/codehaus/jettison/jettison/1.4.0/jettison-1.4.0.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-starter-netflix-eureka-client-3.0.5.jar (Root Library)
- eureka-client-1.10.17.jar
- :x: **jettison-1.4.0.jar** (Vulnerable Library)
<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>
Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by Out of memory. This effect may support a denial of service attack.
<p>Publish Date: 2022-09-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-40150>CVE-2022-40150</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-40150 (High) detected in jettison-1.4.0.jar - autoclosed - ## CVE-2022-40150 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jettison-1.4.0.jar</b></p></summary>
<p>A StAX implementation for JSON.</p>
<p>Library home page: <a href="https://github.com/jettison-json/jettison">https://github.com/jettison-json/jettison</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/codehaus/jettison/jettison/1.4.0/jettison-1.4.0.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-starter-netflix-eureka-client-3.0.5.jar (Root Library)
- eureka-client-1.10.17.jar
- :x: **jettison-1.4.0.jar** (Vulnerable Library)
<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>
Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by Out of memory. This effect may support a denial of service attack.
<p>Publish Date: 2022-09-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-40150>CVE-2022-40150</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in jettison jar autoclosed cve high severity vulnerability vulnerable library jettison jar a stax implementation for json library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org codehaus jettison jettison jettison jar dependency hierarchy spring cloud starter netflix eureka client jar root library eureka client jar x jettison jar vulnerable library found in base branch master vulnerability details those using jettison to parse untrusted xml or json data may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by out of memory this effect may support a denial of service attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with mend | 0 |
241,378 | 26,256,763,662 | IssuesEvent | 2023-01-06 01:55:39 | szb512/cypress | https://api.github.com/repos/szb512/cypress | opened | CVE-2021-23368 (Medium) detected in postcss-7.0.16.tgz | security vulnerability | ## CVE-2021-23368 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-7.0.16.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.16.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.16.tgz</a></p>
<p>Path to dependency file: /cypress/packages/runner/package.json</p>
<p>Path to vulnerable library: /packages/server/node_modules/postcss/package.json,/packages/server/node_modules/postcss/package.json,/packages/server/node_modules/postcss/package.json,/packages/server/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- dependency-tree-6.5.0.tgz (Root Library)
- precinct-5.3.1.tgz
- detective-postcss-3.0.1.tgz
- :x: **postcss-7.0.16.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/szb512/cypress/commit/29dcad339d37f2169e5a640bf8d0d1438f7c18c2">29dcad339d37f2169e5a640bf8d0d1438f7c18c2</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss from 7.0.0 and before 8.2.10 are vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
<p>Publish Date: 2021-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23368>CVE-2021-23368</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23368">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23368</a></p>
<p>Release Date: 2021-04-12</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (dependency-tree): 7.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23368 (Medium) detected in postcss-7.0.16.tgz - ## CVE-2021-23368 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-7.0.16.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.16.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.16.tgz</a></p>
<p>Path to dependency file: /cypress/packages/runner/package.json</p>
<p>Path to vulnerable library: /packages/server/node_modules/postcss/package.json,/packages/server/node_modules/postcss/package.json,/packages/server/node_modules/postcss/package.json,/packages/server/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- dependency-tree-6.5.0.tgz (Root Library)
- precinct-5.3.1.tgz
- detective-postcss-3.0.1.tgz
- :x: **postcss-7.0.16.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/szb512/cypress/commit/29dcad339d37f2169e5a640bf8d0d1438f7c18c2">29dcad339d37f2169e5a640bf8d0d1438f7c18c2</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss from 7.0.0 and before 8.2.10 are vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
<p>Publish Date: 2021-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23368>CVE-2021-23368</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23368">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23368</a></p>
<p>Release Date: 2021-04-12</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (dependency-tree): 7.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in postcss tgz cve medium severity vulnerability vulnerable library postcss tgz tool for transforming styles with js plugins library home page a href path to dependency file cypress packages runner package json path to vulnerable library packages server node modules postcss package json packages server node modules postcss package json packages server node modules postcss package json packages server node modules postcss package json dependency hierarchy dependency tree tgz root library precinct tgz detective postcss tgz x postcss tgz vulnerable library found in head commit a href vulnerability details the package postcss from and before are vulnerable to regular expression denial of service redos during source map parsing publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution postcss direct dependency fix resolution dependency tree step up your open source security game with mend | 0 |
143,459 | 19,180,301,534 | IssuesEvent | 2021-12-04 09:04:35 | AlexRogalskiy/scala-patterns | https://api.github.com/repos/AlexRogalskiy/scala-patterns | opened | CVE-2021-3795 (High) detected in semver-regex-1.0.0.tgz | security vulnerability | ## CVE-2021-3795 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>semver-regex-1.0.0.tgz</b></p></summary>
<p>Regular expression for matching semver versions</p>
<p>Library home page: <a href="https://registry.npmjs.org/semver-regex/-/semver-regex-1.0.0.tgz">https://registry.npmjs.org/semver-regex/-/semver-regex-1.0.0.tgz</a></p>
<p>Path to dependency file: scala-patterns/package.json</p>
<p>Path to vulnerable library: scala-patterns/node_modules/semver-regex/package.json</p>
<p>
Dependency Hierarchy:
- validate-commit-msg-2.14.0.tgz (Root Library)
- :x: **semver-regex-1.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/scala-patterns/commit/42d5f437e3ee9b0e01479139309cf5f8950c7074">42d5f437e3ee9b0e01479139309cf5f8950c7074</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>
semver-regex is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3795>CVE-2021-3795</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sindresorhus/semver-regex/releases/tag/v4.0.1">https://github.com/sindresorhus/semver-regex/releases/tag/v4.0.1</a></p>
<p>Release Date: 2021-09-15</p>
<p>Fix Resolution: semver-regex - 3.1.3,4.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-3795 (High) detected in semver-regex-1.0.0.tgz - ## CVE-2021-3795 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>semver-regex-1.0.0.tgz</b></p></summary>
<p>Regular expression for matching semver versions</p>
<p>Library home page: <a href="https://registry.npmjs.org/semver-regex/-/semver-regex-1.0.0.tgz">https://registry.npmjs.org/semver-regex/-/semver-regex-1.0.0.tgz</a></p>
<p>Path to dependency file: scala-patterns/package.json</p>
<p>Path to vulnerable library: scala-patterns/node_modules/semver-regex/package.json</p>
<p>
Dependency Hierarchy:
- validate-commit-msg-2.14.0.tgz (Root Library)
- :x: **semver-regex-1.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/scala-patterns/commit/42d5f437e3ee9b0e01479139309cf5f8950c7074">42d5f437e3ee9b0e01479139309cf5f8950c7074</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>
semver-regex is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3795>CVE-2021-3795</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sindresorhus/semver-regex/releases/tag/v4.0.1">https://github.com/sindresorhus/semver-regex/releases/tag/v4.0.1</a></p>
<p>Release Date: 2021-09-15</p>
<p>Fix Resolution: semver-regex - 3.1.3,4.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in semver regex tgz cve high severity vulnerability vulnerable library semver regex tgz regular expression for matching semver versions library home page a href path to dependency file scala patterns package json path to vulnerable library scala patterns node modules semver regex package json dependency hierarchy validate commit msg tgz root library x semver regex tgz vulnerable library found in head commit a href found in base branch master vulnerability details semver regex is vulnerable to inefficient regular expression complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution semver regex step up your open source security game with whitesource | 0 |
61,094 | 7,439,127,269 | IssuesEvent | 2018-03-27 04:39:52 | python-trio/trio | https://api.github.com/repos/python-trio/trio | opened | Should we expose RunVars directly? | design discussion potential API breaker | This is a pretty low-priority issue, but something to think about before 1.0 anyway:
Once #478 is merged, we'll have a few `RunVar` objects used directly in trio itself: the default thread limiter exposed via `trio.current_default_worker_thread_limiter`, and the hostname resolver and socket factory test hooks exposed via `trio.socket.set_custom_hostname_resolver` and `trio.socket.set_custom_socket_factory`.
For the last two in particular, the public functions are basically the simplest possible set/get APIs; they exist solely to hide the clunky old `RunLocal` API. Now we have `RunVar`, which is ... basically the same thing, a more usable API for setting/getting these kinds of variables. So maybe we should just... expose that? So e.g. `set_custom_hostname_resolver` would become `custom_hostname_resolver.set`?
The worker thread limiter is a little more subtle. Right now we don't expose any way to change the underlying default limiter object itself; you can adjust the number of simultaneous threads, by getting the object and mutating its `total_tokens` attribute, but you can't replace it wholesale with some other policy. Is there any use case for other policies? I guess you could make a C# thread pool style policy that admits threads after a delay that's proportional to the current pool size... probably anything fancy like this would be better handled by overriding the limiter for specific calls to `run_sync_in_worker_thread`, though. OTOH, exposing a `RunVar` isn't particularly problematic either. (I guess it would let you override the default with one that's just broken, but I don't think there is any particular danger here beyond any other sort of broken code.) | 1.0 | Should we expose RunVars directly? - This is a pretty low-priority issue, but something to think about before 1.0 anyway:
Once #478 is merged, we'll have a few `RunVar` objects used directly in trio itself: the default thread limiter exposed via `trio.current_default_worker_thread_limiter`, and the hostname resolver and socket factory test hooks exposed via `trio.socket.set_custom_hostname_resolver` and `trio.socket.set_custom_socket_factory`.
For the last two in particular, the public functions are basically the simplest possible set/get APIs; they exist solely to hide the clunky old `RunLocal` API. Now we have `RunVar`, which is ... basically the same thing, a more usable API for setting/getting these kinds of variables. So maybe we should just... expose that? So e.g. `set_custom_hostname_resolver` would become `custom_hostname_resolver.set`?
The worker thread limiter is a little more subtle. Right now we don't expose any way to change the underlying default limiter object itself; you can adjust the number of simultaneous threads, by getting the object and mutating its `total_tokens` attribute, but you can't replace it wholesale with some other policy. Is there any use case for other policies? I guess you could make a C# thread pool style policy that admits threads after a delay that's proportional to the current pool size... probably anything fancy like this would be better handled by overriding the limiter for specific calls to `run_sync_in_worker_thread`, though. OTOH, exposing a `RunVar` isn't particularly problematic either. (I guess it would let you override the default with one that's just broken, but I don't think there is any particular danger here beyond any other sort of broken code.) | design | should we expose runvars directly this is a pretty low priority issue but something to think about before anyway once is merged we ll have a few runvar objects used directly in trio itself the default thread limiter exposed via trio current default worker thread limiter and the hostname resolver and socket factory test hooks exposed via trio socket set custom hostname resolver and trio socket set custom socket factory for the last two in particular the public functions are basically the simplest possible set get apis they exist solely to hide the clunky old runlocal api now we have runvar which is basically the same thing a more usable api for setting getting these kinds of variables so maybe we should just expose that so e g set custom hostname resolver would become custom hostname resolver set the worker thread limiter is a little more subtle right now we don t expose any way to change the underlying default limiter object itself you can adjust the number of simultaneous threads by getting the object and mutating its total tokens attribute but you can t replace it wholesale with some other policy is there any use case for other policies i guess you could make a c thread pool style policy that admits threads after a delay that s proportional to the current pool size probably anything fancy like this would be better handled by overriding the limiter for specific calls to run sync in worker thread though otoh exposing a runvar isn t particularly problematic either i guess it would let you override the default with one that s just broken but i don t think there is any particular danger here beyond any other sort of broken code | 1 |
375,741 | 11,133,675,654 | IssuesEvent | 2019-12-20 09:56:06 | comses/comses.net | https://api.github.com/repos/comses/comses.net | closed | build_archive fails due to missing aip directory | bug high priority | the changes to the fs.py seem to have broken archive creation the first time around and are causing the archives to only contain a codemeta.json file. need to investigate the ordering of things:
https://sentry.comses.net/gbci/comsesnet/issues/38
| 1.0 | build_archive fails due to missing aip directory - the changes to the fs.py seem to have broken archive creation the first time around and are causing the archives to only contain a codemeta.json file. need to investigate the ordering of things:
https://sentry.comses.net/gbci/comsesnet/issues/38
| non_design | build archive fails due to missing aip directory the changes to the fs py seem to have broken archive creation the first time around and are causing the archives to only contain a codemeta json file need to investigate the ordering of things | 0 |
25,591 | 3,946,174,266 | IssuesEvent | 2016-04-28 02:25:21 | geetsisbac/YE7GLKCP77LP3XTRJGXDSBHN | https://api.github.com/repos/geetsisbac/YE7GLKCP77LP3XTRJGXDSBHN | closed | htjKT9nUmLxr7D5QNi9nM4tAZP2CBveDK4dGFpkCM3eVGrSsHXZK2XJKcMuylkyu49pqRaC15vnN2YOrdDRS66NRo7bLv+XT4bF+FczllB/Y+w1P1wIiEkjazMAE7BaQCDIbZndPGE7IJYP4v40hwK8lyRYOqlQBJTF9xPa5fdw= | design | d+/xSu2Im/FP5z6iRZnGuBTPws0p06MFq3gNku/Lg3vv1ygG08eyJwBc4SIUDxEQuuMaO2E3mMUyAe84VxB7lZBqR4ZH6iX6B38KVBaw84SFUr1f+cBpqTYWJFVcGu63yPcY0eEkeUC/0oPne7X1qakxjlmqk0aMYMupnMDNmi/mbOdslZ58tDV2gaQRuGBa0KFaadt9Opje5B6VJTU9u3ZHHH1VsSa+AOTSN9M9KVhazKN48Yo6iq128lL1jI9MUx9m+HaQQEJoNPlRjkmTe4vOcCO8Iy2STzIJcdVrpmSEtWkroOBy46LmlkBEuiobUfzwY7zADAEVWcf7DaFHshKBHLcm+Z8uTYiNX6BBCSlzI6YFE6geM9T2SYXE7gKH9cWQ69WKIT/gwL0c6awXcuaj2rfT5+p21+XwnpmoZRwRlDf3ykOczbDIruYv2hafZ5eIfEg58UgWrOkopTS6h+0tr1BoQPwip4QB4KtW9Ms8isQAxkIRxn3jEl4SLGeb2KksdTHIfDMqzJKeInKwFZSeSyayXLoEG0HbgtuNmeWbo1rYCUCiEfJkym5iayTS804kLZmcjvfPlfEOVViRJnraV28tAF9GMmj3oaL36xphC6xcguplbIcodX1pdtMg0k018KzKtXzMKUQUtGmkRPQdQw5zhsxf1V+7kD191lxPiM1tiu6QTp/GeRzE20JvOtRu6CmJ6u9DhjY36fS1UuP2zN4o3UBw4aCvFG2C62T0Q6zvuf4kCI+n/zBZjtmVpsaEAbnoI5booeb2dCDfVem6N0cu7wan9bLxIfFpODIeBziMyyZ8p0Ue6w41e+t3cjUM80Uj+SRgPv1VAi5eI2Le1O4+IflwGpHiSxc3SnJ7gWUKZfRyYBR1EJUYT7W3dTyG4eKnWjgw0ZbkFk3zYZh72upjQvTl1neXUg/bjnEG7Bn0256CJS3dXw1cJ4N8z1KKHHoOwLDCPtEeD0/jke+LmQde4tp9v9Psb+np3fnvKXNnlrHJfqfVWBm4jht7js7lftb7xIA0+fp3OcUfLAD4Yz2XVcMPzZYwpIv3rEZdQBPCvH6RNhOA5A/FSjNy08TvDOwIggPoWmpnvMJOQ/860MMHSPFzGXoKwTYINsXuco+MfK9A3qWHzGzQvwyPZ8/DsWjX7JGb334ZILTuufKxtlVMMjI+U7gmmj0xwMTKvWLCeMLFgC4837RF5AmRhlglV54nsGTE0gyX4Ea31MCCvOfGc7AHCFOiI6mkblRHRBsLo/8rEdLFq6Xq0IWyPKL8tdF7aowhJu2xF1o4AmmMOWDIhMqIEiArm1Hc+JSp9X5ta04cKmmJ512VyJDrORvkRX7nwc4MZG8p20Hc0cl5KE8f77Qpkl8V4bKQK1YcYkQG+lQDraziqIS+gTr7SGycScf9ZRahQA45TeBbi2a3ZLZ/YiGgc8gjdMF6AaZcTZ257zUr/vVqrrFFZurkk2kUpXnz/v9svFeCZB2ThCPIo0F3SwflKNgBYZYStwiN6IMxnVt61bZj4dcpwXKjfbRcfPunwJNN/g/TP9mhKny0Bi+PbmbNr7d/e/L6tsmzovZaf7w9g9ccdgJhai2lJzE0tjSZsNY8TjGulP+jr59F9XKeQEQT6JS3YyVGtTBSHvA2ZdWqz+2vcEOdeOi0lbxqMygiL0GhBfUIm+VeUUhengCQF+apmUQXl75Cb+uAJI9iIAqD14TH3JWhsMh3Kbw39/1IvGZPoaKqtQ2SkICnOHKuDzgI/jPo+W8tSGC2CZSOBI7G5xjTMD8273lmjtgp+v0bw02L6bqgqr3ikUhsnEnH/WUWoUAOOU3gW4uJVhL+0S2HG1GdS18A8KA2mH1MpXaFRKXZsqOOButHxvsYM9o3n8qxgYBQUH5VWs1lq0vPmF6AeHNmUHgDdtamMrgkaxQLuFtJgw+7LRPAOBmKsI/XzANaFfiaumbRbltkI9MVeO7JibSeNGGa1+LavQtALJukr4ftPg7wC9SjgyIfSk3jCEL+wfRVK3vH8m41fQwQffSsR+i0BlINHrSw2XMFugRxlVZC6R/luVuN9poKWrWlk8k3x4pw9T5TZwOUAyT/OjPiORCh8pR5rfFa5t1o4tFYOwIVNm6dkfck2cNJT/yboQVzUCTvS0uf+/QyBYvODWribLIq2nQ3FqULU9X9lt+tzfsVctHWk90zVjYP6V4ZJRbZoX2dJ+w2Qlnn/XtaxHWpthoMDBnF6U0G90nD42KwzgBqRWTWgUjk/uPc+d67OUu3vgYJoNB0ID7Jn2NQsoKg62NrRUFsNd/rF8tOFL4VjeT35hd5S8sHMQNSc7m2M56+odtHsR85s+eH1ByqTACFgJrUUKU8AnZMnvG+R18PAXjxZswY/dmHIQBvPvOeKNIE7SGTXmfhzelMBs1ONxNTVyzJMWIElxJgGY9MK6fcaKjzwsGhItqPbgXysEZSF00GX7/2ORDXjps0BwSzbQFTi+wn8mhn1OHrQnWUtwJQ2KXziUiG83tezFdkHc/Jfh30D+P9XDEJ9HydbERQsrVfVp25VD4VzoHJCy4oZLJz25FtOsXd1unVoV1LK0jDuvO5vdURq9UvNkW9pt/2bwCPX9C57plXIyO3nCUbxVf5pK9Bjzqdw2mE5R+faEfHtIzVmGlCEGn4aFJW2oX7CM/RJu2JilUxAFU78P91j2yojMtIlI+aanUW62pXLlO9YYEkFhJVxoDz54yozh4l76AkRlc5i0tinNqlyhDR3cGphugKALP4CLHB4lLqW4g89yXR5aKbIZZQ41hzhR1e3eP7J6vu4i3ihEmqAfYepmnN8nS6dxQ79UUUc5x/jHwe3cFaq0lhEXCc2EaJkzSeK8pQbh9nWWAUR/pdQJAl2LhSNVc/sZDTGiqDuLfPywlxE8aO6HZ/MgC6yw4557K2/BVm95fkcZIny1RzqU5Et1zanS/wjvP6qq5IGBoaYiuGfjv4xglFEOsdEa7gZTzH1feyrAchp6l4Qmk9If8rjzNo/rje9wYPANz+wjPU7ugkS4WUErclrqWRvSpr1k4bJtCYZOgTAkEOPToEQY6kr2Tw5+zWwWBvvvzUK/80QcgeAjpGeJEdUgHq/e8Bo4Hp6atEHqBvE/gHfRneRnqSx7bPY8hiYBlAVaO+RYWfWApymX3fu/Rjbvut2BY8FIeh7vt95tuseX9PV/YNYrb+xi3UdveGnJKBLlg16ZlaMGhxchxWepqQBhVd0upF7u+Kf4JKVW+Ft0rYmeF0gcokRGbzmTS8yPA9K7C3izpl2UfFSVaAcGyOkpIcjkWiJEO/Al7Wfsl0U8GJ7Dvtzc6f3cpkeRBlr0rhDf3GQ93510+MwCowErJKx4rr9wMJaDbMMZYxKJJR42T6btBLXggVwKrdJYpXJn2eN0CsePtD74E6Pk2U/BBiCKQgckT1Mybk/NTVHcc+SAZjIjy8XftZz7GwmYSe+tBcLf9J3vvXNRM+HS/9fi/trB8q9sRrCTUJXSIKzfUFWr1MsU5UZLdQD6jt2xZu8yzi/rkJhwfHoMG+9ITBwe4G5/69aFjkooA2/uK/e8tDEzejixs55zqwwCs4JCihHw6STLotoSJ23FdEREFmuNiMcBK2OMo/plxDnaYq6A167ewn5tdoJ3vyd2ch5iV3gc1Wr2DBz8qdlTO8ThpaGHrLvu0B13IKplJGURJv4xvemB+vnDL1eqHT0tUe0Wyze5jSw2MYqeZLc802Lc2YdwMHkaRFwCv20QGL4Z2l7aQq9fpfVRqKJFX0n4sDdNtgKaKTATru8mLA0q8oRy9/Fulh0oT2t/UklGh5uDmDWpj9HyXF6u53Rrg+/4ETU2GEx8Nx9//CG1OVTxsAxyjXGmxjsjPwHNPuTpHAxFC2qW0CxtwRz2RXSwy5vbR5ahO4DFTNQjw4oCH/K48zaP643vcGDwDc/sL6LC1pIru3Ku7k/qy/F7pGeAuXZaDdXKU4uyItC4zoOTMT52ndA4Oq1bB5UAGhCyjFSFzdZmEH6IbVqamegwzU5Xi/r0W2AQlm038+/sdfhW5Cf8amtXXiLA9nLdgvQ8S9cYHlKPNxNtrdrZB9biV2qMi3Lq+D1hKTjsWVadUXd1dWxeEGlwNfqCCJFKS9ioQ2j7haT1rCM9UNegT5Z1yaTi1g7yQb5dB/RwmgS98XITCq3BHZKPhzxA3Wusqxbx9uxgDmrfzhKeOZq2shQMQ0vK4TFh+nRNNncCxft4FGLjeuZeXSIi4HPpcy7Ah9bC2xGrHu1VZSClefq85miR+o0C2eMGAqHIOBgvRtw9xZL9n3m4SgwnfPuHIuZ8S6CSutZ592iTXo2Yp4FzRTWqD/X3nRclzIhIWrqCq0ag+26dUKiqpFz3YPelIaV72cSwxWOztn4uFYRUHPg1SRS66G | 1.0 | htjKT9nUmLxr7D5QNi9nM4tAZP2CBveDK4dGFpkCM3eVGrSsHXZK2XJKcMuylkyu49pqRaC15vnN2YOrdDRS66NRo7bLv+XT4bF+FczllB/Y+w1P1wIiEkjazMAE7BaQCDIbZndPGE7IJYP4v40hwK8lyRYOqlQBJTF9xPa5fdw= - d+/xSu2Im/FP5z6iRZnGuBTPws0p06MFq3gNku/Lg3vv1ygG08eyJwBc4SIUDxEQuuMaO2E3mMUyAe84VxB7lZBqR4ZH6iX6B38KVBaw84SFUr1f+cBpqTYWJFVcGu63yPcY0eEkeUC/0oPne7X1qakxjlmqk0aMYMupnMDNmi/mbOdslZ58tDV2gaQRuGBa0KFaadt9Opje5B6VJTU9u3ZHHH1VsSa+AOTSN9M9KVhazKN48Yo6iq128lL1jI9MUx9m+HaQQEJoNPlRjkmTe4vOcCO8Iy2STzIJcdVrpmSEtWkroOBy46LmlkBEuiobUfzwY7zADAEVWcf7DaFHshKBHLcm+Z8uTYiNX6BBCSlzI6YFE6geM9T2SYXE7gKH9cWQ69WKIT/gwL0c6awXcuaj2rfT5+p21+XwnpmoZRwRlDf3ykOczbDIruYv2hafZ5eIfEg58UgWrOkopTS6h+0tr1BoQPwip4QB4KtW9Ms8isQAxkIRxn3jEl4SLGeb2KksdTHIfDMqzJKeInKwFZSeSyayXLoEG0HbgtuNmeWbo1rYCUCiEfJkym5iayTS804kLZmcjvfPlfEOVViRJnraV28tAF9GMmj3oaL36xphC6xcguplbIcodX1pdtMg0k018KzKtXzMKUQUtGmkRPQdQw5zhsxf1V+7kD191lxPiM1tiu6QTp/GeRzE20JvOtRu6CmJ6u9DhjY36fS1UuP2zN4o3UBw4aCvFG2C62T0Q6zvuf4kCI+n/zBZjtmVpsaEAbnoI5booeb2dCDfVem6N0cu7wan9bLxIfFpODIeBziMyyZ8p0Ue6w41e+t3cjUM80Uj+SRgPv1VAi5eI2Le1O4+IflwGpHiSxc3SnJ7gWUKZfRyYBR1EJUYT7W3dTyG4eKnWjgw0ZbkFk3zYZh72upjQvTl1neXUg/bjnEG7Bn0256CJS3dXw1cJ4N8z1KKHHoOwLDCPtEeD0/jke+LmQde4tp9v9Psb+np3fnvKXNnlrHJfqfVWBm4jht7js7lftb7xIA0+fp3OcUfLAD4Yz2XVcMPzZYwpIv3rEZdQBPCvH6RNhOA5A/FSjNy08TvDOwIggPoWmpnvMJOQ/860MMHSPFzGXoKwTYINsXuco+MfK9A3qWHzGzQvwyPZ8/DsWjX7JGb334ZILTuufKxtlVMMjI+U7gmmj0xwMTKvWLCeMLFgC4837RF5AmRhlglV54nsGTE0gyX4Ea31MCCvOfGc7AHCFOiI6mkblRHRBsLo/8rEdLFq6Xq0IWyPKL8tdF7aowhJu2xF1o4AmmMOWDIhMqIEiArm1Hc+JSp9X5ta04cKmmJ512VyJDrORvkRX7nwc4MZG8p20Hc0cl5KE8f77Qpkl8V4bKQK1YcYkQG+lQDraziqIS+gTr7SGycScf9ZRahQA45TeBbi2a3ZLZ/YiGgc8gjdMF6AaZcTZ257zUr/vVqrrFFZurkk2kUpXnz/v9svFeCZB2ThCPIo0F3SwflKNgBYZYStwiN6IMxnVt61bZj4dcpwXKjfbRcfPunwJNN/g/TP9mhKny0Bi+PbmbNr7d/e/L6tsmzovZaf7w9g9ccdgJhai2lJzE0tjSZsNY8TjGulP+jr59F9XKeQEQT6JS3YyVGtTBSHvA2ZdWqz+2vcEOdeOi0lbxqMygiL0GhBfUIm+VeUUhengCQF+apmUQXl75Cb+uAJI9iIAqD14TH3JWhsMh3Kbw39/1IvGZPoaKqtQ2SkICnOHKuDzgI/jPo+W8tSGC2CZSOBI7G5xjTMD8273lmjtgp+v0bw02L6bqgqr3ikUhsnEnH/WUWoUAOOU3gW4uJVhL+0S2HG1GdS18A8KA2mH1MpXaFRKXZsqOOButHxvsYM9o3n8qxgYBQUH5VWs1lq0vPmF6AeHNmUHgDdtamMrgkaxQLuFtJgw+7LRPAOBmKsI/XzANaFfiaumbRbltkI9MVeO7JibSeNGGa1+LavQtALJukr4ftPg7wC9SjgyIfSk3jCEL+wfRVK3vH8m41fQwQffSsR+i0BlINHrSw2XMFugRxlVZC6R/luVuN9poKWrWlk8k3x4pw9T5TZwOUAyT/OjPiORCh8pR5rfFa5t1o4tFYOwIVNm6dkfck2cNJT/yboQVzUCTvS0uf+/QyBYvODWribLIq2nQ3FqULU9X9lt+tzfsVctHWk90zVjYP6V4ZJRbZoX2dJ+w2Qlnn/XtaxHWpthoMDBnF6U0G90nD42KwzgBqRWTWgUjk/uPc+d67OUu3vgYJoNB0ID7Jn2NQsoKg62NrRUFsNd/rF8tOFL4VjeT35hd5S8sHMQNSc7m2M56+odtHsR85s+eH1ByqTACFgJrUUKU8AnZMnvG+R18PAXjxZswY/dmHIQBvPvOeKNIE7SGTXmfhzelMBs1ONxNTVyzJMWIElxJgGY9MK6fcaKjzwsGhItqPbgXysEZSF00GX7/2ORDXjps0BwSzbQFTi+wn8mhn1OHrQnWUtwJQ2KXziUiG83tezFdkHc/Jfh30D+P9XDEJ9HydbERQsrVfVp25VD4VzoHJCy4oZLJz25FtOsXd1unVoV1LK0jDuvO5vdURq9UvNkW9pt/2bwCPX9C57plXIyO3nCUbxVf5pK9Bjzqdw2mE5R+faEfHtIzVmGlCEGn4aFJW2oX7CM/RJu2JilUxAFU78P91j2yojMtIlI+aanUW62pXLlO9YYEkFhJVxoDz54yozh4l76AkRlc5i0tinNqlyhDR3cGphugKALP4CLHB4lLqW4g89yXR5aKbIZZQ41hzhR1e3eP7J6vu4i3ihEmqAfYepmnN8nS6dxQ79UUUc5x/jHwe3cFaq0lhEXCc2EaJkzSeK8pQbh9nWWAUR/pdQJAl2LhSNVc/sZDTGiqDuLfPywlxE8aO6HZ/MgC6yw4557K2/BVm95fkcZIny1RzqU5Et1zanS/wjvP6qq5IGBoaYiuGfjv4xglFEOsdEa7gZTzH1feyrAchp6l4Qmk9If8rjzNo/rje9wYPANz+wjPU7ugkS4WUErclrqWRvSpr1k4bJtCYZOgTAkEOPToEQY6kr2Tw5+zWwWBvvvzUK/80QcgeAjpGeJEdUgHq/e8Bo4Hp6atEHqBvE/gHfRneRnqSx7bPY8hiYBlAVaO+RYWfWApymX3fu/Rjbvut2BY8FIeh7vt95tuseX9PV/YNYrb+xi3UdveGnJKBLlg16ZlaMGhxchxWepqQBhVd0upF7u+Kf4JKVW+Ft0rYmeF0gcokRGbzmTS8yPA9K7C3izpl2UfFSVaAcGyOkpIcjkWiJEO/Al7Wfsl0U8GJ7Dvtzc6f3cpkeRBlr0rhDf3GQ93510+MwCowErJKx4rr9wMJaDbMMZYxKJJR42T6btBLXggVwKrdJYpXJn2eN0CsePtD74E6Pk2U/BBiCKQgckT1Mybk/NTVHcc+SAZjIjy8XftZz7GwmYSe+tBcLf9J3vvXNRM+HS/9fi/trB8q9sRrCTUJXSIKzfUFWr1MsU5UZLdQD6jt2xZu8yzi/rkJhwfHoMG+9ITBwe4G5/69aFjkooA2/uK/e8tDEzejixs55zqwwCs4JCihHw6STLotoSJ23FdEREFmuNiMcBK2OMo/plxDnaYq6A167ewn5tdoJ3vyd2ch5iV3gc1Wr2DBz8qdlTO8ThpaGHrLvu0B13IKplJGURJv4xvemB+vnDL1eqHT0tUe0Wyze5jSw2MYqeZLc802Lc2YdwMHkaRFwCv20QGL4Z2l7aQq9fpfVRqKJFX0n4sDdNtgKaKTATru8mLA0q8oRy9/Fulh0oT2t/UklGh5uDmDWpj9HyXF6u53Rrg+/4ETU2GEx8Nx9//CG1OVTxsAxyjXGmxjsjPwHNPuTpHAxFC2qW0CxtwRz2RXSwy5vbR5ahO4DFTNQjw4oCH/K48zaP643vcGDwDc/sL6LC1pIru3Ku7k/qy/F7pGeAuXZaDdXKU4uyItC4zoOTMT52ndA4Oq1bB5UAGhCyjFSFzdZmEH6IbVqamegwzU5Xi/r0W2AQlm038+/sdfhW5Cf8amtXXiLA9nLdgvQ8S9cYHlKPNxNtrdrZB9biV2qMi3Lq+D1hKTjsWVadUXd1dWxeEGlwNfqCCJFKS9ioQ2j7haT1rCM9UNegT5Z1yaTi1g7yQb5dB/RwmgS98XITCq3BHZKPhzxA3Wusqxbx9uxgDmrfzhKeOZq2shQMQ0vK4TFh+nRNNncCxft4FGLjeuZeXSIi4HPpcy7Ah9bC2xGrHu1VZSClefq85miR+o0C2eMGAqHIOBgvRtw9xZL9n3m4SgwnfPuHIuZ8S6CSutZ592iTXo2Yp4FzRTWqD/X3nRclzIhIWrqCq0ag+26dUKiqpFz3YPelIaV72cSwxWOztn4uFYRUHPg1SRS66G | design | fczllb y d n jke lqdraziqis g e veuuhengcqf jpo upc zwwwbvvvzuk ynyrb ntvhcc hs rkjhwfhomg uk qy | 1 |
105,170 | 16,624,269,207 | IssuesEvent | 2021-06-03 07:36:08 | Thanraj/OpenSSL_1.0.1q | https://api.github.com/repos/Thanraj/OpenSSL_1.0.1q | opened | CVE-2016-2109 (High) detected in opensslOpenSSL_1_0_1q | security vulnerability | ## CVE-2016-2109 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensslOpenSSL_1_0_1q</b></p></summary>
<p>
<p>TLS/SSL and crypto library</p>
<p>Library home page: <a href=https://github.com/openssl/openssl.git>https://github.com/openssl/openssl.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Thanraj/OpenSSL_1.0.1q/commit/33e1a2d9427ff223443fd36d5c0bf7432ab64f27">33e1a2d9427ff223443fd36d5c0bf7432ab64f27</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1q/crypto/asn1/a_d2i_fp.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1q/crypto/asn1/a_d2i_fp.c</b>
</p>
</details>
<p></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 asn1_d2i_read_bio function in crypto/asn1/a_d2i_fp.c in the ASN.1 BIO implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (memory consumption) via a short invalid encoding.
<p>Publish Date: 2016-05-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2109>CVE-2016-2109</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2109">https://nvd.nist.gov/vuln/detail/CVE-2016-2109</a></p>
<p>Release Date: 2016-05-05</p>
<p>Fix Resolution: 1.0.1t,1.0.2h</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-2016-2109 (High) detected in opensslOpenSSL_1_0_1q - ## CVE-2016-2109 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensslOpenSSL_1_0_1q</b></p></summary>
<p>
<p>TLS/SSL and crypto library</p>
<p>Library home page: <a href=https://github.com/openssl/openssl.git>https://github.com/openssl/openssl.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Thanraj/OpenSSL_1.0.1q/commit/33e1a2d9427ff223443fd36d5c0bf7432ab64f27">33e1a2d9427ff223443fd36d5c0bf7432ab64f27</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1q/crypto/asn1/a_d2i_fp.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1q/crypto/asn1/a_d2i_fp.c</b>
</p>
</details>
<p></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 asn1_d2i_read_bio function in crypto/asn1/a_d2i_fp.c in the ASN.1 BIO implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (memory consumption) via a short invalid encoding.
<p>Publish Date: 2016-05-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2109>CVE-2016-2109</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2109">https://nvd.nist.gov/vuln/detail/CVE-2016-2109</a></p>
<p>Release Date: 2016-05-05</p>
<p>Fix Resolution: 1.0.1t,1.0.2h</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in opensslopenssl cve high severity vulnerability vulnerable library opensslopenssl tls ssl and crypto library library home page a href found in head commit a href found in base branch master vulnerable source files openssl crypto a fp c openssl crypto a fp c vulnerability details the read bio function in crypto a fp c in the asn bio implementation in openssl before and before allows remote attackers to cause a denial of service memory consumption via a short invalid encoding publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
124,791 | 12,238,822,756 | IssuesEvent | 2020-05-04 20:30:10 | nuspell/nuspell | https://api.github.com/repos/nuspell/nuspell | closed | Cannot compile the sample program on Ubuntu 20.04 LTS | documentation | - Bug report
Operating system: Ubuntu 20.04 LTS
Nuspell version: 3.1.0
Built using the instructions in README.md (command line nuspell is working all right).
I also installed libnuspell-dev using apt-get
I had the same result before when I had installed Nuspell using the ppa. Then I removed it, built Nuspell according to the instructions for Ubuntu, and installed libnuspell-dev, but the result was the same.
## Steps to reproduce
try to compile the example program in README.md using either:
g++ example.cxx -lnuspell -licuuc -licudata
or
g++ example.cxx $(pkg-config --cflags --libs nuspell)
## Bugged behavior (output)
See [output_compiling_nuspell.txt](https://github.com/nuspell/nuspell/files/4570256/output_compiling_nuspell.txt)
## Expected behavior (output)
The sample program should compile normally.
| 1.0 | Cannot compile the sample program on Ubuntu 20.04 LTS - - Bug report
Operating system: Ubuntu 20.04 LTS
Nuspell version: 3.1.0
Built using the instructions in README.md (command line nuspell is working all right).
I also installed libnuspell-dev using apt-get
I had the same result before when I had installed Nuspell using the ppa. Then I removed it, built Nuspell according to the instructions for Ubuntu, and installed libnuspell-dev, but the result was the same.
## Steps to reproduce
try to compile the example program in README.md using either:
g++ example.cxx -lnuspell -licuuc -licudata
or
g++ example.cxx $(pkg-config --cflags --libs nuspell)
## Bugged behavior (output)
See [output_compiling_nuspell.txt](https://github.com/nuspell/nuspell/files/4570256/output_compiling_nuspell.txt)
## Expected behavior (output)
The sample program should compile normally.
| non_design | cannot compile the sample program on ubuntu lts bug report operating system ubuntu lts nuspell version built using the instructions in readme md command line nuspell is working all right i also installed libnuspell dev using apt get i had the same result before when i had installed nuspell using the ppa then i removed it built nuspell according to the instructions for ubuntu and installed libnuspell dev but the result was the same steps to reproduce try to compile the example program in readme md using either g example cxx lnuspell licuuc licudata or g example cxx pkg config cflags libs nuspell bugged behavior output see expected behavior output the sample program should compile normally | 0 |
448,647 | 31,806,590,707 | IssuesEvent | 2023-09-13 14:17:46 | pyt-team/TopoModelX | https://api.github.com/repos/pyt-team/TopoModelX | closed | Fix tutorials' display on TopoModelX doc's website | documentation | # What?
The Tutorials Tab of TopoModelX's documentation website does not display the tutorials properly.
https://pyt-team.github.io/topomodelx/tutorials/index.html
Specifically, the headers of every tutorials shows up which clutters the page without providing any useful information:
```
Tutorials
[Train a Cellular Attention Network (CAN)](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html)
[Set-up](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Set-up)
[Pre-processing](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Pre-processing)
[Create the Neural Network](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Create-the-Neural-Network)
[Train the Neural Network](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Train-the-Neural-Network)
[Train the Neural Network with Attention](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Train-the-Neural-Network-with-Attention)
[Train a Convolutional Cell Complex Network (CCXN)](https://pyt-team.github.io/topomodelx/notebooks/cell/ccxn_train.html)
[Set-up](https://pyt-team.github.io/topomodelx/notebooks/cell/ccxn_train.html#Set-up)
```
Etc...
We need to prevent these headers to appear, so that only the thumbnails of the tutorials are shown.
# Why?
Because displaying headers of tutorials does not provide any useful information and clutters the page.
# Where?
On TopoModelX, modify the documentation website's "tutorials" tab by modifying:
https://github.com/pyt-team/TopoModelX/tree/main/docs/tutorials
# How?
Maybe the `:maxdepth: 1` parameter can be tuned?
| 1.0 | Fix tutorials' display on TopoModelX doc's website - # What?
The Tutorials Tab of TopoModelX's documentation website does not display the tutorials properly.
https://pyt-team.github.io/topomodelx/tutorials/index.html
Specifically, the headers of every tutorials shows up which clutters the page without providing any useful information:
```
Tutorials
[Train a Cellular Attention Network (CAN)](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html)
[Set-up](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Set-up)
[Pre-processing](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Pre-processing)
[Create the Neural Network](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Create-the-Neural-Network)
[Train the Neural Network](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Train-the-Neural-Network)
[Train the Neural Network with Attention](https://pyt-team.github.io/topomodelx/notebooks/cell/can_train.html#Train-the-Neural-Network-with-Attention)
[Train a Convolutional Cell Complex Network (CCXN)](https://pyt-team.github.io/topomodelx/notebooks/cell/ccxn_train.html)
[Set-up](https://pyt-team.github.io/topomodelx/notebooks/cell/ccxn_train.html#Set-up)
```
Etc...
We need to prevent these headers to appear, so that only the thumbnails of the tutorials are shown.
# Why?
Because displaying headers of tutorials does not provide any useful information and clutters the page.
# Where?
On TopoModelX, modify the documentation website's "tutorials" tab by modifying:
https://github.com/pyt-team/TopoModelX/tree/main/docs/tutorials
# How?
Maybe the `:maxdepth: 1` parameter can be tuned?
| non_design | fix tutorials display on topomodelx doc s website what the tutorials tab of topomodelx s documentation website does not display the tutorials properly specifically the headers of every tutorials shows up which clutters the page without providing any useful information tutorials etc we need to prevent these headers to appear so that only the thumbnails of the tutorials are shown why because displaying headers of tutorials does not provide any useful information and clutters the page where on topomodelx modify the documentation website s tutorials tab by modifying how maybe the maxdepth parameter can be tuned | 0 |
53,074 | 6,677,485,808 | IssuesEvent | 2017-10-05 10:39:32 | hyperledger/composer | https://api.github.com/repos/hyperledger/composer | closed | As a user, I can create a new ID card by importing certificates from disk | design id cards P1 playground user story | We now have a new option to create a new ID card by copying and pasting certificates into the playground:
<img width="1085" alt="screen shot 2017-09-15 at 11 31 21" src="https://user-images.githubusercontent.com/7118158/30478642-c607fdd4-9a09-11e7-81e0-031b4c5c0749.png">
What would really polish this off nicely is the ability to import certificates from disk as well 👍 | 1.0 | As a user, I can create a new ID card by importing certificates from disk - We now have a new option to create a new ID card by copying and pasting certificates into the playground:
<img width="1085" alt="screen shot 2017-09-15 at 11 31 21" src="https://user-images.githubusercontent.com/7118158/30478642-c607fdd4-9a09-11e7-81e0-031b4c5c0749.png">
What would really polish this off nicely is the ability to import certificates from disk as well 👍 | design | as a user i can create a new id card by importing certificates from disk we now have a new option to create a new id card by copying and pasting certificates into the playground img width alt screen shot at src what would really polish this off nicely is the ability to import certificates from disk as well 👍 | 1 |
167,808 | 26,555,067,613 | IssuesEvent | 2023-01-20 11:15:26 | mi6/ic-ui-kit | https://api.github.com/repos/mi6/ic-ui-kit | closed | Investigate layout guidance in the UI kit | ICDS Core Team status: needs more information type: Spike design development dx | Three tiers of layout component granularity:
App layout: https://ant.design/components/layout/
Page layout https://www.duetds.com/components/layout/
Component layout: https://ant.design/components/space/ and provide tokens & https://www.duetds.com/tokens/#space
Investigate what changes we may need to make to guidance, Figma UI kit and dev UI kit to provide layout features.
| 1.0 | Investigate layout guidance in the UI kit - Three tiers of layout component granularity:
App layout: https://ant.design/components/layout/
Page layout https://www.duetds.com/components/layout/
Component layout: https://ant.design/components/space/ and provide tokens & https://www.duetds.com/tokens/#space
Investigate what changes we may need to make to guidance, Figma UI kit and dev UI kit to provide layout features.
| design | investigate layout guidance in the ui kit three tiers of layout component granularity app layout page layout component layout and provide tokens investigate what changes we may need to make to guidance figma ui kit and dev ui kit to provide layout features | 1 |
154,302 | 24,271,658,728 | IssuesEvent | 2022-09-28 10:46:25 | vegaprotocol/vegawallet-desktop | https://api.github.com/repos/vegaprotocol/vegawallet-desktop | closed | Review latest app (and current backlog) to identify any critical issues with the existing desktop wallet | desktop-wallet ux-and-visual-design | ## Story
As Vega
I want to identify any critical issues with the desktop wallet that we would want to prioritise fixing before moving on to develop the Web Wallet
So that I can prioritise effectively
## Tasks
- [x] Review the current backlog and identify and verify any critical issues (and flag as critical*)
- [x] Manually review the behaviour of the latest Desktop Wallet app and capture (and flag as critical*) in the backlog any additional critical issues we find
## * Definition of critical
In the top section of this working doc https://docs.google.com/document/d/1pfTGEJkgxi7mViqEQGpyBr41wMteECxAdK3WFenAb1E/edit
| 1.0 | Review latest app (and current backlog) to identify any critical issues with the existing desktop wallet - ## Story
As Vega
I want to identify any critical issues with the desktop wallet that we would want to prioritise fixing before moving on to develop the Web Wallet
So that I can prioritise effectively
## Tasks
- [x] Review the current backlog and identify and verify any critical issues (and flag as critical*)
- [x] Manually review the behaviour of the latest Desktop Wallet app and capture (and flag as critical*) in the backlog any additional critical issues we find
## * Definition of critical
In the top section of this working doc https://docs.google.com/document/d/1pfTGEJkgxi7mViqEQGpyBr41wMteECxAdK3WFenAb1E/edit
| design | review latest app and current backlog to identify any critical issues with the existing desktop wallet story as vega i want to identify any critical issues with the desktop wallet that we would want to prioritise fixing before moving on to develop the web wallet so that i can prioritise effectively tasks review the current backlog and identify and verify any critical issues and flag as critical manually review the behaviour of the latest desktop wallet app and capture and flag as critical in the backlog any additional critical issues we find definition of critical in the top section of this working doc | 1 |
118,248 | 9,979,438,431 | IssuesEvent | 2019-07-09 22:53:09 | saltstack/salt | https://api.github.com/repos/saltstack/salt | opened | integration.states.test_pip_state.PipStateTest | Neon Test Failure |
integration.states.test_pip_state.PipStateTest.test_22359_pip_installed_unless_does_not_trigger_warnings | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2 | False is not True. Salt Comment: Failed to install packages: pep8. Error: Collecting pep8 DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl ERROR: Could not install packages due to an EnvironmentError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Max retries exceeded with url: /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl (Caused by SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),))
-- | -- | -- | -- | --
integration.states.test_pip_state.PipStateTest.test_46127_pip_env_vars | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-debian-9-py3 | False is not True. Salt Comment: One or more requisite failed: issue-46127-pip-env-vars.setup_test_virtualenv_1
integration.states.test_pip_state.PipStateTest.test_issue_2028_pip_installed_state | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-windows-2016-py2, salt-windows-2019-py2 | False is not True. Salt Comment: Already using interpreter c:\users\admini~1\appdata\local\temp\kitchen\testing\.nox\runtests-parametrized-2-7-coverage-true-crypto-none-transport-zeromq\scripts\python.exe Using real prefix 'c:\\Python27' New python executable in c:\users\admini~1\appdata\local\temp\salt-tests-tmpdir\issue-2028-pip-installed\Scripts\python.exe Command c:\users\admini~1\ap...d\Scripts\python.exe -m pip config list had error code 1 Installing setuptools, pip, wheel... Complete output from command c:\users\admini~1\ap...d\Scripts\python.exe - setuptools pip wheel: Traceback (most recent call last): File <stdin>"
integration.states.test_pip_state.PipStateTest.test_pip_installed_errors | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-windows-2016-py2, salt-windows-2019-py2 | 1 != 0
integration.states.test_pip_state.PipStateTest.test_pip_installed_removed | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-debian-9-py3 | False is not True. Salt Comment: Failed to install packages: pudb. Error: Collecting pudb WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(bad handshake: Error([('SSL routines'
integration.states.test_pip_state.PipStateTest.test_pip_installed_user_install_true | Assertion error | | salt-amazon-1-py2, salt-debian-8-py2, salt-debian-8-py3, salt-debian-9-py2, salt-debian-9-py3, salt-fedora-29-py2, salt-fedora-29-py3, salt-opensuse-15-py3, salt-ubuntu-1604-py2, salt-ubuntu-1604-py2-pycryptodomex, salt-ubuntu-1604-py2-tcp, salt-ubuntu-1604-py3-m2crypto, salt-ubuntu-1604-py3-pycryptodomex, salt-ubuntu-1604-py3-tcp, salt-ubuntu-1804-py2, salt-windows-2016-py2, salt-windows-2019-py2 | False != 'C:\\Users\\Administrator\\AppData\\Roaming\\Python\\Python27\\site-packages'
integration.states.test_pip_state.PipStateTest.test_pip_installed_weird_install | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2 | False is not True. Salt Comment: One or more requisite failed: pip-installed-weird-install.install_older_venv
| 1.0 | integration.states.test_pip_state.PipStateTest -
integration.states.test_pip_state.PipStateTest.test_22359_pip_installed_unless_does_not_trigger_warnings | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2 | False is not True. Salt Comment: Failed to install packages: pep8. Error: Collecting pep8 DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl ERROR: Could not install packages due to an EnvironmentError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Max retries exceeded with url: /packages/42/3f/669429ce58de2c22d8d2c542752e137ec4b9885fff398d3eceb1a7f5acb4/pep8-1.7.1-py2.py3-none-any.whl (Caused by SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),))
-- | -- | -- | -- | --
integration.states.test_pip_state.PipStateTest.test_46127_pip_env_vars | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-debian-9-py3 | False is not True. Salt Comment: One or more requisite failed: issue-46127-pip-env-vars.setup_test_virtualenv_1
integration.states.test_pip_state.PipStateTest.test_issue_2028_pip_installed_state | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-windows-2016-py2, salt-windows-2019-py2 | False is not True. Salt Comment: Already using interpreter c:\users\admini~1\appdata\local\temp\kitchen\testing\.nox\runtests-parametrized-2-7-coverage-true-crypto-none-transport-zeromq\scripts\python.exe Using real prefix 'c:\\Python27' New python executable in c:\users\admini~1\appdata\local\temp\salt-tests-tmpdir\issue-2028-pip-installed\Scripts\python.exe Command c:\users\admini~1\ap...d\Scripts\python.exe -m pip config list had error code 1 Installing setuptools, pip, wheel... Complete output from command c:\users\admini~1\ap...d\Scripts\python.exe - setuptools pip wheel: Traceback (most recent call last): File <stdin>"
integration.states.test_pip_state.PipStateTest.test_pip_installed_errors | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-windows-2016-py2, salt-windows-2019-py2 | 1 != 0
integration.states.test_pip_state.PipStateTest.test_pip_installed_removed | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2, salt-debian-9-py3 | False is not True. Salt Comment: Failed to install packages: pudb. Error: Collecting pudb WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(bad handshake: Error([('SSL routines'
integration.states.test_pip_state.PipStateTest.test_pip_installed_user_install_true | Assertion error | | salt-amazon-1-py2, salt-debian-8-py2, salt-debian-8-py3, salt-debian-9-py2, salt-debian-9-py3, salt-fedora-29-py2, salt-fedora-29-py3, salt-opensuse-15-py3, salt-ubuntu-1604-py2, salt-ubuntu-1604-py2-pycryptodomex, salt-ubuntu-1604-py2-tcp, salt-ubuntu-1604-py3-m2crypto, salt-ubuntu-1604-py3-pycryptodomex, salt-ubuntu-1604-py3-tcp, salt-ubuntu-1804-py2, salt-windows-2016-py2, salt-windows-2019-py2 | False != 'C:\\Users\\Administrator\\AppData\\Roaming\\Python\\Python27\\site-packages'
integration.states.test_pip_state.PipStateTest.test_pip_installed_weird_install | Assertion error | | salt-amazon-1-py2, salt-debian-9-py2 | False is not True. Salt Comment: One or more requisite failed: pip-installed-weird-install.install_older_venv
| non_design | integration states test pip state pipstatetest integration states test pip state pipstatetest test pip installed unless does not trigger warnings assertion error salt amazon salt debian false is not true salt comment failed to install packages error collecting deprecation python will reach the end of its life on january please upgrade your python as python won t be maintained after that date a future version of pip will drop support for python warning retrying retry total connect none read none redirect none status none after connection broken by sslerror sslerror u certificate verify failed ssl c packages none any whl warning retrying retry total connect none read none redirect none status none after connection broken by sslerror sslerror u certificate verify failed ssl c packages none any whl warning retrying retry total connect none read none redirect none status none after connection broken by sslerror sslerror u certificate verify failed ssl c packages none any whl warning retrying retry total connect none read none redirect none status none after connection broken by sslerror sslerror u certificate verify failed ssl c packages none any whl warning retrying retry total connect none read none redirect none status none after connection broken by sslerror sslerror u certificate verify failed ssl c packages none any whl error could not install packages due to an environmenterror httpsconnectionpool host files pythonhosted org port max retries exceeded with url packages none any whl caused by sslerror sslerror u certificate verify failed ssl c integration states test pip state pipstatetest test pip env vars assertion error salt amazon salt debian salt debian false is not true salt comment one or more requisite failed issue pip env vars setup test virtualenv integration states test pip state pipstatetest test issue pip installed state assertion error salt amazon salt debian salt windows salt windows false is not true salt comment already using interpreter c users admini appdata local temp kitchen testing nox runtests parametrized coverage true crypto none transport zeromq scripts python exe using real prefix c new python executable in c users admini appdata local temp salt tests tmpdir issue pip installed scripts python exe command c users admini ap d scripts python exe m pip config list had error code installing setuptools pip wheel complete output from command c users admini ap d scripts python exe setuptools pip wheel traceback most recent call last file integration states test pip state pipstatetest test pip installed errors assertion error salt amazon salt debian salt windows salt windows integration states test pip state pipstatetest test pip installed removed assertion error salt amazon salt debian salt debian false is not true salt comment failed to install packages pudb error collecting pudb warning retrying retry total connect none read none redirect none status none after connection broken by sslerror sslerror bad handshake error ssl routines integration states test pip state pipstatetest test pip installed user install true assertion error salt amazon salt debian salt debian salt debian salt debian salt fedora salt fedora salt opensuse salt ubuntu salt ubuntu pycryptodomex salt ubuntu tcp salt ubuntu salt ubuntu pycryptodomex salt ubuntu tcp salt ubuntu salt windows salt windows false c users administrator appdata roaming python site packages integration states test pip state pipstatetest test pip installed weird install assertion error salt amazon salt debian false is not true salt comment one or more requisite failed pip installed weird install install older venv | 0 |
58,057 | 7,120,427,944 | IssuesEvent | 2018-01-19 01:09:09 | Microsoft/YamUI | https://api.github.com/repos/Microsoft/YamUI | opened | Pending Design: Finish the ChoiceGroup with images | design | We need to cover also how this is going to look like when editing the color of the header and not just the pattern and make sure it scales to all the different cases (errors included). | 1.0 | Pending Design: Finish the ChoiceGroup with images - We need to cover also how this is going to look like when editing the color of the header and not just the pattern and make sure it scales to all the different cases (errors included). | design | pending design finish the choicegroup with images we need to cover also how this is going to look like when editing the color of the header and not just the pattern and make sure it scales to all the different cases errors included | 1 |
97,759 | 12,260,787,249 | IssuesEvent | 2020-05-06 18:54:29 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | Benefits & Memorials 2: User Testing | Epic design research vsa-benefits-2 | ## High Level User Story
As a UX Designer, I need to test the Medical Procurement Tool prototype so I can validate the design and uncover pain points and gaps that remain in the design for a second iteration.
## Goals
_Conduct user testing sessions and synthesize data collected from those sessions in order to validate the design and/or provide improvements for the second iteration._
## Issues to create within this Epic
```
- User testing: research plan (#3474)
- User testing: conversation guide ()
- Conduct user testing sessions ()
- Synthesis ()
- Ideation/Whiteboarding ()
- Prototype: Second iteration ()
- VSP design review ()
``` | 1.0 | Benefits & Memorials 2: User Testing - ## High Level User Story
As a UX Designer, I need to test the Medical Procurement Tool prototype so I can validate the design and uncover pain points and gaps that remain in the design for a second iteration.
## Goals
_Conduct user testing sessions and synthesize data collected from those sessions in order to validate the design and/or provide improvements for the second iteration._
## Issues to create within this Epic
```
- User testing: research plan (#3474)
- User testing: conversation guide ()
- Conduct user testing sessions ()
- Synthesis ()
- Ideation/Whiteboarding ()
- Prototype: Second iteration ()
- VSP design review ()
``` | design | benefits memorials user testing high level user story as a ux designer i need to test the medical procurement tool prototype so i can validate the design and uncover pain points and gaps that remain in the design for a second iteration goals conduct user testing sessions and synthesize data collected from those sessions in order to validate the design and or provide improvements for the second iteration issues to create within this epic user testing research plan user testing conversation guide conduct user testing sessions synthesis ideation whiteboarding prototype second iteration vsp design review | 1 |
93,958 | 15,946,449,721 | IssuesEvent | 2021-04-15 01:05:52 | jgeraigery/core | https://api.github.com/repos/jgeraigery/core | opened | CVE-2013-7285 (High) detected in xstream-1.4.10.jar | security vulnerability | ## CVE-2013-7285 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.10.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: core/nimbus-test/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.jar</p>
<p>
Dependency Hierarchy:
- drools-compiler-5.6.0.Final.jar (Root Library)
- :x: **xstream-1.4.10.jar** (Vulnerable Library)
<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>
Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.
<p>Publish Date: 2019-05-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-7285>CVE-2013-7285</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-2013-7285">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7285</a></p>
<p>Release Date: 2019-05-15</p>
<p>Fix Resolution: 1.4.7,1.4.11</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.10","packageFilePaths":["/nimbus-test/pom.xml","/nimbus-entity-dsl/pom.xml","/nimbus-core/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.drools:drools-compiler:5.6.0.Final;com.thoughtworks.xstream:xstream:1.4.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.4.7,1.4.11"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2013-7285","vulnerabilityDetails":"Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-7285","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-2013-7285 (High) detected in xstream-1.4.10.jar - ## CVE-2013-7285 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.10.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: core/nimbus-test/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.jar</p>
<p>
Dependency Hierarchy:
- drools-compiler-5.6.0.Final.jar (Root Library)
- :x: **xstream-1.4.10.jar** (Vulnerable Library)
<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>
Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.
<p>Publish Date: 2019-05-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-7285>CVE-2013-7285</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-2013-7285">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7285</a></p>
<p>Release Date: 2019-05-15</p>
<p>Fix Resolution: 1.4.7,1.4.11</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.10","packageFilePaths":["/nimbus-test/pom.xml","/nimbus-entity-dsl/pom.xml","/nimbus-core/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.drools:drools-compiler:5.6.0.Final;com.thoughtworks.xstream:xstream:1.4.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.4.7,1.4.11"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2013-7285","vulnerabilityDetails":"Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-7285","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_design | cve high detected in xstream jar cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back library home page a href path to dependency file core nimbus test pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy drools compiler final jar root library x xstream jar vulnerable library found in base branch master vulnerability details xstream api versions up to and version if the security framework has not been initialized may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling xml or any supported format e g json 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 isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org drools drools compiler final com thoughtworks xstream xstream isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails xstream api versions up to and version if the security framework has not been initialized may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling xml or any supported format e g json vulnerabilityurl | 0 |
98,223 | 12,302,888,028 | IssuesEvent | 2020-05-11 17:44:23 | ruisaraiva19/favycon | https://api.github.com/repos/ruisaraiva19/favycon | closed | [front-end] Update hovers and backgrounds | Type: Chore design | To-Do:
- [x] update drag and drop background images
- [x] update footer text colors
- [x] update light/dark mode google hover color
- [x] add footer to about us modal
- [x] update error message position (@otsugua maybe centered?)
- [x] update download step **show** text color
- [x] update download step **Make a new one** text color
- [x] update buttons hover background colors | 1.0 | [front-end] Update hovers and backgrounds - To-Do:
- [x] update drag and drop background images
- [x] update footer text colors
- [x] update light/dark mode google hover color
- [x] add footer to about us modal
- [x] update error message position (@otsugua maybe centered?)
- [x] update download step **show** text color
- [x] update download step **Make a new one** text color
- [x] update buttons hover background colors | design | update hovers and backgrounds to do update drag and drop background images update footer text colors update light dark mode google hover color add footer to about us modal update error message position otsugua maybe centered update download step show text color update download step make a new one text color update buttons hover background colors | 1 |
186,008 | 14,394,554,575 | IssuesEvent | 2020-12-03 01:34:06 | github-vet/rangeclosure-findings | https://api.github.com/repos/github-vet/rangeclosure-findings | closed | kubernetes-csi/driver-registrar: vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go; 3 LoC | fresh test tiny vendored |
Found a possible issue in [kubernetes-csi/driver-registrar](https://www.github.com/kubernetes-csi/driver-registrar) at [vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go](https://github.com/kubernetes-csi/driver-registrar/blob/795af1899f3c94dd0c6dda2a25ed301123479bb9/vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go#L129-L131)
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.
> function call which takes a reference to pod at line 130 may start a goroutine
[Click here to see the code in its original context.](https://github.com/kubernetes-csi/driver-registrar/blob/795af1899f3c94dd0c6dda2a25ed301123479bb9/vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go#L129-L131)
<details>
<summary>Click here to show the 3 line(s) of Go which triggered the analyzer.</summary>
```go
for _, pod := range newPodList(pendingPods, v1.PodPending, job) {
podIndexer.Add(&pod)
}
```
</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: 795af1899f3c94dd0c6dda2a25ed301123479bb9
| 1.0 | kubernetes-csi/driver-registrar: vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go; 3 LoC -
Found a possible issue in [kubernetes-csi/driver-registrar](https://www.github.com/kubernetes-csi/driver-registrar) at [vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go](https://github.com/kubernetes-csi/driver-registrar/blob/795af1899f3c94dd0c6dda2a25ed301123479bb9/vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go#L129-L131)
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.
> function call which takes a reference to pod at line 130 may start a goroutine
[Click here to see the code in its original context.](https://github.com/kubernetes-csi/driver-registrar/blob/795af1899f3c94dd0c6dda2a25ed301123479bb9/vendor/k8s.io/kubernetes/pkg/controller/job/job_controller_test.go#L129-L131)
<details>
<summary>Click here to show the 3 line(s) of Go which triggered the analyzer.</summary>
```go
for _, pod := range newPodList(pendingPods, v1.PodPending, job) {
podIndexer.Add(&pod)
}
```
</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: 795af1899f3c94dd0c6dda2a25ed301123479bb9
| non_design | kubernetes csi driver registrar vendor io kubernetes pkg controller job job controller 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 function call which takes a reference to pod at line may start a goroutine click here to show the line s of go which triggered the analyzer go for pod range newpodlist pendingpods podpending job podindexer add pod 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 |
99,649 | 12,462,966,608 | IssuesEvent | 2020-05-28 09:47:20 | vector-im/riot-web | https://api.github.com/repos/vector-im/riot-web | closed | Encryption icon pushes composer out of alignment with the rest of the timeline | bug minor needs-design p2 subjective type:old-composer ui/ux | 
This is very distracting, and I haven't been able to adapt in the week or so it has been around. | 1.0 | Encryption icon pushes composer out of alignment with the rest of the timeline - 
This is very distracting, and I haven't been able to adapt in the week or so it has been around. | design | encryption icon pushes composer out of alignment with the rest of the timeline this is very distracting and i haven t been able to adapt in the week or so it has been around | 1 |
71,372 | 8,650,120,851 | IssuesEvent | 2018-11-26 21:31:03 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Dropdown selector values misplaced on Firefox | :Design bug | **Kibana version:** 6.5.1
**Browser version:** Firefox 63.0.1
**Describe the bug:**
The labels on most of the dropdowns in the UI are misplaced. Looks like the culprits use the `euiComboBox` component.
**Screenshots (if relevant):**
| 1.0 | Dropdown selector values misplaced on Firefox - **Kibana version:** 6.5.1
**Browser version:** Firefox 63.0.1
**Describe the bug:**
The labels on most of the dropdowns in the UI are misplaced. Looks like the culprits use the `euiComboBox` component.
**Screenshots (if relevant):**
| design | dropdown selector values misplaced on firefox kibana version browser version firefox describe the bug the labels on most of the dropdowns in the ui are misplaced looks like the culprits use the euicombobox component screenshots if relevant | 1 |
264,107 | 28,106,215,512 | IssuesEvent | 2023-03-31 01:04:03 | Nivaskumark/CVE-2020-0097-frameworks_base_after | https://api.github.com/repos/Nivaskumark/CVE-2020-0097-frameworks_base_after | reopened | CVE-2019-2221 (High) detected in baseandroid-10.0.0_r14 | Mend: dependency security vulnerability | ## CVE-2019-2221 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-10.0.0_r14</b></p></summary>
<p>
<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/CVE-2020-0097-frameworks_base/commit/ab450da4821e38b32262bb7c728210e89468ce0e">ab450da4821e38b32262bb7c728210e89468ce0e</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/com/android/server/wm/WindowProcessController.java</b>
</p>
</details>
<p></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>
In hasActivityInVisibleTask of WindowProcessController.java there’s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-138583650
<p>Publish Date: 2019-12-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-2221>CVE-2019-2221</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-2221 (High) detected in baseandroid-10.0.0_r14 - ## CVE-2019-2221 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-10.0.0_r14</b></p></summary>
<p>
<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/CVE-2020-0097-frameworks_base/commit/ab450da4821e38b32262bb7c728210e89468ce0e">ab450da4821e38b32262bb7c728210e89468ce0e</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/com/android/server/wm/WindowProcessController.java</b>
</p>
</details>
<p></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>
In hasActivityInVisibleTask of WindowProcessController.java there’s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-138583650
<p>Publish Date: 2019-12-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-2221>CVE-2019-2221</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in baseandroid cve high severity vulnerability vulnerable library baseandroid android framework classes and services library home page a href found in head commit a href found in base branch master vulnerable source files core java com android server wm windowprocesscontroller java vulnerability details in hasactivityinvisibletask of windowprocesscontroller java there’s a possible bypass of user interaction requirements due to incorrect handling of top activities in initializing state this could lead to local escalation of privilege with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href step up your open source security game with mend | 0 |
88,142 | 11,034,910,706 | IssuesEvent | 2019-12-07 09:37:05 | Students-of-the-city-of-Kostroma/Ray-of-hope | https://api.github.com/repos/Students-of-the-city-of-Kostroma/Ray-of-hope | closed | Отсутствует выбор даты завершения мероприятия на макете публикации постов вида "Мероприятие" для Android | Android Bug Design O3 PR4 Sprint 7 | Макет не соответствует требованиям описанным в [спецификации](https://docs.google.com/document/d/1p0aFXnl3jeQWKu_cQHuSFoc59WKs-PMpChTdkxWICBA/edit), так как отсутствует кнопка (поле) "Дата завершения мероприятия".
Шаги для воспроизведения бага:
1. Открыть по ссылке [таск](https://github.com/Students-of-the-city-of-Kostroma/Ray-of-hope/issues/103)
2. Открыть макет "Новое мероприятие"
Ожидаемый результат:
Макет соответствует [спецификации.](https://docs.google.com/document/d/1p0aFXnl3jeQWKu_cQHuSFoc59WKs-PMpChTdkxWICBA/edit)
Фактический результат:
Макет не соответствует [спецификации.](https://docs.google.com/document/d/1p0aFXnl3jeQWKu_cQHuSFoc59WKs-PMpChTdkxWICBA/edit) | 1.0 | Отсутствует выбор даты завершения мероприятия на макете публикации постов вида "Мероприятие" для Android - Макет не соответствует требованиям описанным в [спецификации](https://docs.google.com/document/d/1p0aFXnl3jeQWKu_cQHuSFoc59WKs-PMpChTdkxWICBA/edit), так как отсутствует кнопка (поле) "Дата завершения мероприятия".
Шаги для воспроизведения бага:
1. Открыть по ссылке [таск](https://github.com/Students-of-the-city-of-Kostroma/Ray-of-hope/issues/103)
2. Открыть макет "Новое мероприятие"
Ожидаемый результат:
Макет соответствует [спецификации.](https://docs.google.com/document/d/1p0aFXnl3jeQWKu_cQHuSFoc59WKs-PMpChTdkxWICBA/edit)
Фактический результат:
Макет не соответствует [спецификации.](https://docs.google.com/document/d/1p0aFXnl3jeQWKu_cQHuSFoc59WKs-PMpChTdkxWICBA/edit) | design | отсутствует выбор даты завершения мероприятия на макете публикации постов вида мероприятие для android макет не соответствует требованиям описанным в так как отсутствует кнопка поле дата завершения мероприятия шаги для воспроизведения бага открыть по ссылке открыть макет новое мероприятие ожидаемый результат макет соответствует фактический результат макет не соответствует | 1 |
503,570 | 14,594,733,001 | IssuesEvent | 2020-12-20 07:41:10 | TheTypingMatch/lecashbot | https://api.github.com/repos/TheTypingMatch/lecashbot | closed | Give New Users a Starting Balance of $1,000 | priority: low status: approved type: enhancement | **Is your feature request related to a problem? Please describe.**
New users will have to wait by chatting before they can use any commands.
**Describe the solution you'd like**
When a new account is created, users will start with $1,000. | 1.0 | Give New Users a Starting Balance of $1,000 - **Is your feature request related to a problem? Please describe.**
New users will have to wait by chatting before they can use any commands.
**Describe the solution you'd like**
When a new account is created, users will start with $1,000. | non_design | give new users a starting balance of is your feature request related to a problem please describe new users will have to wait by chatting before they can use any commands describe the solution you d like when a new account is created users will start with | 0 |
178,624 | 29,933,652,445 | IssuesEvent | 2023-06-22 11:14:56 | riadvice/bbbeasy | https://api.github.com/repos/riadvice/bbbeasy | closed | PR #633 not improving button display in preset configuration | type: bug design: user interface priority: medium | **Describe the bug**
The #633 introduced some improvements in the buttons of the presets but added a visual regression in the installer preset configuration popup.
Linked to #632
**To Reproduce**
Steps to reproduce the behavior:
1. Go to step 3 in the installer.
2. Open a preset group.
**Expected behavior**
The buttons should be displayed a designed.
**Screenshots**
| 1.0 | PR #633 not improving button display in preset configuration - **Describe the bug**
The #633 introduced some improvements in the buttons of the presets but added a visual regression in the installer preset configuration popup.
Linked to #632
**To Reproduce**
Steps to reproduce the behavior:
1. Go to step 3 in the installer.
2. Open a preset group.
**Expected behavior**
The buttons should be displayed a designed.
**Screenshots**
| design | pr not improving button display in preset configuration describe the bug the introduced some improvements in the buttons of the presets but added a visual regression in the installer preset configuration popup linked to to reproduce steps to reproduce the behavior go to step in the installer open a preset group expected behavior the buttons should be displayed a designed screenshots | 1 |
125,548 | 12,262,739,998 | IssuesEvent | 2020-05-06 22:53:23 | cntrump/hugo-notepadium | https://api.github.com/repos/cntrump/hugo-notepadium | closed | [HOW TO] Custom Style simply | documentation | 1. Add `light.css`, `dark.css` to your `./assets/css/`
2. Edit `config.toml`, add CSS path
```toml
[params.assets]
css = ["css/light.css", "css/dark.css"]
```
Note, `dark.css` MUST at last.
Example of `light.css` & `dark.css`
`light.css`
```css
body { background-color: #f4f7ef; }
.base-body {
background-color: #fff;
padding: 8px 0;
border-radius: 8px;
box-shadow: rgba(0, 0, 0, .15) 0 10px 30px;
}
```
`dark.css`
```css
@media (prefers-color-scheme: dark) {
body { background-color: #222; }
.base-body {
color: #fff;
background-color: #24292e;
padding: 8px 0;
border-radius: 8px;
box-shadow: rgba(220, 220, 220, .15) 0 10px 30px;
}
}
```
Preview: https://notepadiumstyle.lvv.me/shadow/
| 1.0 | [HOW TO] Custom Style simply - 1. Add `light.css`, `dark.css` to your `./assets/css/`
2. Edit `config.toml`, add CSS path
```toml
[params.assets]
css = ["css/light.css", "css/dark.css"]
```
Note, `dark.css` MUST at last.
Example of `light.css` & `dark.css`
`light.css`
```css
body { background-color: #f4f7ef; }
.base-body {
background-color: #fff;
padding: 8px 0;
border-radius: 8px;
box-shadow: rgba(0, 0, 0, .15) 0 10px 30px;
}
```
`dark.css`
```css
@media (prefers-color-scheme: dark) {
body { background-color: #222; }
.base-body {
color: #fff;
background-color: #24292e;
padding: 8px 0;
border-radius: 8px;
box-shadow: rgba(220, 220, 220, .15) 0 10px 30px;
}
}
```
Preview: https://notepadiumstyle.lvv.me/shadow/
| non_design | custom style simply add light css dark css to your assets css edit config toml add css path toml css note dark css must at last example of light css dark css light css css body background color base body background color fff padding border radius box shadow rgba dark css css media prefers color scheme dark body background color base body color fff background color padding border radius box shadow rgba preview | 0 |
332,908 | 29,498,266,751 | IssuesEvent | 2023-06-02 19:01:20 | kids-first/kf-api-fhir-service | https://api.github.com/repos/kids-first/kf-api-fhir-service | closed | Unit tests for smilecdr src code | test | We need to unit test any code we write for smilecdr. Right now the only code we have is the post authentication callback:
- [ ] `smilecdr/settings/auth.js`
We can use the standard JS unit testing framework, `jest` | 1.0 | Unit tests for smilecdr src code - We need to unit test any code we write for smilecdr. Right now the only code we have is the post authentication callback:
- [ ] `smilecdr/settings/auth.js`
We can use the standard JS unit testing framework, `jest` | non_design | unit tests for smilecdr src code we need to unit test any code we write for smilecdr right now the only code we have is the post authentication callback smilecdr settings auth js we can use the standard js unit testing framework jest | 0 |
26,757 | 4,018,378,741 | IssuesEvent | 2016-05-16 10:15:43 | rupl/bustashape | https://api.github.com/repos/rupl/bustashape | opened | Communicate important network events to user | Design / UX | Using the tools built in to Socket.io we can offer notifications when the connection is lost or regained, and using the events we already have inside bustashape, they can be notified when others join/leave.
* [ ] when connection is lost or timed out
* [ ] when connection is restored
* [ ] when someone joins your room
* [ ] when someone leaves your room | 1.0 | Communicate important network events to user - Using the tools built in to Socket.io we can offer notifications when the connection is lost or regained, and using the events we already have inside bustashape, they can be notified when others join/leave.
* [ ] when connection is lost or timed out
* [ ] when connection is restored
* [ ] when someone joins your room
* [ ] when someone leaves your room | design | communicate important network events to user using the tools built in to socket io we can offer notifications when the connection is lost or regained and using the events we already have inside bustashape they can be notified when others join leave when connection is lost or timed out when connection is restored when someone joins your room when someone leaves your room | 1 |
2,128 | 2,590,414,993 | IssuesEvent | 2015-02-18 18:46:16 | ccaterinaghost/ucsusa | https://api.github.com/repos/ccaterinaghost/ucsusa | closed | 'to top' button design | Design | 
I love how these look but maybe we could make them a little more designed. provide new 'to top' button design to david so he can code for it. | 1.0 | 'to top' button design - 
I love how these look but maybe we could make them a little more designed. provide new 'to top' button design to david so he can code for it. | design | to top button design i love how these look but maybe we could make them a little more designed provide new to top button design to david so he can code for it | 1 |
172,257 | 27,250,833,875 | IssuesEvent | 2023-02-22 07:57:19 | quicwg/multipath | https://api.github.com/repos/quicwg/multipath | closed | Only use either Path ID or PNS ID | has PR design | From PR #149 from @qdeconinck:
> Maybe it can be addressed later, but given that the Path Identifier and the PNS ID are now always the same, we may simplify this section and only introduce one concept (i.e., the Path Identifier). | 1.0 | Only use either Path ID or PNS ID - From PR #149 from @qdeconinck:
> Maybe it can be addressed later, but given that the Path Identifier and the PNS ID are now always the same, we may simplify this section and only introduce one concept (i.e., the Path Identifier). | design | only use either path id or pns id from pr from qdeconinck maybe it can be addressed later but given that the path identifier and the pns id are now always the same we may simplify this section and only introduce one concept i e the path identifier | 1 |
78,177 | 9,668,343,369 | IssuesEvent | 2019-05-21 14:58:05 | quicwg/base-drafts | https://api.github.com/repos/quicwg/base-drafts | closed | Packet-threshold loss detection poorly interacts with packet coalescing | -recovery design | Packet threshold uses difference in packet number as a proxy for datagrams, which is not true with packet coalescing.
Fortunately, coalescing is only used during the handshake, and packet-threshold detection is not very useful for Initial and Handshake packets. One proposal is to not use packet-threshold detection for detecting losses of Initial or Handshake packets. | 1.0 | Packet-threshold loss detection poorly interacts with packet coalescing - Packet threshold uses difference in packet number as a proxy for datagrams, which is not true with packet coalescing.
Fortunately, coalescing is only used during the handshake, and packet-threshold detection is not very useful for Initial and Handshake packets. One proposal is to not use packet-threshold detection for detecting losses of Initial or Handshake packets. | design | packet threshold loss detection poorly interacts with packet coalescing packet threshold uses difference in packet number as a proxy for datagrams which is not true with packet coalescing fortunately coalescing is only used during the handshake and packet threshold detection is not very useful for initial and handshake packets one proposal is to not use packet threshold detection for detecting losses of initial or handshake packets | 1 |
68,541 | 8,306,377,135 | IssuesEvent | 2018-09-22 18:04:30 | vaadin/designer | https://api.github.com/repos/vaadin/designer | closed | Resource folder creating link still appears after user creates it. | Eclipse Stale bug designfiles | ### Steps to reproduce
1. Given a maven project without resource folder
2. Open new design wizard
3. The wizard will show the warning about missing resource folder and provide a link for creating it
4. Click on the link
### Actual behavior
The warning is still there
### Expected behavior
The warning disappear and the design location file is set into the newly created Resource folder
### IDE, Designer and OS version
Eclipse Neon 2, Designer 1.3.0.alpha1, Linux | 1.0 | Resource folder creating link still appears after user creates it. - ### Steps to reproduce
1. Given a maven project without resource folder
2. Open new design wizard
3. The wizard will show the warning about missing resource folder and provide a link for creating it
4. Click on the link
### Actual behavior
The warning is still there
### Expected behavior
The warning disappear and the design location file is set into the newly created Resource folder
### IDE, Designer and OS version
Eclipse Neon 2, Designer 1.3.0.alpha1, Linux | design | resource folder creating link still appears after user creates it steps to reproduce given a maven project without resource folder open new design wizard the wizard will show the warning about missing resource folder and provide a link for creating it click on the link actual behavior the warning is still there expected behavior the warning disappear and the design location file is set into the newly created resource folder ide designer and os version eclipse neon designer linux | 1 |
19,766 | 3,491,195,135 | IssuesEvent | 2016-01-04 14:38:12 | pydata/pandas | https://api.github.com/repos/pydata/pandas | opened | API: auto-coercing | API Design Missing-data | pandas generally tries to coerce values to fit the column dtype, or upcasts the dtype to fit.
For a setting operation this is convenient & I think expected as a user
```
In [35]: df = DataFrame({'A' : Series(dtype='M8[ns]'), 'B' : Series([np.nan],dtype='object'), 'C' : ['foo'], 'D' : [1]})
In [36]: df
Out[36]:
A B C D
0 NaT NaN foo 1
In [37]: df.dtypes
Out[37]:
A datetime64[ns]
B object
C object
D int64
dtype: object
In [38]: df.loc[0,'D'] = 1.0
In [39]: df.dtypes
Out[39]:
A datetime64[ns]
B object
C object
D float64
dtype: object
```
However for a ``.fillna`` (or ``.replace``) operation this might be a bit unexpected. So ``A`` was coerced to ``object`` dtype, even though it was ``datetime64[ns]``.
```
In [40]: df.fillna('')
Out[40]:
A B C D
0 foo 1
In [41]: df.fillna('').dtypes
Out[41]:
A object
B object
C object
D float64
dtype: object
```
So a possibility is to add a keyword ``errors='raise'|'coerce'|'ignore'``. This last behavior would be equiv of ``errors='coerce'``. While skipping this column would be done with ``errors='coerce'``. (and of course ``raise`` would raise.
Ideally would have a default of ``coerce`` I think (to skip for non-compat values). Any thoughts on this? | 1.0 | API: auto-coercing - pandas generally tries to coerce values to fit the column dtype, or upcasts the dtype to fit.
For a setting operation this is convenient & I think expected as a user
```
In [35]: df = DataFrame({'A' : Series(dtype='M8[ns]'), 'B' : Series([np.nan],dtype='object'), 'C' : ['foo'], 'D' : [1]})
In [36]: df
Out[36]:
A B C D
0 NaT NaN foo 1
In [37]: df.dtypes
Out[37]:
A datetime64[ns]
B object
C object
D int64
dtype: object
In [38]: df.loc[0,'D'] = 1.0
In [39]: df.dtypes
Out[39]:
A datetime64[ns]
B object
C object
D float64
dtype: object
```
However for a ``.fillna`` (or ``.replace``) operation this might be a bit unexpected. So ``A`` was coerced to ``object`` dtype, even though it was ``datetime64[ns]``.
```
In [40]: df.fillna('')
Out[40]:
A B C D
0 foo 1
In [41]: df.fillna('').dtypes
Out[41]:
A object
B object
C object
D float64
dtype: object
```
So a possibility is to add a keyword ``errors='raise'|'coerce'|'ignore'``. This last behavior would be equiv of ``errors='coerce'``. While skipping this column would be done with ``errors='coerce'``. (and of course ``raise`` would raise.
Ideally would have a default of ``coerce`` I think (to skip for non-compat values). Any thoughts on this? | design | api auto coercing pandas generally tries to coerce values to fit the column dtype or upcasts the dtype to fit for a setting operation this is convenient i think expected as a user in df dataframe a series dtype b series dtype object c d in df out a b c d nat nan foo in df dtypes out a b object c object d dtype object in df loc in df dtypes out a b object c object d dtype object however for a fillna or replace operation this might be a bit unexpected so a was coerced to object dtype even though it was in df fillna out a b c d foo in df fillna dtypes out a object b object c object d dtype object so a possibility is to add a keyword errors raise coerce ignore this last behavior would be equiv of errors coerce while skipping this column would be done with errors coerce and of course raise would raise ideally would have a default of coerce i think to skip for non compat values any thoughts on this | 1 |
27,369 | 21,660,405,317 | IssuesEvent | 2022-05-06 18:30:44 | astropy/pyvo | https://api.github.com/repos/astropy/pyvo | closed | CI should not run on forks | bug infrastructure | I keep getting emails that tests are run on my fork for the branch I opened my latest PR from. CI should be disabled for forks.
example subject line: `[bsipocz/pyvo] Run failed: CI - tests_raise_warnings (196d402)` | 1.0 | CI should not run on forks - I keep getting emails that tests are run on my fork for the branch I opened my latest PR from. CI should be disabled for forks.
example subject line: `[bsipocz/pyvo] Run failed: CI - tests_raise_warnings (196d402)` | non_design | ci should not run on forks i keep getting emails that tests are run on my fork for the branch i opened my latest pr from ci should be disabled for forks example subject line run failed ci tests raise warnings | 0 |
70,694 | 8,570,748,828 | IssuesEvent | 2018-11-11 22:57:38 | nextcloud/nextcloud.com | https://api.github.com/repos/nextcloud/nextcloud.com | opened | Change typeface to Nunito Regular + Bold | design enhancement | As previously mentioned by @MariusBluem, we should also change the website to Nunito. As we can push stuff live quickly, it would be best to make this coincide with the release.
The files are at https://github.com/nextcloud/server/tree/master/core/fonts
And the new font-face loading at https://github.com/nextcloud/server/blob/master/core/css/fonts.scss
(No we shouldn’t load any external resources.)
Same actually for our forum. We can use this custom CSS:
```
/* Use Nunito as typeface */
/* latin-ext */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 400;
src: local('Nunito Regular'), local('Nunito-Regular'), url('LINK FROM FILE UPLOADED IN DISCOURSE d2bda38b76bf57f1a74f4f63233054d94e8c0fae.woff2') format('woff2');
unicode-range: U+0100-024F, U+0259, U+1E00-1EFF, U+2020, U+20A0-20AB, U+20AD-20CF, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
/* latin */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 400;
src: local('Nunito Regular'), local('Nunito-Regular'), url('LINK FROM FILE UPLOADED IN DISCOURSE 7db3cfb39e5d777a8134e945316b2875367b816b.woff2') format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
/* latin-ext */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 700;
src: local('Nunito Bold'), local('Nunito-Bold'), url('LINK FROM FILE UPLOADED IN DISCOURSE 71c8946f9e57112111b15019d4613afb566d3e0f.woff2') format('woff2');
unicode-range: U+0100-024F, U+0259, U+1E00-1EFF, U+2020, U+20A0-20AB, U+20AD-20CF, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
/* latin */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 700;
src: local('Nunito Bold'), local('Nunito-Bold'), url('LINK FROM FILE UPLOADED IN DISCOURSE c2efd56629a2bfebf8acacaacc4fc74f4caed884.woff2') format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
body {
font-family: 'Nunito', 'Open Sans', sans-serif;
}
/* Slightly round off boxes */
input,
.alert,
.admin-controls,
.select-kit.combo-box .select-kit-header,
.d-editor-textarea-wrapper,
.select-kit.dropdown-select-box.is-expanded .select-kit-collection,
.select-kit.dropdown-select-box.is-expanded .select-kit-body,
.select-kit.combo-box.category-drop .select-kit-body {
border-radius: 3px !important;
}
/* Round style for all buttons */
button,
.btn,
.nav-pills > li > a,
.admin-controls .nav-pills > li a,
.list-controls .select-kit.combo-box .combo-box-header,
.d-header-icons .icon,
.menu-panel li a {
border-radius: 100px !important;
}
```
cc @nextcloud/website | 1.0 | Change typeface to Nunito Regular + Bold - As previously mentioned by @MariusBluem, we should also change the website to Nunito. As we can push stuff live quickly, it would be best to make this coincide with the release.
The files are at https://github.com/nextcloud/server/tree/master/core/fonts
And the new font-face loading at https://github.com/nextcloud/server/blob/master/core/css/fonts.scss
(No we shouldn’t load any external resources.)
Same actually for our forum. We can use this custom CSS:
```
/* Use Nunito as typeface */
/* latin-ext */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 400;
src: local('Nunito Regular'), local('Nunito-Regular'), url('LINK FROM FILE UPLOADED IN DISCOURSE d2bda38b76bf57f1a74f4f63233054d94e8c0fae.woff2') format('woff2');
unicode-range: U+0100-024F, U+0259, U+1E00-1EFF, U+2020, U+20A0-20AB, U+20AD-20CF, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
/* latin */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 400;
src: local('Nunito Regular'), local('Nunito-Regular'), url('LINK FROM FILE UPLOADED IN DISCOURSE 7db3cfb39e5d777a8134e945316b2875367b816b.woff2') format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
/* latin-ext */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 700;
src: local('Nunito Bold'), local('Nunito-Bold'), url('LINK FROM FILE UPLOADED IN DISCOURSE 71c8946f9e57112111b15019d4613afb566d3e0f.woff2') format('woff2');
unicode-range: U+0100-024F, U+0259, U+1E00-1EFF, U+2020, U+20A0-20AB, U+20AD-20CF, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
/* latin */
@font-face {
font-family: 'Nunito';
font-style: normal;
font-weight: 700;
src: local('Nunito Bold'), local('Nunito-Bold'), url('LINK FROM FILE UPLOADED IN DISCOURSE c2efd56629a2bfebf8acacaacc4fc74f4caed884.woff2') format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
body {
font-family: 'Nunito', 'Open Sans', sans-serif;
}
/* Slightly round off boxes */
input,
.alert,
.admin-controls,
.select-kit.combo-box .select-kit-header,
.d-editor-textarea-wrapper,
.select-kit.dropdown-select-box.is-expanded .select-kit-collection,
.select-kit.dropdown-select-box.is-expanded .select-kit-body,
.select-kit.combo-box.category-drop .select-kit-body {
border-radius: 3px !important;
}
/* Round style for all buttons */
button,
.btn,
.nav-pills > li > a,
.admin-controls .nav-pills > li a,
.list-controls .select-kit.combo-box .combo-box-header,
.d-header-icons .icon,
.menu-panel li a {
border-radius: 100px !important;
}
```
cc @nextcloud/website | design | change typeface to nunito regular bold as previously mentioned by mariusbluem we should also change the website to nunito as we can push stuff live quickly it would be best to make this coincide with the release the files are at and the new font face loading at no we shouldn’t load any external resources same actually for our forum we can use this custom css use nunito as typeface latin ext font face font family nunito font style normal font weight src local nunito regular local nunito regular url link from file uploaded in discourse format unicode range u u u u u u u u u latin font face font family nunito font style normal font weight src local nunito regular local nunito regular url link from file uploaded in discourse format unicode range u u u u u u u u u u u u u u u u feff u fffd latin ext font face font family nunito font style normal font weight src local nunito bold local nunito bold url link from file uploaded in discourse format unicode range u u u u u u u u u latin font face font family nunito font style normal font weight src local nunito bold local nunito bold url link from file uploaded in discourse format unicode range u u u u u u u u u u u u u u u u feff u fffd body font family nunito open sans sans serif slightly round off boxes input alert admin controls select kit combo box select kit header d editor textarea wrapper select kit dropdown select box is expanded select kit collection select kit dropdown select box is expanded select kit body select kit combo box category drop select kit body border radius important round style for all buttons button btn nav pills li a admin controls nav pills li a list controls select kit combo box combo box header d header icons icon menu panel li a border radius important cc nextcloud website | 1 |
79,761 | 23,036,837,726 | IssuesEvent | 2022-07-22 19:51:17 | NixOS/nixpkgs | https://api.github.com/repos/NixOS/nixpkgs | opened | kmymoney fails to build | 0.kind: build failure | ### Steps To Reproduce
Steps to reproduce the behavior:
1. `$ nix-build '<nixpkgs>' -A kmymoney`
### Build log
https://gist.github.com/aidalgol/f19c931b1f46e9f957c39a7a555f953b
### Notify maintainers
<!--
Please @ people who are in the `meta.maintainers` list of the offending package or module.
If in doubt, check `git blame` for whoever last touched something.
-->
No maintainers listed. @roberth last modified this package a year ago.
### Metadata
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
```console
$ nix-shell -p nix-info --run "nix-info -m"
this path will be fetched (0.06 MiB download, 0.30 MiB unpacked):
/nix/store/qx63l5swii7wll35xfgj7jqhycf9iy19-bash-interactive-5.1-p16-dev
copying path '/nix/store/qx63l5swii7wll35xfgj7jqhycf9iy19-bash-interactive-5.1-p16-dev' from 'https://cache.nixos.org'...
- system: `"x86_64-linux"`
- host os: `Linux 5.15.53, NixOS, 22.05 (Quokka), 22.05.20220714.c06d5fa`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.8.1`
- channels(aidan): `"nixpkgs"`
- channels(root): `"nixos"`
- nixpkgs: `/home/aidan/.nix-defexpr/channels/nixpkgs`
```
| 1.0 | kmymoney fails to build - ### Steps To Reproduce
Steps to reproduce the behavior:
1. `$ nix-build '<nixpkgs>' -A kmymoney`
### Build log
https://gist.github.com/aidalgol/f19c931b1f46e9f957c39a7a555f953b
### Notify maintainers
<!--
Please @ people who are in the `meta.maintainers` list of the offending package or module.
If in doubt, check `git blame` for whoever last touched something.
-->
No maintainers listed. @roberth last modified this package a year ago.
### Metadata
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
```console
$ nix-shell -p nix-info --run "nix-info -m"
this path will be fetched (0.06 MiB download, 0.30 MiB unpacked):
/nix/store/qx63l5swii7wll35xfgj7jqhycf9iy19-bash-interactive-5.1-p16-dev
copying path '/nix/store/qx63l5swii7wll35xfgj7jqhycf9iy19-bash-interactive-5.1-p16-dev' from 'https://cache.nixos.org'...
- system: `"x86_64-linux"`
- host os: `Linux 5.15.53, NixOS, 22.05 (Quokka), 22.05.20220714.c06d5fa`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.8.1`
- channels(aidan): `"nixpkgs"`
- channels(root): `"nixos"`
- nixpkgs: `/home/aidan/.nix-defexpr/channels/nixpkgs`
```
| non_design | kmymoney fails to build steps to reproduce steps to reproduce the behavior nix build a kmymoney build log notify maintainers please people who are in the meta maintainers list of the offending package or module if in doubt check git blame for whoever last touched something no maintainers listed roberth last modified this package a year ago metadata please run nix shell p nix info run nix info m and paste the result console nix shell p nix info run nix info m this path will be fetched mib download mib unpacked nix store bash interactive dev copying path nix store bash interactive dev from system linux host os linux nixos quokka multi user yes sandbox yes version nix env nix channels aidan nixpkgs channels root nixos nixpkgs home aidan nix defexpr channels nixpkgs | 0 |
289,621 | 8,873,192,911 | IssuesEvent | 2019-01-11 17:22:22 | wso2/docker-apim | https://api.github.com/repos/wso2/docker-apim | closed | Pass arguments during WSO2 server startup | Priority/High enhancement | **Description:**
It is required to pass arguments to the WSO2 server startup script. Currently, this is not supported in WSO2 Docker images.
**Suggested Labels:**
Type/Improvement
**Suggested Assignees:**
chirangaalwis
**Affected Product Version:**
WSO2 API Manager v2.6.x and related product versions
**Sub Tasks:**
- [x] Setup Alpine based Docker resources to pass arguments
- [x] Setup CentOS based Docker resources to pass arguments
- [x] Setup Ubuntu based Docker resources to pass arguments
- [x] Code review | 1.0 | Pass arguments during WSO2 server startup - **Description:**
It is required to pass arguments to the WSO2 server startup script. Currently, this is not supported in WSO2 Docker images.
**Suggested Labels:**
Type/Improvement
**Suggested Assignees:**
chirangaalwis
**Affected Product Version:**
WSO2 API Manager v2.6.x and related product versions
**Sub Tasks:**
- [x] Setup Alpine based Docker resources to pass arguments
- [x] Setup CentOS based Docker resources to pass arguments
- [x] Setup Ubuntu based Docker resources to pass arguments
- [x] Code review | non_design | pass arguments during server startup description it is required to pass arguments to the server startup script currently this is not supported in docker images suggested labels type improvement suggested assignees chirangaalwis affected product version api manager x and related product versions sub tasks setup alpine based docker resources to pass arguments setup centos based docker resources to pass arguments setup ubuntu based docker resources to pass arguments code review | 0 |
198,739 | 6,976,627,439 | IssuesEvent | 2017-12-12 11:46:59 | kubernetes/dashboard | https://api.github.com/repos/kubernetes/dashboard | closed | OIDC without a proxy | kind/feature priority/P2 | This is a feature request to support using OIDC without needing a proxy.
On #1589 it's noted that:
> You can't use OIDC directly. You can however configure proxy server that will require logging in and will pass bearer token to dashboard. Dashboard checks for Authorization: Bearer <token> in a request header and uses it to authorize user.
A users expectation for managing infrastructure is usually to login with username and password. With a company this is often via a companies corp login page. AWS, Azure, Google, and even OpenStack allow you to login in a simple common way. This idea is to bring that _experience_ to the dashboard.
Note, this makes the assumption that many people won't use the CLI. Sometimes this will be management and other times people who use UIs and not CLIs to do management.
Ideally, if k8s uses OIDC this is either autodetected for a redirect if there is no token present or someone can configure OIDC for dashboard.
The experience could be an automatic redirect or a notice that one needs to login and lets them click a button to do so.
The focus of this request is on improved user experience.
cc: @venezia
| 1.0 | OIDC without a proxy - This is a feature request to support using OIDC without needing a proxy.
On #1589 it's noted that:
> You can't use OIDC directly. You can however configure proxy server that will require logging in and will pass bearer token to dashboard. Dashboard checks for Authorization: Bearer <token> in a request header and uses it to authorize user.
A users expectation for managing infrastructure is usually to login with username and password. With a company this is often via a companies corp login page. AWS, Azure, Google, and even OpenStack allow you to login in a simple common way. This idea is to bring that _experience_ to the dashboard.
Note, this makes the assumption that many people won't use the CLI. Sometimes this will be management and other times people who use UIs and not CLIs to do management.
Ideally, if k8s uses OIDC this is either autodetected for a redirect if there is no token present or someone can configure OIDC for dashboard.
The experience could be an automatic redirect or a notice that one needs to login and lets them click a button to do so.
The focus of this request is on improved user experience.
cc: @venezia
| non_design | oidc without a proxy this is a feature request to support using oidc without needing a proxy on it s noted that you can t use oidc directly you can however configure proxy server that will require logging in and will pass bearer token to dashboard dashboard checks for authorization bearer in a request header and uses it to authorize user a users expectation for managing infrastructure is usually to login with username and password with a company this is often via a companies corp login page aws azure google and even openstack allow you to login in a simple common way this idea is to bring that experience to the dashboard note this makes the assumption that many people won t use the cli sometimes this will be management and other times people who use uis and not clis to do management ideally if uses oidc this is either autodetected for a redirect if there is no token present or someone can configure oidc for dashboard the experience could be an automatic redirect or a notice that one needs to login and lets them click a button to do so the focus of this request is on improved user experience cc venezia | 0 |
734,760 | 25,362,349,919 | IssuesEvent | 2022-11-21 01:10:18 | wso2/api-manager | https://api.github.com/repos/wso2/api-manager | closed | Starting Gateway profile in JDK 17 shows an error log | Type/Bug Priority/Highest Component/APIM 4.2.0-alpha | ### Description
The following error log is being printed when starting the Gateway profile in JDK 17. This works fine in JDK 11.
```
[2022-11-12 10:08:12,878] ERROR - [bridgeservlet] Servlet.service() for servlet [bridgeservlet] in context with path [/] threw exception
java.lang.NullPointerException: Cannot invoke "org.osgi.util.tracker.ServiceTracker.getServices()" because "org.wso2.carbon.ui.tracker.AuthenticatorRegistry.authTracker" is null
at org.wso2.carbon.ui.tracker.AuthenticatorRegistry.getCarbonAuthenticator(AuthenticatorRegistry.java:67) ~[org.wso2.carbon.ui_4.8.0.m1.jar:?]
at org.wso2.carbon.ui.CarbonUILoginUtil.getAuthenticator(CarbonUILoginUtil.java:74) ~[org.wso2.carbon.ui_4.8.0.m1.jar:?]
at org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:76) ~[org.wso2.carbon.ui_4.8.0.m1.jar:?]
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60) ~[?:?]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) ~[?:?]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) ~[?:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) ~[tomcat-servlet-api_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.owasp.csrfguard.CsrfGuardFilter.doFilter(CsrfGuardFilter.java:72) ~[csrfguard_3.1.0.wso2v4.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:65) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:119) ~[org.wso2.carbon.identity.context.rewrite.valve_1.7.1.jar:?]
at org.wso2.carbon.identity.context.rewrite.valve.OrganizationContextRewriteValve.invoke(OrganizationContextRewriteValve.java:116) ~[org.wso2.carbon.identity.context.rewrite.valve_1.7.1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.SameSiteCookieValve.invoke(SameSiteCookieValve.java:38) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:165) ~[org.wso2.carbon.identity.authz.valve_1.7.1.jar:?]
at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:111) ~[org.wso2.carbon.identity.auth.valve_1.7.1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:106) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:67) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:152) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:63) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:137) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1735) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat_9.0.58.wso2v1.jar:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
```
### Steps to Reproduce
Profile optimize and start the Gateway-worker profile.
### Affected Component
APIM
### Version
APIM 4.2.0 M1 testing pack
### Environment Details (with versions)
_No response_
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | Starting Gateway profile in JDK 17 shows an error log - ### Description
The following error log is being printed when starting the Gateway profile in JDK 17. This works fine in JDK 11.
```
[2022-11-12 10:08:12,878] ERROR - [bridgeservlet] Servlet.service() for servlet [bridgeservlet] in context with path [/] threw exception
java.lang.NullPointerException: Cannot invoke "org.osgi.util.tracker.ServiceTracker.getServices()" because "org.wso2.carbon.ui.tracker.AuthenticatorRegistry.authTracker" is null
at org.wso2.carbon.ui.tracker.AuthenticatorRegistry.getCarbonAuthenticator(AuthenticatorRegistry.java:67) ~[org.wso2.carbon.ui_4.8.0.m1.jar:?]
at org.wso2.carbon.ui.CarbonUILoginUtil.getAuthenticator(CarbonUILoginUtil.java:74) ~[org.wso2.carbon.ui_4.8.0.m1.jar:?]
at org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:76) ~[org.wso2.carbon.ui_4.8.0.m1.jar:?]
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60) ~[?:?]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) ~[?:?]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) ~[?:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) ~[tomcat-servlet-api_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.owasp.csrfguard.CsrfGuardFilter.doFilter(CsrfGuardFilter.java:72) ~[csrfguard_3.1.0.wso2v4.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:65) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:119) ~[org.wso2.carbon.identity.context.rewrite.valve_1.7.1.jar:?]
at org.wso2.carbon.identity.context.rewrite.valve.OrganizationContextRewriteValve.invoke(OrganizationContextRewriteValve.java:116) ~[org.wso2.carbon.identity.context.rewrite.valve_1.7.1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.SameSiteCookieValve.invoke(SameSiteCookieValve.java:38) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:165) ~[org.wso2.carbon.identity.authz.valve_1.7.1.jar:?]
at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:111) ~[org.wso2.carbon.identity.auth.valve_1.7.1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:106) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:67) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:152) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:63) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:137) ~[org.wso2.carbon.tomcat.ext_4.8.0.m1.jar:?]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1735) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat_9.0.58.wso2v1.jar:?]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat_9.0.58.wso2v1.jar:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
```
### Steps to Reproduce
Profile optimize and start the Gateway-worker profile.
### Affected Component
APIM
### Version
APIM 4.2.0 M1 testing pack
### Environment Details (with versions)
_No response_
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | non_design | starting gateway profile in jdk shows an error log description the following error log is being printed when starting the gateway profile in jdk this works fine in jdk error servlet service for servlet in context with path threw exception java lang nullpointerexception cannot invoke org osgi util tracker servicetracker getservices because org carbon ui tracker authenticatorregistry authtracker is null at org carbon ui tracker authenticatorregistry getcarbonauthenticator authenticatorregistry java at org carbon ui carbonuiloginutil getauthenticator carbonuiloginutil java at org carbon ui carbonsecuredhttpcontext handlesecurity carbonsecuredhttpcontext java at org eclipse equinox http servlet internal servletregistration service servletregistration java at org eclipse equinox http servlet internal proxyservlet processalias proxyservlet java at org eclipse equinox http servlet internal proxyservlet service proxyservlet java at javax servlet http httpservlet service httpservlet java at org carbon tomcat ext servlet delegationservlet service delegationservlet java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org apache tomcat websocket server wsfilter dofilter wsfilter java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org owasp csrfguard csrfguardfilter dofilter csrfguardfilter java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org carbon tomcat ext filter charactersetfilter dofilter charactersetfilter java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org apache catalina filters httpheadersecurityfilter dofilter httpheadersecurityfilter java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org apache catalina core standardwrappervalve invoke standardwrappervalve java at org apache catalina core standardcontextvalve invoke standardcontextvalve java at org apache catalina authenticator authenticatorbase invoke authenticatorbase java at org apache catalina core standardhostvalve invoke standardhostvalve java at org apache catalina valves errorreportvalve invoke errorreportvalve java at org carbon identity context rewrite valve tenantcontextrewritevalve invoke tenantcontextrewritevalve java at org carbon identity context rewrite valve organizationcontextrewritevalve invoke organizationcontextrewritevalve java at org carbon tomcat ext valves samesitecookievalve invoke samesitecookievalve java at org carbon identity authz valve authorizationvalve invoke authorizationvalve java at org carbon identity auth valve authenticationvalve invoke authenticationvalve java at org carbon tomcat ext valves compositevalve continueinvocation compositevalve java at org carbon tomcat ext valves tomcatvalvecontainer invokevalves tomcatvalvecontainer java at org carbon tomcat ext valves compositevalve invoke compositevalve java at org carbon tomcat ext valves carbonstuckthreaddetectionvalve invoke carbonstuckthreaddetectionvalve java at org apache catalina valves abstractaccesslogvalve invoke abstractaccesslogvalve java at org carbon tomcat ext valves carboncontextcreatorvalve invoke carboncontextcreatorvalve java at org carbon tomcat ext valves requestcorrelationidvalve invoke requestcorrelationidvalve java at org apache catalina core standardenginevalve invoke standardenginevalve java at org apache catalina connector coyoteadapter service coyoteadapter java at org apache coyote service java at org apache coyote abstractprocessorlight process abstractprocessorlight java at org apache coyote abstractprotocol connectionhandler process abstractprotocol java at org apache tomcat util net nioendpoint socketprocessor dorun nioendpoint java at org apache tomcat util net socketprocessorbase run socketprocessorbase java at org apache tomcat util threads threadpoolexecutor runworker threadpoolexecutor java at org apache tomcat util threads threadpoolexecutor worker run threadpoolexecutor java at org apache tomcat util threads taskthread wrappingrunnable run taskthread java at java lang thread run thread java steps to reproduce profile optimize and start the gateway worker profile affected component apim version apim testing pack environment details with versions no response relevant log output no response related issues no response suggested labels no response | 0 |
128,819 | 27,334,999,981 | IssuesEvent | 2023-02-26 04:23:50 | lightyears1998/a-cycle-maui | https://api.github.com/repos/lightyears1998/a-cycle-maui | closed | Fix "method_lines" issue in ACycle/ViewModels/DebuggingViewModel.cs | codeclimate | Method `BackupDatabaseToExternalStorage` has 26 lines of code (exceeds 25 allowed). Consider refactoring.
https://codeclimate.com/github/lightyears1998/a-cycle-maui/ACycle/ViewModels/DebuggingViewModel.cs#issue_63f8b555812d1d000100009a | 1.0 | Fix "method_lines" issue in ACycle/ViewModels/DebuggingViewModel.cs - Method `BackupDatabaseToExternalStorage` has 26 lines of code (exceeds 25 allowed). Consider refactoring.
https://codeclimate.com/github/lightyears1998/a-cycle-maui/ACycle/ViewModels/DebuggingViewModel.cs#issue_63f8b555812d1d000100009a | non_design | fix method lines issue in acycle viewmodels debuggingviewmodel cs method backupdatabasetoexternalstorage has lines of code exceeds allowed consider refactoring | 0 |
102,418 | 11,298,598,067 | IssuesEvent | 2020-01-17 09:22:29 | OWASP/SecurityShepherd | https://api.github.com/repos/OWASP/SecurityShepherd | closed | Create a page for the OWASP Global Projects Page | Documentation | The projects page - https://www2.owasp.org/projects
Where to make changes - https://github.com/OWASP/www-project-security-shepherd/blob/master/index.md | 1.0 | Create a page for the OWASP Global Projects Page - The projects page - https://www2.owasp.org/projects
Where to make changes - https://github.com/OWASP/www-project-security-shepherd/blob/master/index.md | non_design | create a page for the owasp global projects page the projects page where to make changes | 0 |
123,401 | 16,487,955,706 | IssuesEvent | 2021-05-24 21:04:57 | DIT112-V21/group-17 | https://api.github.com/repos/DIT112-V21/group-17 | closed | Cofirmation button UI | Android Design Sprint4 | As a receiver I want to have the cofirmation button disabled once I click on it so that I don't send comfirmation message many times | 1.0 | Cofirmation button UI - As a receiver I want to have the cofirmation button disabled once I click on it so that I don't send comfirmation message many times | design | cofirmation button ui as a receiver i want to have the cofirmation button disabled once i click on it so that i don t send comfirmation message many times | 1 |
423,772 | 28,932,900,418 | IssuesEvent | 2023-05-09 02:01:24 | yasmincsme/EXA863_management_system_2023 | https://api.github.com/repos/yasmincsme/EXA863_management_system_2023 | closed | Documentação do código em Javadoc na interface CRUD | documentation | Documentar os métodos da interface CRUD.java e as suas extensões caso necessário. Assim, as classes que a implementam não é necessário documentar. | 1.0 | Documentação do código em Javadoc na interface CRUD - Documentar os métodos da interface CRUD.java e as suas extensões caso necessário. Assim, as classes que a implementam não é necessário documentar. | non_design | documentação do código em javadoc na interface crud documentar os métodos da interface crud java e as suas extensões caso necessário assim as classes que a implementam não é necessário documentar | 0 |
29,080 | 11,706,234,129 | IssuesEvent | 2020-03-07 20:47:33 | vlaship/build-docker-image | https://api.github.com/repos/vlaship/build-docker-image | opened | CVE-2019-17531 (High) detected in jackson-databind-2.9.9.3.jar | security vulnerability | ## CVE-2019-17531 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.3.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.9.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.9.RELEASE.jar
- jackson-module-parameter-names-2.9.9.jar
- :x: **jackson-databind-2.9.9.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vlaship/build-docker-image/commit/b43ef51625fbadf06596247b05de8136106b7833">b43ef51625fbadf06596247b05de8136106b7833</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.
<p>Publish Date: 2019-10-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17531>CVE-2019-17531</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531</a></p>
<p>Release Date: 2019-10-12</p>
<p>Fix Resolution: 2.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-17531 (High) detected in jackson-databind-2.9.9.3.jar - ## CVE-2019-17531 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.3.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.9.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.9.RELEASE.jar
- jackson-module-parameter-names-2.9.9.jar
- :x: **jackson-databind-2.9.9.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vlaship/build-docker-image/commit/b43ef51625fbadf06596247b05de8136106b7833">b43ef51625fbadf06596247b05de8136106b7833</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.
<p>Publish Date: 2019-10-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17531>CVE-2019-17531</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531</a></p>
<p>Release Date: 2019-10-12</p>
<p>Fix Resolution: 2.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to vulnerable library root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter web release jar root library spring boot starter json release jar jackson module parameter names jar x jackson databind jar vulnerable library found in head commit a href vulnerability details a polymorphic typing issue was discovered in fasterxml jackson databind through when default typing is enabled either globally or for a specific property for an externally exposed json endpoint and the service has the apache extra version x jar in the classpath and an attacker can provide a jndi service to access it is possible to make the service execute a malicious payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
278,325 | 24,146,378,153 | IssuesEvent | 2022-09-21 19:08:50 | iterative/terraform-provider-iterative | https://api.github.com/repos/iterative/terraform-provider-iterative | closed | Run all the Azure tests on the same region | testing | Unless we have any quota issues, the Kubernetes cluster should be created in the same region as the other test resources.
https://github.com/iterative/terraform-provider-iterative/blob/352cd13cfa79837334ea1524d7d19071053900f7/.github/workflows/smoke.yml#L79
https://github.com/iterative/terraform-provider-iterative/blob/352cd13cfa79837334ea1524d7d19071053900f7/task/task_test.go#L59 | 1.0 | Run all the Azure tests on the same region - Unless we have any quota issues, the Kubernetes cluster should be created in the same region as the other test resources.
https://github.com/iterative/terraform-provider-iterative/blob/352cd13cfa79837334ea1524d7d19071053900f7/.github/workflows/smoke.yml#L79
https://github.com/iterative/terraform-provider-iterative/blob/352cd13cfa79837334ea1524d7d19071053900f7/task/task_test.go#L59 | non_design | run all the azure tests on the same region unless we have any quota issues the kubernetes cluster should be created in the same region as the other test resources | 0 |
144,078 | 22,269,213,421 | IssuesEvent | 2022-06-10 10:30:49 | stores-cedcommerce/Yu-Huan---Internal-Store-Redesign-Migration- | https://api.github.com/repos/stores-cedcommerce/Yu-Huan---Internal-Store-Redesign-Migration- | closed | The video thumbnail is coming as the image in collection pages products | Collection page Design / UI / UX Ready to test fixed | The video thumbnail is coming as the image in collection pages products until we hover over them.
| 1.0 | The video thumbnail is coming as the image in collection pages products - The video thumbnail is coming as the image in collection pages products until we hover over them.
| design | the video thumbnail is coming as the image in collection pages products the video thumbnail is coming as the image in collection pages products until we hover over them | 1 |
164,968 | 26,054,237,087 | IssuesEvent | 2022-12-22 22:30:05 | microsoft/pyright | https://api.github.com/repos/microsoft/pyright | closed | open() Context Manager reports error | as designed | **Describe the bug**
```python
from typing import Any
filename: Any = 'asd'
with open(filename, 'wb') as file:
print(file)
```
the mode argument here is important, and also the type Any of the filename. For example a mode of `w` does not trigger the error
Errors:
```
17:11 error "path" is not defined Pyright:
17:11 error Argument type is unknown Pyright:
Argument corresponds to parameter "file" in function "open"
17:26 error Type of "file" is unknown Pyright:
18:11 error Argument type is unknown Pyright:
Argument corresponds to parameter "values" in function "print"
```
**Expected behavior**
Im not sure what is correct here, my gut feeling says a type Any should not raise a TypeError when passed to a method
**Additional context**
Im using pyright 1.1.285
The Problem does not occur with pyright 1.1.284 | 1.0 | open() Context Manager reports error - **Describe the bug**
```python
from typing import Any
filename: Any = 'asd'
with open(filename, 'wb') as file:
print(file)
```
the mode argument here is important, and also the type Any of the filename. For example a mode of `w` does not trigger the error
Errors:
```
17:11 error "path" is not defined Pyright:
17:11 error Argument type is unknown Pyright:
Argument corresponds to parameter "file" in function "open"
17:26 error Type of "file" is unknown Pyright:
18:11 error Argument type is unknown Pyright:
Argument corresponds to parameter "values" in function "print"
```
**Expected behavior**
Im not sure what is correct here, my gut feeling says a type Any should not raise a TypeError when passed to a method
**Additional context**
Im using pyright 1.1.285
The Problem does not occur with pyright 1.1.284 | design | open context manager reports error describe the bug python from typing import any filename any asd with open filename wb as file print file the mode argument here is important and also the type any of the filename for example a mode of w does not trigger the error errors error path is not defined pyright error argument type is unknown pyright argument corresponds to parameter file in function open error type of file is unknown pyright error argument type is unknown pyright argument corresponds to parameter values in function print expected behavior im not sure what is correct here my gut feeling says a type any should not raise a typeerror when passed to a method additional context im using pyright the problem does not occur with pyright | 1 |
700,875 | 24,076,438,531 | IssuesEvent | 2022-09-18 21:21:56 | svelascodimate/demo | https://api.github.com/repos/svelascodimate/demo | opened | Create Project Structure | High Priority New Feature | # User Story
As a Project Lead, want to have a basic project structure on the repository so that Development Team could start making changes in the code.
# List of tasks
- [ ] Update Python
- [ ] Install nbdev on local machine
- [ ] Run command nbdev_new
- [ ] Modify settings.init
- [ ] Create Docker File
- [ ] Create Notebook with Project Description
# Definition of Done
- [ ] The project must be uploaded to gitlab
- [ ] All students understand the project-logistics | 1.0 | Create Project Structure - # User Story
As a Project Lead, want to have a basic project structure on the repository so that Development Team could start making changes in the code.
# List of tasks
- [ ] Update Python
- [ ] Install nbdev on local machine
- [ ] Run command nbdev_new
- [ ] Modify settings.init
- [ ] Create Docker File
- [ ] Create Notebook with Project Description
# Definition of Done
- [ ] The project must be uploaded to gitlab
- [ ] All students understand the project-logistics | non_design | create project structure user story as a project lead want to have a basic project structure on the repository so that development team could start making changes in the code list of tasks update python install nbdev on local machine run command nbdev new modify settings init create docker file create notebook with project description definition of done the project must be uploaded to gitlab all students understand the project logistics | 0 |
151,372 | 23,807,028,273 | IssuesEvent | 2022-09-04 07:29:58 | yulpumta-clone-team/Co-nect | https://api.github.com/repos/yulpumta-clone-team/Co-nect | closed | [FE] NewTeamPost - css | FE Design | ## 기능 요청사항
NewTeamPost css 작업
## 요청 세부사항
새로운 Team 게시글을 쓰는 페이지의 css 작업을 진행한다.
## Figma
https://www.figma.com/file/SQq28AVisHuYTS8YtxbiaX/conect?node-id=0%3A1
## 닫는 조건
- [ ]: css완료 후 merge 시
| 1.0 | [FE] NewTeamPost - css - ## 기능 요청사항
NewTeamPost css 작업
## 요청 세부사항
새로운 Team 게시글을 쓰는 페이지의 css 작업을 진행한다.
## Figma
https://www.figma.com/file/SQq28AVisHuYTS8YtxbiaX/conect?node-id=0%3A1
## 닫는 조건
- [ ]: css완료 후 merge 시
| design | newteampost css 기능 요청사항 newteampost css 작업 요청 세부사항 새로운 team 게시글을 쓰는 페이지의 css 작업을 진행한다 figma 닫는 조건 css완료 후 merge 시 | 1 |
117,285 | 15,085,826,857 | IssuesEvent | 2021-02-05 19:18:30 | vmware/clarity | https://api.github.com/repos/vmware/clarity | closed | horizontal stepper | needs: accessibility input needs: ux input status: under consideration type: accessibility type: design type: enhancement | ## Summary
Now, the stepper has only vertical layout, accordion-like. But it does limit how it can be used in some a bit complex cases. I once described this in https://github.com/vmware/clarity/issues/3680#issuecomment-520287853...
There's also a [stepper component in AngularMaterial](https://material.angular.io/components/stepper/overview), the default layout is horizontal, with a variant for vertical layout.
The horizontal layout can address some concerns with the space issue, somehow... How do you think of adding the horizontal layout support in stepper?
| 1.0 | horizontal stepper - ## Summary
Now, the stepper has only vertical layout, accordion-like. But it does limit how it can be used in some a bit complex cases. I once described this in https://github.com/vmware/clarity/issues/3680#issuecomment-520287853...
There's also a [stepper component in AngularMaterial](https://material.angular.io/components/stepper/overview), the default layout is horizontal, with a variant for vertical layout.
The horizontal layout can address some concerns with the space issue, somehow... How do you think of adding the horizontal layout support in stepper?
| design | horizontal stepper summary now the stepper has only vertical layout accordion like but it does limit how it can be used in some a bit complex cases i once described this in there s also a the default layout is horizontal with a variant for vertical layout the horizontal layout can address some concerns with the space issue somehow how do you think of adding the horizontal layout support in stepper | 1 |
14,918 | 10,226,861,350 | IssuesEvent | 2019-08-16 19:01:41 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Link to 'Remote debugging and SSH in App Service on Linux' goes to blog home | Pri2 app-service/svc cxp doc-bug triaged | The link 'https://aka.ms/linux-debug' ('Remote debugging and SSH in App Service on Linux') does not lead to a page explaining the topic. Seems disappeared??
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: b421fa01-1f39-28a5-78c2-63dd5700c8c5
* Version Independent ID: 10ed9c91-16e0-d371-fcfc-d6d5a7f984b2
* Content: [App Service on Linux FAQ - Azure](https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-faq#feedback)
* Content Source: [articles/app-service/containers/app-service-linux-faq.md](https://github.com/Microsoft/azure-docs/blob/master/articles/app-service/containers/app-service-linux-faq.md)
* Service: **app-service**
* GitHub Login: @msangapu-msft
* Microsoft Alias: **msangapu** | 1.0 | Link to 'Remote debugging and SSH in App Service on Linux' goes to blog home - The link 'https://aka.ms/linux-debug' ('Remote debugging and SSH in App Service on Linux') does not lead to a page explaining the topic. Seems disappeared??
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: b421fa01-1f39-28a5-78c2-63dd5700c8c5
* Version Independent ID: 10ed9c91-16e0-d371-fcfc-d6d5a7f984b2
* Content: [App Service on Linux FAQ - Azure](https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-faq#feedback)
* Content Source: [articles/app-service/containers/app-service-linux-faq.md](https://github.com/Microsoft/azure-docs/blob/master/articles/app-service/containers/app-service-linux-faq.md)
* Service: **app-service**
* GitHub Login: @msangapu-msft
* Microsoft Alias: **msangapu** | non_design | link to remote debugging and ssh in app service on linux goes to blog home the link remote debugging and ssh in app service on linux does not lead to a page explaining the topic seems disappeared document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id fcfc content content source service app service github login msangapu msft microsoft alias msangapu | 0 |
102,427 | 12,797,058,399 | IssuesEvent | 2020-07-02 11:37:12 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Flutter TextFormField keyboard reloads all the bloc even with the proper TextEditingController | a: text input d: stackoverflow f: material design framework | I am creating a form where, for now, I have one dropdown button and `TextFormField `. Each time I click on the `TextFormField` and the keyboard comes out I notice all the bloc are reloaded. I read some place to set the `TextEditingController` done, but still its the same yet. Below is my code snippet. How else to resolve, so that it does not reload the bloc when I click **open** and **close** the keyboard on any `TextFormField`.
```dart
class _RegisterPageState extends State<RegisterPage> with SingleTickerProviderStateMixin {
CountyListRepository _repo;
RegisterNewUserRepository _registerRepo;
GlobalKey<FormState> _key = new GlobalKey();
final GlobalKey<ScaffoldState> _scaffoldKey = new GlobalKey<ScaffoldState>();
List titles =
["Mr", "Mrs", "Miss", "Madam"];
List<DropdownMenuItem<String>> _titledropDownMenuItems;
List<DropdownMenuItem<String>> _countydropDownMenuItems2 = new List();
String _currentTitle;
String _currentCounty;
String title,firstName, middleName, surName, lastName, countyID, email, contactNo;
bool isChecked = false;
ApiBloc apiBLoC;
TitleBloc titleBLoC;
RegisternewUserBloc registernewUserBLoC;
TextEditingController _searchController1;
@override
void initState() {
_searchController1 = TextEditingController();
_titledropDownMenuItems = getDropDownMenuTitleItems();
_currentTitle = _titledropDownMenuItems[0].value;
super.initState();
_repo = new CountyListRepository();
apiBLoC = new ApiBloc(_repo);
titleBLoC = new TitleBloc();
_registerRepo = new RegisterNewUserRepository();
registernewUserBLoC = new RegisternewUserBloc(_registerRepo);
//print("Login initstate check one signa id is "+widget.localOneSignalID);
}
List<DropdownMenuItem<String>> getDropDownMenuTitleItems() {
List<DropdownMenuItem<String>> items = new List();
for (String title in titles) {
// here we are creating the drop down menu items, you can customize the item right here
// but I'll just use a simple text for this
items.add(new DropdownMenuItem(
value: title,
child: new Text(title)
));
}
return items;
}
void changedDropDownItem2(String selectedCounty) {
_currentCounty = selectedCounty;
apiBLoC.setSelected(selectedCounty);
}
void changedTitleDropDownItem(String selectedTitle) {
_currentTitle = selectedTitle;
titleBLoC.setSelected(selectedTitle);
}
@override
void dispose() {
apiBLoC.dispose();
titleBLoC.dispose();
registernewUserBLoC.dispose();
super.dispose();
}
Widget build(BuildContext context) {
return BlocProviderTree(
blocProviders: [
BlocProvider<ApiBloc>(
bloc: apiBLoC,
),
BlocProvider<TitleBloc>(
bloc: titleBLoC,
),
],
child: Scaffold(
backgroundColor: Colors.white,
key: _scaffoldKey,
body: SafeArea(
child: SingleChildScrollView(
padding: EdgeInsets.symmetric(horizontal: 30.0),
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
crossAxisAlignment: CrossAxisAlignment.stretch,
children: <Widget>[
Form(
key: _key,
//autovalidate: _validate,
child: formUI(),
),
],
)
)
)
)
);
}
Widget formUI() {
return new Column(
children: <Widget>[
BlocBuilder(
bloc: titleBLoC,
builder: (BuildContext context, TitleState state) {
print("Build title dropdown "+state.toString());
if(state is TitleInitialState){
return DropdownButtonFormField(
//hint: Text('Select County'),
onChanged: changedTitleDropDownItem,
items: _titledropDownMenuItems,
value: _currentTitle,
decoration: InputDecoration(
labelText: 'Title',
),
validator: validateDropDown,
);
}
else if(state is SetTitleSelectedState){
title = state.selectedTitle;
return DropdownButtonFormField(
//hint: Text('Select County'),
onChanged: changedTitleDropDownItem,
items: _titledropDownMenuItems,
value: state.selectedTitle,
decoration: InputDecoration(
labelText: 'Title',
),
validator: validateDropDown,
);
}
return Container(height: 0, width: 0,);
}
),
SizedBox(
height: 10.0,
),
TextFormField(
onChanged: (value) => firstName = value,
validator: validateName,
maxLength: 20,
decoration: InputDecoration(
labelText: 'First Name ',
//errorText: "Enter First Name",
),
controller: _searchController1,
),
SizedBox(
height: 10.0,
),
TextFormField(
onChanged: (value) => middleName = value,
validator: validateName,
maxLength: 20,
decoration: InputDecoration(
labelText: 'Middle Name ',
//errorText: "Enter First Name",
),
controller: _searchController1,
),
SizedBox(
height: 10.0,
),
``` | 1.0 | Flutter TextFormField keyboard reloads all the bloc even with the proper TextEditingController - I am creating a form where, for now, I have one dropdown button and `TextFormField `. Each time I click on the `TextFormField` and the keyboard comes out I notice all the bloc are reloaded. I read some place to set the `TextEditingController` done, but still its the same yet. Below is my code snippet. How else to resolve, so that it does not reload the bloc when I click **open** and **close** the keyboard on any `TextFormField`.
```dart
class _RegisterPageState extends State<RegisterPage> with SingleTickerProviderStateMixin {
CountyListRepository _repo;
RegisterNewUserRepository _registerRepo;
GlobalKey<FormState> _key = new GlobalKey();
final GlobalKey<ScaffoldState> _scaffoldKey = new GlobalKey<ScaffoldState>();
List titles =
["Mr", "Mrs", "Miss", "Madam"];
List<DropdownMenuItem<String>> _titledropDownMenuItems;
List<DropdownMenuItem<String>> _countydropDownMenuItems2 = new List();
String _currentTitle;
String _currentCounty;
String title,firstName, middleName, surName, lastName, countyID, email, contactNo;
bool isChecked = false;
ApiBloc apiBLoC;
TitleBloc titleBLoC;
RegisternewUserBloc registernewUserBLoC;
TextEditingController _searchController1;
@override
void initState() {
_searchController1 = TextEditingController();
_titledropDownMenuItems = getDropDownMenuTitleItems();
_currentTitle = _titledropDownMenuItems[0].value;
super.initState();
_repo = new CountyListRepository();
apiBLoC = new ApiBloc(_repo);
titleBLoC = new TitleBloc();
_registerRepo = new RegisterNewUserRepository();
registernewUserBLoC = new RegisternewUserBloc(_registerRepo);
//print("Login initstate check one signa id is "+widget.localOneSignalID);
}
List<DropdownMenuItem<String>> getDropDownMenuTitleItems() {
List<DropdownMenuItem<String>> items = new List();
for (String title in titles) {
// here we are creating the drop down menu items, you can customize the item right here
// but I'll just use a simple text for this
items.add(new DropdownMenuItem(
value: title,
child: new Text(title)
));
}
return items;
}
void changedDropDownItem2(String selectedCounty) {
_currentCounty = selectedCounty;
apiBLoC.setSelected(selectedCounty);
}
void changedTitleDropDownItem(String selectedTitle) {
_currentTitle = selectedTitle;
titleBLoC.setSelected(selectedTitle);
}
@override
void dispose() {
apiBLoC.dispose();
titleBLoC.dispose();
registernewUserBLoC.dispose();
super.dispose();
}
Widget build(BuildContext context) {
return BlocProviderTree(
blocProviders: [
BlocProvider<ApiBloc>(
bloc: apiBLoC,
),
BlocProvider<TitleBloc>(
bloc: titleBLoC,
),
],
child: Scaffold(
backgroundColor: Colors.white,
key: _scaffoldKey,
body: SafeArea(
child: SingleChildScrollView(
padding: EdgeInsets.symmetric(horizontal: 30.0),
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
crossAxisAlignment: CrossAxisAlignment.stretch,
children: <Widget>[
Form(
key: _key,
//autovalidate: _validate,
child: formUI(),
),
],
)
)
)
)
);
}
Widget formUI() {
return new Column(
children: <Widget>[
BlocBuilder(
bloc: titleBLoC,
builder: (BuildContext context, TitleState state) {
print("Build title dropdown "+state.toString());
if(state is TitleInitialState){
return DropdownButtonFormField(
//hint: Text('Select County'),
onChanged: changedTitleDropDownItem,
items: _titledropDownMenuItems,
value: _currentTitle,
decoration: InputDecoration(
labelText: 'Title',
),
validator: validateDropDown,
);
}
else if(state is SetTitleSelectedState){
title = state.selectedTitle;
return DropdownButtonFormField(
//hint: Text('Select County'),
onChanged: changedTitleDropDownItem,
items: _titledropDownMenuItems,
value: state.selectedTitle,
decoration: InputDecoration(
labelText: 'Title',
),
validator: validateDropDown,
);
}
return Container(height: 0, width: 0,);
}
),
SizedBox(
height: 10.0,
),
TextFormField(
onChanged: (value) => firstName = value,
validator: validateName,
maxLength: 20,
decoration: InputDecoration(
labelText: 'First Name ',
//errorText: "Enter First Name",
),
controller: _searchController1,
),
SizedBox(
height: 10.0,
),
TextFormField(
onChanged: (value) => middleName = value,
validator: validateName,
maxLength: 20,
decoration: InputDecoration(
labelText: 'Middle Name ',
//errorText: "Enter First Name",
),
controller: _searchController1,
),
SizedBox(
height: 10.0,
),
``` | design | flutter textformfield keyboard reloads all the bloc even with the proper texteditingcontroller i am creating a form where for now i have one dropdown button and textformfield each time i click on the textformfield and the keyboard comes out i notice all the bloc are reloaded i read some place to set the texteditingcontroller done but still its the same yet below is my code snippet how else to resolve so that it does not reload the bloc when i click open and close the keyboard on any textformfield dart class registerpagestate extends state with singletickerproviderstatemixin countylistrepository repo registernewuserrepository registerrepo globalkey key new globalkey final globalkey scaffoldkey new globalkey list titles list titledropdownmenuitems list new list string currenttitle string currentcounty string title firstname middlename surname lastname countyid email contactno bool ischecked false apibloc apibloc titlebloc titlebloc registernewuserbloc registernewuserbloc texteditingcontroller override void initstate texteditingcontroller titledropdownmenuitems getdropdownmenutitleitems currenttitle titledropdownmenuitems value super initstate repo new countylistrepository apibloc new apibloc repo titlebloc new titlebloc registerrepo new registernewuserrepository registernewuserbloc new registernewuserbloc registerrepo print login initstate check one signa id is widget localonesignalid list getdropdownmenutitleitems list items new list for string title in titles here we are creating the drop down menu items you can customize the item right here but i ll just use a simple text for this items add new dropdownmenuitem value title child new text title return items void string selectedcounty currentcounty selectedcounty apibloc setselected selectedcounty void changedtitledropdownitem string selectedtitle currenttitle selectedtitle titlebloc setselected selectedtitle override void dispose apibloc dispose titlebloc dispose registernewuserbloc dispose super dispose widget build buildcontext context return blocprovidertree blocproviders blocprovider bloc apibloc blocprovider bloc titlebloc child scaffold backgroundcolor colors white key scaffoldkey body safearea child singlechildscrollview padding edgeinsets symmetric horizontal child column mainaxisalignment mainaxisalignment center crossaxisalignment crossaxisalignment stretch children form key key autovalidate validate child formui widget formui return new column children blocbuilder bloc titlebloc builder buildcontext context titlestate state print build title dropdown state tostring if state is titleinitialstate return dropdownbuttonformfield hint text select county onchanged changedtitledropdownitem items titledropdownmenuitems value currenttitle decoration inputdecoration labeltext title validator validatedropdown else if state is settitleselectedstate title state selectedtitle return dropdownbuttonformfield hint text select county onchanged changedtitledropdownitem items titledropdownmenuitems value state selectedtitle decoration inputdecoration labeltext title validator validatedropdown return container height width sizedbox height textformfield onchanged value firstname value validator validatename maxlength decoration inputdecoration labeltext first name errortext enter first name controller sizedbox height textformfield onchanged value middlename value validator validatename maxlength decoration inputdecoration labeltext middle name errortext enter first name controller sizedbox height | 1 |
10,752 | 2,963,385,550 | IssuesEvent | 2015-07-10 09:59:50 | mysociety/alaveteli | https://api.github.com/repos/mysociety/alaveteli | closed | Design whitelabel and alavetelitheme versions of an HTML widget to go on other sites | design eu | AskTheEU version visible at http://www.asktheeu.org/en/request/651/widget
<!---
@huboard:{"order":1947.0,"milestone_order":2044,"custom_state":"blocked"}
-->
| 1.0 | Design whitelabel and alavetelitheme versions of an HTML widget to go on other sites - AskTheEU version visible at http://www.asktheeu.org/en/request/651/widget
<!---
@huboard:{"order":1947.0,"milestone_order":2044,"custom_state":"blocked"}
-->
| design | design whitelabel and alavetelitheme versions of an html widget to go on other sites asktheeu version visible at huboard order milestone order custom state blocked | 1 |
26,444 | 4,710,673,233 | IssuesEvent | 2016-10-14 11:02:08 | bridgedotnet/Bridge | https://api.github.com/repos/bridgedotnet/Bridge | closed | Bridge.fn.bind produce a memory leaks | defect | http://deck.net/cb3d8869609e9184beb85ad401227711
Bridge.fn.bind(obj, method) save reference to the "obj" into "method.$$bind" and keep it forever. This can produce huge memory leaks.
Solution:
```js
#before
Bridge.fn.bind(obj, obj.method)
#after
(obj.method = Bridge.fn.bind(obj, obj.method))
```
this will replace instance method property with a new bounded function.
| 1.0 | Bridge.fn.bind produce a memory leaks - http://deck.net/cb3d8869609e9184beb85ad401227711
Bridge.fn.bind(obj, method) save reference to the "obj" into "method.$$bind" and keep it forever. This can produce huge memory leaks.
Solution:
```js
#before
Bridge.fn.bind(obj, obj.method)
#after
(obj.method = Bridge.fn.bind(obj, obj.method))
```
this will replace instance method property with a new bounded function.
| non_design | bridge fn bind produce a memory leaks bridge fn bind obj method save reference to the obj into method bind and keep it forever this can produce huge memory leaks solution js before bridge fn bind obj obj method after obj method bridge fn bind obj obj method this will replace instance method property with a new bounded function | 0 |
80,903 | 30,591,609,181 | IssuesEvent | 2023-07-21 17:33:47 | dotCMS/core | https://api.github.com/repos/dotCMS/core | opened | Variable Typo in Block Editor | Type : Defect Triage | ### Parent Issue
_No response_
### Problem Statement
The word count and character count variables that currently appear in the Block Editor are, respectively, `wordCount` and `chartCount`. I think the second one should probably be `charCount`.
I made a PR to rectify it: https://github.com/dotCMS/core/pull/25589
However, I'm just opening up this Issue in case there's discussion needed re: the existing `chartCount` variables in the existing Block Editors out in the wild.
Does something like this require a UT? Is it reasonable to believe it will correct itself over time?
I'll include a minor breaking change entry in the following release notes, too, in case anyone has done any development using that data.
### Steps to Reproduce
N/A
### Acceptance Criteria
Just making sure that there are no dangers or snags.
### dotCMS Version
22.12 - 23.07
### Proposed Objective
Technical User Experience
### Proposed Priority
Priority 4 - Trivial
### External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
_No response_
### Assumptions & Initiation Needs
_No response_
### Quality Assurance Notes & Workarounds
_No response_
### Sub-Tasks & Estimates
_No response_ | 1.0 | Variable Typo in Block Editor - ### Parent Issue
_No response_
### Problem Statement
The word count and character count variables that currently appear in the Block Editor are, respectively, `wordCount` and `chartCount`. I think the second one should probably be `charCount`.
I made a PR to rectify it: https://github.com/dotCMS/core/pull/25589
However, I'm just opening up this Issue in case there's discussion needed re: the existing `chartCount` variables in the existing Block Editors out in the wild.
Does something like this require a UT? Is it reasonable to believe it will correct itself over time?
I'll include a minor breaking change entry in the following release notes, too, in case anyone has done any development using that data.
### Steps to Reproduce
N/A
### Acceptance Criteria
Just making sure that there are no dangers or snags.
### dotCMS Version
22.12 - 23.07
### Proposed Objective
Technical User Experience
### Proposed Priority
Priority 4 - Trivial
### External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
_No response_
### Assumptions & Initiation Needs
_No response_
### Quality Assurance Notes & Workarounds
_No response_
### Sub-Tasks & Estimates
_No response_ | non_design | variable typo in block editor parent issue no response problem statement the word count and character count variables that currently appear in the block editor are respectively wordcount and chartcount i think the second one should probably be charcount i made a pr to rectify it however i m just opening up this issue in case there s discussion needed re the existing chartcount variables in the existing block editors out in the wild does something like this require a ut is it reasonable to believe it will correct itself over time i ll include a minor breaking change entry in the following release notes too in case anyone has done any development using that data steps to reproduce n a acceptance criteria just making sure that there are no dangers or snags dotcms version proposed objective technical user experience proposed priority priority trivial external links slack conversations support tickets figma designs etc no response assumptions initiation needs no response quality assurance notes workarounds no response sub tasks estimates no response | 0 |
74,037 | 8,961,521,204 | IssuesEvent | 2019-01-28 09:53:16 | SharePoint/sp-dev-docs | https://api.github.com/repos/SharePoint/sp-dev-docs | closed | Site design for team site not applying theme | Needs: Triage :mag: area:site-design | #### Category
- [ ] Question
- [ ] Typo
- [x] Bug
- [ ] Additional article idea
#### Expected or Desired Behavior
I've created a simple site script to set the theme and regional settings. I've deployed this as a team site design with the -IsDefault switch. I'm expecting the theme and regional settings are applied when a team site is created.
#### Observed Behavior
The regional settings are applied but the theme isn't. When I go to the change the look menu it is empty.
If I do the same with a communication site the theme is applied correctly.
#### Steps to Reproduce
1. Create site script with applyTheme and setRegionalSettings verbs.
2. Deploy script and design using PowerShell and the -IsDefault switch.
3. Create new team site.
| 1.0 | Site design for team site not applying theme - #### Category
- [ ] Question
- [ ] Typo
- [x] Bug
- [ ] Additional article idea
#### Expected or Desired Behavior
I've created a simple site script to set the theme and regional settings. I've deployed this as a team site design with the -IsDefault switch. I'm expecting the theme and regional settings are applied when a team site is created.
#### Observed Behavior
The regional settings are applied but the theme isn't. When I go to the change the look menu it is empty.
If I do the same with a communication site the theme is applied correctly.
#### Steps to Reproduce
1. Create site script with applyTheme and setRegionalSettings verbs.
2. Deploy script and design using PowerShell and the -IsDefault switch.
3. Create new team site.
| design | site design for team site not applying theme category question typo bug additional article idea expected or desired behavior i ve created a simple site script to set the theme and regional settings i ve deployed this as a team site design with the isdefault switch i m expecting the theme and regional settings are applied when a team site is created observed behavior the regional settings are applied but the theme isn t when i go to the change the look menu it is empty if i do the same with a communication site the theme is applied correctly steps to reproduce create site script with applytheme and setregionalsettings verbs deploy script and design using powershell and the isdefault switch create new team site | 1 |
2,124 | 2,590,224,027 | IssuesEvent | 2015-02-18 17:36:29 | paulkore/moneytracker | https://api.github.com/repos/paulkore/moneytracker | opened | Replace the "EDIT" links with button on event records | design enhancement | Currently each record in the event view has an "edit" link that sends the user to the record's form.
This doesn't look appropriate (it's kind of outdated).
I suggest replacing the link with a button.
Note that this needs to be executed differently in the two available views (desktop and mobile).
| 1.0 | Replace the "EDIT" links with button on event records - Currently each record in the event view has an "edit" link that sends the user to the record's form.
This doesn't look appropriate (it's kind of outdated).
I suggest replacing the link with a button.
Note that this needs to be executed differently in the two available views (desktop and mobile).
| design | replace the edit links with button on event records currently each record in the event view has an edit link that sends the user to the record s form this doesn t look appropriate it s kind of outdated i suggest replacing the link with a button note that this needs to be executed differently in the two available views desktop and mobile | 1 |
425,223 | 29,239,671,126 | IssuesEvent | 2023-05-23 00:52:55 | bit-bangin/GetYouTubeTranscript | https://api.github.com/repos/bit-bangin/GetYouTubeTranscript | closed | Gather requirements | documentation | - Determine functional requirements (what the system should accomplish).
- Determine nonfunctional requirements (how the system should behave).
- Inclusive of performance, security, user experience.
- Consider constraints | 1.0 | Gather requirements - - Determine functional requirements (what the system should accomplish).
- Determine nonfunctional requirements (how the system should behave).
- Inclusive of performance, security, user experience.
- Consider constraints | non_design | gather requirements determine functional requirements what the system should accomplish determine nonfunctional requirements how the system should behave inclusive of performance security user experience consider constraints | 0 |
79,523 | 28,356,523,862 | IssuesEvent | 2023-04-12 07:45:57 | zed-industries/community | https://api.github.com/repos/zed-industries/community | closed | Go to definition is not working (golang) | defect go language | ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
- just open go project and it's working at the first place
- go language server is already installed
### Environment
Zed: v0.80.5 (stable)
OS: macOS 13.3.0
Memory: 16 GiB
Architecture: aarch64
### If applicable, add mockups / screenshots to help explain present your vision of the feature
_No response_
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
```
no views in session
2023-04-06T02:54:41 [ERROR] no views in session
2023-04-06T02:54:41 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:42 [ERROR] no views in session
2023-04-06T02:54:42 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:42 [ERROR] no views in session
2023-04-06T02:54:42 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:45 [ERROR] no views in session
2023-04-06T02:54:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:45 [ERROR] no views in session
2023-04-06T02:54:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:47 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:47 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:47 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:49 [ERROR] no views in session
2023-04-06T02:54:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:49 [ERROR] no views in session
2023-04-06T02:54:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:52 [ERROR] no views in session
2023-04-06T02:54:52 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:52 [ERROR] no views in session
2023-04-06T02:54:52 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:52 [ERROR] no views in session
2023-04-06T02:54:52 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:53 [ERROR] failed to format via language server
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
2023-04-06T03:03:58 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:35 [ERROR] no views in session
2023-04-06T03:24:35 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:36 [ERROR] no views in session
2023-04-06T03:24:36 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:38 [ERROR] no views in session
2023-04-06T03:24:38 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:38 [ERROR] no views in session
2023-04-06T03:24:38 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:39 [ERROR] no views in session
2023-04-06T03:24:39 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:40 [ERROR] no views in session
2023-04-06T03:24:40 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:45 [ERROR] no views in session
2023-04-06T03:24:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:45 [ERROR] no views in session
2023-04-06T03:24:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:46 [ERROR] no views in session
2023-04-06T03:24:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:46 [ERROR] no views in session
2023-04-06T03:24:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:47 [ERROR] no views in session
2023-04-06T03:24:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:47 [ERROR] no views in session
2023-04-06T03:24:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:47 [ERROR] no views in session
2023-04-06T03:24:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:48 [ERROR] no views in session
2023-04-06T03:24:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:50 [ERROR] no views in session
2023-04-06T03:24:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:51 [ERROR] no views in session
2023-04-06T03:24:58 [ERROR] no views in session
2023-04-06T03:24:58 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:59 [ERROR] no views in session
2023-04-06T03:24:59 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:59 [ERROR] no views in session
2023-04-06T03:24:59 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:00 [ERROR] no views in session
2023-04-06T03:25:00 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:00 [ERROR] no views in session
2023-04-06T03:25:00 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:02 [ERROR] no views in session
2023-04-06T03:25:02 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:02 [ERROR] no views in session
2023-04-06T03:25:02 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:03 [ERROR] no views in session
2023-04-06T03:25:03 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:03 [ERROR] no views in session
2023-04-06T03:25:03 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:04 [ERROR] no views in session
2023-04-06T03:25:04 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] no views in session
2023-04-06T03:25:05 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] no views in session
2023-04-06T03:25:06 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:06 [ERROR] no views in session
2023-04-06T03:25:07 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:07 [ERROR] no views in session
2023-04-06T03:25:08 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:08 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:08 [ERROR] no views in session
2023-04-06T03:25:09 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:09 [ERROR] no views in session
2023-04-06T03:25:15 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:15 [ERROR] no views in session
2023-04-06T03:25:16 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:16 [ERROR] no views in session
2023-04-06T03:25:17 [ERROR] no views in session
2023-04-06T03:25:17 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:17 [ERROR] no views in session
2023-04-06T03:25:17 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:18 [ERROR] no views in session
2023-04-06T03:25:18 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] no views in session
2023-04-06T03:25:19 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] no views in session
2023-04-06T03:25:20 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] no views in session
2023-04-06T03:25:20 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] no views in session
2023-04-06T03:25:20 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:23 [ERROR] no views in session
2023-04-06T03:25:23 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:24 [ERROR] no views in session
2023-04-06T03:25:24 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:25 [ERROR] no views in session
2023-04-06T03:25:25 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:25 [ERROR] no views in session
2023-04-06T03:25:25 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:26 [ERROR] no views in session
2023-04-06T03:25:26 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:26 [ERROR] no views in session
2023-04-06T03:25:26 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:48 [ERROR] no views in session
2023-04-06T03:29:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:48 [ERROR] no views in session
2023-04-06T03:29:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:49 [ERROR] no views in session
2023-04-06T03:29:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:51 [ERROR] no views in session
2023-04-06T03:29:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:52 [ERROR] no views in session
2023-04-06T03:29:52 [ERROR] lsp request failed
Caused by:
no views in session
``` | 1.0 | Go to definition is not working (golang) - ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
- just open go project and it's working at the first place
- go language server is already installed
### Environment
Zed: v0.80.5 (stable)
OS: macOS 13.3.0
Memory: 16 GiB
Architecture: aarch64
### If applicable, add mockups / screenshots to help explain present your vision of the feature
_No response_
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
```
no views in session
2023-04-06T02:54:41 [ERROR] no views in session
2023-04-06T02:54:41 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:42 [ERROR] no views in session
2023-04-06T02:54:42 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:42 [ERROR] no views in session
2023-04-06T02:54:42 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:43 [ERROR] no views in session
2023-04-06T02:54:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:44 [ERROR] no views in session
2023-04-06T02:54:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:45 [ERROR] no views in session
2023-04-06T02:54:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:45 [ERROR] no views in session
2023-04-06T02:54:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:46 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:47 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:47 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:47 [ERROR] no views in session
2023-04-06T02:54:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:48 [ERROR] no views in session
2023-04-06T02:54:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:49 [ERROR] no views in session
2023-04-06T02:54:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:49 [ERROR] no views in session
2023-04-06T02:54:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:50 [ERROR] no views in session
2023-04-06T02:54:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:51 [ERROR] no views in session
2023-04-06T02:54:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:52 [ERROR] no views in session
2023-04-06T02:54:52 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:52 [ERROR] no views in session
2023-04-06T02:54:52 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:52 [ERROR] no views in session
2023-04-06T02:54:52 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:53 [ERROR] failed to format via language server
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T02:54:54 [ERROR] lsp request failed
2023-04-06T03:03:58 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:31 [ERROR] no views in session
2023-04-06T03:24:31 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:32 [ERROR] no views in session
2023-04-06T03:24:32 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:33 [ERROR] no views in session
2023-04-06T03:24:33 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:35 [ERROR] no views in session
2023-04-06T03:24:35 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:36 [ERROR] no views in session
2023-04-06T03:24:36 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:37 [ERROR] no views in session
2023-04-06T03:24:37 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:38 [ERROR] no views in session
2023-04-06T03:24:38 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:38 [ERROR] no views in session
2023-04-06T03:24:38 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:39 [ERROR] no views in session
2023-04-06T03:24:39 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:40 [ERROR] no views in session
2023-04-06T03:24:40 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:45 [ERROR] no views in session
2023-04-06T03:24:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:45 [ERROR] no views in session
2023-04-06T03:24:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:46 [ERROR] no views in session
2023-04-06T03:24:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:46 [ERROR] no views in session
2023-04-06T03:24:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:47 [ERROR] no views in session
2023-04-06T03:24:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:47 [ERROR] no views in session
2023-04-06T03:24:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:47 [ERROR] no views in session
2023-04-06T03:24:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:48 [ERROR] no views in session
2023-04-06T03:24:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:50 [ERROR] no views in session
2023-04-06T03:24:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:51 [ERROR] no views in session
2023-04-06T03:24:58 [ERROR] no views in session
2023-04-06T03:24:58 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:59 [ERROR] no views in session
2023-04-06T03:24:59 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:24:59 [ERROR] no views in session
2023-04-06T03:24:59 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:00 [ERROR] no views in session
2023-04-06T03:25:00 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:00 [ERROR] no views in session
2023-04-06T03:25:00 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:02 [ERROR] no views in session
2023-04-06T03:25:02 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:02 [ERROR] no views in session
2023-04-06T03:25:02 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:03 [ERROR] no views in session
2023-04-06T03:25:03 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:03 [ERROR] no views in session
2023-04-06T03:25:03 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:04 [ERROR] no views in session
2023-04-06T03:25:04 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] no views in session
2023-04-06T03:25:05 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:05 [ERROR] no views in session
2023-04-06T03:25:06 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:06 [ERROR] no views in session
2023-04-06T03:25:07 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:07 [ERROR] no views in session
2023-04-06T03:25:08 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:08 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:08 [ERROR] no views in session
2023-04-06T03:25:09 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:09 [ERROR] no views in session
2023-04-06T03:25:15 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:15 [ERROR] no views in session
2023-04-06T03:25:16 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:16 [ERROR] no views in session
2023-04-06T03:25:17 [ERROR] no views in session
2023-04-06T03:25:17 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:17 [ERROR] no views in session
2023-04-06T03:25:17 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:18 [ERROR] no views in session
2023-04-06T03:25:18 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] no views in session
2023-04-06T03:25:19 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:19 [ERROR] no views in session
2023-04-06T03:25:20 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] no views in session
2023-04-06T03:25:20 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] lsp completion request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] no views in session
2023-04-06T03:25:20 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:20 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:21 [ERROR] no views in session
2023-04-06T03:25:21 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:23 [ERROR] no views in session
2023-04-06T03:25:23 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:24 [ERROR] no views in session
2023-04-06T03:25:24 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:25 [ERROR] no views in session
2023-04-06T03:25:25 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:25 [ERROR] no views in session
2023-04-06T03:25:25 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:26 [ERROR] no views in session
2023-04-06T03:25:26 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:25:26 [ERROR] no views in session
2023-04-06T03:25:26 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] no views in session
2023-04-06T03:27:43 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:44 [ERROR] no views in session
2023-04-06T03:27:44 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:45 [ERROR] lsp request failed
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:46 [ERROR] no views in session
2023-04-06T03:27:46 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:47 [ERROR] lsp request failed
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:48 [ERROR] no views in session
2023-04-06T03:27:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:49 [ERROR] no views in session
2023-04-06T03:27:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:27:50 [ERROR] no views in session
2023-04-06T03:27:50 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:29 [ERROR] no views in session
2023-04-06T03:29:29 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:48 [ERROR] no views in session
2023-04-06T03:29:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:48 [ERROR] no views in session
2023-04-06T03:29:48 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:49 [ERROR] no views in session
2023-04-06T03:29:49 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:51 [ERROR] no views in session
2023-04-06T03:29:51 [ERROR] lsp request failed
Caused by:
no views in session
2023-04-06T03:29:52 [ERROR] no views in session
2023-04-06T03:29:52 [ERROR] lsp request failed
Caused by:
no views in session
``` | non_design | go to definition is not working golang check for existing issues completed describe the bug provide steps to reproduce it just open go project and it s working at the first place go language server is already installed environment zed stable os macos memory gib architecture if applicable add mockups screenshots to help explain present your vision of the feature no response if applicable attach your library logs zed zed log file to this issue if you only need the most recent lines you can run the zed open log command palette action to see the last no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session failed to format via language server caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed caused by no views in session lsp completion request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp completion request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp completion request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed caused by no views in session lsp completion request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp completion request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp completion request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session lsp request failed no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session no views in session lsp request failed caused by no views in session | 0 |
68,190 | 8,229,270,754 | IssuesEvent | 2018-09-07 08:51:45 | jungvonmatt/amp.dev | https://api.github.com/repos/jungvonmatt/amp.dev | opened | Refine text stylings | department:design department:development type:improvement | ## Objective
The text stylings that have already been implemented (namely CM_Copy) need to be refined in close consultation with the design dept.
## Background
While looking at the demo site for [CM_Copy](https://jungvonmatt.github.io/amp.dev/styleguide/molecules/copy.html) the styles need to be adjusted in a way they fit the updated design of BCM_Headline and BCM_Copy.
## Tasks
- [ ] Check current implementation for differences to updated design
- [ ] Update implementation
| 1.0 | Refine text stylings - ## Objective
The text stylings that have already been implemented (namely CM_Copy) need to be refined in close consultation with the design dept.
## Background
While looking at the demo site for [CM_Copy](https://jungvonmatt.github.io/amp.dev/styleguide/molecules/copy.html) the styles need to be adjusted in a way they fit the updated design of BCM_Headline and BCM_Copy.
## Tasks
- [ ] Check current implementation for differences to updated design
- [ ] Update implementation
| design | refine text stylings objective the text stylings that have already been implemented namely cm copy need to be refined in close consultation with the design dept background while looking at the demo site for the styles need to be adjusted in a way they fit the updated design of bcm headline and bcm copy tasks check current implementation for differences to updated design update implementation | 1 |
101,744 | 12,704,442,749 | IssuesEvent | 2020-06-23 01:26:11 | ropensci/drake | https://api.github.com/repos/ropensci/drake | closed | Handle drake_config objects more rigorously | difficulty: advanced topic: design | ## Prework
- [x] Read and abide by `drake`'s [code of conduct](https://github.com/ropensci/drake/blob/master/CODE_OF_CONDUCT.md).
- [x] Search for duplicates among the [existing issues](https://github.com/ropensci/drake/issues), both open and closed.
## Description
We should add more rigor and validation to `drake_config()` objects, similar to #1183. And we should prevent other methods from wrecking the structure, re #1190.
| 1.0 | Handle drake_config objects more rigorously - ## Prework
- [x] Read and abide by `drake`'s [code of conduct](https://github.com/ropensci/drake/blob/master/CODE_OF_CONDUCT.md).
- [x] Search for duplicates among the [existing issues](https://github.com/ropensci/drake/issues), both open and closed.
## Description
We should add more rigor and validation to `drake_config()` objects, similar to #1183. And we should prevent other methods from wrecking the structure, re #1190.
| design | handle drake config objects more rigorously prework read and abide by drake s search for duplicates among the both open and closed description we should add more rigor and validation to drake config objects similar to and we should prevent other methods from wrecking the structure re | 1 |
54,936 | 6,883,581,112 | IssuesEvent | 2017-11-21 09:54:58 | consul/consul | https://api.github.com/repos/consul/consul | opened | Allow admins to send global / massive notifications | needs design | Admins need to be able to send notifications to all users or to a subset of them filtered by different criteria like validation status, geozone, etc... seems like the criteria will be so different and complex that just being able to "select all users/authors" on existing features and going to a "Send notifications" panel from there would be the best option. We need some UI/UX design around it | 1.0 | Allow admins to send global / massive notifications - Admins need to be able to send notifications to all users or to a subset of them filtered by different criteria like validation status, geozone, etc... seems like the criteria will be so different and complex that just being able to "select all users/authors" on existing features and going to a "Send notifications" panel from there would be the best option. We need some UI/UX design around it | design | allow admins to send global massive notifications admins need to be able to send notifications to all users or to a subset of them filtered by different criteria like validation status geozone etc seems like the criteria will be so different and complex that just being able to select all users authors on existing features and going to a send notifications panel from there would be the best option we need some ui ux design around it | 1 |
58,126 | 7,125,363,275 | IssuesEvent | 2018-01-19 22:40:42 | EricKip254/SDP | https://api.github.com/repos/EricKip254/SDP | closed | Function-2 | Coding Design Documentation Testing | Write the definition of a value-returning function that inputs data into a variable of type
tourType. | 1.0 | Function-2 - Write the definition of a value-returning function that inputs data into a variable of type
tourType. | design | function write the definition of a value returning function that inputs data into a variable of type tourtype | 1 |
200,477 | 15,108,828,602 | IssuesEvent | 2021-02-08 17:05:25 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | E2E Spec Failures for WordPress with Nested Themes | [Package] E2E Tests | <!--
Please fill out ALL required sections. Bug reports with missing information will
be closed.
Before submitting a bug report:
- Check if the bug has already been fixed by updating WordPress and/or Gutenberg.
- Check if the bug is caused by a plugin by deactivating all plugins except Gutenberg.
- Check if the bug is caused by a theme by activating a default theme e.g. Twenty Twenty.
- Check if the bug has already been reported by searching https://github.com/WordPress/gutenberg/issues.
If this is a security issue, please report it in HackerOne instead:
https://hackerone.com/wordpress
-->
## Description
<!-- Please write a brief description of the bug. -->
When running e2e specs in a wordpress instance where themes live in a nested directory (Ex. `wp-content/themes/nested/seedlet-blocks` instead of `wp-content/themes/seedlet-blocks`), various e2e specs fail
## Step-by-step reproduction instructions
<!--
Please list the steps needed to reproduce the bug. For example:
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
-->
- Select a block theme that enables site editing
- Visit site editor in IE11 browser
## Screenshots or screen recording (optional)
<!--
If possible, please upload a screenshot or screen recording which demonstrates
the bug. You can use LIEcap to create a GIF screen recording:
https://www.cockos.com/licecap/
-->
## WordPress information
- WordPress version: 5.7-alpha-49962
- Gutenberg version: Dev version up to commit 6accb5b
- Are all plugins except Gutenberg deactivated? Yes
- Are you using a default theme (e.g. Twenty Twenty-One)? No (Using TT1-blocks)
## Device information
- Device: Macbook Pro
- Operating system: macOS Big Sur 11.0.1
- Browser: IE11
| 1.0 | E2E Spec Failures for WordPress with Nested Themes - <!--
Please fill out ALL required sections. Bug reports with missing information will
be closed.
Before submitting a bug report:
- Check if the bug has already been fixed by updating WordPress and/or Gutenberg.
- Check if the bug is caused by a plugin by deactivating all plugins except Gutenberg.
- Check if the bug is caused by a theme by activating a default theme e.g. Twenty Twenty.
- Check if the bug has already been reported by searching https://github.com/WordPress/gutenberg/issues.
If this is a security issue, please report it in HackerOne instead:
https://hackerone.com/wordpress
-->
## Description
<!-- Please write a brief description of the bug. -->
When running e2e specs in a wordpress instance where themes live in a nested directory (Ex. `wp-content/themes/nested/seedlet-blocks` instead of `wp-content/themes/seedlet-blocks`), various e2e specs fail
## Step-by-step reproduction instructions
<!--
Please list the steps needed to reproduce the bug. For example:
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
-->
- Select a block theme that enables site editing
- Visit site editor in IE11 browser
## Screenshots or screen recording (optional)
<!--
If possible, please upload a screenshot or screen recording which demonstrates
the bug. You can use LIEcap to create a GIF screen recording:
https://www.cockos.com/licecap/
-->
## WordPress information
- WordPress version: 5.7-alpha-49962
- Gutenberg version: Dev version up to commit 6accb5b
- Are all plugins except Gutenberg deactivated? Yes
- Are you using a default theme (e.g. Twenty Twenty-One)? No (Using TT1-blocks)
## Device information
- Device: Macbook Pro
- Operating system: macOS Big Sur 11.0.1
- Browser: IE11
| non_design | spec failures for wordpress with nested themes please fill out all required sections bug reports with missing information will be closed before submitting a bug report check if the bug has already been fixed by updating wordpress and or gutenberg check if the bug is caused by a plugin by deactivating all plugins except gutenberg check if the bug is caused by a theme by activating a default theme e g twenty twenty check if the bug has already been reported by searching if this is a security issue please report it in hackerone instead description when running specs in a wordpress instance where themes live in a nested directory ex wp content themes nested seedlet blocks instead of wp content themes seedlet blocks various specs fail step by step reproduction instructions please list the steps needed to reproduce the bug for example go to click on scroll down to select a block theme that enables site editing visit site editor in browser screenshots or screen recording optional if possible please upload a screenshot or screen recording which demonstrates the bug you can use liecap to create a gif screen recording wordpress information wordpress version alpha gutenberg version dev version up to commit are all plugins except gutenberg deactivated yes are you using a default theme e g twenty twenty one no using blocks device information device macbook pro operating system macos big sur browser | 0 |
20,267 | 3,574,701,493 | IssuesEvent | 2016-01-27 13:08:59 | ThibaultLatrille/ControverSciences | https://api.github.com/repos/ThibaultLatrille/ControverSciences | closed | Accueil 3 | **** urgent design | Ah. Un autre détail, les icones dans la partie contribuer sont floues ^^
Sur la page https://www.controversciences.org/
Par : P. Guille Escuret
Navigateur : chrome modern linux webkit | 1.0 | Accueil 3 - Ah. Un autre détail, les icones dans la partie contribuer sont floues ^^
Sur la page https://www.controversciences.org/
Par : P. Guille Escuret
Navigateur : chrome modern linux webkit | design | accueil ah un autre détail les icones dans la partie contribuer sont floues sur la page par p guille escuret navigateur chrome modern linux webkit | 1 |
166,378 | 26,345,932,956 | IssuesEvent | 2023-01-10 22:04:14 | ephios-dev/ephios | https://api.github.com/repos/ephios-dev/ephios | closed | Filter event list | [P] major [C] feature [C] design/ui | As a user, I expect the event list to offer the follwing filters:
- event type
- search field
Possible filters (consider keeping the UI slight)
- state of my participation / can I sign up?
- calendar (prior to/after selected date) | 1.0 | Filter event list - As a user, I expect the event list to offer the follwing filters:
- event type
- search field
Possible filters (consider keeping the UI slight)
- state of my participation / can I sign up?
- calendar (prior to/after selected date) | design | filter event list as a user i expect the event list to offer the follwing filters event type search field possible filters consider keeping the ui slight state of my participation can i sign up calendar prior to after selected date | 1 |
35,657 | 14,792,762,684 | IssuesEvent | 2021-01-12 15:07:30 | ONRR/onrr.gov-site | https://api.github.com/repos/ONRR/onrr.gov-site | closed | User would like changes to be made to two webpages. | Service Now maintenance | Page updates https://www.onrr.gov/IndianServices/index.htm:
1. "The mission of the State and Indian Outreach is to serve as an advocate for the fulfillment of ONRR trust responsibility and to resolve Indian mineral issues."
Can you please change "the State" to "FIMO", please?
Page Updates https://www.onrr.gov/IndianServices/index.htm:
2. "These regularly scheduled outreach meetings enable us to answer questions, listen to concerns and suggestions for improvement, and identify and resolve mineral-related problems in partnership with the Department of the Interior's Bureau of Indian Affairs, Bureau of Land Management, and Office of the Special Trustee for American Indians."
"Office of Special Trustee for American Indians" needs to be changed to "Bureau of Trust Funds Administration." | 1.0 | User would like changes to be made to two webpages. - Page updates https://www.onrr.gov/IndianServices/index.htm:
1. "The mission of the State and Indian Outreach is to serve as an advocate for the fulfillment of ONRR trust responsibility and to resolve Indian mineral issues."
Can you please change "the State" to "FIMO", please?
Page Updates https://www.onrr.gov/IndianServices/index.htm:
2. "These regularly scheduled outreach meetings enable us to answer questions, listen to concerns and suggestions for improvement, and identify and resolve mineral-related problems in partnership with the Department of the Interior's Bureau of Indian Affairs, Bureau of Land Management, and Office of the Special Trustee for American Indians."
"Office of Special Trustee for American Indians" needs to be changed to "Bureau of Trust Funds Administration." | non_design | user would like changes to be made to two webpages page updates the mission of the state and indian outreach is to serve as an advocate for the fulfillment of onrr trust responsibility and to resolve indian mineral issues can you please change the state to fimo please page updates these regularly scheduled outreach meetings enable us to answer questions listen to concerns and suggestions for improvement and identify and resolve mineral related problems in partnership with the department of the interior s bureau of indian affairs bureau of land management and office of the special trustee for american indians office of special trustee for american indians needs to be changed to bureau of trust funds administration | 0 |
65,108 | 7,856,622,230 | IssuesEvent | 2018-06-21 08:13:19 | greatnewcls/HLNLL3FFR3NVETEIL4MMB55N | https://api.github.com/repos/greatnewcls/HLNLL3FFR3NVETEIL4MMB55N | reopened | BEN/Grj2IkqXS0bEHVo5TBWCRGaNcuG1LtgVBN5CJo9WskTruh0apcYflsiQVkxwY2y1Scu9wp5USKR+3jW9H81HzDMoxBqh7ZSxhrEhPfvlslXMPBEOlzuqdd85oj3TMw/IzmKeWuWT2TLVKJ7zVEgnAo6a2B0N3qQPvuw7myI= | design | FwNk5RdeuQgTGL7KpoIFjsoquL0LoPYUFYOhN5upnX+6GjUZdrKjq2d5CnZgs+tmfDRX2XMEFrYvbrn78ndd5wl6aQc0l+npHisIXx99tDrzMCqlvloYlcflnC38sefZ+L2krc994zx79bPXBC4uRQdf0pa5kOYwmn2aLQz8gSl2W5m45FOY3R7Ri4y8/dbZu/vMFZmS2ngTnD+WGrdvfvPGT11ycjaHJbMOX11wgv7OAfE9DDJgXzTihWMdtxAR84ZJkbjPnWYX/ARrKI3RWkWJBjHgt3/iIVBmNlmO8qla/CkiYJfUjqLm+GEBTXCOijsZGHZ+gZi7g2nypI7eC8Y+4MFGG6dtpCk6Au33gnC39fd97vSzxoWOxChsMbC7aYfJ5ft6RTe5M00ex36AaybeyzuwvobqHUMb7eZhohCAPCEGtAwKmpp41zda1Z6OEYzOOG0t6GD0kYd2jwaljzURZoyCOi0SUgrMVEgo95dufqTl7jMPnVxBKyLKp0nnqhipdGFJ/cUebIf87Hg3b9UtN55iLKlE1/hL6+w0TUdQtj7xkwQZS3sDbigrgMJtClu7CL7CrFX8UT3eTQD0DqXdJ2rMYHAvNpJS39WRQB3UuY5n4HCMQ+r81RkAr+oOlvVuc6bkMINajPePmA6aGF8eixccnsha7AUB6vAVAhZDuI/tvMkOY2c0Cy4gr7/mBFLKUsqQhc6wsPJjy7pXtf9s2JSI5TlzAO4gxOMI/uJV2/K/tEWRm6qwkHr6n5ZH9r30kgxcLPHS2gH1K8q11nJMubK/sf5QRl2pddlmlwmTdhlNscYYk7IViZ4rttSjTyDFXj+UAjh27xnin4/VctUtN55iLKlE1/hL6+w0TUfmRbm3sE4awo4kcFrGwg8/11sgAHKIuGOiMACCGU8vUbcnXH9rTX7TdB4r8JMgPYbbogb72kJAeqWR9DUEqEH8z+H1Ahz3gyeXaP7h0eXmukZIZOZPuMYxYM6PuilGehBdFevi0lWVFGq609fFqsDZ/MDTsP/oxTcKOpEYwjn5l5eoS+yiwox61OvCFDvbvJ2sDJv98vN4rtNZSZOHvuUXEkkRABaW3iDpfR31XIYu2nmwjLxvXe1oJJP79yug3THZfpWtyF8V+RmZQY/Qvast | 1.0 | BEN/Grj2IkqXS0bEHVo5TBWCRGaNcuG1LtgVBN5CJo9WskTruh0apcYflsiQVkxwY2y1Scu9wp5USKR+3jW9H81HzDMoxBqh7ZSxhrEhPfvlslXMPBEOlzuqdd85oj3TMw/IzmKeWuWT2TLVKJ7zVEgnAo6a2B0N3qQPvuw7myI= - FwNk5RdeuQgTGL7KpoIFjsoquL0LoPYUFYOhN5upnX+6GjUZdrKjq2d5CnZgs+tmfDRX2XMEFrYvbrn78ndd5wl6aQc0l+npHisIXx99tDrzMCqlvloYlcflnC38sefZ+L2krc994zx79bPXBC4uRQdf0pa5kOYwmn2aLQz8gSl2W5m45FOY3R7Ri4y8/dbZu/vMFZmS2ngTnD+WGrdvfvPGT11ycjaHJbMOX11wgv7OAfE9DDJgXzTihWMdtxAR84ZJkbjPnWYX/ARrKI3RWkWJBjHgt3/iIVBmNlmO8qla/CkiYJfUjqLm+GEBTXCOijsZGHZ+gZi7g2nypI7eC8Y+4MFGG6dtpCk6Au33gnC39fd97vSzxoWOxChsMbC7aYfJ5ft6RTe5M00ex36AaybeyzuwvobqHUMb7eZhohCAPCEGtAwKmpp41zda1Z6OEYzOOG0t6GD0kYd2jwaljzURZoyCOi0SUgrMVEgo95dufqTl7jMPnVxBKyLKp0nnqhipdGFJ/cUebIf87Hg3b9UtN55iLKlE1/hL6+w0TUdQtj7xkwQZS3sDbigrgMJtClu7CL7CrFX8UT3eTQD0DqXdJ2rMYHAvNpJS39WRQB3UuY5n4HCMQ+r81RkAr+oOlvVuc6bkMINajPePmA6aGF8eixccnsha7AUB6vAVAhZDuI/tvMkOY2c0Cy4gr7/mBFLKUsqQhc6wsPJjy7pXtf9s2JSI5TlzAO4gxOMI/uJV2/K/tEWRm6qwkHr6n5ZH9r30kgxcLPHS2gH1K8q11nJMubK/sf5QRl2pddlmlwmTdhlNscYYk7IViZ4rttSjTyDFXj+UAjh27xnin4/VctUtN55iLKlE1/hL6+w0TUfmRbm3sE4awo4kcFrGwg8/11sgAHKIuGOiMACCGU8vUbcnXH9rTX7TdB4r8JMgPYbbogb72kJAeqWR9DUEqEH8z+H1Ahz3gyeXaP7h0eXmukZIZOZPuMYxYM6PuilGehBdFevi0lWVFGq609fFqsDZ/MDTsP/oxTcKOpEYwjn5l5eoS+yiwox61OvCFDvbvJ2sDJv98vN4rtNZSZOHvuUXEkkRABaW3iDpfR31XIYu2nmwjLxvXe1oJJP79yug3THZfpWtyF8V+RmZQY/Qvast | design | ben dbzu ckiyjfujqlm gebtxcoijszghz k mdtsp rmzqy qvast | 1 |
274,912 | 20,883,419,397 | IssuesEvent | 2022-03-23 00:31:55 | Australian-Imaging-Service/arcana | https://api.github.com/repos/Australian-Imaging-Service/arcana | opened | Add description of how to set up environment for development to docs | documentation | Add a description of a recommended configuration for development environment to configuration | 1.0 | Add description of how to set up environment for development to docs - Add a description of a recommended configuration for development environment to configuration | non_design | add description of how to set up environment for development to docs add a description of a recommended configuration for development environment to configuration | 0 |
32,970 | 12,155,144,437 | IssuesEvent | 2020-04-25 11:47:12 | scriptex/atanas.info | https://api.github.com/repos/scriptex/atanas.info | closed | CVE-2018-14040 (Medium) detected in bootstrap-3.3.5.min.js | security vulnerability | ## CVE-2018-14040 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.5.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.5/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.5/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/atanas.info/node_modules/autocomplete.js/test/playground_jquery.html</p>
<p>Path to vulnerable library: /atanas.info/node_modules/autocomplete.js/test/playground_jquery.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.5.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scriptex/atanas.info/commit/88a9403d72b353289413e867c44000a247fa0324">88a9403d72b353289413e867c44000a247fa0324</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-14040 (Medium) detected in bootstrap-3.3.5.min.js - ## CVE-2018-14040 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.5.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.5/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.5/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/atanas.info/node_modules/autocomplete.js/test/playground_jquery.html</p>
<p>Path to vulnerable library: /atanas.info/node_modules/autocomplete.js/test/playground_jquery.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.5.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scriptex/atanas.info/commit/88a9403d72b353289413e867c44000a247fa0324">88a9403d72b353289413e867c44000a247fa0324</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in bootstrap min js cve medium severity vulnerability vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file tmp ws scm atanas info node modules autocomplete js test playground jquery html path to vulnerable library atanas info node modules autocomplete js test playground jquery html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href vulnerability details in bootstrap before xss is possible in the collapse data parent attribute publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org webjars npm bootstrap org webjars bootstrap step up your open source security game with whitesource | 0 |
260,822 | 8,215,457,045 | IssuesEvent | 2018-09-05 05:36:58 | Komet/MediaElch | https://api.github.com/repos/Komet/MediaElch | closed | wrong id for The Movie DB | bug high priority | with the latest update the id for TMDB is set to '**id**xxxxx' up till now the leading '**id**' was not part of the tag <tmdbid>**id**xxxxx</tmdbid>. The effect is that if I want to scrape with TMDB again, the id can not be found since it is then showing up as '**idid**xxxxx'
To be backwards compatible the '**id**' should be removed again from the tag. | 1.0 | wrong id for The Movie DB - with the latest update the id for TMDB is set to '**id**xxxxx' up till now the leading '**id**' was not part of the tag <tmdbid>**id**xxxxx</tmdbid>. The effect is that if I want to scrape with TMDB again, the id can not be found since it is then showing up as '**idid**xxxxx'
To be backwards compatible the '**id**' should be removed again from the tag. | non_design | wrong id for the movie db with the latest update the id for tmdb is set to id xxxxx up till now the leading id was not part of the tag id xxxxx the effect is that if i want to scrape with tmdb again the id can not be found since it is then showing up as idid xxxxx to be backwards compatible the id should be removed again from the tag | 0 |
144,789 | 22,550,314,552 | IssuesEvent | 2022-06-27 04:23:15 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | closed | [Feature]: Need a dashboard to monitor the health of everything in the fat container | Enhancement Deployment UX Improvement Needs Design Needs More Info High community DevOps Pod | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Summary
Requested by user on Discord. Also seems like a very useful feature in general.
```
Hello. Does appsmith has any endpoint url to check the service status with status codes etc?
Not the apps status. Appsmith whole service
```
### Why should this be worked on?
Allows users to monitor Appsmith service. | 1.0 | [Feature]: Need a dashboard to monitor the health of everything in the fat container - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Summary
Requested by user on Discord. Also seems like a very useful feature in general.
```
Hello. Does appsmith has any endpoint url to check the service status with status codes etc?
Not the apps status. Appsmith whole service
```
### Why should this be worked on?
Allows users to monitor Appsmith service. | design | need a dashboard to monitor the health of everything in the fat container is there an existing issue for this i have searched the existing issues summary requested by user on discord also seems like a very useful feature in general hello does appsmith has any endpoint url to check the service status with status codes etc not the apps status appsmith whole service why should this be worked on allows users to monitor appsmith service | 1 |
621,242 | 19,581,404,586 | IssuesEvent | 2022-01-04 21:53:51 | rubrikinc/rubrik-sdk-for-powershell | https://api.github.com/repos/rubrikinc/rubrik-sdk-for-powershell | closed | Add -ExistingSnapshotRetention parameter to various Protect-* cmdlets | platform-windows kind-enhancement help-wanted exp-intermediate platform-linux platform-mac priority-p2 | The `Protect-RubrikVM` cmdlet provides the ability to modify retention of existing snapshots when using the `-DoNotProtect` parameter by specifing `-ExistingSnapshotRetention` when unprotecting.
This is also referenced in [Issue 785](https://github.com/rubrikinc/rubrik-sdk-for-powershell/issues/785)
This functionality should also be available on
* Protect-RubrikFileset
* Protect-RubrikDatabase
* Protect-RubrikHyperVVM
* Protect-RubrikNutanixVM
| 1.0 | Add -ExistingSnapshotRetention parameter to various Protect-* cmdlets - The `Protect-RubrikVM` cmdlet provides the ability to modify retention of existing snapshots when using the `-DoNotProtect` parameter by specifing `-ExistingSnapshotRetention` when unprotecting.
This is also referenced in [Issue 785](https://github.com/rubrikinc/rubrik-sdk-for-powershell/issues/785)
This functionality should also be available on
* Protect-RubrikFileset
* Protect-RubrikDatabase
* Protect-RubrikHyperVVM
* Protect-RubrikNutanixVM
| non_design | add existingsnapshotretention parameter to various protect cmdlets the protect rubrikvm cmdlet provides the ability to modify retention of existing snapshots when using the donotprotect parameter by specifing existingsnapshotretention when unprotecting this is also referenced in this functionality should also be available on protect rubrikfileset protect rubrikdatabase protect rubrikhypervvm protect rubriknutanixvm | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.