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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
681,306 | 23,305,065,192 | IssuesEvent | 2022-08-07 22:20:25 | docker-mailserver/docker-mailserver | https://api.github.com/repos/docker-mailserver/docker-mailserver | opened | [FR] Improvements regarding OIDC | meta/needs triage priority/low | I've tagged this as an issue as I've had to completely hack around with various parts of this docker project to get what I want it to do with regards to loading stuff how I want it to load, and I thought it would probably be nice to get this made far nicer.
I'd like to volunteer myself to at least partly solve this issue as I want to make what I've done far easier to main - at present I'm relocating init scripts in an attempt to modify fewer files.
c.f.: <https://github.com/docker-mailserver/docker-mailserver/issues/2312>
## Life so far
```
COPY conf/dovecot/09-auth.conf /etc/dovecot/conf.d/09-auth.conf
COPY conf/dovecot/auth-ldap.conf.ext /etc/dovecot/conf.d/auth-ldap.conf.ext
COPY conf/dovecot/auth-oauth2.conf.ext /etc/dovecot/conf.d/auth-oauth2.conf.ext
COPY conf/dovecot/dovecot-oauth2.conf.ext /etc/dovecot/dovecot-oauth2.conf.ext
```
### `scripts/setup-stack.sh`
Within my hijacked `start-mailserver.sh` I have the following:
```
configomat.sh OAUTH_ /etc/dovecot/dovecot-oauth2.conf.ext
```
Notwithstanding that I realise that this should actually be `OAUTH2_` (sue me, I wasn't thinking) - this is a rather easy addition to the project as we can just stick it within [setup-stack.sh](https://github.com/docker-mailserver/docker-mailserver/blob/master/target/scripts/startup/setup-stack.sh) somewhere.
### `dovecot/10-auth.conf`
At present I'm doing weird magic in order to ensure that the OAUTH2 driver is being loaded before the LDAP driver i.e., I'm creating a separate file called `09-auth.conf` and inserting my required config entries in there.
I had tried setting LDAP to specific authentication mechanisms but internally rewritten e-mails stopped getting delivered.
The project has its own `10-auth.conf` [file](https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/10-auth.conf) which has the following order:
```
#!include auth-system.conf.ext
#!include auth-sql.conf.ext
#!include auth-ldap.conf.ext
!include auth-passwdfile.inc
#!include auth-checkpassword.conf.ext
#!include auth-vpopmail.conf.ext
#!include auth-static.conf.ext
```
Where would we put the reference for `auth-oauth2.conf.ext`? I'd personally rank it above LDAP but below SQL.
### `dovecot/auth-oauth2.conf.ext`
```
passdb {
driver = oauth2
mechanisms = oauthbearer xoauth2
args = /etc/dovecot/dovecot-oauth2.conf.ext
skip = authenticated
}
```
### `dovecot/dovecot-oauth2.conf.ext`
```
client_id = ?
client_secret = ?
grant_url = https://localhost/grant
introspection_mode = post
introspection_url = https://localhost/introspection
tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt
```
### Other improvements
In my copy of `dovecot-ldap.conf.ext` I have removed the LDAP userdb and I've decided to solely rely on a static userdb entry instead.
That's probably a silly mistake on my behalf but what is a good idea to add to that file is something like `skip = authenticated` or even something `skip =` so that this can be modified out of the box via an environment variable
## So, what do?
I think this is what we'll need to do:
* Implement an `ENABLE_OAUTH2` that will uncomment and include the OAUTH2 driver
* Ensure that OAUTH2 is loaded before LDAP to avoid un-necessary failed auth attempts (it will shout at you because the JWT is unsurprisingly too long for LDAP to comprehend)
Seem fair? | 1.0 | [FR] Improvements regarding OIDC - I've tagged this as an issue as I've had to completely hack around with various parts of this docker project to get what I want it to do with regards to loading stuff how I want it to load, and I thought it would probably be nice to get this made far nicer.
I'd like to volunteer myself to at least partly solve this issue as I want to make what I've done far easier to main - at present I'm relocating init scripts in an attempt to modify fewer files.
c.f.: <https://github.com/docker-mailserver/docker-mailserver/issues/2312>
## Life so far
```
COPY conf/dovecot/09-auth.conf /etc/dovecot/conf.d/09-auth.conf
COPY conf/dovecot/auth-ldap.conf.ext /etc/dovecot/conf.d/auth-ldap.conf.ext
COPY conf/dovecot/auth-oauth2.conf.ext /etc/dovecot/conf.d/auth-oauth2.conf.ext
COPY conf/dovecot/dovecot-oauth2.conf.ext /etc/dovecot/dovecot-oauth2.conf.ext
```
### `scripts/setup-stack.sh`
Within my hijacked `start-mailserver.sh` I have the following:
```
configomat.sh OAUTH_ /etc/dovecot/dovecot-oauth2.conf.ext
```
Notwithstanding that I realise that this should actually be `OAUTH2_` (sue me, I wasn't thinking) - this is a rather easy addition to the project as we can just stick it within [setup-stack.sh](https://github.com/docker-mailserver/docker-mailserver/blob/master/target/scripts/startup/setup-stack.sh) somewhere.
### `dovecot/10-auth.conf`
At present I'm doing weird magic in order to ensure that the OAUTH2 driver is being loaded before the LDAP driver i.e., I'm creating a separate file called `09-auth.conf` and inserting my required config entries in there.
I had tried setting LDAP to specific authentication mechanisms but internally rewritten e-mails stopped getting delivered.
The project has its own `10-auth.conf` [file](https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/10-auth.conf) which has the following order:
```
#!include auth-system.conf.ext
#!include auth-sql.conf.ext
#!include auth-ldap.conf.ext
!include auth-passwdfile.inc
#!include auth-checkpassword.conf.ext
#!include auth-vpopmail.conf.ext
#!include auth-static.conf.ext
```
Where would we put the reference for `auth-oauth2.conf.ext`? I'd personally rank it above LDAP but below SQL.
### `dovecot/auth-oauth2.conf.ext`
```
passdb {
driver = oauth2
mechanisms = oauthbearer xoauth2
args = /etc/dovecot/dovecot-oauth2.conf.ext
skip = authenticated
}
```
### `dovecot/dovecot-oauth2.conf.ext`
```
client_id = ?
client_secret = ?
grant_url = https://localhost/grant
introspection_mode = post
introspection_url = https://localhost/introspection
tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt
```
### Other improvements
In my copy of `dovecot-ldap.conf.ext` I have removed the LDAP userdb and I've decided to solely rely on a static userdb entry instead.
That's probably a silly mistake on my behalf but what is a good idea to add to that file is something like `skip = authenticated` or even something `skip =` so that this can be modified out of the box via an environment variable
## So, what do?
I think this is what we'll need to do:
* Implement an `ENABLE_OAUTH2` that will uncomment and include the OAUTH2 driver
* Ensure that OAUTH2 is loaded before LDAP to avoid un-necessary failed auth attempts (it will shout at you because the JWT is unsurprisingly too long for LDAP to comprehend)
Seem fair? | non_design | improvements regarding oidc i ve tagged this as an issue as i ve had to completely hack around with various parts of this docker project to get what i want it to do with regards to loading stuff how i want it to load and i thought it would probably be nice to get this made far nicer i d like to volunteer myself to at least partly solve this issue as i want to make what i ve done far easier to main at present i m relocating init scripts in an attempt to modify fewer files c f life so far copy conf dovecot auth conf etc dovecot conf d auth conf copy conf dovecot auth ldap conf ext etc dovecot conf d auth ldap conf ext copy conf dovecot auth conf ext etc dovecot conf d auth conf ext copy conf dovecot dovecot conf ext etc dovecot dovecot conf ext scripts setup stack sh within my hijacked start mailserver sh i have the following configomat sh oauth etc dovecot dovecot conf ext notwithstanding that i realise that this should actually be sue me i wasn t thinking this is a rather easy addition to the project as we can just stick it within somewhere dovecot auth conf at present i m doing weird magic in order to ensure that the driver is being loaded before the ldap driver i e i m creating a separate file called auth conf and inserting my required config entries in there i had tried setting ldap to specific authentication mechanisms but internally rewritten e mails stopped getting delivered the project has its own auth conf which has the following order include auth system conf ext include auth sql conf ext include auth ldap conf ext include auth passwdfile inc include auth checkpassword conf ext include auth vpopmail conf ext include auth static conf ext where would we put the reference for auth conf ext i d personally rank it above ldap but below sql dovecot auth conf ext passdb driver mechanisms oauthbearer args etc dovecot dovecot conf ext skip authenticated dovecot dovecot conf ext client id client secret grant url introspection mode post introspection url tls ca cert file etc ssl certs ca certificates crt other improvements in my copy of dovecot ldap conf ext i have removed the ldap userdb and i ve decided to solely rely on a static userdb entry instead that s probably a silly mistake on my behalf but what is a good idea to add to that file is something like skip authenticated or even something skip so that this can be modified out of the box via an environment variable so what do i think this is what we ll need to do implement an enable that will uncomment and include the driver ensure that is loaded before ldap to avoid un necessary failed auth attempts it will shout at you because the jwt is unsurprisingly too long for ldap to comprehend seem fair | 0 |
21,444 | 7,023,008,007 | IssuesEvent | 2017-12-22 13:30:23 | opencv/opencv | https://api.github.com/repos/opencv/opencv | closed | aarch64: too many warnings about 'fpic' | bug category: build/install | When building recent OpenCV (including 3.4-rc), hundreds of warning ( ```cc1plus: warning: /home/firefly/opencv-fork/build/modules/ts/precomp.hpp.gch/opencv_ts_Release.gch: created and used with different settings of -fpic``` ) appears when using **gcc 5.4.0** on **Aarch64**
##### System information (version)
- OpenCV => 3.4-rc (after #8198)
- Operating System / Platform => Jetson TX1, Jetson TX2, FireFly RK3399, PINE64, ODROID-C2 (All aarch64)
- Compiler => All **gcc 5.4.0**
##### Detailed description
The warning is just a warning, but it happens a lot during the build, for example more than 400 warnings during the build on Jetson TX1.
```
$ grep warning:.*fpic arm-jetson-tx1-build.txt | wc -l
411
```
I'm not sure which to go, either
* disable the warning
* find out which compiler option is making this warning
Any suggestion, please ?
##### Extra information
Looking on my local machines, it seems it only happens on GCC 5.4.0 on ARM64bit
I confirmed this doesn't happen on GCC 6.3.0, 4.9.2 (both on ARM64bit)
Unfortunately, I don't have other platform(x86, amd64) which uses gcc 5.4.0, so I'm not sure either the version or platform is causing this problem.
| 1.0 | aarch64: too many warnings about 'fpic' - When building recent OpenCV (including 3.4-rc), hundreds of warning ( ```cc1plus: warning: /home/firefly/opencv-fork/build/modules/ts/precomp.hpp.gch/opencv_ts_Release.gch: created and used with different settings of -fpic``` ) appears when using **gcc 5.4.0** on **Aarch64**
##### System information (version)
- OpenCV => 3.4-rc (after #8198)
- Operating System / Platform => Jetson TX1, Jetson TX2, FireFly RK3399, PINE64, ODROID-C2 (All aarch64)
- Compiler => All **gcc 5.4.0**
##### Detailed description
The warning is just a warning, but it happens a lot during the build, for example more than 400 warnings during the build on Jetson TX1.
```
$ grep warning:.*fpic arm-jetson-tx1-build.txt | wc -l
411
```
I'm not sure which to go, either
* disable the warning
* find out which compiler option is making this warning
Any suggestion, please ?
##### Extra information
Looking on my local machines, it seems it only happens on GCC 5.4.0 on ARM64bit
I confirmed this doesn't happen on GCC 6.3.0, 4.9.2 (both on ARM64bit)
Unfortunately, I don't have other platform(x86, amd64) which uses gcc 5.4.0, so I'm not sure either the version or platform is causing this problem.
| non_design | too many warnings about fpic when building recent opencv including rc hundreds of warning warning home firefly opencv fork build modules ts precomp hpp gch opencv ts release gch created and used with different settings of fpic appears when using gcc on system information version opencv rc after operating system platform jetson jetson firefly odroid all compiler all gcc detailed description the warning is just a warning but it happens a lot during the build for example more than warnings during the build on jetson grep warning fpic arm jetson build txt wc l i m not sure which to go either disable the warning find out which compiler option is making this warning any suggestion please extra information looking on my local machines it seems it only happens on gcc on i confirmed this doesn t happen on gcc both on unfortunately i don t have other platform which uses gcc so i m not sure either the version or platform is causing this problem | 0 |
45,674 | 5,950,606,173 | IssuesEvent | 2017-05-26 17:12:02 | kamal1978/LTFHC | https://api.github.com/repos/kamal1978/LTFHC | closed | Register design issues | app design high priority | Register not taking up full space on tablet. Also, vertical scroll bar only shows up if you scroll all the way to the right (it should always appear on the screen). Happening in all languages (but worse in French than in English).
| 1.0 | Register design issues - Register not taking up full space on tablet. Also, vertical scroll bar only shows up if you scroll all the way to the right (it should always appear on the screen). Happening in all languages (but worse in French than in English).
| design | register design issues register not taking up full space on tablet also vertical scroll bar only shows up if you scroll all the way to the right it should always appear on the screen happening in all languages but worse in french than in english | 1 |
87,924 | 25,253,147,888 | IssuesEvent | 2022-11-15 16:02:47 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | [API Proposal]: `OperatingSystem.IsWASI()` | api-suggestion arch-wasm area-Build-mono | ### Background and motivation
Adding new RID for compiling Mono to [WebAssembly System Interface](https://wasi.dev/) platform.
Related discussion https://github.com/dotnet/runtime/issues/77780 and https://github.com/dotnet/runtime/pull/78376
### API Proposal
```diff
namespace System;
public sealed class OperatingSystem : ISerializable, ICloneable
{
+ public static bool IsWASI();
}
```
### API Usage
```csharp
if (OperatingSystem.IsWASI())
{
throw new PlatformNotSupportedException();
}
```
### Alternative Designs
WASI is abreviation so we prefer all upper case. Alternatively we could have:
```
public static bool IsWasi();
```
### Risks
_No response_ | 1.0 | [API Proposal]: `OperatingSystem.IsWASI()` - ### Background and motivation
Adding new RID for compiling Mono to [WebAssembly System Interface](https://wasi.dev/) platform.
Related discussion https://github.com/dotnet/runtime/issues/77780 and https://github.com/dotnet/runtime/pull/78376
### API Proposal
```diff
namespace System;
public sealed class OperatingSystem : ISerializable, ICloneable
{
+ public static bool IsWASI();
}
```
### API Usage
```csharp
if (OperatingSystem.IsWASI())
{
throw new PlatformNotSupportedException();
}
```
### Alternative Designs
WASI is abreviation so we prefer all upper case. Alternatively we could have:
```
public static bool IsWasi();
```
### Risks
_No response_ | non_design | operatingsystem iswasi background and motivation adding new rid for compiling mono to platform related discussion and api proposal diff namespace system public sealed class operatingsystem iserializable icloneable public static bool iswasi api usage csharp if operatingsystem iswasi throw new platformnotsupportedexception alternative designs wasi is abreviation so we prefer all upper case alternatively we could have public static bool iswasi risks no response | 0 |
69,031 | 8,369,140,110 | IssuesEvent | 2018-10-04 16:28:00 | poanetwork/blockscout | https://api.github.com/repos/poanetwork/blockscout | opened | DAI Chain Design Template | design priority: high team: contributor | @arthurra
@pashagonchar just finished the design for the Dai Chain. We're looking for some feedback regarding the design.
- There is a new background image on the statistics block which looks great. How hard would this be to implement?
- Can we add this image or another background image to other chains as well?
<img width="1280" alt="blockscout_dai_2" src="https://user-images.githubusercontent.com/17620007/46488509-daa26180-c7d0-11e8-82cf-6f695a755ef7.png">
| 1.0 | DAI Chain Design Template - @arthurra
@pashagonchar just finished the design for the Dai Chain. We're looking for some feedback regarding the design.
- There is a new background image on the statistics block which looks great. How hard would this be to implement?
- Can we add this image or another background image to other chains as well?
<img width="1280" alt="blockscout_dai_2" src="https://user-images.githubusercontent.com/17620007/46488509-daa26180-c7d0-11e8-82cf-6f695a755ef7.png">
| design | dai chain design template arthurra pashagonchar just finished the design for the dai chain we re looking for some feedback regarding the design there is a new background image on the statistics block which looks great how hard would this be to implement can we add this image or another background image to other chains as well img width alt blockscout dai src | 1 |
16,395 | 10,482,078,682 | IssuesEvent | 2019-09-24 11:07:10 | edgexfoundry/edgex-go | https://api.github.com/repos/edgexfoundry/edgex-go | opened | Remove code obsoleted by common bootstrap package | core-services fuji | Dependent upon completion of #1801, #1802, #1803, #1804, #1805, #1806, #1807, #1808, #1809, and #1810. | 1.0 | Remove code obsoleted by common bootstrap package - Dependent upon completion of #1801, #1802, #1803, #1804, #1805, #1806, #1807, #1808, #1809, and #1810. | non_design | remove code obsoleted by common bootstrap package dependent upon completion of and | 0 |
303,577 | 26,217,389,980 | IssuesEvent | 2023-01-04 12:10:30 | quarkusio/quarkus | https://api.github.com/repos/quarkusio/quarkus | closed | Different behavior in TestIdentityAssociation for getDeferredIdentity and getIdentity | kind/bug area/security area/testing | ### Describe the bug
The logic in `io.quarkus.test.security.TestIdentityAssociation` for `getDeferredIdentity` and `getIdentity` is different. This results in certain situations where the `SecurityIdentity` read via `getDeferredIdentity()` is different from the `SecurityIdentity` obtained via `getIdentity()`.
The `getIdentity` method was adjusted with https://github.com/quarkusio/quarkus/commit/e1f50c118b0385ada180a6f6b48dc83515ac2d37 , but the `getDeferredIdentity` wasn't.
### Expected behavior
`TestIdentityAssociation.getDeferredIdentity().await().indefinitely()` always equals `TestIdentityAssociation.getIdentity()`
### Actual behavior
TestIdentityAssociation.getDeferredIdentity()` always returns the testIdentity if one exists.
`TestIdentityAssociation.getIdentity()` checks the underlying identity first.
### How to Reproduce?
I do not have a reproducer project. But can be isolated relatively easily.
1. Call `SecurityIdentityAssociation#setIdentity` (with SecurityIdentity that isn't anonymous)
2. Result of `getIdentity` differs from `getDeferredIdentity().await().indefinitely()`
### Output of `uname -a` or `ver`
_No response_
### Output of `java -version`
_No response_
### GraalVM version (if different from Java)
_No response_
### Quarkus version or git rev
2.15.1.Final
### Build tool (ie. output of `mvnw --version` or `gradlew --version`)
_No response_
### Additional information
_No response_ | 1.0 | Different behavior in TestIdentityAssociation for getDeferredIdentity and getIdentity - ### Describe the bug
The logic in `io.quarkus.test.security.TestIdentityAssociation` for `getDeferredIdentity` and `getIdentity` is different. This results in certain situations where the `SecurityIdentity` read via `getDeferredIdentity()` is different from the `SecurityIdentity` obtained via `getIdentity()`.
The `getIdentity` method was adjusted with https://github.com/quarkusio/quarkus/commit/e1f50c118b0385ada180a6f6b48dc83515ac2d37 , but the `getDeferredIdentity` wasn't.
### Expected behavior
`TestIdentityAssociation.getDeferredIdentity().await().indefinitely()` always equals `TestIdentityAssociation.getIdentity()`
### Actual behavior
TestIdentityAssociation.getDeferredIdentity()` always returns the testIdentity if one exists.
`TestIdentityAssociation.getIdentity()` checks the underlying identity first.
### How to Reproduce?
I do not have a reproducer project. But can be isolated relatively easily.
1. Call `SecurityIdentityAssociation#setIdentity` (with SecurityIdentity that isn't anonymous)
2. Result of `getIdentity` differs from `getDeferredIdentity().await().indefinitely()`
### Output of `uname -a` or `ver`
_No response_
### Output of `java -version`
_No response_
### GraalVM version (if different from Java)
_No response_
### Quarkus version or git rev
2.15.1.Final
### Build tool (ie. output of `mvnw --version` or `gradlew --version`)
_No response_
### Additional information
_No response_ | non_design | different behavior in testidentityassociation for getdeferredidentity and getidentity describe the bug the logic in io quarkus test security testidentityassociation for getdeferredidentity and getidentity is different this results in certain situations where the securityidentity read via getdeferredidentity is different from the securityidentity obtained via getidentity the getidentity method was adjusted with but the getdeferredidentity wasn t expected behavior testidentityassociation getdeferredidentity await indefinitely always equals testidentityassociation getidentity actual behavior testidentityassociation getdeferredidentity always returns the testidentity if one exists testidentityassociation getidentity checks the underlying identity first how to reproduce i do not have a reproducer project but can be isolated relatively easily call securityidentityassociation setidentity with securityidentity that isn t anonymous result of getidentity differs from getdeferredidentity await indefinitely output of uname a or ver no response output of java version no response graalvm version if different from java no response quarkus version or git rev final build tool ie output of mvnw version or gradlew version no response additional information no response | 0 |
1,655 | 2,563,198,477 | IssuesEvent | 2015-02-06 10:47:17 | mozilla-services/readinglist | https://api.github.com/repos/mozilla-services/readinglist | closed | Disable the PUT endpoint | API-design | Even though it makes sense in a RESTful approach, it is wise to disable it since it's not relevant in the context of readinglist | 1.0 | Disable the PUT endpoint - Even though it makes sense in a RESTful approach, it is wise to disable it since it's not relevant in the context of readinglist | design | disable the put endpoint even though it makes sense in a restful approach it is wise to disable it since it s not relevant in the context of readinglist | 1 |
129,656 | 17,857,490,946 | IssuesEvent | 2021-09-05 10:16:23 | evan361425/flutter-pos-system | https://api.github.com/repos/evan361425/flutter-pos-system | closed | 顧客設定外觀 | design | 首頁會有很多設定，每個設定使用 [Card](https://material.io/components/cards)，
每個 Card 輸出設定名稱、選項和選項預設值、還有該設定的模式（#105）
- 預設值要上色
- 模式要標示
點進去後設定各個屬性（#105） | 1.0 | 顧客設定外觀 - 首頁會有很多設定，每個設定使用 [Card](https://material.io/components/cards)，
每個 Card 輸出設定名稱、選項和選項預設值、還有該設定的模式（#105）
- 預設值要上色
- 模式要標示
點進去後設定各個屬性（#105） | design | 顧客設定外觀 首頁會有很多設定，每個設定使用 每個 card 輸出設定名稱、選項和選項預設值、還有該設定的模式（ ） 預設值要上色 模式要標示 點進去後設定各個屬性（ ） | 1 |
112,837 | 14,292,108,322 | IssuesEvent | 2020-11-24 00:13:59 | mexyn/statev_v2_issues | https://api.github.com/repos/mexyn/statev_v2_issues | closed | Chemieanzug und Gasmaske | confirmed gamedesign solved |
**Character Name**
Noah Draper
**Zeitpunkt (Datum / Uhrzeit)**
Jederzeit
**Beobachtetes Verhalten**
Der Chemieanzug besitzt eine Gasmaske, dennoch bekommt man die Meldung in den Häusern: Es wird eine Gasmaske benötigt
**Erwartetes Verhalten**
Auf die Produktion oder was es sein soll muss man zugreifen können mit Anzug, außer es ist gewollt. Weiters können Gasmasken nicht in Schneiderei hergestellt werden
**Schritte um den Fehler nachvollziehen zu können**
Mit chemieanzug in Drogenhaus gehen und auf roten Marker drücken, dann kommt die Meldung mit der Gasmaske
| 1.0 | Chemieanzug und Gasmaske -
**Character Name**
Noah Draper
**Zeitpunkt (Datum / Uhrzeit)**
Jederzeit
**Beobachtetes Verhalten**
Der Chemieanzug besitzt eine Gasmaske, dennoch bekommt man die Meldung in den Häusern: Es wird eine Gasmaske benötigt
**Erwartetes Verhalten**
Auf die Produktion oder was es sein soll muss man zugreifen können mit Anzug, außer es ist gewollt. Weiters können Gasmasken nicht in Schneiderei hergestellt werden
**Schritte um den Fehler nachvollziehen zu können**
Mit chemieanzug in Drogenhaus gehen und auf roten Marker drücken, dann kommt die Meldung mit der Gasmaske
| design | chemieanzug und gasmaske character name noah draper zeitpunkt datum uhrzeit jederzeit beobachtetes verhalten der chemieanzug besitzt eine gasmaske dennoch bekommt man die meldung in den häusern es wird eine gasmaske benötigt erwartetes verhalten auf die produktion oder was es sein soll muss man zugreifen können mit anzug außer es ist gewollt weiters können gasmasken nicht in schneiderei hergestellt werden schritte um den fehler nachvollziehen zu können mit chemieanzug in drogenhaus gehen und auf roten marker drücken dann kommt die meldung mit der gasmaske | 1 |
288,875 | 8,852,573,150 | IssuesEvent | 2019-01-08 18:44:37 | visit-dav/issues-test | https://api.github.com/repos/visit-dav/issues-test | closed | Scatter plot hangs when using color var. | asc bug crash likelihood medium priority reviewed severity high wrong results | In parallel if there are more processors than chunks to process - a common case when material selection is used.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 348
Status: Resolved
Project: VisIt
Tracker: Bug
Priority: Urgent
Subject: Scatter plot hangs when using color var.
Assigned to: Cyrus Harrison
Category: -
Target version: 2.1
Author: Cyrus Harrison
Start: 08/17/2010
Due date:
% Done: 0%
Estimated time:
Created: 08/17/2010 02:50 pm
Updated: 08/17/2010 05:23 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.0.2
Impact:
Expected Use:
OS: All
Support Group: DOE/ASC
Description:
In parallel if there are more processors than chunks to process - a common case when material selection is used.
Comments:
Hi Everyone,This commmit fixes two parallel related issues with the scatter plot:1) Creating a colored scatter plot when you had more procs than chunks(domains) to process (say after a material selection) would cause an invalid merge exception & a parallel hang. (This resolves #348)2) Spatial extents were invalid when there are were more procs than chunks to process.Sending Scatter/avtScatterFilter.CSending Scatter/avtScatterFilter.hTransmitting file data ..Committed revision r12249.-Cyrus
| 1.0 | Scatter plot hangs when using color var. - In parallel if there are more processors than chunks to process - a common case when material selection is used.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 348
Status: Resolved
Project: VisIt
Tracker: Bug
Priority: Urgent
Subject: Scatter plot hangs when using color var.
Assigned to: Cyrus Harrison
Category: -
Target version: 2.1
Author: Cyrus Harrison
Start: 08/17/2010
Due date:
% Done: 0%
Estimated time:
Created: 08/17/2010 02:50 pm
Updated: 08/17/2010 05:23 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.0.2
Impact:
Expected Use:
OS: All
Support Group: DOE/ASC
Description:
In parallel if there are more processors than chunks to process - a common case when material selection is used.
Comments:
Hi Everyone,This commmit fixes two parallel related issues with the scatter plot:1) Creating a colored scatter plot when you had more procs than chunks(domains) to process (say after a material selection) would cause an invalid merge exception & a parallel hang. (This resolves #348)2) Spatial extents were invalid when there are were more procs than chunks to process.Sending Scatter/avtScatterFilter.CSending Scatter/avtScatterFilter.hTransmitting file data ..Committed revision r12249.-Cyrus
| non_design | scatter plot hangs when using color var in parallel if there are more processors than chunks to process a common case when material selection is used redmine migration this ticket was migrated from redmine as such not all information was able to be captured in the transition below is a complete record of the original redmine ticket ticket number status resolved project visit tracker bug priority urgent subject scatter plot hangs when using color var assigned to cyrus harrison category target version author cyrus harrison start due date done estimated time created pm updated pm likelihood occasional severity crash wrong results found in version impact expected use os all support group doe asc description in parallel if there are more processors than chunks to process a common case when material selection is used comments hi everyone this commmit fixes two parallel related issues with the scatter plot creating a colored scatter plot when you had more procs than chunks domains to process say after a material selection would cause an invalid merge exception a parallel hang this resolves spatial extents were invalid when there are were more procs than chunks to process sending scatter avtscatterfilter csending scatter avtscatterfilter htransmitting file data committed revision cyrus | 0 |
43,477 | 5,637,693,209 | IssuesEvent | 2017-04-06 09:49:46 | owncloud/core | https://api.github.com/repos/owncloud/core | closed | LDAP wizard tab: if you mouse over the "descriptions" of each field, the cursor turns into a finger cursor. | app:user_ldap bug design junior job sev4-low | ### Steps to reproduce
1. Go to LDAP wizard
2. Mouse over the "descriptions" of any field (all tabs have the same behaviour)
### Expected behaviour
The cursor should not change.
### Actual behaviour
The cursor turns into a finger cursor.
### Server configuration
**Operating system**:
Ubuntu 14.04
**Web server:**
Apache
**Database:**
MySQL
**PHP version:**
5.5.9
**ownCloud version:**ownCloud 9.0 pre alpha (daily) Build:2015-11-05T05:14:55+00:00 b23159fa5e9540aa10dd9e39124fe8471f129a02
**Updated from an older ownCloud or fresh install:**
Fresh
**List of activated apps:**
**The content of config/config.php:**
```
```
**Are you using external storage, if yes which one:** local/smb/sftp/...
No
**Are you using encryption:**
No
**Logs**
```
```
### Client configuration
**browser**
Firefox.
| 1.0 | LDAP wizard tab: if you mouse over the "descriptions" of each field, the cursor turns into a finger cursor. - ### Steps to reproduce
1. Go to LDAP wizard
2. Mouse over the "descriptions" of any field (all tabs have the same behaviour)
### Expected behaviour
The cursor should not change.
### Actual behaviour
The cursor turns into a finger cursor.
### Server configuration
**Operating system**:
Ubuntu 14.04
**Web server:**
Apache
**Database:**
MySQL
**PHP version:**
5.5.9
**ownCloud version:**ownCloud 9.0 pre alpha (daily) Build:2015-11-05T05:14:55+00:00 b23159fa5e9540aa10dd9e39124fe8471f129a02
**Updated from an older ownCloud or fresh install:**
Fresh
**List of activated apps:**
**The content of config/config.php:**
```
```
**Are you using external storage, if yes which one:** local/smb/sftp/...
No
**Are you using encryption:**
No
**Logs**
```
```
### Client configuration
**browser**
Firefox.
| design | ldap wizard tab if you mouse over the descriptions of each field the cursor turns into a finger cursor steps to reproduce go to ldap wizard mouse over the descriptions of any field all tabs have the same behaviour expected behaviour the cursor should not change actual behaviour the cursor turns into a finger cursor server configuration operating system ubuntu web server apache database mysql php version owncloud version owncloud pre alpha daily build updated from an older owncloud or fresh install fresh list of activated apps the content of config config php are you using external storage if yes which one local smb sftp no are you using encryption no logs client configuration browser firefox | 1 |
166,147 | 26,288,490,746 | IssuesEvent | 2023-01-08 04:54:24 | sowbug/groove | https://api.github.com/repos/sowbug/groove | closed | Get the voice story straight | enhancement design instrument | One way of looking at a synth is a set of voices that stay on call for servicing note events. There are a few problems currently:
- I'm not reusing any polyphony logic.
- That logic is broken.
I think that a synth should be composed of things that implement a voice trait. | 1.0 | Get the voice story straight - One way of looking at a synth is a set of voices that stay on call for servicing note events. There are a few problems currently:
- I'm not reusing any polyphony logic.
- That logic is broken.
I think that a synth should be composed of things that implement a voice trait. | design | get the voice story straight one way of looking at a synth is a set of voices that stay on call for servicing note events there are a few problems currently i m not reusing any polyphony logic that logic is broken i think that a synth should be composed of things that implement a voice trait | 1 |
138,820 | 20,727,810,751 | IssuesEvent | 2022-03-14 05:35:21 | RussKie/winforms | https://api.github.com/repos/RussKie/winforms | opened | VS designer is not working! Again! | area: VS designer untriaged | ### Environment
Version 17.2.0 Preview 3.0 [32305.25.main]
### .NET version
.NET 7.0 Preview2
### Did this work in a previous version of Visual Studio?
Yes, it did. VS 16.11.
### Issue description
Nothing works...
### Steps to reproduce
Double click on Form1.cs
### Diagnostics
```shell
[16:23:00.6429015] Added 'System.Windows.Forms'
[16:23:00.6439022] Loaded System in 00:00:00.0000063 [thread 14]
[16:23:00.6439022] Processed 'System' in 00:00:00.0004935
[16:23:00.6539018] Added 'System'
[16:23:00.6539018] Loaded System.Drawing in 00:00:00.0000066 [thread 14]
[16:23:00.6539018] Processed 'System.Drawing' in 00:00:00.0000558
[16:23:00.6549012] Creating VSCodeDomDesignerLoader
[16:23:00.6559010] Added 'System.Drawing'
[16:23:00.6559010] Loaded System.Design in 00:00:00.0000054 [thread 14]
[16:23:00.6599033] Processed 'System.Design' in 00:00:00.0045879
[16:23:00.6669036] Added 'System.Design'
[16:23:00.6669036] Loaded System.Drawing.Design in 00:00:00.0000068 [thread 14]
[16:23:00.6669036] Processed 'System.Drawing.Design' in 00:00:00.0000600
[16:23:00.6679027] Added 'System.Drawing.Design'
[16:23:00.6779013] [Thread 1] Creating design-time ITypeResolutionService.
[16:23:00.6949031] Start processing enqueued assemblies
[16:23:00.6949031] Loaded Microsoft.WinForms.DesignTools.Protocol in 00:00:00.0000073 [thread 68]
[16:23:00.6949031] Processed 'Microsoft.WinForms.DesignTools.Protocol' in 00:00:00.0008305
[16:23:00.6969029] Added 'Microsoft.WinForms.DesignTools.Protocol'
[16:23:00.6969029] Loaded Microsoft.WinForms.DesignTools.Client in 00:00:00.0000055 [thread 68]
[16:23:00.7159056] Processed 'Microsoft.WinForms.DesignTools.Client' in 00:00:00.0182444
[16:23:00.7169065] Added 'Microsoft.WinForms.DesignTools.Client'
[16:23:00.8049025] [Thread 81] Launching server...
[16:23:02.3128302] [External]: Preparing shadow cache folder
[16:23:02.3148303] [External]: Copying design tools server common files from: 'c:\program files\microsoft visual studio\2022\preview\common7\ide\commonextensions\microsoft\windows.forms\DesignToolsServer\Common'
[16:23:02.4318274] [External]: Copying design tool server platform-specific files from: 'c:\program files\microsoft visual studio\2022\preview\common7\ide\commonextensions\microsoft\windows.forms\DesignToolsServer\x64'
[16:23:02.4368263] [External]: Copying project output file: 'D:\Development\!Repro\2183-FlowLayoutPanel-External\External\bin\Debug\net6.0-windows\External.dll'
[16:23:02.4388287] [External]: Copying 'D:\Development\!Repro\2183-FlowLayoutPanel-External\External\obj\Debug\net6.0-windows\External.designer.deps.json' to 'DesignToolsServer.deps.json'
[16:23:02.4398271] [External]: Copying 'D:\Development\!Repro\2183-FlowLayoutPanel-External\External\obj\Debug\net6.0-windows\External.designer.runtimeconfig.json' to 'DesignToolsServer.runtimeconfig.json'
[16:23:02.5648267] [External]: Launching design tools server process...
[16:23:03.4268475] [External]: Connected to named pipe: DesignToolsServer.75060394-8743-4e33-ab96-a768579ed5f8
[16:23:03.4308482] [External]: info: Design Tools Server[0]
[16:23:03.4308482] [External]: Connecting to pipe: DesignToolsServer.75060394-8743-4e33-ab96-a768579ed5f8...
[16:23:03.4308482] [External]: info: Design Tools Server[0]
[16:23:03.4308482] [External]: Successfully connected to pipe: DesignToolsServer.75060394-8743-4e33-ab96-a768579ed5f8
[16:23:03.4653857] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.4653857] [External]: Creating DesignToolsServer [thread 1]
[16:23:03.4673856] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.4673856] [External]: Starting UI thread [thread 1]
[16:23:03.5243854] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.5243854] [External]: Performing start up tasks [thread 7]
[16:23:03.5973853] [External]: info: Design Tools Server[0]
[16:23:03.5973853] [External]: UI thread started
[16:23:03.7203855] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.7203855] [External]: Wait for start up tasks to complete... [thread 9]
[16:23:03.7773857] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.7773857] [External]: Loaded server manifest [thread 11]
[16:23:03.7773857] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.7773857] [External]: Loading design-time assemblies [thread 11]
[16:23:03.9223852] [External]: info: Microsoft.DotNet.DesignTools.Server.ServerProtocolContext[0]
[16:23:03.9223852] [External]: Building MEF composition....
```
| 1.0 | VS designer is not working! Again! - ### Environment
Version 17.2.0 Preview 3.0 [32305.25.main]
### .NET version
.NET 7.0 Preview2
### Did this work in a previous version of Visual Studio?
Yes, it did. VS 16.11.
### Issue description
Nothing works...
### Steps to reproduce
Double click on Form1.cs
### Diagnostics
```shell
[16:23:00.6429015] Added 'System.Windows.Forms'
[16:23:00.6439022] Loaded System in 00:00:00.0000063 [thread 14]
[16:23:00.6439022] Processed 'System' in 00:00:00.0004935
[16:23:00.6539018] Added 'System'
[16:23:00.6539018] Loaded System.Drawing in 00:00:00.0000066 [thread 14]
[16:23:00.6539018] Processed 'System.Drawing' in 00:00:00.0000558
[16:23:00.6549012] Creating VSCodeDomDesignerLoader
[16:23:00.6559010] Added 'System.Drawing'
[16:23:00.6559010] Loaded System.Design in 00:00:00.0000054 [thread 14]
[16:23:00.6599033] Processed 'System.Design' in 00:00:00.0045879
[16:23:00.6669036] Added 'System.Design'
[16:23:00.6669036] Loaded System.Drawing.Design in 00:00:00.0000068 [thread 14]
[16:23:00.6669036] Processed 'System.Drawing.Design' in 00:00:00.0000600
[16:23:00.6679027] Added 'System.Drawing.Design'
[16:23:00.6779013] [Thread 1] Creating design-time ITypeResolutionService.
[16:23:00.6949031] Start processing enqueued assemblies
[16:23:00.6949031] Loaded Microsoft.WinForms.DesignTools.Protocol in 00:00:00.0000073 [thread 68]
[16:23:00.6949031] Processed 'Microsoft.WinForms.DesignTools.Protocol' in 00:00:00.0008305
[16:23:00.6969029] Added 'Microsoft.WinForms.DesignTools.Protocol'
[16:23:00.6969029] Loaded Microsoft.WinForms.DesignTools.Client in 00:00:00.0000055 [thread 68]
[16:23:00.7159056] Processed 'Microsoft.WinForms.DesignTools.Client' in 00:00:00.0182444
[16:23:00.7169065] Added 'Microsoft.WinForms.DesignTools.Client'
[16:23:00.8049025] [Thread 81] Launching server...
[16:23:02.3128302] [External]: Preparing shadow cache folder
[16:23:02.3148303] [External]: Copying design tools server common files from: 'c:\program files\microsoft visual studio\2022\preview\common7\ide\commonextensions\microsoft\windows.forms\DesignToolsServer\Common'
[16:23:02.4318274] [External]: Copying design tool server platform-specific files from: 'c:\program files\microsoft visual studio\2022\preview\common7\ide\commonextensions\microsoft\windows.forms\DesignToolsServer\x64'
[16:23:02.4368263] [External]: Copying project output file: 'D:\Development\!Repro\2183-FlowLayoutPanel-External\External\bin\Debug\net6.0-windows\External.dll'
[16:23:02.4388287] [External]: Copying 'D:\Development\!Repro\2183-FlowLayoutPanel-External\External\obj\Debug\net6.0-windows\External.designer.deps.json' to 'DesignToolsServer.deps.json'
[16:23:02.4398271] [External]: Copying 'D:\Development\!Repro\2183-FlowLayoutPanel-External\External\obj\Debug\net6.0-windows\External.designer.runtimeconfig.json' to 'DesignToolsServer.runtimeconfig.json'
[16:23:02.5648267] [External]: Launching design tools server process...
[16:23:03.4268475] [External]: Connected to named pipe: DesignToolsServer.75060394-8743-4e33-ab96-a768579ed5f8
[16:23:03.4308482] [External]: info: Design Tools Server[0]
[16:23:03.4308482] [External]: Connecting to pipe: DesignToolsServer.75060394-8743-4e33-ab96-a768579ed5f8...
[16:23:03.4308482] [External]: info: Design Tools Server[0]
[16:23:03.4308482] [External]: Successfully connected to pipe: DesignToolsServer.75060394-8743-4e33-ab96-a768579ed5f8
[16:23:03.4653857] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.4653857] [External]: Creating DesignToolsServer [thread 1]
[16:23:03.4673856] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.4673856] [External]: Starting UI thread [thread 1]
[16:23:03.5243854] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.5243854] [External]: Performing start up tasks [thread 7]
[16:23:03.5973853] [External]: info: Design Tools Server[0]
[16:23:03.5973853] [External]: UI thread started
[16:23:03.7203855] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.7203855] [External]: Wait for start up tasks to complete... [thread 9]
[16:23:03.7773857] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.7773857] [External]: Loaded server manifest [thread 11]
[16:23:03.7773857] [External]: info: Microsoft.DotNet.DesignTools.Server.DesignToolsServer[0]
[16:23:03.7773857] [External]: Loading design-time assemblies [thread 11]
[16:23:03.9223852] [External]: info: Microsoft.DotNet.DesignTools.Server.ServerProtocolContext[0]
[16:23:03.9223852] [External]: Building MEF composition....
```
| design | vs designer is not working again environment version preview net version net did this work in a previous version of visual studio yes it did vs issue description nothing works steps to reproduce double click on cs diagnostics shell added system windows forms loaded system in processed system in added system loaded system drawing in processed system drawing in creating vscodedomdesignerloader added system drawing loaded system design in processed system design in added system design loaded system drawing design in processed system drawing design in added system drawing design creating design time ityperesolutionservice start processing enqueued assemblies loaded microsoft winforms designtools protocol in processed microsoft winforms designtools protocol in added microsoft winforms designtools protocol loaded microsoft winforms designtools client in processed microsoft winforms designtools client in added microsoft winforms designtools client launching server preparing shadow cache folder copying design tools server common files from c program files microsoft visual studio preview ide commonextensions microsoft windows forms designtoolsserver common copying design tool server platform specific files from c program files microsoft visual studio preview ide commonextensions microsoft windows forms designtoolsserver copying project output file d development repro flowlayoutpanel external external bin debug windows external dll copying d development repro flowlayoutpanel external external obj debug windows external designer deps json to designtoolsserver deps json copying d development repro flowlayoutpanel external external obj debug windows external designer runtimeconfig json to designtoolsserver runtimeconfig json launching design tools server process connected to named pipe designtoolsserver info design tools server connecting to pipe designtoolsserver info design tools server successfully connected to pipe designtoolsserver info microsoft dotnet designtools server designtoolsserver creating designtoolsserver info microsoft dotnet designtools server designtoolsserver starting ui thread info microsoft dotnet designtools server designtoolsserver performing start up tasks info design tools server ui thread started info microsoft dotnet designtools server designtoolsserver wait for start up tasks to complete info microsoft dotnet designtools server designtoolsserver loaded server manifest info microsoft dotnet designtools server designtoolsserver loading design time assemblies info microsoft dotnet designtools server serverprotocolcontext building mef composition | 1 |
38,902 | 6,713,390,004 | IssuesEvent | 2017-10-13 13:18:26 | MaLL-UFSCar/bayessets | https://api.github.com/repos/MaLL-UFSCar/bayessets | closed | Documentation and usage examples for Bernoulli BS | documentation | The projects needs a minimal documentation that shows how to use the Bernoulli BS in the basic case. | 1.0 | Documentation and usage examples for Bernoulli BS - The projects needs a minimal documentation that shows how to use the Bernoulli BS in the basic case. | non_design | documentation and usage examples for bernoulli bs the projects needs a minimal documentation that shows how to use the bernoulli bs in the basic case | 0 |
30,494 | 8,555,137,134 | IssuesEvent | 2018-11-08 09:10:26 | mozilla-mobile/reference-browser | https://api.github.com/repos/mozilla-mobile/reference-browser | opened | Cleanup flavors and build in parallel | 🏗️ build 🤖 automation | Let's speed up our builds:
* Build all variants in parallel
* Remove unneeded variants (Maybe we should just go with GeckoView Nightly only for now?) | 1.0 | Cleanup flavors and build in parallel - Let's speed up our builds:
* Build all variants in parallel
* Remove unneeded variants (Maybe we should just go with GeckoView Nightly only for now?) | non_design | cleanup flavors and build in parallel let s speed up our builds build all variants in parallel remove unneeded variants maybe we should just go with geckoview nightly only for now | 0 |
138,447 | 20,592,001,367 | IssuesEvent | 2022-03-05 00:45:35 | microsoft/azuredatastudio | https://api.github.com/repos/microsoft/azuredatastudio | opened | allow extension to specify the table designer summary report format | Enhancement Triage: Done Area - Designer | we should support text and md. | 1.0 | allow extension to specify the table designer summary report format - we should support text and md. | design | allow extension to specify the table designer summary report format we should support text and md | 1 |
62,554 | 7,611,134,047 | IssuesEvent | 2018-05-01 12:30:28 | hyperledger/composer | https://api.github.com/repos/hyperledger/composer | closed | Making feedback improvements to enhance "perceived performance" during operations | design playground stale | <!--- Provide a general summary of the issue in the Title above -->
We would like to look into adding small microinteractions throughout the playground to increase the perceived performance of operations.
Some ideas:
- Submit transactions in the background and show notification when they are done, allowing users to continue working whilst they happen.
- When deploying to HSBN for the first time, could we provide more information on what is going on (other than a spinner).
The bottom line - make waiting enjoyable :)
| 1.0 | Making feedback improvements to enhance "perceived performance" during operations - <!--- Provide a general summary of the issue in the Title above -->
We would like to look into adding small microinteractions throughout the playground to increase the perceived performance of operations.
Some ideas:
- Submit transactions in the background and show notification when they are done, allowing users to continue working whilst they happen.
- When deploying to HSBN for the first time, could we provide more information on what is going on (other than a spinner).
The bottom line - make waiting enjoyable :)
| design | making feedback improvements to enhance perceived performance during operations we would like to look into adding small microinteractions throughout the playground to increase the perceived performance of operations some ideas submit transactions in the background and show notification when they are done allowing users to continue working whilst they happen when deploying to hsbn for the first time could we provide more information on what is going on other than a spinner the bottom line make waiting enjoyable | 1 |
110,805 | 16,990,980,497 | IssuesEvent | 2021-06-30 20:26:01 | joshnewton31080/angular | https://api.github.com/repos/joshnewton31080/angular | opened | CVE-2021-23343 (High) detected in path-parse-1.0.5.tgz | security vulnerability | ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.5.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.5.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.5.tgz</a></p>
<p>Path to dependency file: angular/aio/aio-builds-setup/dockerbuild/scripts-js/package.json</p>
<p>Path to vulnerable library: angular/aio/aio-builds-setup/dockerbuild/scripts-js/node_modules/path-parse</p>
<p>
Dependency Hierarchy:
- tslint-6.1.3.tgz (Root Library)
- resolve-1.4.0.tgz
- :x: **path-parse-1.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/joshnewton31080/angular/commit/0754f95d8686bc67f2d9e82ca6b2652dc6fd0bf3">0754f95d8686bc67f2d9e82ca6b2652dc6fd0bf3</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>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</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/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: path-parse - 1.0.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"path-parse","packageVersion":"1.0.5","packageFilePaths":["/aio/aio-builds-setup/dockerbuild/scripts-js/package.json"],"isTransitiveDependency":true,"dependencyTree":"tslint:6.1.3;resolve:1.4.0;path-parse:1.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"path-parse - 1.0.7"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23343","vulnerabilityDetails":"All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-23343 (High) detected in path-parse-1.0.5.tgz - ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.5.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.5.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.5.tgz</a></p>
<p>Path to dependency file: angular/aio/aio-builds-setup/dockerbuild/scripts-js/package.json</p>
<p>Path to vulnerable library: angular/aio/aio-builds-setup/dockerbuild/scripts-js/node_modules/path-parse</p>
<p>
Dependency Hierarchy:
- tslint-6.1.3.tgz (Root Library)
- resolve-1.4.0.tgz
- :x: **path-parse-1.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/joshnewton31080/angular/commit/0754f95d8686bc67f2d9e82ca6b2652dc6fd0bf3">0754f95d8686bc67f2d9e82ca6b2652dc6fd0bf3</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>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</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/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: path-parse - 1.0.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"path-parse","packageVersion":"1.0.5","packageFilePaths":["/aio/aio-builds-setup/dockerbuild/scripts-js/package.json"],"isTransitiveDependency":true,"dependencyTree":"tslint:6.1.3;resolve:1.4.0;path-parse:1.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"path-parse - 1.0.7"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23343","vulnerabilityDetails":"All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_design | cve high detected in path parse tgz cve high severity vulnerability vulnerable library path parse tgz node js path parse ponyfill library home page a href path to dependency file angular aio aio builds setup dockerbuild scripts js package json path to vulnerable library angular aio aio builds setup dockerbuild scripts js node modules path parse dependency hierarchy tslint tgz root library resolve tgz x path parse tgz vulnerable library found in head commit a href found in base branch master vulnerability details all versions of package path parse are vulnerable to regular expression denial of service redos via splitdevicere splittailre and splitpathre regular expressions redos exhibits polynomial worst case time 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 path parse isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree tslint resolve path parse isminimumfixversionavailable true minimumfixversion path parse basebranches vulnerabilityidentifier cve vulnerabilitydetails all versions of package path parse are vulnerable to regular expression denial of service redos via splitdevicere splittailre and splitpathre regular expressions redos exhibits polynomial worst case time complexity vulnerabilityurl | 0 |
133,791 | 18,356,103,620 | IssuesEvent | 2021-10-08 18:25:25 | Dima2021/moby | https://api.github.com/repos/Dima2021/moby | opened | CVE-2018-16875 (High) detected in github.com/google/certificate-transparency-go-v1.0.20, github.com/google/certificate-transparency-go/x509-v1.0.20 | security vulnerability | ## CVE-2018-16875 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>github.com/google/certificate-transparency-go-v1.0.20</b>, <b>github.com/google/certificate-transparency-go/x509-v1.0.20</b></p></summary>
<p>
<details><summary><b>github.com/google/certificate-transparency-go-v1.0.20</b></p></summary>
<p>Auditing for TLS certificates (Go code)</p>
<p>
Dependency Hierarchy:
- github.com/cloudflare/cfssl/csr-1.3.2 (Root Library)
- github.com/cloudflare/cfssl/helpers-1.3.2
- :x: **github.com/google/certificate-transparency-go-v1.0.20** (Vulnerable Library)
</details>
<details><summary><b>github.com/google/certificate-transparency-go/x509-v1.0.20</b></p></summary>
<p>Auditing for TLS certificates (Go code)</p>
<p>
Dependency Hierarchy:
- github.com/cloudflare/cfssl/csr-1.3.2 (Root Library)
- github.com/cloudflare/cfssl/helpers-1.3.2
- :x: **github.com/google/certificate-transparency-go/x509-v1.0.20** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/moby/commit/74c0db1e26014a7f5e115cea39a5b8613c912db7">74c0db1e26014a7f5e115cea39a5b8613c912db7</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
<p>Publish Date: 2018-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16875>CVE-2018-16875</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-2018-16875">https://nvd.nist.gov/vuln/detail/CVE-2018-16875</a></p>
<p>Release Date: 2018-12-14</p>
<p>Fix Resolution: 1.10.6,1.11.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"GO","packageName":"github.com/google/certificate-transparency-go","packageVersion":"v1.0.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/cloudflare/cfssl/csr:1.3.2;github.com/cloudflare/cfssl/helpers:1.3.2;github.com/google/certificate-transparency-go:v1.0.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.10.6,1.11.3"},{"packageType":"GO","packageName":"github.com/google/certificate-transparency-go/x509","packageVersion":"v1.0.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/cloudflare/cfssl/csr:1.3.2;github.com/cloudflare/cfssl/helpers:1.3.2;github.com/google/certificate-transparency-go/x509:v1.0.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.10.6,1.11.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-16875","vulnerabilityDetails":"The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16875","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-16875 (High) detected in github.com/google/certificate-transparency-go-v1.0.20, github.com/google/certificate-transparency-go/x509-v1.0.20 - ## CVE-2018-16875 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>github.com/google/certificate-transparency-go-v1.0.20</b>, <b>github.com/google/certificate-transparency-go/x509-v1.0.20</b></p></summary>
<p>
<details><summary><b>github.com/google/certificate-transparency-go-v1.0.20</b></p></summary>
<p>Auditing for TLS certificates (Go code)</p>
<p>
Dependency Hierarchy:
- github.com/cloudflare/cfssl/csr-1.3.2 (Root Library)
- github.com/cloudflare/cfssl/helpers-1.3.2
- :x: **github.com/google/certificate-transparency-go-v1.0.20** (Vulnerable Library)
</details>
<details><summary><b>github.com/google/certificate-transparency-go/x509-v1.0.20</b></p></summary>
<p>Auditing for TLS certificates (Go code)</p>
<p>
Dependency Hierarchy:
- github.com/cloudflare/cfssl/csr-1.3.2 (Root Library)
- github.com/cloudflare/cfssl/helpers-1.3.2
- :x: **github.com/google/certificate-transparency-go/x509-v1.0.20** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/moby/commit/74c0db1e26014a7f5e115cea39a5b8613c912db7">74c0db1e26014a7f5e115cea39a5b8613c912db7</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
<p>Publish Date: 2018-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16875>CVE-2018-16875</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-2018-16875">https://nvd.nist.gov/vuln/detail/CVE-2018-16875</a></p>
<p>Release Date: 2018-12-14</p>
<p>Fix Resolution: 1.10.6,1.11.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"GO","packageName":"github.com/google/certificate-transparency-go","packageVersion":"v1.0.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/cloudflare/cfssl/csr:1.3.2;github.com/cloudflare/cfssl/helpers:1.3.2;github.com/google/certificate-transparency-go:v1.0.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.10.6,1.11.3"},{"packageType":"GO","packageName":"github.com/google/certificate-transparency-go/x509","packageVersion":"v1.0.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/cloudflare/cfssl/csr:1.3.2;github.com/cloudflare/cfssl/helpers:1.3.2;github.com/google/certificate-transparency-go/x509:v1.0.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.10.6,1.11.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-16875","vulnerabilityDetails":"The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16875","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_design | cve high detected in github com google certificate transparency go github com google certificate transparency go cve high severity vulnerability vulnerable libraries github com google certificate transparency go github com google certificate transparency go github com google certificate transparency go auditing for tls certificates go code dependency hierarchy github com cloudflare cfssl csr root library github com cloudflare cfssl helpers x github com google certificate transparency go vulnerable library github com google certificate transparency go auditing for tls certificates go code dependency hierarchy github com cloudflare cfssl csr root library github com cloudflare cfssl helpers x github com google certificate transparency go vulnerable library found in head commit a href found in base branch master vulnerability details the crypto package of go before and x before does not limit the amount of work performed for each chain verification which might allow attackers to craft pathological inputs leading to a cpu denial of service go tls servers accepting client certificates and tls clients are affected 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 isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree github com cloudflare cfssl csr github com cloudflare cfssl helpers github com google certificate transparency go isminimumfixversionavailable true minimumfixversion packagetype go packagename github com google certificate transparency go packageversion packagefilepaths istransitivedependency true dependencytree github com cloudflare cfssl csr github com cloudflare cfssl helpers github com google certificate transparency go isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails the crypto package of go before and x before does not limit the amount of work performed for each chain verification which might allow attackers to craft pathological inputs leading to a cpu denial of service go tls servers accepting client certificates and tls clients are affected vulnerabilityurl | 0 |
43,603 | 11,269,627,819 | IssuesEvent | 2020-01-14 09:18:52 | xamarin/xamarin-android | https://api.github.com/repos/xamarin/xamarin-android | closed | APT0000: unexpected element <activity> found in <manifest>. | Area: App+Library Build need-info | ### Steps to Reproduce
1. Enable aapt2 (Use incremental android packaging system ) in Android Build >> General
2. Build the application
### Expected Behavior
We should be able get the sucessful build
### Actual Behavior
**Local Build Error** : APT0000: unexpected element <activity> found in <manifest>.
**App Center Build Error (only after enabling .aab build) :**
1. APT0000: unexpected element <activity> found in <manifest>.
2. ##[error]Error: The process '/Library/Frameworks/Mono.framework/Versions/6_4_0/bin/msbuild' failed with exit code 1
### Local Version Information
=== Visual Studio Community 2019 for Mac ===
Version 8.4 (build 2657)
Installation UUID: e68b7427-2235-4d07-8203-ade9ce959a07
GTK+ 2.24.23 (Raleigh theme)
Xamarin.Mac 5.16.1.25 (issue-7441-d16-3-vsmac / 881172e73)
Package version: 606000155
=== Mono Framework MDK ===
Runtime:
Mono 6.6.0.155 (2019-08/296a9afdb24) (64-bit)
Package version: 606000155
=== Roslyn (Language Service) ===
3.4.0-beta4-19562-05+ff930dec4565e2bc424ad3bf3e22ecb20542c87d
=== NuGet ===
Version: 5.3.0.6192
=== .NET Core SDK ===
SDK: /usr/local/share/dotnet/sdk/3.1.100/Sdks
SDK Versions:
3.1.100
3.0.101
2.1.701
2.1.700
2.1.505
2.1.302
2.1.300-preview2-008533
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/6.6.0/lib/mono/msbuild/Current/bin/Sdks
=== .NET Core Runtime ===
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
3.1.0
3.0.1
2.1.14
2.1.12
2.1.11
2.1.9
2.1.2
2.1.0-preview2-26406-04
=== Xamarin.Profiler ===
Version: 1.6.12.29
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Updater ===
Version: 11
=== Apple Developer Tools ===
Xcode 11.3 (15712)
Build 11C29
=== Xamarin.Mac ===
Version: 6.8.3.0 (Visual Studio Community)
Hash: 0d8fe219c
Branch: d16-4
Build date: 2019-12-04 13:06:40-0500
=== Xamarin.iOS ===
Version: 13.8.3.0 (Visual Studio Community)
Hash: 0d8fe219c
Branch: d16-4
Build date: 2019-12-04 13:06:41-0500
=== Xamarin Designer ===
Version: 16.4.0.468
Hash: 519082ea8
Branch: remotes/origin/d16-4
Build date: 2019-12-04 16:21:00 UTC
=== Xamarin.Android ===
Version: 10.1.1.0 (Visual Studio Community)
Commit: xamarin-android/d16-4/f2c9364
Android SDK: /Users/abhijeet/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
7.0 (API level 24)
7.1 (API level 25)
8.0 (API level 26)
8.1 (API level 27)
SDK Tools Version: 26.1.1
SDK Platform Tools Version: 29.0.5
SDK Build Tools Version: 29.0.2
Build Information:
Mono: bef1e63
Java.Interop: xamarin/java.interop/d16-4@c4e569f
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.28.0@46204c4
Xamarin.Android Tools: xamarin/xamarin-android-tools/master@9f4ed4b
=== Microsoft Mobile OpenJDK ===
Java SDK: /Users/abhijeet/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_8.0.25
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL
=== Android SDK Manager ===
Version: 16.4.0.9
Hash: 3f7256f
Branch: remotes/origin/d16-4
Build date: 2019-12-19 18:59:12 UTC
=== Android Device Manager ===
Version: 16.4.0.28
Hash: 68e9956
Branch: remotes/origin/d16-4
Build date: 2019-12-19 18:59:32 UTC
=== Xamarin Inspector ===
Version: 1.4.3
Hash: db27525
Branch: 1.4-release
Build date: Mon, 09 Jul 2018 21:20:18 GMT
Client compatibility: 1
=== Build Information ===
Release ID: 804002657
Git revision: 4c6723413e884e024466fc93ff10e938bca7f721
Build date: 2020-01-06 18:20:13+00
Build branch: release-8.4
Xamarin extensions: 0f572cad12fd3886cd8e21a8b93b86e29ceaf111
=== Operating System ===
Mac OS X 10.14.6
Darwin 18.7.0 Darwin Kernel Version 18.7.0
Thu Jun 20 18:42:21 PDT 2019
root:xnu-4903.270.47~4/RELEASE_X86_64 x86_64
| 1.0 | APT0000: unexpected element <activity> found in <manifest>. - ### Steps to Reproduce
1. Enable aapt2 (Use incremental android packaging system ) in Android Build >> General
2. Build the application
### Expected Behavior
We should be able get the sucessful build
### Actual Behavior
**Local Build Error** : APT0000: unexpected element <activity> found in <manifest>.
**App Center Build Error (only after enabling .aab build) :**
1. APT0000: unexpected element <activity> found in <manifest>.
2. ##[error]Error: The process '/Library/Frameworks/Mono.framework/Versions/6_4_0/bin/msbuild' failed with exit code 1
### Local Version Information
=== Visual Studio Community 2019 for Mac ===
Version 8.4 (build 2657)
Installation UUID: e68b7427-2235-4d07-8203-ade9ce959a07
GTK+ 2.24.23 (Raleigh theme)
Xamarin.Mac 5.16.1.25 (issue-7441-d16-3-vsmac / 881172e73)
Package version: 606000155
=== Mono Framework MDK ===
Runtime:
Mono 6.6.0.155 (2019-08/296a9afdb24) (64-bit)
Package version: 606000155
=== Roslyn (Language Service) ===
3.4.0-beta4-19562-05+ff930dec4565e2bc424ad3bf3e22ecb20542c87d
=== NuGet ===
Version: 5.3.0.6192
=== .NET Core SDK ===
SDK: /usr/local/share/dotnet/sdk/3.1.100/Sdks
SDK Versions:
3.1.100
3.0.101
2.1.701
2.1.700
2.1.505
2.1.302
2.1.300-preview2-008533
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/6.6.0/lib/mono/msbuild/Current/bin/Sdks
=== .NET Core Runtime ===
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
3.1.0
3.0.1
2.1.14
2.1.12
2.1.11
2.1.9
2.1.2
2.1.0-preview2-26406-04
=== Xamarin.Profiler ===
Version: 1.6.12.29
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Updater ===
Version: 11
=== Apple Developer Tools ===
Xcode 11.3 (15712)
Build 11C29
=== Xamarin.Mac ===
Version: 6.8.3.0 (Visual Studio Community)
Hash: 0d8fe219c
Branch: d16-4
Build date: 2019-12-04 13:06:40-0500
=== Xamarin.iOS ===
Version: 13.8.3.0 (Visual Studio Community)
Hash: 0d8fe219c
Branch: d16-4
Build date: 2019-12-04 13:06:41-0500
=== Xamarin Designer ===
Version: 16.4.0.468
Hash: 519082ea8
Branch: remotes/origin/d16-4
Build date: 2019-12-04 16:21:00 UTC
=== Xamarin.Android ===
Version: 10.1.1.0 (Visual Studio Community)
Commit: xamarin-android/d16-4/f2c9364
Android SDK: /Users/abhijeet/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
7.0 (API level 24)
7.1 (API level 25)
8.0 (API level 26)
8.1 (API level 27)
SDK Tools Version: 26.1.1
SDK Platform Tools Version: 29.0.5
SDK Build Tools Version: 29.0.2
Build Information:
Mono: bef1e63
Java.Interop: xamarin/java.interop/d16-4@c4e569f
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.28.0@46204c4
Xamarin.Android Tools: xamarin/xamarin-android-tools/master@9f4ed4b
=== Microsoft Mobile OpenJDK ===
Java SDK: /Users/abhijeet/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_8.0.25
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL
=== Android SDK Manager ===
Version: 16.4.0.9
Hash: 3f7256f
Branch: remotes/origin/d16-4
Build date: 2019-12-19 18:59:12 UTC
=== Android Device Manager ===
Version: 16.4.0.28
Hash: 68e9956
Branch: remotes/origin/d16-4
Build date: 2019-12-19 18:59:32 UTC
=== Xamarin Inspector ===
Version: 1.4.3
Hash: db27525
Branch: 1.4-release
Build date: Mon, 09 Jul 2018 21:20:18 GMT
Client compatibility: 1
=== Build Information ===
Release ID: 804002657
Git revision: 4c6723413e884e024466fc93ff10e938bca7f721
Build date: 2020-01-06 18:20:13+00
Build branch: release-8.4
Xamarin extensions: 0f572cad12fd3886cd8e21a8b93b86e29ceaf111
=== Operating System ===
Mac OS X 10.14.6
Darwin 18.7.0 Darwin Kernel Version 18.7.0
Thu Jun 20 18:42:21 PDT 2019
root:xnu-4903.270.47~4/RELEASE_X86_64 x86_64
| non_design | unexpected element found in steps to reproduce enable use incremental android packaging system in android build general build the application expected behavior we should be able get the sucessful build actual behavior local build error unexpected element found in app center build error only after enabling aab build unexpected element found in error the process library frameworks mono framework versions bin msbuild failed with exit code local version information visual studio community for mac version build installation uuid gtk raleigh theme xamarin mac issue vsmac package version mono framework mdk runtime mono bit package version roslyn language service nuget version net core sdk sdk usr local share dotnet sdk sdks sdk versions msbuild sdks library frameworks mono framework versions lib mono msbuild current bin sdks net core runtime runtime usr local share dotnet dotnet runtime versions xamarin profiler version location applications xamarin profiler app contents macos xamarin profiler updater version apple developer tools xcode build xamarin mac version visual studio community hash branch build date xamarin ios version visual studio community hash branch build date xamarin designer version hash branch remotes origin build date utc xamarin android version visual studio community commit xamarin android android sdk users abhijeet library developer xamarin android sdk macosx supported android versions api level api level api level api level api level api level api level sdk tools version sdk platform tools version sdk build tools version build information mono java interop xamarin java interop proguard xamarin proguard master sqlite xamarin sqlite xamarin android tools xamarin xamarin android tools master microsoft mobile openjdk java sdk users abhijeet library developer xamarin jdk microsoft dist openjdk android designer epl code available here android sdk manager version hash branch remotes origin build date utc android device manager version hash branch remotes origin build date utc xamarin inspector version hash branch release build date mon jul gmt client compatibility build information release id git revision build date build branch release xamarin extensions operating system mac os x darwin darwin kernel version thu jun pdt root xnu release | 0 |
232,065 | 25,564,927,422 | IssuesEvent | 2022-11-30 13:39:04 | yaeljacobs67/npm-plugin | https://api.github.com/repos/yaeljacobs67/npm-plugin | opened | CVE-2022-38900 (High) detected in decode-uri-component-0.2.0.tgz | security vulnerability | ## CVE-2022-38900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p></summary>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.1.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- source-map-resolve-0.5.2.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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>
| True | CVE-2022-38900 (High) detected in decode-uri-component-0.2.0.tgz - ## CVE-2022-38900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p></summary>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.1.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- source-map-resolve-0.5.2.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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>
| non_design | cve high detected in decode uri component tgz cve high severity vulnerability vulnerable library decode uri component tgz a better decodeuricomponent library home page a href dependency hierarchy grunt cli tgz root library liftoff tgz findup sync tgz micromatch tgz snapdragon tgz source map resolve tgz x decode uri component tgz vulnerable library vulnerability details decode uri component is vulnerable to improper input validation resulting in dos 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 | 0 |
163,160 | 25,762,689,422 | IssuesEvent | 2022-12-08 22:02:24 | CDCgov/prime-reportstream | https://api.github.com/repos/CDCgov/prime-reportstream | closed | Publish "Built for you: New in Reportstream" | design onboarding-ops Epic needs-info content pipeline experience | ## Problem Statement
As a user of ReportStream, I want to know what newly built product information and feature has become available for me.
As an organization, ReportStream needs multiple ways to communicate about new offerings to users.
## Note
- One way is a public webpage, "Build for you: new in ReportStream"
- [Example 1](https://www.intercom.com/changes/en) and [Example 2](https://mailchimp.com/whats-new/)
## To Do
- [ ] Engineers make two changes to existing release notes operations: 1) link PR with original ticket that has user outcome(s) described; 2) Write PR title as [original ticket number] + [title]. detailed proposal [here.](https://cdc.sharepoint.com/:p:/r/teams/USDSatCDC/Shared%20Documents/PRIME%20ReportStream/Releases/ReleaseNotesProposal.pptx?d=w961c0804374b48f98df066d3fcd3ce2c&csf=1&web=1&e=f0wVYU ) TLDR [one-pager here](https://cdc.sharepoint.com/:w:/t/USDSatCDC/ERjfi1u0TN5OubshesUvnSQBgOLOEO4Ig5XWQYfskgYh3g?e=6OqlRB).
- [ ] Product managers create user-friendly content, day after every sprint
- [ ] Experience team create and maintain webpage and ensures user-friendly content adheres to plain language and content style guidelines
## Consideration
Best practices for formatting summarized release notes:
- Title / Heading (keep it short, clear, and catchy so user feels compelled to read)
- Company / Product Name (help user to know which product is being updated)
- Version and Date (helps user to know when the changes were made)
- New Features (descriptive text and images/videos of new features)
- Fixed Issues (mention what was fixed and how they improve problems in past)
- Improvements (include enhancements from last version)
- Additional Resources (link up any how-tos or other resources)
| 1.0 | Publish "Built for you: New in Reportstream" - ## Problem Statement
As a user of ReportStream, I want to know what newly built product information and feature has become available for me.
As an organization, ReportStream needs multiple ways to communicate about new offerings to users.
## Note
- One way is a public webpage, "Build for you: new in ReportStream"
- [Example 1](https://www.intercom.com/changes/en) and [Example 2](https://mailchimp.com/whats-new/)
## To Do
- [ ] Engineers make two changes to existing release notes operations: 1) link PR with original ticket that has user outcome(s) described; 2) Write PR title as [original ticket number] + [title]. detailed proposal [here.](https://cdc.sharepoint.com/:p:/r/teams/USDSatCDC/Shared%20Documents/PRIME%20ReportStream/Releases/ReleaseNotesProposal.pptx?d=w961c0804374b48f98df066d3fcd3ce2c&csf=1&web=1&e=f0wVYU ) TLDR [one-pager here](https://cdc.sharepoint.com/:w:/t/USDSatCDC/ERjfi1u0TN5OubshesUvnSQBgOLOEO4Ig5XWQYfskgYh3g?e=6OqlRB).
- [ ] Product managers create user-friendly content, day after every sprint
- [ ] Experience team create and maintain webpage and ensures user-friendly content adheres to plain language and content style guidelines
## Consideration
Best practices for formatting summarized release notes:
- Title / Heading (keep it short, clear, and catchy so user feels compelled to read)
- Company / Product Name (help user to know which product is being updated)
- Version and Date (helps user to know when the changes were made)
- New Features (descriptive text and images/videos of new features)
- Fixed Issues (mention what was fixed and how they improve problems in past)
- Improvements (include enhancements from last version)
- Additional Resources (link up any how-tos or other resources)
| design | publish built for you new in reportstream problem statement as a user of reportstream i want to know what newly built product information and feature has become available for me as an organization reportstream needs multiple ways to communicate about new offerings to users note one way is a public webpage build for you new in reportstream and to do engineers make two changes to existing release notes operations link pr with original ticket that has user outcome s described write pr title as detailed proposal tldr product managers create user friendly content day after every sprint experience team create and maintain webpage and ensures user friendly content adheres to plain language and content style guidelines consideration best practices for formatting summarized release notes title heading keep it short clear and catchy so user feels compelled to read company product name help user to know which product is being updated version and date helps user to know when the changes were made new features descriptive text and images videos of new features fixed issues mention what was fixed and how they improve problems in past improvements include enhancements from last version additional resources link up any how tos or other resources | 1 |
63,000 | 7,663,942,329 | IssuesEvent | 2018-05-12 00:33:16 | plugdj/Issues-and-Reports | https://api.github.com/repos/plugdj/Issues-and-Reports | closed | Settings button invisible & Join Date text too large for small screen resolution | Bug Fixed Redesign V1 Web Application | <!--
These comments will be invisible in your issue once it is created.
You can delete them or keep them, but please read all of it.
PLEASE:
1. Check the README.md file (it's the first view when you open the repository);
LINK: https://github.com/plugdj/Issues-and-Reports
2. Search for your issue, if it is already submitted, add an emoji reaction or give feedback;
3. If you need to report a security breach or any other sensitive issue (involving privacy or exploits),
DON'T DO IT HERE, email security@plug.dj instead.
4. If you need to report an issue regarding account recovery or account details,
DON'T DO IT HERE, email support@plug.dj instead.
5. Check the Status Page for stability or connection issues, avoid submitting what is there;
LINK: https://status.plug.dj
6. If your issue can be submitted here, read the requirements (questions below);
7. Be precise, provide images, let others know how you encountered the issue;
8. Be polite, telling people what to do will not get an issue fixed faster;
-->
<!-- Examples: [Web App Issue, Mobile App Issue] -->
### PLATFORM Issue
Web App Issue
<!-- Examples: [plug.dj Web version 1.5.6.10975], [plug.dj Android Beta Version 2.6.7] -->
#### plug.dj version
Plug.dj Web Version 1.6.0.11743
<!-- Examples: [Google Nexus 4 Android 5.0.1, Chrome 60.0.3112.66 Beta 64-bit] -->
<!-- HOW TO CHECK: https://github.com/plugdj/Issues-and-Reports/blob/master/.github/CONTRIBUTING.md#versions -->
#### OS/Browser Name and Version
Windows 10 Home 1709 16299.371, 67.0.3396.30 (Official Build) beta (64-bit) (cohort: Beta)
<!--
CORRECT:
- [x] Reloading the page/app
- [X] Reloading the page/app
WRONG:
- [ x ] Reloading the page/app
- [ x ] Reloading the page/app
- [x ] Reloading the page/app
- [yes] Reloading the page/app
-->
#### I have tried
- [x] Reloading the page/app
- [x] Clearing (browser) cache, cookies or (mobile) app data
- [x] Switching to the default language (English)
- [x] Disabling all extensions and scripts (browser only)
- [ ] Reinstalling the app (mobile only)
<!-- Please be as descriptive as possible, upload images to https://imgur.com -->
#### Description, Images, Logs
http://i.tfle.xyz/2018-05-08_22-15-10.png
http://i.tfle.xyz/2018-05-08_22-15-51.png
##### Steps to reproduce:
Click on the settings menu via any means, easiest being the avatar at the top right
The settings button is not visible on the screen resolution of 1366x768
Click on the friends menu via any means, easiest being the avatar at the top right
The join date is way too large.
<!-- Do not post your email address as that could put your account in danger -->
<!-- Examples: [Plug Technologies, Inc.; 23810294; https://plug.dj/@/plug-technologies-inc] -->
#### plug.dj username, profile link or user ID
https://plug.dj/@/thedark1337-plug-dev
| 1.0 | Settings button invisible & Join Date text too large for small screen resolution - <!--
These comments will be invisible in your issue once it is created.
You can delete them or keep them, but please read all of it.
PLEASE:
1. Check the README.md file (it's the first view when you open the repository);
LINK: https://github.com/plugdj/Issues-and-Reports
2. Search for your issue, if it is already submitted, add an emoji reaction or give feedback;
3. If you need to report a security breach or any other sensitive issue (involving privacy or exploits),
DON'T DO IT HERE, email security@plug.dj instead.
4. If you need to report an issue regarding account recovery or account details,
DON'T DO IT HERE, email support@plug.dj instead.
5. Check the Status Page for stability or connection issues, avoid submitting what is there;
LINK: https://status.plug.dj
6. If your issue can be submitted here, read the requirements (questions below);
7. Be precise, provide images, let others know how you encountered the issue;
8. Be polite, telling people what to do will not get an issue fixed faster;
-->
<!-- Examples: [Web App Issue, Mobile App Issue] -->
### PLATFORM Issue
Web App Issue
<!-- Examples: [plug.dj Web version 1.5.6.10975], [plug.dj Android Beta Version 2.6.7] -->
#### plug.dj version
Plug.dj Web Version 1.6.0.11743
<!-- Examples: [Google Nexus 4 Android 5.0.1, Chrome 60.0.3112.66 Beta 64-bit] -->
<!-- HOW TO CHECK: https://github.com/plugdj/Issues-and-Reports/blob/master/.github/CONTRIBUTING.md#versions -->
#### OS/Browser Name and Version
Windows 10 Home 1709 16299.371, 67.0.3396.30 (Official Build) beta (64-bit) (cohort: Beta)
<!--
CORRECT:
- [x] Reloading the page/app
- [X] Reloading the page/app
WRONG:
- [ x ] Reloading the page/app
- [ x ] Reloading the page/app
- [x ] Reloading the page/app
- [yes] Reloading the page/app
-->
#### I have tried
- [x] Reloading the page/app
- [x] Clearing (browser) cache, cookies or (mobile) app data
- [x] Switching to the default language (English)
- [x] Disabling all extensions and scripts (browser only)
- [ ] Reinstalling the app (mobile only)
<!-- Please be as descriptive as possible, upload images to https://imgur.com -->
#### Description, Images, Logs
http://i.tfle.xyz/2018-05-08_22-15-10.png
http://i.tfle.xyz/2018-05-08_22-15-51.png
##### Steps to reproduce:
Click on the settings menu via any means, easiest being the avatar at the top right
The settings button is not visible on the screen resolution of 1366x768
Click on the friends menu via any means, easiest being the avatar at the top right
The join date is way too large.
<!-- Do not post your email address as that could put your account in danger -->
<!-- Examples: [Plug Technologies, Inc.; 23810294; https://plug.dj/@/plug-technologies-inc] -->
#### plug.dj username, profile link or user ID
https://plug.dj/@/thedark1337-plug-dev
| design | settings button invisible join date text too large for small screen resolution these comments will be invisible in your issue once it is created you can delete them or keep them but please read all of it please check the readme md file it s the first view when you open the repository link search for your issue if it is already submitted add an emoji reaction or give feedback if you need to report a security breach or any other sensitive issue involving privacy or exploits don t do it here email security plug dj instead if you need to report an issue regarding account recovery or account details don t do it here email support plug dj instead check the status page for stability or connection issues avoid submitting what is there link if your issue can be submitted here read the requirements questions below be precise provide images let others know how you encountered the issue be polite telling people what to do will not get an issue fixed faster platform issue web app issue plug dj version plug dj web version os browser name and version windows home official build beta bit cohort beta correct reloading the page app reloading the page app wrong reloading the page app reloading the page app reloading the page app reloading the page app i have tried reloading the page app clearing browser cache cookies or mobile app data switching to the default language english disabling all extensions and scripts browser only reinstalling the app mobile only description images logs steps to reproduce click on the settings menu via any means easiest being the avatar at the top right the settings button is not visible on the screen resolution of click on the friends menu via any means easiest being the avatar at the top right the join date is way too large plug dj username profile link or user id | 1 |
277,316 | 24,059,501,855 | IssuesEvent | 2022-09-16 20:33:00 | eclipse/dirigible | https://api.github.com/repos/eclipse/dirigible | closed | [Test] Use h2 in AbstractDirigibleTest | component-core tests | Add `Configuration.set("DIRIGIBLE_DATABASE_H2_URL", "jdbc:h2:mem:xsk-tests");`
to the AbstractDirigibleTest class, so that it uses h2 instead of derby. | 1.0 | [Test] Use h2 in AbstractDirigibleTest - Add `Configuration.set("DIRIGIBLE_DATABASE_H2_URL", "jdbc:h2:mem:xsk-tests");`
to the AbstractDirigibleTest class, so that it uses h2 instead of derby. | non_design | use in abstractdirigibletest add configuration set dirigible database url jdbc mem xsk tests to the abstractdirigibletest class so that it uses instead of derby | 0 |
191,562 | 22,215,806,326 | IssuesEvent | 2022-06-08 01:25:34 | Nivaskumark/kernel_v4.1.15 | https://api.github.com/repos/Nivaskumark/kernel_v4.1.15 | reopened | CVE-2018-1065 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2018-1065 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b></p></summary>
<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 netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/ipv4/netfilter/arp_tables.c, ipt_do_table in net/ipv4/netfilter/ip_tables.c, and ip6t_do_table in net/ipv6/netfilter/ip6_tables.c.
<p>Publish Date: 2018-03-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1065>CVE-2018-1065</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>4.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1065">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1065</a></p>
<p>Release Date: 2018-03-02</p>
<p>Fix Resolution: v4.16</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-1065 (Medium) detected in multiple libraries - ## CVE-2018-1065 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b></p></summary>
<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 netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/ipv4/netfilter/arp_tables.c, ipt_do_table in net/ipv4/netfilter/ip_tables.c, and ip6t_do_table in net/ipv6/netfilter/ip6_tables.c.
<p>Publish Date: 2018-03-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1065>CVE-2018-1065</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>4.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1065">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1065</a></p>
<p>Release Date: 2018-03-02</p>
<p>Fix Resolution: v4.16</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 multiple libraries cve medium severity vulnerability vulnerable libraries linuxlinux linuxlinux linuxlinux vulnerability details the netfilter subsystem in the linux kernel through mishandles the case of a rule blob that contains a jump but lacks a user defined chain which allows local users to cause a denial of service null pointer dereference by leveraging the cap net raw or cap net admin capability related to arpt do table in net netfilter arp tables c ipt do table in net netfilter ip tables c and do table in net netfilter tables c publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
88,375 | 11,089,534,805 | IssuesEvent | 2019-12-14 19:11:58 | howToCodeWell/code-challenges | https://api.github.com/repos/howToCodeWell/code-challenges | closed | Add icons for languages used | design enhancement | These icons should be based on the technologies used such as PHP, JS, Symfony etc..
Icons need to be downloaded from somewhere | 1.0 | Add icons for languages used - These icons should be based on the technologies used such as PHP, JS, Symfony etc..
Icons need to be downloaded from somewhere | design | add icons for languages used these icons should be based on the technologies used such as php js symfony etc icons need to be downloaded from somewhere | 1 |
40,782 | 8,847,362,711 | IssuesEvent | 2019-01-08 01:22:07 | pnp/pnpjs | https://api.github.com/repos/pnp/pnpjs | closed | Can't make batching work in sp-taxonomy | area: code status: details needed type: bug | ### Category
- [ ] Enhancement
- [x] Bug
- [x] Question
- [ ] Documentation gap/issue
### Version
Please specify what version of the library you are using: [1.2.7]
Please specify what version(s) of SharePoint you are targeting: [SharePoint Online]
### Expected / Desired Behavior / Question
Batching for `sp-taxonomy` works
### Observed Behavior
I don't see any outgoing requests after `batch.execute`
### Steps to Reproduce
```typescript
taxonomy.setup({
spfxContext: this.context
});
var termStores = await taxonomy.termStores.get();
let returnTerms: IPickerTerm[] = [];
for (let i = 0, len = termStores.length; i < len; i++) {
const pnpTermStore = termStores[i];
const pnpTerms = await pnpTermStore.getTerms({
TermLabel: 'Mar',
StringMatchOption: StringMatchOption.StartsWith,
DefaultLabelOnly: true,
TrimUnavailable: true,
ResultCollectionSize: 10
}).get();
const batch = taxonomy.createBatch();
// in real scenario there should be pnpTerms.forEach
const term = pnpTerms[0];
term.termSet.inBatch(batch).get().then(termSet => {
console.log(termSet);
});
term.labels.inBatch(batch).get().then(labels => {
console.log(labels);
});
await batch.execute();
``` | 1.0 | Can't make batching work in sp-taxonomy - ### Category
- [ ] Enhancement
- [x] Bug
- [x] Question
- [ ] Documentation gap/issue
### Version
Please specify what version of the library you are using: [1.2.7]
Please specify what version(s) of SharePoint you are targeting: [SharePoint Online]
### Expected / Desired Behavior / Question
Batching for `sp-taxonomy` works
### Observed Behavior
I don't see any outgoing requests after `batch.execute`
### Steps to Reproduce
```typescript
taxonomy.setup({
spfxContext: this.context
});
var termStores = await taxonomy.termStores.get();
let returnTerms: IPickerTerm[] = [];
for (let i = 0, len = termStores.length; i < len; i++) {
const pnpTermStore = termStores[i];
const pnpTerms = await pnpTermStore.getTerms({
TermLabel: 'Mar',
StringMatchOption: StringMatchOption.StartsWith,
DefaultLabelOnly: true,
TrimUnavailable: true,
ResultCollectionSize: 10
}).get();
const batch = taxonomy.createBatch();
// in real scenario there should be pnpTerms.forEach
const term = pnpTerms[0];
term.termSet.inBatch(batch).get().then(termSet => {
console.log(termSet);
});
term.labels.inBatch(batch).get().then(labels => {
console.log(labels);
});
await batch.execute();
``` | non_design | can t make batching work in sp taxonomy category enhancement bug question documentation gap issue version please specify what version of the library you are using please specify what version s of sharepoint you are targeting expected desired behavior question batching for sp taxonomy works observed behavior i don t see any outgoing requests after batch execute steps to reproduce typescript taxonomy setup spfxcontext this context var termstores await taxonomy termstores get let returnterms ipickerterm for let i len termstores length i len i const pnptermstore termstores const pnpterms await pnptermstore getterms termlabel mar stringmatchoption stringmatchoption startswith defaultlabelonly true trimunavailable true resultcollectionsize get const batch taxonomy createbatch in real scenario there should be pnpterms foreach const term pnpterms term termset inbatch batch get then termset console log termset term labels inbatch batch get then labels console log labels await batch execute | 0 |
40,166 | 5,188,487,254 | IssuesEvent | 2017-01-20 20:05:51 | phetsims/unit-rates | https://api.github.com/repos/phetsims/unit-rates | closed | clarify where state is saved/restored | design:general | I think I have a handle on where state is saved/restored -- each item has its own state. But wanted to clarify.
| 1.0 | clarify where state is saved/restored - I think I have a handle on where state is saved/restored -- each item has its own state. But wanted to clarify.
| design | clarify where state is saved restored i think i have a handle on where state is saved restored each item has its own state but wanted to clarify | 1 |
61,361 | 7,460,928,426 | IssuesEvent | 2018-03-30 22:08:59 | sitecrafting/conifer | https://api.github.com/repos/sitecrafting/conifer | closed | Refactor Menu/MenuItem classes | design easy | Move these to the `Conifer\Navigation` namespace. This is where `MenuItemMatcher` will eventually go. | 1.0 | Refactor Menu/MenuItem classes - Move these to the `Conifer\Navigation` namespace. This is where `MenuItemMatcher` will eventually go. | design | refactor menu menuitem classes move these to the conifer navigation namespace this is where menuitemmatcher will eventually go | 1 |
61,083 | 7,438,793,298 | IssuesEvent | 2018-03-27 02:33:27 | jon-str/EmuSandbox | https://api.github.com/repos/jon-str/EmuSandbox | opened | [EmuSandbox-RM-DSGN-D] Design test REGISTER class | design roadmap | Design object to be named "REGISTER ." "REGISTER " will contain BinaryValue relevant to the size of the register in bits
Must have:
- value
- ToString() | 1.0 | [EmuSandbox-RM-DSGN-D] Design test REGISTER class - Design object to be named "REGISTER ." "REGISTER " will contain BinaryValue relevant to the size of the register in bits
Must have:
- value
- ToString() | design | design test register class design object to be named register register will contain binaryvalue relevant to the size of the register in bits must have value tostring | 1 |
160,047 | 6,068,709,116 | IssuesEvent | 2017-06-15 00:56:18 | nossas/bonde-server | https://api.github.com/repos/nossas/bonde-server | opened | Community invitation link on email redirecting to an invalid page | Priority: High Stage: Backlog Type: Bug | # Related pull-requests
- Release v0.5.8 #666
# Description
When a community member invites someone else to join to his community, an email has been sent like:
<img width="1188" alt="screen shot 2017-06-14 at 21 52 25" src="https://user-images.githubusercontent.com/5435389/27160643-13ccf832-514c-11e7-89e7-6379caf45bd3.png">
When the invited person clicks on the **@invitation.link** link, it is redirecting to an invalid BONDE page. | 1.0 | Community invitation link on email redirecting to an invalid page - # Related pull-requests
- Release v0.5.8 #666
# Description
When a community member invites someone else to join to his community, an email has been sent like:
<img width="1188" alt="screen shot 2017-06-14 at 21 52 25" src="https://user-images.githubusercontent.com/5435389/27160643-13ccf832-514c-11e7-89e7-6379caf45bd3.png">
When the invited person clicks on the **@invitation.link** link, it is redirecting to an invalid BONDE page. | non_design | community invitation link on email redirecting to an invalid page related pull requests release description when a community member invites someone else to join to his community an email has been sent like img width alt screen shot at src when the invited person clicks on the invitation link link it is redirecting to an invalid bonde page | 0 |
21,792 | 7,085,580,600 | IssuesEvent | 2018-01-11 11:28:34 | systemd/systemd | https://api.github.com/repos/systemd/systemd | closed | systemd-236 fails to build without libgcrypt being present | build-system has-pr | ### Submission type
<!-- Delete the inappropriate option below: -->
- Bug report
<!-- **NOTE:** Do not submit anything other than bug reports or RFEs via the issue tracker! -->
### systemd version the issue has been seen with
> 236
<!-- **NOTE:** Do not submit bug reports about anything but the two most recently released systemd versions upstream! -->
<!-- For older version please use distribution trackers (see https://github.com/systemd/systemd/blob/master/.github/CONTRIBUTING.md#filing-issues). -->
### Used distribution
> Exherbo
### In case of bug report: Expected behaviour you didn't see
> Compile successfully
### In case of bug report: Unexpected behaviour you saw
> Error during compilation
```
x86_64-pc-linux-gnu-cc -Itest-dnssec@exe -I. -I../systemd-236 -I../systemd-236/ -Isrc/libsystemd-network -I../systemd-236/src/libsystemd-network -I../systemd-236/src/libsystemd/sd-network -I../systemd-236/src/libsystemd/sd-netlink -I../systemd-236/src/libsystemd/sd-id128 -I../systemd-236/src/libsystemd/sd-hwdb -I../systemd-236/src/libsystemd/sd-device -I../systemd-236/src/libsystemd/sd-bus -Isrc/core -I../systemd-236/src/core -Isrc/libudev -I../systemd-236/src/libudev -Isrc/udev -I../systemd-236/src/udev -Isrc/login -I../systemd-236/src/login -Isrc/timesync -I../systemd-236/src/timesync -Isrc/resolve -I../systemd-236/src/resolve -Isrc/journal -I../systemd-236/src/journal -Isrc/systemd -I../systemd-236/src/systemd -Isrc/shared -I../systemd-236/src/shared -Isrc/basic -I../systemd-236/src/basic -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong -fPIE --param=ssp-buffer-size=4 -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -march=native -O2 -march=native -O2 -MMD -MQ 'test-dnssec@exe/src_resolve_test-dnssec.c.o' -MF 'test-dnssec@exe/src_resolve_test-dnssec.c.o.d' -o 'test-dnssec@exe/src_resolve_test-dnssec.c.o' -c ../systemd-236/src/resolve/test-dnssec.c
../systemd-236/src/resolve/test-dnssec.c:22:20: fatal error: gcrypt.h: No such file or directory
#include <gcrypt.h>
^
compilation terminated.
```
### In case of bug report: Steps to reproduce the problem
> Uninstall libgcrypt from your system and try to build systemd-236 passing `-Dgcrypt=false` to meson.
The problem looks like it has been introduced with https://github.com/systemd/systemd/commit/cb9eeb062c323391fcd98da0c30e844fa5162e90.
| 1.0 | systemd-236 fails to build without libgcrypt being present - ### Submission type
<!-- Delete the inappropriate option below: -->
- Bug report
<!-- **NOTE:** Do not submit anything other than bug reports or RFEs via the issue tracker! -->
### systemd version the issue has been seen with
> 236
<!-- **NOTE:** Do not submit bug reports about anything but the two most recently released systemd versions upstream! -->
<!-- For older version please use distribution trackers (see https://github.com/systemd/systemd/blob/master/.github/CONTRIBUTING.md#filing-issues). -->
### Used distribution
> Exherbo
### In case of bug report: Expected behaviour you didn't see
> Compile successfully
### In case of bug report: Unexpected behaviour you saw
> Error during compilation
```
x86_64-pc-linux-gnu-cc -Itest-dnssec@exe -I. -I../systemd-236 -I../systemd-236/ -Isrc/libsystemd-network -I../systemd-236/src/libsystemd-network -I../systemd-236/src/libsystemd/sd-network -I../systemd-236/src/libsystemd/sd-netlink -I../systemd-236/src/libsystemd/sd-id128 -I../systemd-236/src/libsystemd/sd-hwdb -I../systemd-236/src/libsystemd/sd-device -I../systemd-236/src/libsystemd/sd-bus -Isrc/core -I../systemd-236/src/core -Isrc/libudev -I../systemd-236/src/libudev -Isrc/udev -I../systemd-236/src/udev -Isrc/login -I../systemd-236/src/login -Isrc/timesync -I../systemd-236/src/timesync -Isrc/resolve -I../systemd-236/src/resolve -Isrc/journal -I../systemd-236/src/journal -Isrc/systemd -I../systemd-236/src/systemd -Isrc/shared -I../systemd-236/src/shared -Isrc/basic -I../systemd-236/src/basic -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong -fPIE --param=ssp-buffer-size=4 -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -march=native -O2 -march=native -O2 -MMD -MQ 'test-dnssec@exe/src_resolve_test-dnssec.c.o' -MF 'test-dnssec@exe/src_resolve_test-dnssec.c.o.d' -o 'test-dnssec@exe/src_resolve_test-dnssec.c.o' -c ../systemd-236/src/resolve/test-dnssec.c
../systemd-236/src/resolve/test-dnssec.c:22:20: fatal error: gcrypt.h: No such file or directory
#include <gcrypt.h>
^
compilation terminated.
```
### In case of bug report: Steps to reproduce the problem
> Uninstall libgcrypt from your system and try to build systemd-236 passing `-Dgcrypt=false` to meson.
The problem looks like it has been introduced with https://github.com/systemd/systemd/commit/cb9eeb062c323391fcd98da0c30e844fa5162e90.
| non_design | systemd fails to build without libgcrypt being present submission type bug report systemd version the issue has been seen with used distribution exherbo in case of bug report expected behaviour you didn t see compile successfully in case of bug report unexpected behaviour you saw error during compilation pc linux gnu cc itest dnssec exe i i systemd i systemd isrc libsystemd network i systemd src libsystemd network i systemd src libsystemd sd network i systemd src libsystemd sd netlink i systemd src libsystemd sd i systemd src libsystemd sd hwdb i systemd src libsystemd sd device i systemd src libsystemd sd bus isrc core i systemd src core isrc libudev i systemd src libudev isrc udev i systemd src udev isrc login i systemd src login isrc timesync i systemd src timesync isrc resolve i systemd src resolve isrc journal i systemd src journal isrc systemd i systemd src systemd isrc shared i systemd src shared isrc basic i systemd src basic fdiagnostics color always pipe d file offset bits wall winvalid pch std g wextra werror undef wlogical op wmissing include dirs wold style definition wpointer arith winit self wdeclaration after statement wfloat equal wsuggest attribute noreturn werror missing prototypes werror implicit function declaration werror missing declarations werror return type werror incompatible pointer types werror format wstrict prototypes wredundant decls wmissing noreturn wshadow wendif labels wstrict aliasing wwrite strings werror overflow wdate time wnested externs ffast math fno common fdiagnostics show option fno strict aliasing fvisibility hidden fstack protector fstack protector strong fpie param ssp buffer size wno unused parameter wno missing field initializers wno unused result wno format signedness wno error nonnull werror shadow include config h march native march native mmd mq test dnssec exe src resolve test dnssec c o mf test dnssec exe src resolve test dnssec c o d o test dnssec exe src resolve test dnssec c o c systemd src resolve test dnssec c systemd src resolve test dnssec c fatal error gcrypt h no such file or directory include compilation terminated in case of bug report steps to reproduce the problem uninstall libgcrypt from your system and try to build systemd passing dgcrypt false to meson the problem looks like it has been introduced with | 0 |
166,734 | 26,400,636,109 | IssuesEvent | 2023-01-13 00:40:24 | gotogether-s/gotogether-s | https://api.github.com/repos/gotogether-s/gotogether-s | closed | Layout | design | ## About
Update style of Layout component
## To do list
- [x] Sort import lines of Layout component
- [x] Replace HTML with MUI in Layout component | 1.0 | Layout - ## About
Update style of Layout component
## To do list
- [x] Sort import lines of Layout component
- [x] Replace HTML with MUI in Layout component | design | layout about update style of layout component to do list sort import lines of layout component replace html with mui in layout component | 1 |
482,969 | 13,916,805,031 | IssuesEvent | 2020-10-21 04:22:18 | code4moldova/voluntar-web | https://api.github.com/repos/code4moldova/voluntar-web | closed | [Admin] Lift "New Request" page into a dialog | Complexity: Low 👶 Priority: Medium Scope: Requests Type: Feature ✨ hacktoberfest | Right now "New Request" page is showed in a new page.
Lift all that page content into a dialog, and keep user on same page without navigation
Trigger "New Request" page using button on http://localhost:4200/admin/requests/list
https://material.angular.io/components/dialog/overview | 1.0 | [Admin] Lift "New Request" page into a dialog - Right now "New Request" page is showed in a new page.
Lift all that page content into a dialog, and keep user on same page without navigation
Trigger "New Request" page using button on http://localhost:4200/admin/requests/list
https://material.angular.io/components/dialog/overview | non_design | lift new request page into a dialog right now new request page is showed in a new page lift all that page content into a dialog and keep user on same page without navigation trigger new request page using button on | 0 |
49,353 | 6,200,323,060 | IssuesEvent | 2017-07-06 00:35:53 | jupyterlab/jupyterlab | https://api.github.com/repos/jupyterlab/jupyterlab | closed | Files - Sorting by Name and Last Modified | pkg:filebrowser tag:Design and UX type:Enhancement | I am using Jupyter Lab version - 0.16.2.
I tried sort by Name and Last modified in Files section on Left hand side and observed following behaviour:
Behaviour on Sort by Name:
a. Folders and files will be grouped
b. Folder will be shown first and sorted according to name
c. Files will be show after folders and sorted according to name
Behaviour on Sort by Modified:
a. Folder and files are jumbled
b. Last modified file or folder will be shown first
Is this expected behaviour and is there anyway to make both behaviour same?
<img width="342" alt="sortbyname" src="https://cloud.githubusercontent.com/assets/895174/25312495/6f962680-2838-11e7-8745-4322df3b31d4.png">
<img width="336" alt="sortbylastmodified" src="https://cloud.githubusercontent.com/assets/895174/25312496/6f96682a-2838-11e7-82c0-6792a66d4740.png">
| 1.0 | Files - Sorting by Name and Last Modified - I am using Jupyter Lab version - 0.16.2.
I tried sort by Name and Last modified in Files section on Left hand side and observed following behaviour:
Behaviour on Sort by Name:
a. Folders and files will be grouped
b. Folder will be shown first and sorted according to name
c. Files will be show after folders and sorted according to name
Behaviour on Sort by Modified:
a. Folder and files are jumbled
b. Last modified file or folder will be shown first
Is this expected behaviour and is there anyway to make both behaviour same?
<img width="342" alt="sortbyname" src="https://cloud.githubusercontent.com/assets/895174/25312495/6f962680-2838-11e7-8745-4322df3b31d4.png">
<img width="336" alt="sortbylastmodified" src="https://cloud.githubusercontent.com/assets/895174/25312496/6f96682a-2838-11e7-82c0-6792a66d4740.png">
| design | files sorting by name and last modified i am using jupyter lab version i tried sort by name and last modified in files section on left hand side and observed following behaviour behaviour on sort by name a folders and files will be grouped b folder will be shown first and sorted according to name c files will be show after folders and sorted according to name behaviour on sort by modified a folder and files are jumbled b last modified file or folder will be shown first is this expected behaviour and is there anyway to make both behaviour same img width alt sortbyname src img width alt sortbylastmodified src | 1 |
44,173 | 17,867,828,746 | IssuesEvent | 2021-09-06 11:43:52 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | Read include paths and compiler args from environment variables (CL.exe specific) | Language Service Feature Request more votes needed | CL.EXE is able to consume additional switches, besides what the compiler command line provides, by reading several environment variables.
For IntelliSense, it would help if CppTools reads the following:
- INCLUDE for additional include paths
- _CL_ for additional compilerArgs
There are also others, but I'm not sure if they are relevant for anything related to IntelliSense (_LINK_, _LIB_, LIB, LIBPATH).
Not sure if other compilers are able to read anything in a similar way from the environment. | 1.0 | Read include paths and compiler args from environment variables (CL.exe specific) - CL.EXE is able to consume additional switches, besides what the compiler command line provides, by reading several environment variables.
For IntelliSense, it would help if CppTools reads the following:
- INCLUDE for additional include paths
- _CL_ for additional compilerArgs
There are also others, but I'm not sure if they are relevant for anything related to IntelliSense (_LINK_, _LIB_, LIB, LIBPATH).
Not sure if other compilers are able to read anything in a similar way from the environment. | non_design | read include paths and compiler args from environment variables cl exe specific cl exe is able to consume additional switches besides what the compiler command line provides by reading several environment variables for intellisense it would help if cpptools reads the following include for additional include paths cl for additional compilerargs there are also others but i m not sure if they are relevant for anything related to intellisense link lib lib libpath not sure if other compilers are able to read anything in a similar way from the environment | 0 |
105,426 | 13,184,451,645 | IssuesEvent | 2020-08-12 19:26:25 | farrowking37/Capstone | https://api.github.com/repos/farrowking37/Capstone | opened | Machine Language | Design Project or Sprint | Investigate how difficult it would be to implement a Machine Language model such as GPT-2 or GPT-3 into the program to influence word choice. This would make the resulting cipher text more realistically appear as being properly written text.
This would require learning how to implement a language learning model in Python, adding it to the word selection flow, and evaluating the results to see if they are valuable. | 1.0 | Machine Language - Investigate how difficult it would be to implement a Machine Language model such as GPT-2 or GPT-3 into the program to influence word choice. This would make the resulting cipher text more realistically appear as being properly written text.
This would require learning how to implement a language learning model in Python, adding it to the word selection flow, and evaluating the results to see if they are valuable. | design | machine language investigate how difficult it would be to implement a machine language model such as gpt or gpt into the program to influence word choice this would make the resulting cipher text more realistically appear as being properly written text this would require learning how to implement a language learning model in python adding it to the word selection flow and evaluating the results to see if they are valuable | 1 |
108,323 | 13,615,005,524 | IssuesEvent | 2020-09-23 13:56:33 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | closed | "Expand All" not expanding collapsed text | *as-designed | In a file in the editor window, collapse a large number of sections in the document. Then do a "select all", and "expand selection". This should expand all the collapsed sections back put, but it doesn't change the edit window's collapsed sections at all. No change occurs in the edit window.
Closing the file and re-opening it will not expand text back out. Closing all copies of VSCodium and restarting it also will not reset the state back to default. You have to manually expand them out individually. | 1.0 | "Expand All" not expanding collapsed text - In a file in the editor window, collapse a large number of sections in the document. Then do a "select all", and "expand selection". This should expand all the collapsed sections back put, but it doesn't change the edit window's collapsed sections at all. No change occurs in the edit window.
Closing the file and re-opening it will not expand text back out. Closing all copies of VSCodium and restarting it also will not reset the state back to default. You have to manually expand them out individually. | design | expand all not expanding collapsed text in a file in the editor window collapse a large number of sections in the document then do a select all and expand selection this should expand all the collapsed sections back put but it doesn t change the edit window s collapsed sections at all no change occurs in the edit window closing the file and re opening it will not expand text back out closing all copies of vscodium and restarting it also will not reset the state back to default you have to manually expand them out individually | 1 |
137,010 | 20,027,522,357 | IssuesEvent | 2022-02-01 23:21:20 | mui-org/material-ui | https://api.github.com/repos/mui-org/material-ui | closed | [Fab] Floating action buttion doesn't support colors | enhancement material design component: Fab | ### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
`Fab` component doesn't support any color other than `primary` or `secondary`. This is inconsistent with behaviour of other components like `Button` for example.
This is where the issue lies:
https://github.com/mui-org/material-ui/blob/master/packages/mui-material/src/Fab/Fab.js#L113-L136
Instead of `theme.palette.primary.main` there should be `theme.palette[ownerState.color].main` etc. (some conditions around need to be changed as well here)
### Expected behavior 🤔
`color` property of `Fab` should be consistent with that of other components (like `Button` and many other) and accept all defined colors.
### Steps to reproduce 🕹
https://codesandbox.io/s/customcolor-material-demo-forked-l5fml?file=/demo.js
### Context 🔦
_No response_
### Your environment 🌎
<details>
<summary>`npx @mui/envinfo`</summary>
```
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
```
</details>
| 1.0 | [Fab] Floating action buttion doesn't support colors - ### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
`Fab` component doesn't support any color other than `primary` or `secondary`. This is inconsistent with behaviour of other components like `Button` for example.
This is where the issue lies:
https://github.com/mui-org/material-ui/blob/master/packages/mui-material/src/Fab/Fab.js#L113-L136
Instead of `theme.palette.primary.main` there should be `theme.palette[ownerState.color].main` etc. (some conditions around need to be changed as well here)
### Expected behavior 🤔
`color` property of `Fab` should be consistent with that of other components (like `Button` and many other) and accept all defined colors.
### Steps to reproduce 🕹
https://codesandbox.io/s/customcolor-material-demo-forked-l5fml?file=/demo.js
### Context 🔦
_No response_
### Your environment 🌎
<details>
<summary>`npx @mui/envinfo`</summary>
```
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
```
</details>
| design | floating action buttion doesn t support colors duplicates i have searched the existing issues latest version i have tested the latest version current behavior 😯 fab component doesn t support any color other than primary or secondary this is inconsistent with behaviour of other components like button for example this is where the issue lies instead of theme palette primary main there should be theme palette main etc some conditions around need to be changed as well here expected behavior 🤔 color property of fab should be consistent with that of other components like button and many other and accept all defined colors steps to reproduce 🕹 context 🔦 no response your environment 🌎 npx mui envinfo don t forget to mention which browser you used output from npx mui envinfo goes here | 1 |
74,162 | 8,982,587,733 | IssuesEvent | 2019-01-31 02:48:38 | YACS-RCOS/yacs | https://api.github.com/repos/YACS-RCOS/yacs | closed | Method of limiting course descriptions by default | class:design service:web | Course descriptions are long and take up quite a large amount of page space (for 1-section courses, the description is often taller than the course heading and section combined). These should probably be limited by default and only expandable when the user indicates they want the full text.
A proposed way of doing this: set the description to non-wrapping, forcing it to be limited to one line, and add an ellipsis button at the right that when clicked removes both it and the non-wrapping style. That would be irreversible but would reset when the page reloaded (unless we wanted to do something funky with the cookie).
| 1.0 | Method of limiting course descriptions by default - Course descriptions are long and take up quite a large amount of page space (for 1-section courses, the description is often taller than the course heading and section combined). These should probably be limited by default and only expandable when the user indicates they want the full text.
A proposed way of doing this: set the description to non-wrapping, forcing it to be limited to one line, and add an ellipsis button at the right that when clicked removes both it and the non-wrapping style. That would be irreversible but would reset when the page reloaded (unless we wanted to do something funky with the cookie).
| design | method of limiting course descriptions by default course descriptions are long and take up quite a large amount of page space for section courses the description is often taller than the course heading and section combined these should probably be limited by default and only expandable when the user indicates they want the full text a proposed way of doing this set the description to non wrapping forcing it to be limited to one line and add an ellipsis button at the right that when clicked removes both it and the non wrapping style that would be irreversible but would reset when the page reloaded unless we wanted to do something funky with the cookie | 1 |
109,586 | 13,789,482,471 | IssuesEvent | 2020-10-09 08:56:52 | ryonakano/handy-football | https://api.github.com/repos/ryonakano/handy-football | opened | Show news feed about selected team | Needs Design Priority: Wishlist | From [gabrielpsouza in reddit](https://www.reddit.com/r/elementaryos/comments/j7imtw/new_application_for_football_followers_under/g85i49q/?utm_source=reddit&utm_medium=web2x&context=3):
> …it would also be nice to have a news feed in the app about the teams you select, I see so much potential
| 1.0 | Show news feed about selected team - From [gabrielpsouza in reddit](https://www.reddit.com/r/elementaryos/comments/j7imtw/new_application_for_football_followers_under/g85i49q/?utm_source=reddit&utm_medium=web2x&context=3):
> …it would also be nice to have a news feed in the app about the teams you select, I see so much potential
| design | show news feed about selected team from …it would also be nice to have a news feed in the app about the teams you select i see so much potential | 1 |
303,615 | 26,218,325,637 | IssuesEvent | 2023-01-04 12:55:18 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: follower-reads/mixed-version/single-region failed | C-test-failure O-robot O-roachtest branch-master release-blocker T-kv | roachtest.follower-reads/mixed-version/single-region [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8153407?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8153407?buildTab=artifacts#/follower-reads/mixed-version/single-region) on master @ [0725273ac7f789ba8ed78aacaf73cc953ca47fe8](https://github.com/cockroachdb/cockroach/commits/0725273ac7f789ba8ed78aacaf73cc953ca47fe8):
```
test artifacts and logs in: /artifacts/follower-reads/mixed-version/single-region/run_1
(follower_reads.go:765).verifyHighFollowerReadRatios: too many intervals with more than 1 nodes with low follower read ratios: 23 intervals > 4 threshold. Bad intervals:
interval 10:41:30-10:41:40: n1 ratio: 0.004 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:41:40-10:41:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:41:50-10:42:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:00-10:42:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:10-10:42:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:20-10:42:30: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:30-10:42:40: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:40-10:42:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:50-10:43:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:00-10:43:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:10-10:43:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:20-10:43:30: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:30-10:43:40: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:40-10:43:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:50-10:44:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:00-10:44:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:10-10:44:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:20-10:44:30: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:30-10:44:40: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:40-10:44:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:50-10:45:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:45:00-10:45:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:45:10-10:45:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=2</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</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>
<details><summary>Same failure on other branches</summary>
<p>
- #94577 roachtest: follower-reads/mixed-version/single-region failed [C-test-failure O-roachtest O-robot T-kv branch-release-22.2 release-blocker]
- #94506 roachtest: follower-reads/mixed-version/single-region failed [C-test-failure O-roachtest O-robot T-kv branch-release-22.1 release-blocker]
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*follower-reads/mixed-version/single-region.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-23014 | 2.0 | roachtest: follower-reads/mixed-version/single-region failed - roachtest.follower-reads/mixed-version/single-region [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8153407?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8153407?buildTab=artifacts#/follower-reads/mixed-version/single-region) on master @ [0725273ac7f789ba8ed78aacaf73cc953ca47fe8](https://github.com/cockroachdb/cockroach/commits/0725273ac7f789ba8ed78aacaf73cc953ca47fe8):
```
test artifacts and logs in: /artifacts/follower-reads/mixed-version/single-region/run_1
(follower_reads.go:765).verifyHighFollowerReadRatios: too many intervals with more than 1 nodes with low follower read ratios: 23 intervals > 4 threshold. Bad intervals:
interval 10:41:30-10:41:40: n1 ratio: 0.004 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:41:40-10:41:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:41:50-10:42:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:00-10:42:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:10-10:42:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:20-10:42:30: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:30-10:42:40: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:40-10:42:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:42:50-10:43:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:00-10:43:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:10-10:43:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:20-10:43:30: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:30-10:43:40: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:40-10:43:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:43:50-10:44:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:00-10:44:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:10-10:44:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:20-10:44:30: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:30-10:44:40: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:40-10:44:50: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:44:50-10:45:00: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:45:00-10:45:10: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
interval 10:45:10-10:45:20: n1 ratio: 0.000 n2 ratio: 0.000 n3 ratio: 0.000
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=2</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</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>
<details><summary>Same failure on other branches</summary>
<p>
- #94577 roachtest: follower-reads/mixed-version/single-region failed [C-test-failure O-roachtest O-robot T-kv branch-release-22.2 release-blocker]
- #94506 roachtest: follower-reads/mixed-version/single-region failed [C-test-failure O-roachtest O-robot T-kv branch-release-22.1 release-blocker]
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*follower-reads/mixed-version/single-region.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-23014 | non_design | roachtest follower reads mixed version single region failed roachtest follower reads mixed version single region with on master test artifacts and logs in artifacts follower reads mixed version single region run follower reads go verifyhighfollowerreadratios too many intervals with more than nodes with low follower read ratios intervals threshold bad intervals interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio interval ratio ratio ratio parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest fs roachtest localssd true roachtest ssd help see see same failure on other branches roachtest follower reads mixed version single region failed roachtest follower reads mixed version single region failed cc cockroachdb kv triage jira issue crdb | 0 |
379,101 | 11,215,706,259 | IssuesEvent | 2020-01-07 03:15:53 | google/ground-android | https://api.github.com/repos/google/ground-android | opened | [Project activation] Can't reactivate project when opening app w/o network | priority: p0 type: bug | **Describe the bug**
The "Project loading" progress dialog spins forever.
**To Reproduce**
Steps to reproduce the behavior:
1. Close the app
2. Turn on Airplane Mode
3. Reopen the app
| 1.0 | [Project activation] Can't reactivate project when opening app w/o network - **Describe the bug**
The "Project loading" progress dialog spins forever.
**To Reproduce**
Steps to reproduce the behavior:
1. Close the app
2. Turn on Airplane Mode
3. Reopen the app
| non_design | can t reactivate project when opening app w o network describe the bug the project loading progress dialog spins forever to reproduce steps to reproduce the behavior close the app turn on airplane mode reopen the app | 0 |
449,981 | 31,879,624,800 | IssuesEvent | 2023-09-16 07:57:55 | nikohoffren/fork-commit-merge | https://api.github.com/repos/nikohoffren/fork-commit-merge | opened | Fork, Commit, Merge - Easy Issue (Markdown) | documentation help wanted good first issue first-contributors first-contributor easy markdown | # Fork, Commit, Merge - Easy Issue (Markdown)
## Correct Markdown Formatting
*Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!*
### Description
Open the `tasks/markdown/easy` directory from the root of your project.
There is `introduction.md` file in the directory that is not properly formatted according to Markdown syntax. Your task is to correct these issues.
Once the `introduction.md` file is properly formatted according to the Markdown syntax, you are done and ready to make a pull request!
*Note: You can test your Markdown code in a editor like [this](https://stackedit.io/)*.
---
Check out [README.md](https://github.com/nikohoffren/fork-commit-merge/blob/main/README.md) for more instructions and how to make a pull request.
Feel free to ask any questions here if you have some problems! | 1.0 | Fork, Commit, Merge - Easy Issue (Markdown) - # Fork, Commit, Merge - Easy Issue (Markdown)
## Correct Markdown Formatting
*Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!*
### Description
Open the `tasks/markdown/easy` directory from the root of your project.
There is `introduction.md` file in the directory that is not properly formatted according to Markdown syntax. Your task is to correct these issues.
Once the `introduction.md` file is properly formatted according to the Markdown syntax, you are done and ready to make a pull request!
*Note: You can test your Markdown code in a editor like [this](https://stackedit.io/)*.
---
Check out [README.md](https://github.com/nikohoffren/fork-commit-merge/blob/main/README.md) for more instructions and how to make a pull request.
Feel free to ask any questions here if you have some problems! | non_design | fork commit merge easy issue markdown fork commit merge easy issue markdown correct markdown formatting note you don t have ask permission to start solving the issue or get assigned since these issues are supposed to be always open for new contributors the actions user bot will reset the file back to previous state for the next contributor after your commit is merged so you can just simply start working with the issue right away description open the tasks markdown easy directory from the root of your project there is introduction md file in the directory that is not properly formatted according to markdown syntax your task is to correct these issues once the introduction md file is properly formatted according to the markdown syntax you are done and ready to make a pull request note you can test your markdown code in a editor like check out for more instructions and how to make a pull request feel free to ask any questions here if you have some problems | 0 |
129,813 | 17,893,079,870 | IssuesEvent | 2021-09-08 03:47:19 | ubyssey/ubyssey.ca | https://api.github.com/repos/ubyssey/ubyssey.ca | opened | Section Page save function | bug design backend | "current_section" variable functionality depends on writes during save(), but the Section Page itself is occasionally buggy in this respect - investigate | 1.0 | Section Page save function - "current_section" variable functionality depends on writes during save(), but the Section Page itself is occasionally buggy in this respect - investigate | design | section page save function current section variable functionality depends on writes during save but the section page itself is occasionally buggy in this respect investigate | 1 |
128,804 | 12,392,121,932 | IssuesEvent | 2020-05-20 13:33:56 | IBM-Blockchain/ansible-collection | https://api.github.com/repos/IBM-Blockchain/ansible-collection | closed | Tutorial commands for Docker are wrong | documentation | ```
Tobias' MacBook Pro:tutorial tobias.hunter@uk.ibm.com$ docker run --rm -v "$PWD:/tutorials" mydockerorg/ansible ansible-playbook /tutorials/build_network.sh -i build
[WARNING]: Unable to parse /build as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'
ERROR! We were unable to read either as JSON nor YAML, these are the errors we got from each:
JSON: Expecting value: line 1 column 1 (char 0)
Syntax Error while loading YAML.
mapping values are not allowed here
The error appears to be in '/tutorials/build_network.sh': line 6, column 16, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
function usage {
echo "Usage: build_network.sh [-i] [build|destroy]" 1>&2
^ here
``` | 1.0 | Tutorial commands for Docker are wrong - ```
Tobias' MacBook Pro:tutorial tobias.hunter@uk.ibm.com$ docker run --rm -v "$PWD:/tutorials" mydockerorg/ansible ansible-playbook /tutorials/build_network.sh -i build
[WARNING]: Unable to parse /build as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'
ERROR! We were unable to read either as JSON nor YAML, these are the errors we got from each:
JSON: Expecting value: line 1 column 1 (char 0)
Syntax Error while loading YAML.
mapping values are not allowed here
The error appears to be in '/tutorials/build_network.sh': line 6, column 16, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
function usage {
echo "Usage: build_network.sh [-i] [build|destroy]" 1>&2
^ here
``` | non_design | tutorial commands for docker are wrong tobias macbook pro tutorial tobias hunter uk ibm com docker run rm v pwd tutorials mydockerorg ansible ansible playbook tutorials build network sh i build unable to parse build as an inventory source no inventory was parsed only implicit localhost is available provided hosts list is empty only localhost is available note that the implicit localhost does not match all error we were unable to read either as json nor yaml these are the errors we got from each json expecting value line column char syntax error while loading yaml mapping values are not allowed here the error appears to be in tutorials build network sh line column but may be elsewhere in the file depending on the exact syntax problem the offending line appears to be function usage echo usage build network sh here | 0 |
36,394 | 4,732,060,956 | IssuesEvent | 2016-10-19 06:02:39 | LLNL/conduit | https://api.github.com/repos/LLNL/conduit | opened | blueprint for ndarray | design | for better compatibility with Sidre N-D Fortran array support and python ndarrays
start with the contiguous case:
+shape (list of ints)
+values (actually 1-d array with values) | 1.0 | blueprint for ndarray - for better compatibility with Sidre N-D Fortran array support and python ndarrays
start with the contiguous case:
+shape (list of ints)
+values (actually 1-d array with values) | design | blueprint for ndarray for better compatibility with sidre n d fortran array support and python ndarrays start with the contiguous case shape list of ints values actually d array with values | 1 |
142,387 | 21,722,947,072 | IssuesEvent | 2022-05-11 03:30:12 | Minaira/2d-rpg-unity | https://api.github.com/repos/Minaira/2d-rpg-unity | opened | Create the starting tilemap | Map Design Mystic Woods Pack | We will need to create a tileset in order to create the tile map.
The Mystic Woods pack has a tileset which we can use to create a basic map to start with.
We need to add these tilesets to the Tile Palette in Unity Editor so that we can use and edit each individual tile.
Create a new folder to store the assets in Assets/Art/mystic-woods/tilesets
How the map looks doesn't really matter for now. | 1.0 | Create the starting tilemap - We will need to create a tileset in order to create the tile map.
The Mystic Woods pack has a tileset which we can use to create a basic map to start with.
We need to add these tilesets to the Tile Palette in Unity Editor so that we can use and edit each individual tile.
Create a new folder to store the assets in Assets/Art/mystic-woods/tilesets
How the map looks doesn't really matter for now. | design | create the starting tilemap we will need to create a tileset in order to create the tile map the mystic woods pack has a tileset which we can use to create a basic map to start with we need to add these tilesets to the tile palette in unity editor so that we can use and edit each individual tile create a new folder to store the assets in assets art mystic woods tilesets how the map looks doesn t really matter for now | 1 |
629,041 | 20,021,776,478 | IssuesEvent | 2022-02-01 17:02:02 | Lumiverse/Atlas-Issues | https://api.github.com/repos/Lumiverse/Atlas-Issues | closed | Cursor do not come out | Bug Medium Priority | Reported by **#FF00FFJuanes** (21/10/2021 07:20:37)
**Description:**
Server default cursor not displayed
**Reproduction:**
Pls help:(
| 1.0 | Cursor do not come out - Reported by **#FF00FFJuanes** (21/10/2021 07:20:37)
**Description:**
Server default cursor not displayed
**Reproduction:**
Pls help:(
| non_design | cursor do not come out reported by description server default cursor not displayed reproduction pls help | 0 |
620,588 | 19,565,397,954 | IssuesEvent | 2022-01-03 23:04:36 | yugabyte/yugabyte-db | https://api.github.com/repos/yugabyte/yugabyte-db | opened | [xCluster] Support automatic detection of new masters in case of decomission or full move | area/docdb priority/low | ### Description
Currently the user has to call alter_universe_replication if there is a source side master full-move or decommission. Ideally, the target DB logic should automatically figure out these new addresses. | 1.0 | [xCluster] Support automatic detection of new masters in case of decomission or full move - ### Description
Currently the user has to call alter_universe_replication if there is a source side master full-move or decommission. Ideally, the target DB logic should automatically figure out these new addresses. | non_design | support automatic detection of new masters in case of decomission or full move description currently the user has to call alter universe replication if there is a source side master full move or decommission ideally the target db logic should automatically figure out these new addresses | 0 |
41,599 | 5,345,208,401 | IssuesEvent | 2017-02-17 16:24:28 | jolocom/little-sister | https://api.github.com/repos/jolocom/little-sister | closed | Adding social media profiles to a profile node | designing user profile user story | The user should be able to add social media profiles as alternative contact information.
1) click the social media field
2) enter an address
3) Ideally, the app should be smart enough to recognize urls from facebook and twitter and select the right type automatically
4) If the type is incorrect, click on the selector and change the type
5) Save the form
 | 1.0 | Adding social media profiles to a profile node - The user should be able to add social media profiles as alternative contact information.
1) click the social media field
2) enter an address
3) Ideally, the app should be smart enough to recognize urls from facebook and twitter and select the right type automatically
4) If the type is incorrect, click on the selector and change the type
5) Save the form
 | design | adding social media profiles to a profile node the user should be able to add social media profiles as alternative contact information click the social media field enter an address ideally the app should be smart enough to recognize urls from facebook and twitter and select the right type automatically if the type is incorrect click on the selector and change the type save the form | 1 |
40,977 | 6,885,975,301 | IssuesEvent | 2017-11-21 17:47:08 | google/protobuf-gradle-plugin | https://api.github.com/repos/google/protobuf-gradle-plugin | closed | This readme.md is outdated.Can't build from gradle. | documentation |
I'm checked the url **https://oss.sonatype.org/content/repositories/snapshots/com/google/protobuf/protobuf-gradle-plugin/** 0.7.2.SNAPSHOT is the lastest.
```
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'grpc-java-demo'.
> Could not resolve all files for configuration ':classpath'.
> Could not find com.google.protobuf:protobuf-gradle-plugin:0.8.3.
Searched in the following locations:
https://oss.sonatype.org/content/repositories/snapshots/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.pom
https://oss.sonatype.org/content/repositories/snapshots/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.jar
Required by:
project :
```
Then I changed 0.8.3 to 0.7.2 got dependency error as blow:
```
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'grpc-java-demo'.
> Could not resolve all files for configuration ':classpath'.
> Could not find commons-lang:commons-lang:2.6.
Searched in the following locations:
https://oss.sonatype.org/content/repositories/snapshots/commons-lang/commons-lang/2.6/commons-lang-2.6.pom
https://oss.sonatype.org/content/repositories/snapshots/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
Required by:
project : > com.google.protobuf:protobuf-gradle-plugin:0.7.2-SNAPSHOT
> Could not find com.google.gradle:osdetector-gradle-plugin:1.2.1.
Searched in the following locations:
https://oss.sonatype.org/content/repositories/snapshots/com/google/gradle/osdetector-gradle-plugin/1.2.1/osdetector-gradle-plugin-1.2.1.pom
https://oss.sonatype.org/content/repositories/snapshots/com/google/gradle/osdetector-gradle-plugin/1.2.1/osdetector-gradle-plugin-1.2.1.jar
Required by:
project : > com.google.protobuf:protobuf-gradle-plugin:0.7.2-SNAPSHOT
``` | 1.0 | This readme.md is outdated.Can't build from gradle. -
I'm checked the url **https://oss.sonatype.org/content/repositories/snapshots/com/google/protobuf/protobuf-gradle-plugin/** 0.7.2.SNAPSHOT is the lastest.
```
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'grpc-java-demo'.
> Could not resolve all files for configuration ':classpath'.
> Could not find com.google.protobuf:protobuf-gradle-plugin:0.8.3.
Searched in the following locations:
https://oss.sonatype.org/content/repositories/snapshots/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.pom
https://oss.sonatype.org/content/repositories/snapshots/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.jar
Required by:
project :
```
Then I changed 0.8.3 to 0.7.2 got dependency error as blow:
```
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'grpc-java-demo'.
> Could not resolve all files for configuration ':classpath'.
> Could not find commons-lang:commons-lang:2.6.
Searched in the following locations:
https://oss.sonatype.org/content/repositories/snapshots/commons-lang/commons-lang/2.6/commons-lang-2.6.pom
https://oss.sonatype.org/content/repositories/snapshots/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
Required by:
project : > com.google.protobuf:protobuf-gradle-plugin:0.7.2-SNAPSHOT
> Could not find com.google.gradle:osdetector-gradle-plugin:1.2.1.
Searched in the following locations:
https://oss.sonatype.org/content/repositories/snapshots/com/google/gradle/osdetector-gradle-plugin/1.2.1/osdetector-gradle-plugin-1.2.1.pom
https://oss.sonatype.org/content/repositories/snapshots/com/google/gradle/osdetector-gradle-plugin/1.2.1/osdetector-gradle-plugin-1.2.1.jar
Required by:
project : > com.google.protobuf:protobuf-gradle-plugin:0.7.2-SNAPSHOT
``` | non_design | this readme md is outdated can t build from gradle i m checked the url snapshot is the lastest failure build failed with an exception what went wrong a problem occurred configuring root project grpc java demo could not resolve all files for configuration classpath could not find com google protobuf protobuf gradle plugin searched in the following locations required by project then i changed to got dependency error as blow failure build failed with an exception what went wrong a problem occurred configuring root project grpc java demo could not resolve all files for configuration classpath could not find commons lang commons lang searched in the following locations required by project com google protobuf protobuf gradle plugin snapshot could not find com google gradle osdetector gradle plugin searched in the following locations required by project com google protobuf protobuf gradle plugin snapshot | 0 |
31,186 | 6,443,911,858 | IssuesEvent | 2017-08-12 02:29:51 | opendatakit/opendatakit | https://api.github.com/repos/opendatakit/opendatakit | closed | Can not publish to a Google Spreadsheet | Aggregate Priority-Medium Type-Defect | Originally reported on Google Code with ID 1140
```
What steps will reproduce the problem?
1. On the submissions page - Publish - Google Spreadsheet - Publish
2.
3.
What is the expected output? What do you see instead?
Expect it to publish. I get an error about the Doclist APi being shutdown. See attached
screen shot.
What version of the product are you using? On what operating system?
Win 7. Version 1.4.5 production
Please provide any additional information below.
Google Fusion Tables works but Spreadsheet does not. Searched and never found this
error listed.
```
Reported by `hfmnw0` on 2015-04-30 15:59:24
<hr>
- _Attachment: Speadsheet Error.PNG<br>_
| 1.0 | Can not publish to a Google Spreadsheet - Originally reported on Google Code with ID 1140
```
What steps will reproduce the problem?
1. On the submissions page - Publish - Google Spreadsheet - Publish
2.
3.
What is the expected output? What do you see instead?
Expect it to publish. I get an error about the Doclist APi being shutdown. See attached
screen shot.
What version of the product are you using? On what operating system?
Win 7. Version 1.4.5 production
Please provide any additional information below.
Google Fusion Tables works but Spreadsheet does not. Searched and never found this
error listed.
```
Reported by `hfmnw0` on 2015-04-30 15:59:24
<hr>
- _Attachment: Speadsheet Error.PNG<br>_
| non_design | can not publish to a google spreadsheet originally reported on google code with id what steps will reproduce the problem on the submissions page publish google spreadsheet publish what is the expected output what do you see instead expect it to publish i get an error about the doclist api being shutdown see attached screen shot what version of the product are you using on what operating system win version production please provide any additional information below google fusion tables works but spreadsheet does not searched and never found this error listed reported by on attachment speadsheet error png error png | 0 |
184,118 | 31,821,238,807 | IssuesEvent | 2023-09-14 02:35:54 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | opened | [UX][Design] Create Lo-Fi Wireframe Structure for Past Appointments | design ux HCE-Checkin | While we work on [scope discovery](https://github.com/department-of-veterans-affairs/va.gov-team/issues/65592) and [back-end user flows](https://github.com/department-of-veterans-affairs/va.gov-team/issues/65593) for travel reimbursement for past appointments, we need to understand what parts of the userflow (Veteran-facing) screens we already have a handle on, in the form of complete or proposed designs, and begin to construct a low-fi wireframe flow with the available screens.
[Link to 18F designs]
## Tasks
- [ ] Create lo-fi wireframes for discovery purposes
- [ ] Identify what design work will still need to be done
- [ ] Share with Kristen and UX
- [ ] Work with Kristen to determine what design work should be done by PCI or Appointments team
- [ ] Create f/u tickets
## AC
- [ ] Initial lo-fi wireframe structure created
- [ ] PCI vs. Appointments team roles have been clarified for next design steps
- [ ] F/u tickets created
| 1.0 | [UX][Design] Create Lo-Fi Wireframe Structure for Past Appointments - While we work on [scope discovery](https://github.com/department-of-veterans-affairs/va.gov-team/issues/65592) and [back-end user flows](https://github.com/department-of-veterans-affairs/va.gov-team/issues/65593) for travel reimbursement for past appointments, we need to understand what parts of the userflow (Veteran-facing) screens we already have a handle on, in the form of complete or proposed designs, and begin to construct a low-fi wireframe flow with the available screens.
[Link to 18F designs]
## Tasks
- [ ] Create lo-fi wireframes for discovery purposes
- [ ] Identify what design work will still need to be done
- [ ] Share with Kristen and UX
- [ ] Work with Kristen to determine what design work should be done by PCI or Appointments team
- [ ] Create f/u tickets
## AC
- [ ] Initial lo-fi wireframe structure created
- [ ] PCI vs. Appointments team roles have been clarified for next design steps
- [ ] F/u tickets created
| design | create lo fi wireframe structure for past appointments while we work on and for travel reimbursement for past appointments we need to understand what parts of the userflow veteran facing screens we already have a handle on in the form of complete or proposed designs and begin to construct a low fi wireframe flow with the available screens tasks create lo fi wireframes for discovery purposes identify what design work will still need to be done share with kristen and ux work with kristen to determine what design work should be done by pci or appointments team create f u tickets ac initial lo fi wireframe structure created pci vs appointments team roles have been clarified for next design steps f u tickets created | 1 |
133,414 | 5,202,871,674 | IssuesEvent | 2017-01-24 10:55:21 | magnolo/newhere | https://api.github.com/repos/magnolo/newhere | closed | 'Rights' of the different account types | bug CMS high priority question translator | 1) [QUESTION] What are the 'rights' attributed to the different account types e.g. super admin, moderator, admin, organisation admin, organisation user, user?
2) [BUG] Ideally, we would be able to attribute 'moderator' to our translators and they would be able to see ONLY their account and the translation tab, which they would have full access to. This is not currently the case. At the moment, when a user is made a 'moderator' they can only see their account and offers (despite having none) as if they were a normal NGO. | 1.0 | 'Rights' of the different account types - 1) [QUESTION] What are the 'rights' attributed to the different account types e.g. super admin, moderator, admin, organisation admin, organisation user, user?
2) [BUG] Ideally, we would be able to attribute 'moderator' to our translators and they would be able to see ONLY their account and the translation tab, which they would have full access to. This is not currently the case. At the moment, when a user is made a 'moderator' they can only see their account and offers (despite having none) as if they were a normal NGO. | non_design | rights of the different account types what are the rights attributed to the different account types e g super admin moderator admin organisation admin organisation user user ideally we would be able to attribute moderator to our translators and they would be able to see only their account and the translation tab which they would have full access to this is not currently the case at the moment when a user is made a moderator they can only see their account and offers despite having none as if they were a normal ngo | 0 |
340,245 | 10,269,299,219 | IssuesEvent | 2019-08-23 08:44:17 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | m.spiegel.de - site is not usable | browser-firefox-mobile engine-gecko priority-important | <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 5.0; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 5.0
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: the optical size of the website is too small. You can not read it.
**Steps to Reproduce**:
The optical size of the website is too small. It does not fit in the full size of the window.
[](https://webcompat.com/uploads/2019/8/6e54178e-f0dc-4cd5-a617-aee1425757ee.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190819150103</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "Request to access cookie or storage on https://optout.adalliance.io/status/ was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 7 column: 16 source: "https://optout.adalliance.io/status/"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://mafo.adalliance.io/ was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 7 column: 20 source: "https://mafo.adalliance.io/mafo.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 78 column: 185 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Ein Aufruf von document.write() durch ein asynchron geladenes externes Skript wurde ignoriert." {file: "https://ad.yieldlab.net/d/7053789/631/2x2?ts=0.4304155682026418" line: 1}]', u'[JavaScript Warning: "Ein Aufruf von document.write() durch ein asynchron geladenes externes Skript wurde ignoriert." {file: "https://ad.yieldlab.net/d/7053789/631/2x2?ts=0.4304155682026418" line: 2}]', u'[JavaScript Warning: "Ein Aufruf von document.write() durch ein asynchron geladenes externes Skript wurde ignoriert." {file: "https://ad.yieldlab.net/d/7053789/631/2x2?ts=0.4304155682026418" line: 3}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 4111 source: "https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 70 column: 288 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 70 column: 288 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 4111 source: "https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 4111 source: "https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it." {file: "https://widgets.outbrain.com/nanoWidget/externals/obPixelFrame/obPixelFrame.htm#p=https%3A%2F%2Fbs.serving-sys.com%2Fserving%2FadServer.bs%3Fcn%3Ddisplay%26c%3D19%26mc%3Dimp%26pli%3D28562974%26PluID%3D0%26ord%3D%255Btimestamp%255D%26rtu%3D-1%26obRequestId%3DY_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj%26obTimestamp%3D1566380989293&ai=105732&nop=1" line: 0}]', u'[JavaScript Warning: "The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it." {file: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 4467 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 6561 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 6496 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/nanoWidget/externals/obPixelFrame/obPixelFrame.htm#p=https%3A%2F%2Fbs.serving-sys.com%2Fserving%2FadServer.bs%3Fcn%3Ddisplay%26c%3D19%26mc%3Dimp%26pli%3D28562974%26PluID%3D0%26ord%3D%255Btimestamp%255D%26rtu%3D-1%26obRequestId%3DY_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj%26obTimestamp%3D1566380989293&ai=105732&nop=1 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 334 source: "https://widgets.outbrain.com/nanoWidget/externals/obPixelFrame/obPixelFrame.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 50 source: "https://sb.scorecardresearch.com/beacon.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 611 source: "https://sb.scorecardresearch.com/beacon.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://spiegel.demdex.net/dest5.html?d_nsid=0#https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 77 source: "https://spiegel.demdex.net/dest5.html?d_nsid=0#https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 287 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 316 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 316 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 825 column: 63 source: "https://pixel.adsafeprotected.com/rjss/st/293514/36917883/skeleton.js?obRequestId=Y_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj&obTimestamp=1566380989293"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 46 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Array.slice is deprecated; use Array.prototype.slice instead" {file: "https://static.adsafeprotected.com/sca.17.4.95.js" line: 32}]', u'[JavaScript Warning: "onmozfullscreenerror sollte nicht mehr verwendet werden." {file: "https://static.adsafeprotected.com/sca.17.4.95.js" line: 33}]', u'[JavaScript Warning: "WebRTC-Schnittstellen mit dem "moz"-Prfix (mozRTCPeerConnection, mozRTCSessionDescription, mozRTCIceCandidate) sollten nicht mehr verwendet werden." {file: "https://static.adsafeprotected.com/sca.17.4.95.js" line: 33}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 825 column: 63 source: "https://pixel.adsafeprotected.com/rjss/st/293514/36917883/skeleton.js?obRequestId=Y_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj&obTimestamp=1566380989293"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 76 source: "https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html line 7 > scriptElement"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 7 column: 6414 source: "https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 148 column: 1194 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Der Orientierungssensor sollte nicht mehr verwendet werden." {file: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q" line: 107}]', u'[JavaScript Warning: "Mit document.write() wurde ein nicht balancierter Baum geschrieben, was dazu gefhrt hat, dass Daten aus dem Netzwerk neu geparst werden mussten. Fr weitere Informationen https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing" {file: "https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html" line: 8}]', u'[JavaScript Warning: "Request to access cookie or storage on https://sync.teads.tv/wigo-no-slot was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 9 column: 39 source: "https://sync.teads.tv/wigo-no-slot"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://ad.atdmt.com/i/img;adv=11287203704923;ec=11287203705169;s.a=12679;c.a=3186425;p.a=3813867;a.a=10159606;aaid=;aaid_lat=;idfa=;cache=INSERT_TIMESTAMP_HERE; was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://ad.atdmt.com/i/img;adv=11287203704923;ec=11287203705169;s.a=12679;c.a=3186425;p.a=3813867;a.a=10159606;aaid=;aaid_lat=;idfa=;cache=INSERT_TIMESTAMP_HERE; was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://imagesrv.adition.com/1x1.gif was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://imagesrv.adition.com/1x1.gif was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true} was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 12 column: 3768 source: "https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true}"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true} was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 12 column: 1675 source: "https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true}"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true} was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 12 column: 1675 source: "https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true}"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/sodar/Enqz_20U.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 35 column: 612 source: "https://tpc.googlesyndication.com/sodar/Enqz_20U.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 265 column: 659 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 1857 source: "https://tpc.googlesyndication.com/pagead/js/r20190815/r20110914/client/window_focus.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 265 column: 659 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 265 column: 659 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 1857 source: "https://tpc.googlesyndication.com/pagead/js/r20190815/r20110914/client/window_focus.js"}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | m.spiegel.de - site is not usable - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 5.0; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 5.0
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: the optical size of the website is too small. You can not read it.
**Steps to Reproduce**:
The optical size of the website is too small. It does not fit in the full size of the window.
[](https://webcompat.com/uploads/2019/8/6e54178e-f0dc-4cd5-a617-aee1425757ee.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190819150103</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "Request to access cookie or storage on https://optout.adalliance.io/status/ was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 7 column: 16 source: "https://optout.adalliance.io/status/"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://mafo.adalliance.io/ was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 7 column: 20 source: "https://mafo.adalliance.io/mafo.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 78 column: 185 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Ein Aufruf von document.write() durch ein asynchron geladenes externes Skript wurde ignoriert." {file: "https://ad.yieldlab.net/d/7053789/631/2x2?ts=0.4304155682026418" line: 1}]', u'[JavaScript Warning: "Ein Aufruf von document.write() durch ein asynchron geladenes externes Skript wurde ignoriert." {file: "https://ad.yieldlab.net/d/7053789/631/2x2?ts=0.4304155682026418" line: 2}]', u'[JavaScript Warning: "Ein Aufruf von document.write() durch ein asynchron geladenes externes Skript wurde ignoriert." {file: "https://ad.yieldlab.net/d/7053789/631/2x2?ts=0.4304155682026418" line: 3}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 4111 source: "https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 67 column: 98 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 70 column: 288 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 70 column: 288 source: "https://widgets.outbrain.com/outbrain.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 4111 source: "https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 4111 source: "https://platform.twitter.com/widgets/widget_iframe.097c1f5038f9e8a0d62a39a892838d66.html?origin=https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it." {file: "https://widgets.outbrain.com/nanoWidget/externals/obPixelFrame/obPixelFrame.htm#p=https%3A%2F%2Fbs.serving-sys.com%2Fserving%2FadServer.bs%3Fcn%3Ddisplay%26c%3D19%26mc%3Dimp%26pli%3D28562974%26PluID%3D0%26ord%3D%255Btimestamp%255D%26rtu%3D-1%26obRequestId%3DY_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj%26obTimestamp%3D1566380989293&ai=105732&nop=1" line: 0}]', u'[JavaScript Warning: "The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it." {file: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 4467 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 6561 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 2700 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 6496 source: "https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 42 column: 22322 source: "https://platform.twitter.com/widgets/follow_button.097c1f5038f9e8a0d62a39a892838d66.de.html#dnt=false&id=twitter-widget-0&lang=de&screen_name=EvaLehnen&show_count=false&show_screen_name=true&size=m&time=1566380991806"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/nanoWidget/externals/obPixelFrame/obPixelFrame.htm#p=https%3A%2F%2Fbs.serving-sys.com%2Fserving%2FadServer.bs%3Fcn%3Ddisplay%26c%3D19%26mc%3Dimp%26pli%3D28562974%26PluID%3D0%26ord%3D%255Btimestamp%255D%26rtu%3D-1%26obRequestId%3DY_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj%26obTimestamp%3D1566380989293&ai=105732&nop=1 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 334 source: "https://widgets.outbrain.com/nanoWidget/externals/obPixelFrame/obPixelFrame.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 50 source: "https://sb.scorecardresearch.com/beacon.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/widgetOBUserSync/obUserSync.html#pid=8507&dmpenabled=true&filterDMP=&csenabled=true&d=n-wfX7ruy6b-0cQuVjKKy3UtlCYp5O_tr4GghZuVs5LWXV8At1sIYWaH_wuyDR8f&gdpr=1&cmpNeeded=false was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 611 source: "https://sb.scorecardresearch.com/beacon.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://spiegel.demdex.net/dest5.html?d_nsid=0#https%3A%2F%2Fm.spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 5 column: 77 source: "https://spiegel.demdex.net/dest5.html?d_nsid=0#https%3A%2F%2Fm.spiegel.de"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 287 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 316 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 316 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 825 column: 63 source: "https://pixel.adsafeprotected.com/rjss/st/293514/36917883/skeleton.js?obRequestId=Y_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj&obTimestamp=1566380989293"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 46 source: "https://vars.hotjar.com/box-90f3a29ef7448451db5af955688970d7.html"}]', u'[JavaScript Warning: "Array.slice is deprecated; use Array.prototype.slice instead" {file: "https://static.adsafeprotected.com/sca.17.4.95.js" line: 32}]', u'[JavaScript Warning: "onmozfullscreenerror sollte nicht mehr verwendet werden." {file: "https://static.adsafeprotected.com/sca.17.4.95.js" line: 33}]', u'[JavaScript Warning: "WebRTC-Schnittstellen mit dem "moz"-Prfix (mozRTCPeerConnection, mozRTCSessionDescription, mozRTCIceCandidate) sollten nicht mehr verwendet werden." {file: "https://static.adsafeprotected.com/sca.17.4.95.js" line: 33}]', u'[JavaScript Warning: "Request to access cookie or storage on https://widgets.outbrain.com/hub/index.html?permalink=https%3A%2F%2Fm.spiegel.de%2Fartikel%2Fa-1279616.html&widgetId=AR_1&fbk=0&ob-template=DE_Spiegel.de was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 825 column: 63 source: "https://pixel.adsafeprotected.com/rjss/st/293514/36917883/skeleton.js?obRequestId=Y_IVrvC2jZYaT6XQk_ti3U9DnVY1fYPcpSshfRESuxm0tALaxj7M0tV396CDOPSj&obTimestamp=1566380989293"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 8 column: 76 source: "https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html line 7 > scriptElement"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 7 column: 6414 source: "https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 148 column: 1194 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Der Orientierungssensor sollte nicht mehr verwendet werden." {file: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q" line: 107}]', u'[JavaScript Warning: "Mit document.write() wurde ein nicht balancierter Baum geschrieben, was dazu gefhrt hat, dass Daten aus dem Netzwerk neu geparst werden mussten. Fr weitere Informationen https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing" {file: "https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html" line: 8}]', u'[JavaScript Warning: "Request to access cookie or storage on https://sync.teads.tv/wigo-no-slot was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 9 column: 39 source: "https://sync.teads.tv/wigo-no-slot"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://ad.atdmt.com/i/img;adv=11287203704923;ec=11287203705169;s.a=12679;c.a=3186425;p.a=3813867;a.a=10159606;aaid=;aaid_lat=;idfa=;cache=INSERT_TIMESTAMP_HERE; was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://ad.atdmt.com/i/img;adv=11287203704923;ec=11287203705169;s.a=12679;c.a=3186425;p.a=3813867;a.a=10159606;aaid=;aaid_lat=;idfa=;cache=INSERT_TIMESTAMP_HERE; was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://imagesrv.adition.com/1x1.gif was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://imagesrv.adition.com/1x1.gif was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 0}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2 was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 85 column: 477 source: "https://s0.2mdn.net/ads/richmedia/studio/pv2/61122948/20190611020252165/index.html?e=69&leftOffset=0&topOffset=0&c=oxDA6zsBQa&t=1&renderingType=2"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true} was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 12 column: 3768 source: "https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true}"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true} was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 12 column: 1675 source: "https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true}"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true} was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 12 column: 1675 source: "https://gum.criteo.com/syncframe?topUrl=m.spiegel.de#{%22optout%22:{%22value%22:false,%22origin%22:0},%22uid%22:{%22origin%22:0},%22idfs%22:{%22origin%22:0},%22sid%22:{%22origin%22:0},%22origin%22:%22publishertag%22,%22version%22:68,%22lwid%22:{%22value%22:%2296ced732-d050-4a39-a380-5749b021c36b%22,%22origin%22:3},%22tld%22:%22spiegel.de%22,%22bundle%22:{%22origin%22:0},%22topUrl%22:%22m.spiegel.de%22,%22cw%22:true}"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 243 column: 47 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/sodar/Enqz_20U.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 35 column: 612 source: "https://tpc.googlesyndication.com/sodar/Enqz_20U.html"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 265 column: 659 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 1857 source: "https://tpc.googlesyndication.com/pagead/js/r20190815/r20110914/client/window_focus.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 265 column: 659 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 265 column: 659 source: "https://s0.2mdn.net/879366/html_inpage_rendering_lib_200_255.js"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 2 column: 243 source: "https://z.moatads.com/essencedigitalemea2015301593033067/moatad.js#moatClientLevel1=9026715&moatClientLevel2=22804332&moatClientLevel3=448373391&moatClientLevel4=117484748&moatClientSlicer1=1043393&moatClientSlicer2=252277373&zMoatG=ct=DE&st=&city=5763&dma=0&zp=&bw=4&moatVCE=0&ord=1773481802&zMoatAUCID=ABAjH0h6Zw3FV9-TIDeNnG6T2V6Q line 50 > eval"}]', u'[JavaScript Warning: "Request to access cookie or storage on https://tpc.googlesyndication.com/safeframe/1-0-35/html/container.html was blocked because we are blocking all third-party storage access requests and content blocking is enabled." {file: "https://m.spiegel.de/reise/fernweh/weltreise-weltenbummler-beschreiben-wie-sie-wieder-nach-hause-kamen-a-1279616.html" line: 1 column: 1857 source: "https://tpc.googlesyndication.com/pagead/js/r20190815/r20110914/client/window_focus.js"}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_design | m spiegel de site is not usable url browser version firefox mobile operating system android tested another browser yes problem type site is not usable description the optical size of the website is too small you can not read it steps to reproduce the optical size of the website is too small it does not fit in the full size of the window browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen true mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel beta console messages u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u from with ❤️ | 0 |
64,638 | 7,822,307,895 | IssuesEvent | 2018-06-14 01:41:10 | monero-project/kovri | https://api.github.com/repos/monero-project/kovri | closed | 'kovri -h' prints 3 error lines at end of output | design maintenance minor | ---
**By submitting this issue, I confirm the following:**
- I have read and understood the developer guide in [kovri-docs](https://github.com/monero-project/kovri-docs).
- I have checked that the issue I am reporting can be replicated or that the feature I am suggesting is not present.
- I have checked opened or recently closed [pull requests](https://github.com/monero-project/kovri/pulls) for existing solutions/implementations to my issue/suggestion.
---
Here's my output:
> [2018-06-12 01:10:03.077251] [0x000072484dc80780] [info]
>
> system:
--host arg (=127.0.0.1)
-p [ --port ] arg (=0)
--data-dir path (=/root/.kovri)
-s [ --service ] arg
-d [ --enable-daemon ]
--disable-console-log
--disable-file-log
--disable-color-log
--enable-auto-flush-log
--log-level arg (=3)
--log-file-name path
-c [ --kovriconf ] path
-t [ --tunnelsconf ] path
>
>
> network:
--enable-ipv6
--enable-floodfill
-b [ --bandwidth ] arg (=L)
--disable-ssu
--disable-ntcp
-r [ --reseed-from ] arg
--disable-https
--disable-su3-verification
>
>
> client:
--httpproxyport arg (=4446)
--httpproxyaddress arg (=127.0.0.1)
--socksproxyport arg (=4447)
--socksproxyaddress arg (=127.0.0.1)
--proxykeys arg
--i2pcontrolport arg (=0)
--i2pcontroladdress arg (=127.0.0.1)
--i2pcontrolpassword arg (=itoopie)
>
> [2018-06-12 01:10:03.077350] [0x000072484dc80780] [error] Configuration: standard exception: 'for more details, see user-guide or config file'
[2018-06-12 01:10:03.077365] [0x000072484dc80780] [error] Instance: standard exception: 'for more details, see user-guide or config file'
[2018-06-12 01:10:03.077383] [0x000072484dc80780] [error] DaemonSingleton: Configure: standard exception: 'for more details, see user-guide or config file'
From IRC:
<anonimal> Those are just ctor function try blocks throwing because a real option was called. Help is thrown in with any invalid command, that could be cleaned up | 1.0 | 'kovri -h' prints 3 error lines at end of output - ---
**By submitting this issue, I confirm the following:**
- I have read and understood the developer guide in [kovri-docs](https://github.com/monero-project/kovri-docs).
- I have checked that the issue I am reporting can be replicated or that the feature I am suggesting is not present.
- I have checked opened or recently closed [pull requests](https://github.com/monero-project/kovri/pulls) for existing solutions/implementations to my issue/suggestion.
---
Here's my output:
> [2018-06-12 01:10:03.077251] [0x000072484dc80780] [info]
>
> system:
--host arg (=127.0.0.1)
-p [ --port ] arg (=0)
--data-dir path (=/root/.kovri)
-s [ --service ] arg
-d [ --enable-daemon ]
--disable-console-log
--disable-file-log
--disable-color-log
--enable-auto-flush-log
--log-level arg (=3)
--log-file-name path
-c [ --kovriconf ] path
-t [ --tunnelsconf ] path
>
>
> network:
--enable-ipv6
--enable-floodfill
-b [ --bandwidth ] arg (=L)
--disable-ssu
--disable-ntcp
-r [ --reseed-from ] arg
--disable-https
--disable-su3-verification
>
>
> client:
--httpproxyport arg (=4446)
--httpproxyaddress arg (=127.0.0.1)
--socksproxyport arg (=4447)
--socksproxyaddress arg (=127.0.0.1)
--proxykeys arg
--i2pcontrolport arg (=0)
--i2pcontroladdress arg (=127.0.0.1)
--i2pcontrolpassword arg (=itoopie)
>
> [2018-06-12 01:10:03.077350] [0x000072484dc80780] [error] Configuration: standard exception: 'for more details, see user-guide or config file'
[2018-06-12 01:10:03.077365] [0x000072484dc80780] [error] Instance: standard exception: 'for more details, see user-guide or config file'
[2018-06-12 01:10:03.077383] [0x000072484dc80780] [error] DaemonSingleton: Configure: standard exception: 'for more details, see user-guide or config file'
From IRC:
<anonimal> Those are just ctor function try blocks throwing because a real option was called. Help is thrown in with any invalid command, that could be cleaned up | design | kovri h prints error lines at end of output by submitting this issue i confirm the following i have read and understood the developer guide in i have checked that the issue i am reporting can be replicated or that the feature i am suggesting is not present i have checked opened or recently closed for existing solutions implementations to my issue suggestion here s my output system host arg p arg data dir path root kovri s arg d disable console log disable file log disable color log enable auto flush log log level arg log file name path c path t path network enable enable floodfill b arg l disable ssu disable ntcp r arg disable https disable verification client httpproxyport arg httpproxyaddress arg socksproxyport arg socksproxyaddress arg proxykeys arg arg arg arg itoopie configuration standard exception for more details see user guide or config file instance standard exception for more details see user guide or config file daemonsingleton configure standard exception for more details see user guide or config file from irc those are just ctor function try blocks throwing because a real option was called help is thrown in with any invalid command that could be cleaned up | 1 |
40,603 | 5,241,668,722 | IssuesEvent | 2017-01-31 16:14:25 | MapStory/mapstory | https://api.github.com/repos/MapStory/mapstory | opened | Add back social logins | design story feature | We removed Facebook and Google login icons from the Sign Up and Login modals so those services could be updated to latest versions. That work was completed by @Coop56. Now just need to add back the icons on the modals.
Not making part of 0.0 but should get addressed before we open up registration again aggressively to any new users.
| 1.0 | Add back social logins - We removed Facebook and Google login icons from the Sign Up and Login modals so those services could be updated to latest versions. That work was completed by @Coop56. Now just need to add back the icons on the modals.
Not making part of 0.0 but should get addressed before we open up registration again aggressively to any new users.
| design | add back social logins we removed facebook and google login icons from the sign up and login modals so those services could be updated to latest versions that work was completed by now just need to add back the icons on the modals not making part of but should get addressed before we open up registration again aggressively to any new users | 1 |
162,463 | 25,542,760,876 | IssuesEvent | 2022-11-29 16:24:47 | microsoft/pyright | https://api.github.com/repos/microsoft/pyright | closed | (member) function checking for None isn't recognized as a guard | enhancement request as designed | **Is your feature request related to a problem? Please describe.**
A clear and concise description of the problem.
```python
class T
...
def is_empty(self):
return self.binf is None or self.bsup is None
t = T()
if not t.is_empty():
x = t.binf + t.bsup
```
isn't recognized as a guard and gives `Operator "+" not supported for types "float | int | Unknown | None" and "float | int | Unknown | None"`
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
Recognize or have a way to flag a (member) function as a guard of some (member) variables also `not self.guard_fn()` should work too
**Additional context**
Add any other context or screenshots about the feature request here.
| 1.0 | (member) function checking for None isn't recognized as a guard - **Is your feature request related to a problem? Please describe.**
A clear and concise description of the problem.
```python
class T
...
def is_empty(self):
return self.binf is None or self.bsup is None
t = T()
if not t.is_empty():
x = t.binf + t.bsup
```
isn't recognized as a guard and gives `Operator "+" not supported for types "float | int | Unknown | None" and "float | int | Unknown | None"`
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
Recognize or have a way to flag a (member) function as a guard of some (member) variables also `not self.guard_fn()` should work too
**Additional context**
Add any other context or screenshots about the feature request here.
| design | member function checking for none isn t recognized as a guard is your feature request related to a problem please describe a clear and concise description of the problem python class t def is empty self return self binf is none or self bsup is none t t if not t is empty x t binf t bsup isn t recognized as a guard and gives operator not supported for types float int unknown none and float int unknown none describe the solution you d like a clear and concise description of what you want to happen recognize or have a way to flag a member function as a guard of some member variables also not self guard fn should work too additional context add any other context or screenshots about the feature request here | 1 |
473,940 | 13,649,601,704 | IssuesEvent | 2020-09-26 15:10:19 | jtenos/Scheduler | https://api.github.com/repos/jtenos/Scheduler | closed | admin terminal app | enhancement low priority | for use with command prompt - in case you don't want to mess with setting up a web application | 1.0 | admin terminal app - for use with command prompt - in case you don't want to mess with setting up a web application | non_design | admin terminal app for use with command prompt in case you don t want to mess with setting up a web application | 0 |
146,041 | 13,169,588,005 | IssuesEvent | 2020-08-11 13:58:18 | neuropoly/spinalcordtoolbox | https://api.github.com/repos/neuropoly/spinalcordtoolbox | closed | Command-line not rendered on RTD | documentation | EDIT 2020-08-07 15:04:06: The comment below is no more accurate. The problem is that the CLI doc is not rendered on RTD, as described in https://github.com/neuropoly/spinalcordtoolbox/issues/2834#issuecomment-670270201.
This is related to SCT not being 100% installable via pip. More details in https://github.com/neuropoly/spinalcordtoolbox/issues/1526.
~I must have done something wrong in the latest commits in, but the API doc does not render anymore in the master build ed976ac5aa153137177c69a9f82031dff969fc03:~
| 1.0 | Command-line not rendered on RTD - EDIT 2020-08-07 15:04:06: The comment below is no more accurate. The problem is that the CLI doc is not rendered on RTD, as described in https://github.com/neuropoly/spinalcordtoolbox/issues/2834#issuecomment-670270201.
This is related to SCT not being 100% installable via pip. More details in https://github.com/neuropoly/spinalcordtoolbox/issues/1526.
~I must have done something wrong in the latest commits in, but the API doc does not render anymore in the master build ed976ac5aa153137177c69a9f82031dff969fc03:~
| non_design | command line not rendered on rtd edit the comment below is no more accurate the problem is that the cli doc is not rendered on rtd as described in this is related to sct not being installable via pip more details in i must have done something wrong in the latest commits in but the api doc does not render anymore in the master build | 0 |
42,455 | 12,891,418,674 | IssuesEvent | 2020-07-13 17:41:55 | jtimberlake/jazz | https://api.github.com/repos/jtimberlake/jazz | opened | CVE-2018-19839 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2018-19839 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.5.3.tgz</b>, <b>node-sass-4.14.1.tgz</b>, <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.5.3.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-ua_20200713172249_EWBNAH/archiveExtraction_GYKECJ/20200713172249/ws-scm_depth_0/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json</p>
<p>Path to vulnerable library: /jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json,/tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json,/tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.4.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/jazz/templates/angular-website-template/app/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/jazz/templates/angular-website-template/app/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.13.10.tgz (Root Library)
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/jazz/commit/f31a850168fa59ceb2dfbdfb70a04c1bbe9b9fec">f31a850168fa59ceb2dfbdfb70a04c1bbe9b9fec</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 LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839>CVE-2018-19839</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839</a></p>
<p>Release Date: 2018-12-04</p>
<p>Fix Resolution: Libsass:3.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.5.3","isTransitiveDependency":false,"dependencyTree":"node-sass:4.5.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.4;node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.13.1","isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.13.10;node-sass:4.13.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"}],"vulnerabilityIdentifier":"CVE-2018-19839","vulnerabilityDetails":"In LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-19839 (Medium) detected in multiple libraries - ## CVE-2018-19839 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.5.3.tgz</b>, <b>node-sass-4.14.1.tgz</b>, <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.5.3.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-ua_20200713172249_EWBNAH/archiveExtraction_GYKECJ/20200713172249/ws-scm_depth_0/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json</p>
<p>Path to vulnerable library: /jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json,/tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json,/tmp/ws-scm/jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.4.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/jazz/templates/angular-website-template/app/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/jazz/templates/angular-website-template/app/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.13.10.tgz (Root Library)
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/jazz/commit/f31a850168fa59ceb2dfbdfb70a04c1bbe9b9fec">f31a850168fa59ceb2dfbdfb70a04c1bbe9b9fec</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 LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839>CVE-2018-19839</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839</a></p>
<p>Release Date: 2018-12-04</p>
<p>Fix Resolution: Libsass:3.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.5.3","isTransitiveDependency":false,"dependencyTree":"node-sass:4.5.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.4;node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.13.1","isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.13.10;node-sass:4.13.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"}],"vulnerabilityIdentifier":"CVE-2018-19839","vulnerabilityDetails":"In LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_design | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries node sass tgz node sass tgz node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws ua ewbnah archiveextraction gykecj ws scm depth jazz core jazz ui src app primary components daterange picker ngx slimscroll ngx slimscroll package json path to vulnerable library jazz core jazz ui src app primary components daterange picker datepicker node modules angular library builder node modules node sass package json tmp ws scm jazz core jazz ui src app primary components daterange picker datepicker node modules angular library builder node modules node sass package json dependency hierarchy x node sass tgz vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm jazz core jazz ui src app primary components daterange picker datepicker package json path to vulnerable library tmp ws scm jazz core jazz ui src app primary components daterange picker datepicker node modules node sass package json tmp ws scm jazz core jazz ui src app primary components daterange picker datepicker node modules node sass package json dependency hierarchy cli tgz root library x node sass tgz vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm jazz templates angular website template app package json path to vulnerable library tmp ws scm jazz templates angular website template app node modules node sass package json dependency hierarchy build angular tgz root library x node sass tgz vulnerable library found in head commit a href vulnerability details in libsass prior to the function handle error in sass context cpp allows attackers to cause a denial of service resulting from a heap based buffer over read via a crafted sass file publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact 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 libsass isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails in libsass prior to the function handle error in sass context cpp allows attackers to cause a denial of service resulting from a heap based buffer over read via a crafted sass file vulnerabilityurl | 0 |
93,444 | 15,887,396,584 | IssuesEvent | 2021-04-10 02:08:32 | turkdevops/framevuerk | https://api.github.com/repos/turkdevops/framevuerk | opened | CVE-2021-23337 (High) detected in multiple libraries | security vulnerability | ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.17.11.tgz</b>, <b>lodash-4.17.15.tgz</b>, <b>lodash-4.17.20.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.17.11.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz</a></p>
<p>Path to dependency file: framevuerk/package.json</p>
<p>Path to vulnerable library: framevuerk/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- html-webpack-plugin-3.2.0.tgz (Root Library)
- :x: **lodash-4.17.11.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: framevuerk/package.json</p>
<p>Path to vulnerable library: framevuerk/node_modules/@babel/types/node_modules/lodash/package.json,framevuerk/node_modules/@babel/helper-regex/node_modules/lodash/package.json,framevuerk/node_modules/@babel/helper-define-map/node_modules/lodash/package.json,framevuerk/node_modules/@babel/generator/node_modules/lodash/package.json,framevuerk/node_modules/@babel/traverse/node_modules/lodash/package.json,framevuerk/node_modules/table/node_modules/lodash/package.json,framevuerk/node_modules/@babel/helper-module-transforms/node_modules/lodash/package.json,framevuerk/node_modules/inquirer/node_modules/lodash/package.json,framevuerk/node_modules/@babel/plugin-transform-block-scoping/node_modules/lodash/package.json,framevuerk/node_modules/eslint/node_modules/lodash/package.json,framevuerk/node_modules/@babel/core/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- core-7.7.5.tgz (Root Library)
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.20.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: framevuerk/package.json</p>
<p>Path to vulnerable library: framevuerk/node_modules/babel-walk/node_modules/lodash/package.json,framevuerk/node_modules/with/node_modules/lodash/package.json,framevuerk/node_modules/async/node_modules/lodash/package.json,framevuerk/node_modules/@vue/compiler-core/node_modules/lodash/package.json,framevuerk/node_modules/@vue/compiler-sfc/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- vue-docgen-api-4.34.2.tgz (Root Library)
- pug-3.0.0.tgz
- pug-code-gen-3.0.1.tgz
- with-7.0.2.tgz
- babel-walk-3.0.0-canary-5.tgz
- types-7.12.12.tgz
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/framevuerk/commit/ec57c77bf757794377a6cab8e22128bbf4aba997">ec57c77bf757794377a6cab8e22128bbf4aba997</a></p>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23337 (High) detected in multiple libraries - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.17.11.tgz</b>, <b>lodash-4.17.15.tgz</b>, <b>lodash-4.17.20.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.17.11.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz</a></p>
<p>Path to dependency file: framevuerk/package.json</p>
<p>Path to vulnerable library: framevuerk/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- html-webpack-plugin-3.2.0.tgz (Root Library)
- :x: **lodash-4.17.11.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: framevuerk/package.json</p>
<p>Path to vulnerable library: framevuerk/node_modules/@babel/types/node_modules/lodash/package.json,framevuerk/node_modules/@babel/helper-regex/node_modules/lodash/package.json,framevuerk/node_modules/@babel/helper-define-map/node_modules/lodash/package.json,framevuerk/node_modules/@babel/generator/node_modules/lodash/package.json,framevuerk/node_modules/@babel/traverse/node_modules/lodash/package.json,framevuerk/node_modules/table/node_modules/lodash/package.json,framevuerk/node_modules/@babel/helper-module-transforms/node_modules/lodash/package.json,framevuerk/node_modules/inquirer/node_modules/lodash/package.json,framevuerk/node_modules/@babel/plugin-transform-block-scoping/node_modules/lodash/package.json,framevuerk/node_modules/eslint/node_modules/lodash/package.json,framevuerk/node_modules/@babel/core/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- core-7.7.5.tgz (Root Library)
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.20.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: framevuerk/package.json</p>
<p>Path to vulnerable library: framevuerk/node_modules/babel-walk/node_modules/lodash/package.json,framevuerk/node_modules/with/node_modules/lodash/package.json,framevuerk/node_modules/async/node_modules/lodash/package.json,framevuerk/node_modules/@vue/compiler-core/node_modules/lodash/package.json,framevuerk/node_modules/@vue/compiler-sfc/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- vue-docgen-api-4.34.2.tgz (Root Library)
- pug-3.0.0.tgz
- pug-code-gen-3.0.1.tgz
- with-7.0.2.tgz
- babel-walk-3.0.0-canary-5.tgz
- types-7.12.12.tgz
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/framevuerk/commit/ec57c77bf757794377a6cab8e22128bbf4aba997">ec57c77bf757794377a6cab8e22128bbf4aba997</a></p>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz lodash tgz lodash modular utilities library home page a href path to dependency file framevuerk package json path to vulnerable library framevuerk node modules lodash package json dependency hierarchy html webpack plugin tgz root library x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file framevuerk package json path to vulnerable library framevuerk node modules babel types node modules lodash package json framevuerk node modules babel helper regex node modules lodash package json framevuerk node modules babel helper define map node modules lodash package json framevuerk node modules babel generator node modules lodash package json framevuerk node modules babel traverse node modules lodash package json framevuerk node modules table node modules lodash package json framevuerk node modules babel helper module transforms node modules lodash package json framevuerk node modules inquirer node modules lodash package json framevuerk node modules babel plugin transform block scoping node modules lodash package json framevuerk node modules eslint node modules lodash package json framevuerk node modules babel core node modules lodash package json dependency hierarchy core tgz root library x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file framevuerk package json path to vulnerable library framevuerk node modules babel walk node modules lodash package json framevuerk node modules with node modules lodash package json framevuerk node modules async node modules lodash package json framevuerk node modules vue compiler core node modules lodash package json framevuerk node modules vue compiler sfc node modules lodash package json dependency hierarchy vue docgen api tgz root library pug tgz pug code gen tgz with tgz babel walk canary tgz types tgz x lodash tgz vulnerable library found in head commit a href found in base branch next vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash step up your open source security game with whitesource | 0 |
114,218 | 14,540,989,107 | IssuesEvent | 2020-12-15 14:02:09 | EveGroup/EveHolder | https://api.github.com/repos/EveGroup/EveHolder | closed | change front-end | design implememts | - [x] register
- [x] login
- [x] visitor
- [x] host
- [x] event list
- [x] visitor list
- [x] event register
- [x] event detail
- [x] dashboard
- [x] create event | 1.0 | change front-end - - [x] register
- [x] login
- [x] visitor
- [x] host
- [x] event list
- [x] visitor list
- [x] event register
- [x] event detail
- [x] dashboard
- [x] create event | design | change front end register login visitor host event list visitor list event register event detail dashboard create event | 1 |
53,549 | 11,089,996,436 | IssuesEvent | 2019-12-14 22:48:00 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | default object from empty value articles list [php 7.4] | No Code Attached Yet | ### Steps to reproduce the issue
Create a menu for of type articles list with enough articles for there to be pagination
### Expected result
Use the pagination without error
### Actual result
### 4.0
Warning: Creating default object from empty value in C:\htdocs\joomla-cms\components\com_content\tmpl\category\default_articles.php on line 24
### Staging - protostar
Warning: Creating default object from empty value in C:\htdocs\cms\components\com_content\views\category\tmpl\default_articles.php on line 18
### Staging - beez
Warning: Creating default object from empty value in C:\htdocs\cms\templates\beez3\html\com_content\category\default_articles.php on line 17
### System information (as much as possible)
**php 7.4**
### Additional comments
I only checked article lists - this may be present for other lists | 1.0 | default object from empty value articles list [php 7.4] - ### Steps to reproduce the issue
Create a menu for of type articles list with enough articles for there to be pagination
### Expected result
Use the pagination without error
### Actual result
### 4.0
Warning: Creating default object from empty value in C:\htdocs\joomla-cms\components\com_content\tmpl\category\default_articles.php on line 24
### Staging - protostar
Warning: Creating default object from empty value in C:\htdocs\cms\components\com_content\views\category\tmpl\default_articles.php on line 18
### Staging - beez
Warning: Creating default object from empty value in C:\htdocs\cms\templates\beez3\html\com_content\category\default_articles.php on line 17
### System information (as much as possible)
**php 7.4**
### Additional comments
I only checked article lists - this may be present for other lists | non_design | default object from empty value articles list steps to reproduce the issue create a menu for of type articles list with enough articles for there to be pagination expected result use the pagination without error actual result warning creating default object from empty value in c htdocs joomla cms components com content tmpl category default articles php on line staging protostar warning creating default object from empty value in c htdocs cms components com content views category tmpl default articles php on line staging beez warning creating default object from empty value in c htdocs cms templates html com content category default articles php on line system information as much as possible php additional comments i only checked article lists this may be present for other lists | 0 |
420,441 | 28,264,294,437 | IssuesEvent | 2023-04-07 04:34:30 | a-calero3/Gestion-de-Inventario-Malibu-Peru | https://api.github.com/repos/a-calero3/Gestion-de-Inventario-Malibu-Peru | opened | Validar el modelo de la base de datos | documentation prioridad: media | Se requiere validar el modelo de la base de datos diseñado para el proyecto con el fin de garantizar su correcta implementación y funcionamiento. Se debe verificar que la estructura de la base de datos es coherente con los requerimientos del sistema. Además, se debe asegurar que se cumplan los estándares de seguridad y privacidad de los datos establecidos para el proyecto. | 1.0 | Validar el modelo de la base de datos - Se requiere validar el modelo de la base de datos diseñado para el proyecto con el fin de garantizar su correcta implementación y funcionamiento. Se debe verificar que la estructura de la base de datos es coherente con los requerimientos del sistema. Además, se debe asegurar que se cumplan los estándares de seguridad y privacidad de los datos establecidos para el proyecto. | non_design | validar el modelo de la base de datos se requiere validar el modelo de la base de datos diseñado para el proyecto con el fin de garantizar su correcta implementación y funcionamiento se debe verificar que la estructura de la base de datos es coherente con los requerimientos del sistema además se debe asegurar que se cumplan los estándares de seguridad y privacidad de los datos establecidos para el proyecto | 0 |
251,292 | 21,467,146,276 | IssuesEvent | 2022-04-26 05:45:41 | sap-tutorials/Tutorials | https://api.github.com/repos/sap-tutorials/Tutorials | closed | Request Product Details with an Integration Scenario - Role collection to be added | SCPTest-trial2 SCPTest-cloudin SCPTest-trial3 High-Prio SCPTest-2204A | Mission: https://developers.sap.com/mission.cp-starter-integration-cpi.html
--------
Hello,
Step 2: https://developers.sap.com/tutorials/cp-starter-isuite-onboard-subscribe.html#:~:text=You%20are%20subscribed%20to%20the%20service%20now.%20Click%20Go%20to%20Application%20in%20the%20Integration%20Suite%20overview%20page.%20Now%20you%20are%20directed%20to%20the%20Integration%20Suite%20Launchpad.
After subscribing the app, the default role (Integration_Provisioner) is not added by default sometimes.
Please add steps to add the roles, or mention it as a note to make sure the role bas been assigned and how to assign if not already done automatically.
Thanks,
Shubham
Labels to be added:
prior - high-prio
Sprint Label: SCPTest-2204A
Scenario label: SCPTest-cloudin
Landscape: trial2, trial3 | 4.0 | Request Product Details with an Integration Scenario - Role collection to be added - Mission: https://developers.sap.com/mission.cp-starter-integration-cpi.html
--------
Hello,
Step 2: https://developers.sap.com/tutorials/cp-starter-isuite-onboard-subscribe.html#:~:text=You%20are%20subscribed%20to%20the%20service%20now.%20Click%20Go%20to%20Application%20in%20the%20Integration%20Suite%20overview%20page.%20Now%20you%20are%20directed%20to%20the%20Integration%20Suite%20Launchpad.
After subscribing the app, the default role (Integration_Provisioner) is not added by default sometimes.
Please add steps to add the roles, or mention it as a note to make sure the role bas been assigned and how to assign if not already done automatically.
Thanks,
Shubham
Labels to be added:
prior - high-prio
Sprint Label: SCPTest-2204A
Scenario label: SCPTest-cloudin
Landscape: trial2, trial3 | non_design | request product details with an integration scenario role collection to be added mission hello step after subscribing the app the default role integration provisioner is not added by default sometimes please add steps to add the roles or mention it as a note to make sure the role bas been assigned and how to assign if not already done automatically thanks shubham labels to be added prior high prio sprint label scptest scenario label scptest cloudin landscape | 0 |
177,678 | 28,965,044,295 | IssuesEvent | 2023-05-10 07:16:44 | OFFTORIVER/BJGG | https://api.github.com/repos/OFFTORIVER/BJGG | opened | [Feat] 이용가능서비스 UI 구현 | ✨ Feat :art: Design | **Issue : Feature**
이용가능한 서비스 탭 영역 UI 구현
**Description**
1. 관련 Asset Import
2. UI 구현
| 1.0 | [Feat] 이용가능서비스 UI 구현 - **Issue : Feature**
이용가능한 서비스 탭 영역 UI 구현
**Description**
1. 관련 Asset Import
2. UI 구현
| design | 이용가능서비스 ui 구현 issue feature 이용가능한 서비스 탭 영역 ui 구현 description 관련 asset import ui 구현 | 1 |
22,231 | 15,054,702,073 | IssuesEvent | 2021-02-03 17:46:35 | aguirre-lab/ml4c3 | https://api.github.com/repos/aguirre-lab/ml4c3 | opened | Add average reward when plotting reward | infrastructure 🚇 | ## What and why
For now only the episode reward is plotted. Also plot average reward in the same figure.
## Solution(s)
Add new capability on Plotter class to overlap plots in the same figure.
## Acceptance criteria
Reward and mean reward are plot on the same figure.
## Blocked by or pending
| 1.0 | Add average reward when plotting reward - ## What and why
For now only the episode reward is plotted. Also plot average reward in the same figure.
## Solution(s)
Add new capability on Plotter class to overlap plots in the same figure.
## Acceptance criteria
Reward and mean reward are plot on the same figure.
## Blocked by or pending
| non_design | add average reward when plotting reward what and why for now only the episode reward is plotted also plot average reward in the same figure solution s add new capability on plotter class to overlap plots in the same figure acceptance criteria reward and mean reward are plot on the same figure blocked by or pending | 0 |
344,569 | 30,751,704,410 | IssuesEvent | 2023-07-28 19:56:13 | saltstack/salt | https://api.github.com/repos/saltstack/salt | opened | [Increase Test Coverage] Batch 129 | Tests | Increase the code coverage percent on the following files to at least 80%.
Please be aware that currently the percentage might be inaccurate if the module uses salt due to #64696
File | Percent
salt/pillar/gpg.py 50
salt/renderers/json.py 18
salt/renderers/json5.py 39
salt/returners/local.py 50
salt/returners/multi_returner.py 20
| 1.0 | [Increase Test Coverage] Batch 129 - Increase the code coverage percent on the following files to at least 80%.
Please be aware that currently the percentage might be inaccurate if the module uses salt due to #64696
File | Percent
salt/pillar/gpg.py 50
salt/renderers/json.py 18
salt/renderers/json5.py 39
salt/returners/local.py 50
salt/returners/multi_returner.py 20
| non_design | batch increase the code coverage percent on the following files to at least please be aware that currently the percentage might be inaccurate if the module uses salt due to file percent salt pillar gpg py salt renderers json py salt renderers py salt returners local py salt returners multi returner py | 0 |
79,727 | 9,937,597,014 | IssuesEvent | 2019-07-02 22:29:14 | microsoft/BotFramework-Emulator | https://api.github.com/repos/microsoft/BotFramework-Emulator | closed | [Bot Inspector] Paged State-Diffing | 4.5 Design Enhancement | ### Paged State-Diffing
Currently to move into state diff mode one has to open a context menu (right-click) and select an option from that menu to render the diff. This was a temporary solution until we had the cycles to build state-diff paging into the Bot State Inspector panel, where you can both move into state diff mode on a given Bot State, and page forward/backward to future/previous bot state diffs via buttons.
*High-level code changes*
- Introduce new buttons in or near the bot state extension to move into and out of state diff mode and page through state diff modes when currently in state diff mode.
- Extension manifest change to support Icons
- Adjustment of the Bot State context menu in the chat control to no longer provide the menu item.
- Provide the extension with all current Activities so it can maintain its own state. | 1.0 | [Bot Inspector] Paged State-Diffing - ### Paged State-Diffing
Currently to move into state diff mode one has to open a context menu (right-click) and select an option from that menu to render the diff. This was a temporary solution until we had the cycles to build state-diff paging into the Bot State Inspector panel, where you can both move into state diff mode on a given Bot State, and page forward/backward to future/previous bot state diffs via buttons.
*High-level code changes*
- Introduce new buttons in or near the bot state extension to move into and out of state diff mode and page through state diff modes when currently in state diff mode.
- Extension manifest change to support Icons
- Adjustment of the Bot State context menu in the chat control to no longer provide the menu item.
- Provide the extension with all current Activities so it can maintain its own state. | design | paged state diffing paged state diffing currently to move into state diff mode one has to open a context menu right click and select an option from that menu to render the diff this was a temporary solution until we had the cycles to build state diff paging into the bot state inspector panel where you can both move into state diff mode on a given bot state and page forward backward to future previous bot state diffs via buttons high level code changes introduce new buttons in or near the bot state extension to move into and out of state diff mode and page through state diff modes when currently in state diff mode extension manifest change to support icons adjustment of the bot state context menu in the chat control to no longer provide the menu item provide the extension with all current activities so it can maintain its own state | 1 |
79,594 | 9,920,423,308 | IssuesEvent | 2019-06-30 09:08:17 | MVCoconut/coconut.data | https://api.github.com/repos/MVCoconut/coconut.data | closed | Review guards design. | design | Guards are a currently undocumented feature, that work roughly like so:
```haxe
class Example implements Model [
@:guard(Math.max(0, Math.min(1, next))
@:editable var volume:Float = 3;
}
```
The guard is called on every update of an editable or observable property, with `prev` being the previous and `next` being the next value. However it's not called upon construction. In this particular case having an abstract over float that does the clamping would be more elegant. Perhaps guards should simply be removed again. | 1.0 | Review guards design. - Guards are a currently undocumented feature, that work roughly like so:
```haxe
class Example implements Model [
@:guard(Math.max(0, Math.min(1, next))
@:editable var volume:Float = 3;
}
```
The guard is called on every update of an editable or observable property, with `prev` being the previous and `next` being the next value. However it's not called upon construction. In this particular case having an abstract over float that does the clamping would be more elegant. Perhaps guards should simply be removed again. | design | review guards design guards are a currently undocumented feature that work roughly like so haxe class example implements model guard math max math min next editable var volume float the guard is called on every update of an editable or observable property with prev being the previous and next being the next value however it s not called upon construction in this particular case having an abstract over float that does the clamping would be more elegant perhaps guards should simply be removed again | 1 |
20,574 | 6,900,272,276 | IssuesEvent | 2017-11-24 17:32:34 | craigbarnes/dte | https://api.github.com/repos/craigbarnes/dte | closed | Generate PDF manual as a single file | build-system documentation | The current [PDF manual](https://github.com/craigbarnes/dte#documentation) is split into 3 separate files in the same way as the man pages, but by convention, PDF manuals are almost always distributed as large, single documents containing everything.
The `dte` PDF manual should follow this convention and should be a concatenation of all 3 man pages. This might require some extra post-processing and/or adjustments to [`docs/ttman.c`](https://github.com/craigbarnes/dte/blob/master/docs/ttman.c). | 1.0 | Generate PDF manual as a single file - The current [PDF manual](https://github.com/craigbarnes/dte#documentation) is split into 3 separate files in the same way as the man pages, but by convention, PDF manuals are almost always distributed as large, single documents containing everything.
The `dte` PDF manual should follow this convention and should be a concatenation of all 3 man pages. This might require some extra post-processing and/or adjustments to [`docs/ttman.c`](https://github.com/craigbarnes/dte/blob/master/docs/ttman.c). | non_design | generate pdf manual as a single file the current is split into separate files in the same way as the man pages but by convention pdf manuals are almost always distributed as large single documents containing everything the dte pdf manual should follow this convention and should be a concatenation of all man pages this might require some extra post processing and or adjustments to | 0 |
97,721 | 16,241,878,380 | IssuesEvent | 2021-05-07 10:30:42 | SmartBear/cucumberstudio-api-documentation | https://api.github.com/repos/SmartBear/cucumberstudio-api-documentation | closed | CVE-2019-16782 (Medium) detected in rack-2.0.4.gem - autoclosed | security vulnerability | ## CVE-2019-16782 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rack-2.0.4.gem</b></p></summary>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
Also see https://rack.github.io/.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.0.4.gem">https://rubygems.org/gems/rack-2.0.4.gem</a></p>
<p>
Dependency Hierarchy:
- middleman-syntax-3.0.0.gem (Root Library)
- middleman-core-4.1.14.gem
- :x: **rack-2.0.4.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
<p>Publish Date: 2019-12-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16782>CVE-2019-16782</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16782">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16782</a></p>
<p>Release Date: 2019-12-18</p>
<p>Fix Resolution: 1.6.12;2.0.8</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Ruby","packageName":"rack","packageVersion":"2.0.4","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"middleman-syntax:3.0.0;middleman-core:4.1.14;rack:2.0.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.6.12;2.0.8"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16782","vulnerabilityDetails":"There\u0027s a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16782","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-16782 (Medium) detected in rack-2.0.4.gem - autoclosed - ## CVE-2019-16782 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rack-2.0.4.gem</b></p></summary>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
Also see https://rack.github.io/.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.0.4.gem">https://rubygems.org/gems/rack-2.0.4.gem</a></p>
<p>
Dependency Hierarchy:
- middleman-syntax-3.0.0.gem (Root Library)
- middleman-core-4.1.14.gem
- :x: **rack-2.0.4.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
<p>Publish Date: 2019-12-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16782>CVE-2019-16782</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16782">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16782</a></p>
<p>Release Date: 2019-12-18</p>
<p>Fix Resolution: 1.6.12;2.0.8</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Ruby","packageName":"rack","packageVersion":"2.0.4","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"middleman-syntax:3.0.0;middleman-core:4.1.14;rack:2.0.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.6.12;2.0.8"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16782","vulnerabilityDetails":"There\u0027s a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16782","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_design | cve medium detected in rack gem autoclosed cve medium severity vulnerability vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call also see library home page a href dependency hierarchy middleman syntax gem root library middleman core gem x rack gem vulnerable library found in base branch master vulnerability details there s a possible information leak session hijack vulnerability in rack rubygem rack this vulnerability is patched in versions and attackers may be able to find and hijack sessions by using timing attacks targeting the session id session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id by carefully measuring the amount of time it takes to look up a session an attacker may be able to find a valid session id and hijack the session the session id itself may be generated randomly but the way the session is indexed by the backing store does not use a secure comparison publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree middleman syntax middleman core rack isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails there a possible information leak session hijack vulnerability in rack rubygem rack this vulnerability is patched in versions and attackers may be able to find and hijack sessions by using timing attacks targeting the session id session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id by carefully measuring the amount of time it takes to look up a session an attacker may be able to find a valid session id and hijack the session the session id itself may be generated randomly but the way the session is indexed by the backing store does not use a secure comparison vulnerabilityurl | 0 |
264,432 | 20,020,412,641 | IssuesEvent | 2022-02-01 15:55:29 | Call-for-Code-for-Racial-Justice/Open-Sentencing | https://api.github.com/repos/Call-for-Code-for-Racial-Justice/Open-Sentencing | opened | New Review/Look for Risks | documentation | ### Background on the problem the feature will solve/improved user experience
We need to keep looking out for any new risks as we make changes. Need someone to review/comment if we see any news risks in terms of data, licenses, or other ideas.
### Describe the solution you'd like
A write up after someone reviews for risks.
### Acceptance Criteria
Write up in issue. Approval by a team member. | 1.0 | New Review/Look for Risks - ### Background on the problem the feature will solve/improved user experience
We need to keep looking out for any new risks as we make changes. Need someone to review/comment if we see any news risks in terms of data, licenses, or other ideas.
### Describe the solution you'd like
A write up after someone reviews for risks.
### Acceptance Criteria
Write up in issue. Approval by a team member. | non_design | new review look for risks background on the problem the feature will solve improved user experience we need to keep looking out for any new risks as we make changes need someone to review comment if we see any news risks in terms of data licenses or other ideas describe the solution you d like a write up after someone reviews for risks acceptance criteria write up in issue approval by a team member | 0 |
39,654 | 5,114,467,422 | IssuesEvent | 2017-01-06 18:35:24 | NuGet/Home | https://api.github.com/repos/NuGet/Home | closed | Trim whitespace from project properties in LegacyCSProj | ClosedAs:ByDesign Style:PackageReference Type:Bug | Properties in MSBuild project files may contain additional whitespace. This space is generally ignored in MSBuild and the project system should handle this also.
This issue tracks the Legacy CSProj project system work for the original issue:
https://github.com/NuGet/Home/issues/3819 | 1.0 | Trim whitespace from project properties in LegacyCSProj - Properties in MSBuild project files may contain additional whitespace. This space is generally ignored in MSBuild and the project system should handle this also.
This issue tracks the Legacy CSProj project system work for the original issue:
https://github.com/NuGet/Home/issues/3819 | design | trim whitespace from project properties in legacycsproj properties in msbuild project files may contain additional whitespace this space is generally ignored in msbuild and the project system should handle this also this issue tracks the legacy csproj project system work for the original issue | 1 |
65,940 | 7,934,426,996 | IssuesEvent | 2018-07-08 19:05:48 | publiclab/plots2 | https://api.github.com/repos/publiclab/plots2 | closed | Minor changes for Social media icons on profile page | HTML design first-timers-only has-pull-request | Hi, this is a [first-timers-only issue](https://publiclab.github.io/community-toolbox/#r=all). This means we've worked to make it more legible to folks who either **haven't contributed to our codebase before, or even folks who haven't contributed to open source before**.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, **consider leaving this one for someone new**, and looking through our general [help wanted](https://github.com/publiclab/plots2/labels/help-wanted) issues. Thanks!
### 🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
Our Profile page needs some minor CSS fixes. Remove hover effects so that on hovering over social media icons, the black line doesn't generate.Instead, add the hover effect to enlarge social media icon on hover.And add the margin between each icon.
File that needs changes - https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb
Thank you!!
### 📋 Step by Step
- [ ] 🙋 **Claim this issue**: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
- [ ] 📝 **Update** the file [app/views/users/profile.html.erb](https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb) in the `plots2` repository so as to do the required changes.
[See this page](https://publiclab.github.io/community-toolbox/#r=all) for some help in taking your first steps!
- [ ] 💾 **Commit** your changes
- [ ] 🔀 **Start a Pull Request**. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
2. You can also [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/) and open a pull request from there.
- [ ] 🏁 **Done** Ask in comments for a review :)
### 🤔❓ Questions?
Leave a comment below!
### Is someone else already working on this?
We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. **If someone seem stuck, offer them some help!** Otherwise, [take a look at some other issues you can help with](https://publiclab.github.io/community-toolbox/#r=all). Thanks!
(This issue was created by [First-Timers-Bot](https://github.com/hoodiehq/first-timers-bot).)
| 1.0 | Minor changes for Social media icons on profile page - Hi, this is a [first-timers-only issue](https://publiclab.github.io/community-toolbox/#r=all). This means we've worked to make it more legible to folks who either **haven't contributed to our codebase before, or even folks who haven't contributed to open source before**.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, **consider leaving this one for someone new**, and looking through our general [help wanted](https://github.com/publiclab/plots2/labels/help-wanted) issues. Thanks!
### 🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
Our Profile page needs some minor CSS fixes. Remove hover effects so that on hovering over social media icons, the black line doesn't generate.Instead, add the hover effect to enlarge social media icon on hover.And add the margin between each icon.
File that needs changes - https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb
Thank you!!
### 📋 Step by Step
- [ ] 🙋 **Claim this issue**: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
- [ ] 📝 **Update** the file [app/views/users/profile.html.erb](https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb) in the `plots2` repository so as to do the required changes.
[See this page](https://publiclab.github.io/community-toolbox/#r=all) for some help in taking your first steps!
- [ ] 💾 **Commit** your changes
- [ ] 🔀 **Start a Pull Request**. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
2. You can also [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/) and open a pull request from there.
- [ ] 🏁 **Done** Ask in comments for a review :)
### 🤔❓ Questions?
Leave a comment below!
### Is someone else already working on this?
We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. **If someone seem stuck, offer them some help!** Otherwise, [take a look at some other issues you can help with](https://publiclab.github.io/community-toolbox/#r=all). Thanks!
(This issue was created by [First-Timers-Bot](https://github.com/hoodiehq/first-timers-bot).)
| design | minor changes for social media icons on profile page hi this is a this means we ve worked to make it more legible to folks who either haven t contributed to our codebase before or even folks who haven t contributed to open source before if that s you we re interested in helping you take the first step and can answer questions and help you out as you do note that we re especially interested in contributions from people from groups underrepresented in free and open source software we know that the process of creating a pull request is the biggest barrier for new contributors this issue is for you 💝 if you have contributed before consider leaving this one for someone new and looking through our general issues thanks 🤔 what you will need to know nothing this issue is meant to welcome you to open source we are happy to walk you through the process our profile page needs some minor css fixes remove hover effects so that on hovering over social media icons the black line doesn t generate instead add the hover effect to enlarge social media icon on hover and add the margin between each icon file that needs changes thank you 📋 step by step 🙋 claim this issue comment below if someone else has claimed it ask if they ve opened a pull request already and if they re stuck maybe you can help them solve a problem or move it along 📝 update the file in the repository so as to do the required changes for some help in taking your first steps 💾 commit your changes 🔀 start a pull request there are two ways how you can start a pull request if you are familiar with the terminal or would like to learn it on how to send a pull request using the terminal you can also and open a pull request from there 🏁 done ask in comments for a review 🤔❓ questions leave a comment below is someone else already working on this we encourage you to link to this issue by mentioning the issue in your pull request so we can see if someone s already started on it if someone seem stuck offer them some help otherwise thanks this issue was created by | 1 |
77,317 | 9,557,297,930 | IssuesEvent | 2019-05-03 11:04:03 | wordpress-mobile/WordPress-Android | https://api.github.com/repos/wordpress-mobile/WordPress-Android | closed | Post Filters - Design Review | Post List [Status] Needs Design Review [Type] Task | Do a full design review of all the changes in `feature/master-post-filters` before it's merged into `develop`. | 1.0 | Post Filters - Design Review - Do a full design review of all the changes in `feature/master-post-filters` before it's merged into `develop`. | design | post filters design review do a full design review of all the changes in feature master post filters before it s merged into develop | 1 |
127,998 | 27,171,765,860 | IssuesEvent | 2023-02-17 20:09:56 | mozilla/foundation.mozilla.org | https://api.github.com/repos/mozilla/foundation.mozilla.org | closed | [PNI Refactor] Add documentation to slider-area.js | engineering buyer's guide 🛍 code cleanup needs grooming | Add documentation (in [JSDoc style](https://jsdoc.app/)) to `source/js/buyers-guide/search/slider-area.js`.
e.g.,
```js
/**
* Represents a book.
* @constructor
* @param {string} title - The title of the book.
* @param {string} author - The author of the book.
*/
function Book(title, author) {
}
```
| 1.0 | [PNI Refactor] Add documentation to slider-area.js - Add documentation (in [JSDoc style](https://jsdoc.app/)) to `source/js/buyers-guide/search/slider-area.js`.
e.g.,
```js
/**
* Represents a book.
* @constructor
* @param {string} title - The title of the book.
* @param {string} author - The author of the book.
*/
function Book(title, author) {
}
```
| non_design | add documentation to slider area js add documentation in to source js buyers guide search slider area js e g js represents a book constructor param string title the title of the book param string author the author of the book function book title author | 0 |
58,759 | 7,177,507,486 | IssuesEvent | 2018-01-31 13:52:55 | jupyterlab/jupyterlab | https://api.github.com/repos/jupyterlab/jupyterlab | closed | File Browser: Handling multiple selections | pkg:filebrowser tag:Design and UX type:Enhancement | Currently in the File Browser you can select multiple file but it doesn't allow you to drag them to a folder which forces you to move them one at a time.
It would be good if the drag action worked with multiple selections
| 1.0 | File Browser: Handling multiple selections - Currently in the File Browser you can select multiple file but it doesn't allow you to drag them to a folder which forces you to move them one at a time.
It would be good if the drag action worked with multiple selections
| design | file browser handling multiple selections currently in the file browser you can select multiple file but it doesn t allow you to drag them to a folder which forces you to move them one at a time it would be good if the drag action worked with multiple selections | 1 |
170,108 | 26,904,387,157 | IssuesEvent | 2023-02-06 17:52:17 | webstudio-is/webstudio-designer | https://api.github.com/repos/webstudio-is/webstudio-designer | opened | UX improvement for Inputs that have both keywords and units | type:enhancement complexity:low area:components area:designer prio:2 | The current implementation shows a select menu button on the input when a user starts typing letters, but a unit menu button when the user types numbers (sometimes - it doesn't seem to show up consistently). This is not a good pattern becuase the unit menu should be visible at all times so the user knows that this input accepts numbers and not just key words.
> My suggestion is similar to the current implementation except that we never show a keyword menu button and always show units (when both are allowed). Keywords can be typed + an autocomplete menu shows, but no keyword select menu.
In the future we could have both menus showing, but the above suggestion would work pretty well and hopefully not require a lot of work. | 1.0 | UX improvement for Inputs that have both keywords and units - The current implementation shows a select menu button on the input when a user starts typing letters, but a unit menu button when the user types numbers (sometimes - it doesn't seem to show up consistently). This is not a good pattern becuase the unit menu should be visible at all times so the user knows that this input accepts numbers and not just key words.
> My suggestion is similar to the current implementation except that we never show a keyword menu button and always show units (when both are allowed). Keywords can be typed + an autocomplete menu shows, but no keyword select menu.
In the future we could have both menus showing, but the above suggestion would work pretty well and hopefully not require a lot of work. | design | ux improvement for inputs that have both keywords and units the current implementation shows a select menu button on the input when a user starts typing letters but a unit menu button when the user types numbers sometimes it doesn t seem to show up consistently this is not a good pattern becuase the unit menu should be visible at all times so the user knows that this input accepts numbers and not just key words my suggestion is similar to the current implementation except that we never show a keyword menu button and always show units when both are allowed keywords can be typed an autocomplete menu shows but no keyword select menu in the future we could have both menus showing but the above suggestion would work pretty well and hopefully not require a lot of work | 1 |
458,041 | 13,167,376,755 | IssuesEvent | 2020-08-11 10:09:46 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | [0.9.0 staging-1711] NullReferenceException when highlight Excavator | Category: Tech Priority: Medium | Step to reproduce:
- jump on the excavator
- start to mousover different part of excavator:
```
NullReferenceException: Object reference not set to an instance of an object.
at EcoEngine.Rendering.RenderingSystem.IsIndirect (UnityEngine.Renderer renderer) [0x00000] in <00000000000000000000000000000000>:0
at EcoEngine.Rendering.RenderingSystem.TryGetIndirectRenderingBatch (UnityEngine.Renderer renderer, EcoEngine.Rendering.IndirectRenderingBatch& batch) [0x00000] in <00000000000000000000000000000000>:0
at EcoEngine.Rendering.RenderingSystem.OnHighlightRenderer (UnityEngine.Renderer renderer) [0x00000] in <00000000000000000000000000000000>:0
at EcoEngine.Rendering.RenderingSystem.OnObjectHighlighted (HighlightableObject obj) [0x00000] in <00000000000000000000000000000000>:0
at System.Action`1[T].Invoke (T obj) [0x00000] in <00000000000000000000000000000000>:0
at HighlightableObject.Highlight (UnityEngine.Color highlightColor) [0x00000] in <00000000000000000000000000000000>:0
at InteractionHighlighter.Highlight (UnityEngine.Color highlightColor) [0x00000] in <00000000000000000000000000000000>:0
at InteractionManager.ProcessInteraction (System.Boolean force) [0x00000] in <00000000000000000000000000000000>:0
at InteractionManager.LateUpdate () [0x00000] in <00000000000000000000000000000000>:0
```
[Player.log](https://github.com/StrangeLoopGames/EcoIssues/files/5050247/Player.log)
| 1.0 | [0.9.0 staging-1711] NullReferenceException when highlight Excavator - Step to reproduce:
- jump on the excavator
- start to mousover different part of excavator:
```
NullReferenceException: Object reference not set to an instance of an object.
at EcoEngine.Rendering.RenderingSystem.IsIndirect (UnityEngine.Renderer renderer) [0x00000] in <00000000000000000000000000000000>:0
at EcoEngine.Rendering.RenderingSystem.TryGetIndirectRenderingBatch (UnityEngine.Renderer renderer, EcoEngine.Rendering.IndirectRenderingBatch& batch) [0x00000] in <00000000000000000000000000000000>:0
at EcoEngine.Rendering.RenderingSystem.OnHighlightRenderer (UnityEngine.Renderer renderer) [0x00000] in <00000000000000000000000000000000>:0
at EcoEngine.Rendering.RenderingSystem.OnObjectHighlighted (HighlightableObject obj) [0x00000] in <00000000000000000000000000000000>:0
at System.Action`1[T].Invoke (T obj) [0x00000] in <00000000000000000000000000000000>:0
at HighlightableObject.Highlight (UnityEngine.Color highlightColor) [0x00000] in <00000000000000000000000000000000>:0
at InteractionHighlighter.Highlight (UnityEngine.Color highlightColor) [0x00000] in <00000000000000000000000000000000>:0
at InteractionManager.ProcessInteraction (System.Boolean force) [0x00000] in <00000000000000000000000000000000>:0
at InteractionManager.LateUpdate () [0x00000] in <00000000000000000000000000000000>:0
```
[Player.log](https://github.com/StrangeLoopGames/EcoIssues/files/5050247/Player.log)
| non_design | nullreferenceexception when highlight excavator step to reproduce jump on the excavator start to mousover different part of excavator nullreferenceexception object reference not set to an instance of an object at ecoengine rendering renderingsystem isindirect unityengine renderer renderer in at ecoengine rendering renderingsystem trygetindirectrenderingbatch unityengine renderer renderer ecoengine rendering indirectrenderingbatch batch in at ecoengine rendering renderingsystem onhighlightrenderer unityengine renderer renderer in at ecoengine rendering renderingsystem onobjecthighlighted highlightableobject obj in at system action invoke t obj in at highlightableobject highlight unityengine color highlightcolor in at interactionhighlighter highlight unityengine color highlightcolor in at interactionmanager processinteraction system boolean force in at interactionmanager lateupdate in | 0 |
1,314 | 2,603,753,062 | IssuesEvent | 2015-02-24 17:44:44 | chrsmith/bwapi | https://api.github.com/repos/chrsmith/bwapi | closed | Game::canBuildHere -- Bad collision logic | auto-migrated Component-Logic Priority-Medium Type-Defect Usability | ```
What steps will reproduce the problem?
1. I've attached an AI module. Run it, playing as Terran.
2. Select your SCVs and right-click on the Command Center so that they are
right next to it.
3. Lift-off the Command Center.
4. Enter "Terran Command Center". (It can be any argument to
UnitTypes::getUnitType.)
5. Circles will be drawn indicating canBuildHere returning true, but a circle
is not drawn where the Command Center originally was.
6. If you land the Command Center back to where it was, the build tile
positions will indicate that you can.
What is the expected output? What do you see instead?
Game::canBuildHere gives a false negative in collision detection between a
proposed building and existing units. Currently, units that occupy the same
build tiles that the proposed building will is taken to mean that the units are
blocking the building. The correct test for collision is if the dimensions boxs
of the units and the proposed building overlap. (The width of the dimension box
is dimensionsLeft() + 1 + dimensionsRight(); similarly for height. The origin
of the dimensions box is Unit::getPosition().) You can verify this test in
StarCraft's GUI (although it seems that it lets you build if a unit is blocking
a little--the unit just resets collision). Since it seems that Unit::build uses
Game::canBuildHere, you can't build even though you should be able to.
What version of the product are you using? On what operating system?
BWAPI 2.8. Windows XP.
Please provide any additional information below.
```
-----
Original issue reported on code.google.com by `eugene.m...@gmail.com` on 16 Aug 2010 at 4:14
Attachments:
* [ExampleAIModule.dll](https://storage.googleapis.com/google-code-attachments/bwapi/issue-233/comment-0/ExampleAIModule.dll)
| 1.0 | Game::canBuildHere -- Bad collision logic - ```
What steps will reproduce the problem?
1. I've attached an AI module. Run it, playing as Terran.
2. Select your SCVs and right-click on the Command Center so that they are
right next to it.
3. Lift-off the Command Center.
4. Enter "Terran Command Center". (It can be any argument to
UnitTypes::getUnitType.)
5. Circles will be drawn indicating canBuildHere returning true, but a circle
is not drawn where the Command Center originally was.
6. If you land the Command Center back to where it was, the build tile
positions will indicate that you can.
What is the expected output? What do you see instead?
Game::canBuildHere gives a false negative in collision detection between a
proposed building and existing units. Currently, units that occupy the same
build tiles that the proposed building will is taken to mean that the units are
blocking the building. The correct test for collision is if the dimensions boxs
of the units and the proposed building overlap. (The width of the dimension box
is dimensionsLeft() + 1 + dimensionsRight(); similarly for height. The origin
of the dimensions box is Unit::getPosition().) You can verify this test in
StarCraft's GUI (although it seems that it lets you build if a unit is blocking
a little--the unit just resets collision). Since it seems that Unit::build uses
Game::canBuildHere, you can't build even though you should be able to.
What version of the product are you using? On what operating system?
BWAPI 2.8. Windows XP.
Please provide any additional information below.
```
-----
Original issue reported on code.google.com by `eugene.m...@gmail.com` on 16 Aug 2010 at 4:14
Attachments:
* [ExampleAIModule.dll](https://storage.googleapis.com/google-code-attachments/bwapi/issue-233/comment-0/ExampleAIModule.dll)
| non_design | game canbuildhere bad collision logic what steps will reproduce the problem i ve attached an ai module run it playing as terran select your scvs and right click on the command center so that they are right next to it lift off the command center enter terran command center it can be any argument to unittypes getunittype circles will be drawn indicating canbuildhere returning true but a circle is not drawn where the command center originally was if you land the command center back to where it was the build tile positions will indicate that you can what is the expected output what do you see instead game canbuildhere gives a false negative in collision detection between a proposed building and existing units currently units that occupy the same build tiles that the proposed building will is taken to mean that the units are blocking the building the correct test for collision is if the dimensions boxs of the units and the proposed building overlap the width of the dimension box is dimensionsleft dimensionsright similarly for height the origin of the dimensions box is unit getposition you can verify this test in starcraft s gui although it seems that it lets you build if a unit is blocking a little the unit just resets collision since it seems that unit build uses game canbuildhere you can t build even though you should be able to what version of the product are you using on what operating system bwapi windows xp please provide any additional information below original issue reported on code google com by eugene m gmail com on aug at attachments | 0 |
134,895 | 19,405,509,153 | IssuesEvent | 2021-12-19 23:02:47 | jayrc7/Movie-of-the-week | https://api.github.com/repos/jayrc7/Movie-of-the-week | closed | Add profile picture support for accounts | enhancement good first issue frontend backend Design | Simply add that functionality in the profile page, DO NOT modify other pages to support profile pictures. Those changes will come later. Must allow the user to choose a picture from their local storage, be able to crop/rotate, and allow it to be changed or removed entirely. Use an appropriate default image (e.g. silhouette of a person). Design must be approved by CODEOWNERS. | 1.0 | Add profile picture support for accounts - Simply add that functionality in the profile page, DO NOT modify other pages to support profile pictures. Those changes will come later. Must allow the user to choose a picture from their local storage, be able to crop/rotate, and allow it to be changed or removed entirely. Use an appropriate default image (e.g. silhouette of a person). Design must be approved by CODEOWNERS. | design | add profile picture support for accounts simply add that functionality in the profile page do not modify other pages to support profile pictures those changes will come later must allow the user to choose a picture from their local storage be able to crop rotate and allow it to be changed or removed entirely use an appropriate default image e g silhouette of a person design must be approved by codeowners | 1 |
95,983 | 12,068,860,886 | IssuesEvent | 2020-04-16 15:19:27 | zinc-collective/compensated | https://api.github.com/repos/zinc-collective/compensated | closed | Add explanation of labels to either CONTRIBUTING.md or separate core/HOWTO.md | design documentation good first issue | _Originally posted by @zspencer in https://github.com/zinc-collective/compensated/issues/50#issuecomment-605694538_
> Issues labeled "enhancement" are the "inner loop" of a [double-loop learning system](https://en.wikipedia.org/wiki/Double-loop_learning). They exist to take the higher-order design considerations and turn them into changes to the underlying documentation, designs, or code. Issues labeled "request for comment" are for the outer-loop.
>
> This ensures people who want to focus on "what to build" don't have to wade through long conversations to get to the mockups/use cases/acceptance tests; and ensures that people who want the broad, overarching philosophy can have those conversations as well.
1. Someone to document the various labels that have been setup and what that means when contributing.
2. Double bonus, work out a competency level which allows one to practice using the labels, in line with a [badgebot](https://github.com/bocoup/bots/wiki/Badgebot)
3. For a real DesignNinga, write a compensated bot that affirms the Coop's values of a warm neighbourhood and Code of Conduct. | 1.0 | Add explanation of labels to either CONTRIBUTING.md or separate core/HOWTO.md - _Originally posted by @zspencer in https://github.com/zinc-collective/compensated/issues/50#issuecomment-605694538_
> Issues labeled "enhancement" are the "inner loop" of a [double-loop learning system](https://en.wikipedia.org/wiki/Double-loop_learning). They exist to take the higher-order design considerations and turn them into changes to the underlying documentation, designs, or code. Issues labeled "request for comment" are for the outer-loop.
>
> This ensures people who want to focus on "what to build" don't have to wade through long conversations to get to the mockups/use cases/acceptance tests; and ensures that people who want the broad, overarching philosophy can have those conversations as well.
1. Someone to document the various labels that have been setup and what that means when contributing.
2. Double bonus, work out a competency level which allows one to practice using the labels, in line with a [badgebot](https://github.com/bocoup/bots/wiki/Badgebot)
3. For a real DesignNinga, write a compensated bot that affirms the Coop's values of a warm neighbourhood and Code of Conduct. | design | add explanation of labels to either contributing md or separate core howto md originally posted by zspencer in issues labeled enhancement are the inner loop of a they exist to take the higher order design considerations and turn them into changes to the underlying documentation designs or code issues labeled request for comment are for the outer loop this ensures people who want to focus on what to build don t have to wade through long conversations to get to the mockups use cases acceptance tests and ensures that people who want the broad overarching philosophy can have those conversations as well someone to document the various labels that have been setup and what that means when contributing double bonus work out a competency level which allows one to practice using the labels in line with a for a real designninga write a compensated bot that affirms the coop s values of a warm neighbourhood and code of conduct | 1 |
163,160 | 20,270,065,795 | IssuesEvent | 2022-02-15 15:28:24 | postgres-ai/database-lab-engine | https://api.github.com/repos/postgres-ai/database-lab-engine | closed | CVE-2020-15257 (Medium) detected in github.com/docker/docker-v20.10.12 - autoclosed | security vulnerability | ## CVE-2020-15257 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/docker/docker-v20.10.12</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/docker-v20.10.12** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/postgres-ai/database-lab-engine/commit/b3ac62d12e3d43994ff7ad836e34da801ed665fb">b3ac62d12e3d43994ff7ad836e34da801ed665fb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.
<p>Publish Date: 2020-12-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15257>CVE-2020-15257</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- 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/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4">https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4</a></p>
<p>Release Date: 2020-12-01</p>
<p>Fix Resolution: v1.3.9,v1.4.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-15257 (Medium) detected in github.com/docker/docker-v20.10.12 - autoclosed - ## CVE-2020-15257 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/docker/docker-v20.10.12</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/docker-v20.10.12** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/postgres-ai/database-lab-engine/commit/b3ac62d12e3d43994ff7ad836e34da801ed665fb">b3ac62d12e3d43994ff7ad836e34da801ed665fb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.
<p>Publish Date: 2020-12-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15257>CVE-2020-15257</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- 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/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4">https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4</a></p>
<p>Release Date: 2020-12-01</p>
<p>Fix Resolution: v1.3.9,v1.4.3</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 github com docker docker autoclosed cve medium severity vulnerability vulnerable library github com docker docker moby project a collaborative project for the container ecosystem to assemble container based systems dependency hierarchy x github com docker docker vulnerable library found in head commit a href found in base branch master vulnerability details containerd is an industry standard container runtime and is available as a daemon for linux and windows in containerd before versions and the containerd shim api is improperly exposed to host network containers access controls for the shim’s api socket verified that the connecting process had an effective uid of but did not otherwise restrict access to the abstract unix domain socket this would allow malicious containers running in the same network namespace as the shim with an effective uid of but otherwise reduced privileges to cause new processes to be run with elevated privileges this vulnerability has been fixed in containerd and users should update to these versions as soon as they are released it should be noted that containers started with an old version of containerd shim should be stopped and restarted as running containers will continue to be vulnerable even after an upgrade if you are not providing the ability for untrusted users to start containers in the same network namespace as the shim typically the host network namespace for example with docker run net host or hostnetwork true in a kubernetes pod and run with an effective uid of you are not vulnerable to this issue if you are running containers with a vulnerable configuration you can deny access to all abstract sockets with apparmor by adding a line similar to deny unix addr to your policy it is best practice to run containers with a reduced set of privileges with a non zero uid and with isolated namespaces the containerd maintainers strongly advise against sharing namespaces with the host reducing the set of isolation mechanisms used for a container necessarily increases that container s privilege regardless of what container runtime is used for running that container 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 changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
252,171 | 27,231,700,917 | IssuesEvent | 2023-02-21 13:43:13 | jgeraigery/ncr-bsp-hmac | https://api.github.com/repos/jgeraigery/ncr-bsp-hmac | opened | coverlet.collector.1.3.0.nupkg: 1 vulnerabilities (highest severity is: 7.5) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>coverlet.collector.1.3.0.nupkg</b></p></summary>
<p>Coverlet is a cross platform code coverage library for .NET, with support for line, branch and metho...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg">https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg</a></p>
<p>Path to dependency file: /dotnet/SendHMACTest/SendHMACTest.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/coverlet.collector/1.3.0/coverlet.collector.1.3.0.nupkg</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/ncr-bsp-hmac/commit/8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf">8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (coverlet.collector.1.3.0.nupkg version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2022-0161](https://github.com/JamesNK/Newtonsoft.Json/commit/7e77bbe1beccceac4fc7b174b53abfefac278b66) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | coverlet.collector.1.3.0.nupkg | Direct | Newtonsoft.Json - 13.0.1;Microsoft.Extensions.ApiDescription.Server - 6.0.0 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2022-0161</summary>
### Vulnerable Library - <b>coverlet.collector.1.3.0.nupkg</b></p>
<p>Coverlet is a cross platform code coverage library for .NET, with support for line, branch and metho...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg">https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg</a></p>
<p>Path to dependency file: /dotnet/SendHMACTest/SendHMACTest.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/coverlet.collector/1.3.0/coverlet.collector.1.3.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **coverlet.collector.1.3.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/ncr-bsp-hmac/commit/8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf">8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper Handling of Exceptional Conditions in Newtonsoft.Json.
Newtonsoft.Json prior to version 13.0.1 is vulnerable to Insecure Defaults due to improper handling of StackOverFlow exception (SOE) whenever nested expressions are being processed. Exploiting this vulnerability results in Denial Of Service (DoS), and it is exploitable when an attacker sends 5 requests that cause SOE in time frame of 5 minutes. This vulnerability affects Internet Information Services (IIS) Applications.
<p>Publish Date: 2022-06-22
<p>URL: <a href=https://github.com/JamesNK/Newtonsoft.Json/commit/7e77bbe1beccceac4fc7b174b53abfefac278b66>WS-2022-0161</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-06-22</p>
<p>Fix Resolution: Newtonsoft.Json - 13.0.1;Microsoft.Extensions.ApiDescription.Server - 6.0.0</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | coverlet.collector.1.3.0.nupkg: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>coverlet.collector.1.3.0.nupkg</b></p></summary>
<p>Coverlet is a cross platform code coverage library for .NET, with support for line, branch and metho...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg">https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg</a></p>
<p>Path to dependency file: /dotnet/SendHMACTest/SendHMACTest.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/coverlet.collector/1.3.0/coverlet.collector.1.3.0.nupkg</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/ncr-bsp-hmac/commit/8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf">8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (coverlet.collector.1.3.0.nupkg version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2022-0161](https://github.com/JamesNK/Newtonsoft.Json/commit/7e77bbe1beccceac4fc7b174b53abfefac278b66) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | coverlet.collector.1.3.0.nupkg | Direct | Newtonsoft.Json - 13.0.1;Microsoft.Extensions.ApiDescription.Server - 6.0.0 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2022-0161</summary>
### Vulnerable Library - <b>coverlet.collector.1.3.0.nupkg</b></p>
<p>Coverlet is a cross platform code coverage library for .NET, with support for line, branch and metho...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg">https://api.nuget.org/packages/coverlet.collector.1.3.0.nupkg</a></p>
<p>Path to dependency file: /dotnet/SendHMACTest/SendHMACTest.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/coverlet.collector/1.3.0/coverlet.collector.1.3.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **coverlet.collector.1.3.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/ncr-bsp-hmac/commit/8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf">8c38af4ddbd9a6bfa627695cfe2dbb9b9aa99acf</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper Handling of Exceptional Conditions in Newtonsoft.Json.
Newtonsoft.Json prior to version 13.0.1 is vulnerable to Insecure Defaults due to improper handling of StackOverFlow exception (SOE) whenever nested expressions are being processed. Exploiting this vulnerability results in Denial Of Service (DoS), and it is exploitable when an attacker sends 5 requests that cause SOE in time frame of 5 minutes. This vulnerability affects Internet Information Services (IIS) Applications.
<p>Publish Date: 2022-06-22
<p>URL: <a href=https://github.com/JamesNK/Newtonsoft.Json/commit/7e77bbe1beccceac4fc7b174b53abfefac278b66>WS-2022-0161</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-06-22</p>
<p>Fix Resolution: Newtonsoft.Json - 13.0.1;Microsoft.Extensions.ApiDescription.Server - 6.0.0</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_design | coverlet collector nupkg vulnerabilities highest severity is vulnerable library coverlet collector nupkg coverlet is a cross platform code coverage library for net with support for line branch and metho library home page a href path to dependency file dotnet sendhmactest sendhmactest csproj path to vulnerable library home wss scanner nuget packages coverlet collector coverlet collector nupkg found in head commit a href vulnerabilities cve severity cvss dependency type fixed in coverlet collector nupkg version remediation available high coverlet collector nupkg direct newtonsoft json microsoft extensions apidescription server details ws vulnerable library coverlet collector nupkg coverlet is a cross platform code coverage library for net with support for line branch and metho library home page a href path to dependency file dotnet sendhmactest sendhmactest csproj path to vulnerable library home wss scanner nuget packages coverlet collector coverlet collector nupkg dependency hierarchy x coverlet collector nupkg vulnerable library found in head commit a href found in base branch main vulnerability details improper handling of exceptional conditions in newtonsoft json newtonsoft json prior to version is vulnerable to insecure defaults due to improper handling of stackoverflow exception soe whenever nested expressions are being processed exploiting this vulnerability results in denial of service dos and it is exploitable when an attacker sends requests that cause soe in time frame of minutes this vulnerability affects internet information services iis applications 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 release date fix resolution newtonsoft json microsoft extensions apidescription server rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
168,399 | 26,642,994,619 | IssuesEvent | 2023-01-25 07:26:40 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | Hunter Genes description has incorrect melee damage numbers | Bug Design | ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [ ] My issue happened while using mods.
### What happened?
The description of the Hunter genes cites an increase of 20-100% to melee damage, however the actual value ranges from 75-150%.
### Reproduction steps
_No response_
### Bug prevalence
Just once
### Version
0.20.16.1
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | 1.0 | Hunter Genes description has incorrect melee damage numbers - ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [ ] My issue happened while using mods.
### What happened?
The description of the Hunter genes cites an increase of 20-100% to melee damage, however the actual value ranges from 75-150%.
### Reproduction steps
_No response_
### Bug prevalence
Just once
### Version
0.20.16.1
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | design | hunter genes description has incorrect melee damage numbers disclaimers i have searched the issue tracker to check if the issue has already been reported my issue happened while using mods what happened the description of the hunter genes cites an increase of to melee damage however the actual value ranges from reproduction steps no response bug prevalence just once version no response which operating system did you encounter this bug on windows relevant error messages and crash reports no response | 1 |
353,946 | 25,143,083,682 | IssuesEvent | 2022-11-10 01:28:14 | hackforla/311-data | https://api.github.com/repos/hackforla/311-data | closed | Locate Previous Beta Usability Testing | Feature: Documentation Size: 3pt role: UI/UX Research | ### Overview
We need to find the research from the Usability Beta Testing so that we can determine if we are missing any potentially key features like grouping NCs and creating comparison reports was a requested feature.
### Action Items
- [ ] Search project [Wiki](https://github.com/hackforla/311-data/wiki) and [Google Drive](https://drive.google.com/drive/folders/1ObUz4mTQmSCwND_WQcOXAuCeKpCwNzmz) for User Testing docs and research.
- [ ] Reorganize folders into relevant team sections
- [ ] Organize folders within team sections with the date in the title using consistent nomenclature
- [ ] Rename folders to express contents clearly
- [ ] Inventory files that will be useful for relevant teams and the project broadly
- [ ] Include links to research in the Resources section below
### Resources/Instructions
| 1.0 | Locate Previous Beta Usability Testing - ### Overview
We need to find the research from the Usability Beta Testing so that we can determine if we are missing any potentially key features like grouping NCs and creating comparison reports was a requested feature.
### Action Items
- [ ] Search project [Wiki](https://github.com/hackforla/311-data/wiki) and [Google Drive](https://drive.google.com/drive/folders/1ObUz4mTQmSCwND_WQcOXAuCeKpCwNzmz) for User Testing docs and research.
- [ ] Reorganize folders into relevant team sections
- [ ] Organize folders within team sections with the date in the title using consistent nomenclature
- [ ] Rename folders to express contents clearly
- [ ] Inventory files that will be useful for relevant teams and the project broadly
- [ ] Include links to research in the Resources section below
### Resources/Instructions
| non_design | locate previous beta usability testing overview we need to find the research from the usability beta testing so that we can determine if we are missing any potentially key features like grouping ncs and creating comparison reports was a requested feature action items search project and for user testing docs and research reorganize folders into relevant team sections organize folders within team sections with the date in the title using consistent nomenclature rename folders to express contents clearly inventory files that will be useful for relevant teams and the project broadly include links to research in the resources section below resources instructions | 0 |
41,125 | 5,309,107,572 | IssuesEvent | 2017-02-12 05:58:49 | njsmith/trio | https://api.github.com/repos/njsmith/trio | opened | Is our current strategy for handling instrument errors optimal? | design discussion | Right now, if an instrumentation callback raises an exception, we (a) print the traceback to stderr, (b) disable that instrument, (c) carry on.
This is the *only* place in trio that discards exceptions instead of handling or propagating them. Is this the right choice?
The motivation is that instrumentation gets called at all kinds of weird times where it's quite difficult to propagate an error, and it's not clear where to propagate to in any case, and while we in general prefer to crash early and noisily in general it's still probably true that no-one wants their instrumentation to take down their server (I think).
The downside is the obvious one: it's easy to miss stuff dumped to stderr, if some tool is trying to automatically collect instrumentation then it could get wedged in unexpected ways if the instrument just disappears, etc.
So, I'm not entirely sure this is the best approach, and would be interested to hear what others think. | 1.0 | Is our current strategy for handling instrument errors optimal? - Right now, if an instrumentation callback raises an exception, we (a) print the traceback to stderr, (b) disable that instrument, (c) carry on.
This is the *only* place in trio that discards exceptions instead of handling or propagating them. Is this the right choice?
The motivation is that instrumentation gets called at all kinds of weird times where it's quite difficult to propagate an error, and it's not clear where to propagate to in any case, and while we in general prefer to crash early and noisily in general it's still probably true that no-one wants their instrumentation to take down their server (I think).
The downside is the obvious one: it's easy to miss stuff dumped to stderr, if some tool is trying to automatically collect instrumentation then it could get wedged in unexpected ways if the instrument just disappears, etc.
So, I'm not entirely sure this is the best approach, and would be interested to hear what others think. | design | is our current strategy for handling instrument errors optimal right now if an instrumentation callback raises an exception we a print the traceback to stderr b disable that instrument c carry on this is the only place in trio that discards exceptions instead of handling or propagating them is this the right choice the motivation is that instrumentation gets called at all kinds of weird times where it s quite difficult to propagate an error and it s not clear where to propagate to in any case and while we in general prefer to crash early and noisily in general it s still probably true that no one wants their instrumentation to take down their server i think the downside is the obvious one it s easy to miss stuff dumped to stderr if some tool is trying to automatically collect instrumentation then it could get wedged in unexpected ways if the instrument just disappears etc so i m not entirely sure this is the best approach and would be interested to hear what others think | 1 |
74,382 | 9,036,670,696 | IssuesEvent | 2019-02-09 01:57:22 | AugurProject/augur | https://api.github.com/repos/AugurProject/augur | closed | Portfolio Pg Design | Design Feature Priority: High Product Critical | 1) Positions - Showing Market title with 24hr % change - this can be expanded open to show all individual outcome for that market - w/ value and 24% change on each outcome (risk assessment).
2) My Markets - list of all open Markets created by the user. (change to Markets Created Markets)
3) Reporting - User's markets they can report on. (will be its own separate pg)
4) Open Orders - will be preset by most recently traded first (will need ability to sort, search if user prefers to group by specific market).
5) Filled Orders - same sorting,searching needed as open orders
| 1.0 | Portfolio Pg Design - 1) Positions - Showing Market title with 24hr % change - this can be expanded open to show all individual outcome for that market - w/ value and 24% change on each outcome (risk assessment).
2) My Markets - list of all open Markets created by the user. (change to Markets Created Markets)
3) Reporting - User's markets they can report on. (will be its own separate pg)
4) Open Orders - will be preset by most recently traded first (will need ability to sort, search if user prefers to group by specific market).
5) Filled Orders - same sorting,searching needed as open orders
| design | portfolio pg design positions showing market title with change this can be expanded open to show all individual outcome for that market w value and change on each outcome risk assessment my markets list of all open markets created by the user change to markets created markets reporting user s markets they can report on will be its own separate pg open orders will be preset by most recently traded first will need ability to sort search if user prefers to group by specific market filled orders same sorting searching needed as open orders | 1 |
6,741 | 7,748,488,905 | IssuesEvent | 2018-05-30 08:29:48 | w3c/dxwg | https://api.github.com/repos/w3c/dxwg | closed | Add mechanism to allow general services to be included in a dcat:Catalog | dcat dcat:Catalog service | Per the resolution of #172 it is necessary to create classes and/or properties to allow a general service to be included in a `dcat:Catalog` | 1.0 | Add mechanism to allow general services to be included in a dcat:Catalog - Per the resolution of #172 it is necessary to create classes and/or properties to allow a general service to be included in a `dcat:Catalog` | non_design | add mechanism to allow general services to be included in a dcat catalog per the resolution of it is necessary to create classes and or properties to allow a general service to be included in a dcat catalog | 0 |
135,391 | 19,568,758,266 | IssuesEvent | 2022-01-04 06:51:15 | quantumlib/Cirq | https://api.github.com/repos/quantumlib/Cirq | closed | Should `cirq.Moment` store operations sorted by the underlying qubits? | triage/accepted area/circuits area/moments kind/design-issue | The iteration order of operations in a `cirq.Moment` currently depends upon the order in which the operations were inserted in the moment. This can lead to cases where two moments `m1 == m2` is True but their `repr`s and iteration order of underlying operations are not the same.
```
> q = cirq.LineQubit.range(2)
> ops = [cirq.X(q[0]), cirq.Y(q[1])]
> m1, m2 = cirq.Moment(ops), cirq.Moment(ops.reverse())
> assert m1 == m2
> for op1, op2 in zip(m1, m2):
...: print(op1 == op2) # Prints False
```
The proposal is to directly store and use `sorted(self.operations, key=lambda op: op.qubits)` as the list of underlying operations in a moment to avoid such inconsistencies and uniquely define the traversal order of operations in equal moments.
| 1.0 | Should `cirq.Moment` store operations sorted by the underlying qubits? - The iteration order of operations in a `cirq.Moment` currently depends upon the order in which the operations were inserted in the moment. This can lead to cases where two moments `m1 == m2` is True but their `repr`s and iteration order of underlying operations are not the same.
```
> q = cirq.LineQubit.range(2)
> ops = [cirq.X(q[0]), cirq.Y(q[1])]
> m1, m2 = cirq.Moment(ops), cirq.Moment(ops.reverse())
> assert m1 == m2
> for op1, op2 in zip(m1, m2):
...: print(op1 == op2) # Prints False
```
The proposal is to directly store and use `sorted(self.operations, key=lambda op: op.qubits)` as the list of underlying operations in a moment to avoid such inconsistencies and uniquely define the traversal order of operations in equal moments.
| design | should cirq moment store operations sorted by the underlying qubits the iteration order of operations in a cirq moment currently depends upon the order in which the operations were inserted in the moment this can lead to cases where two moments is true but their repr s and iteration order of underlying operations are not the same q cirq linequbit range ops cirq y q cirq moment ops cirq moment ops reverse assert for in zip print prints false the proposal is to directly store and use sorted self operations key lambda op op qubits as the list of underlying operations in a moment to avoid such inconsistencies and uniquely define the traversal order of operations in equal moments | 1 |
248,127 | 20,997,432,341 | IssuesEvent | 2022-03-29 14:33:42 | cobudget/cobudget | https://api.github.com/repos/cobudget/cobudget | closed | [DEV] Deploy to a staging environment | needs testing | - [x] Create staging database
- [x] Deploy a branch `staging` to `staging.cobudget.com` | 1.0 | [DEV] Deploy to a staging environment - - [x] Create staging database
- [x] Deploy a branch `staging` to `staging.cobudget.com` | non_design | deploy to a staging environment create staging database deploy a branch staging to staging cobudget com | 0 |
9,509 | 2,906,234,587 | IssuesEvent | 2015-06-19 08:40:19 | ramu2016/SXUMX357FFAWEJHBMNM54FBQ | https://api.github.com/repos/ramu2016/SXUMX357FFAWEJHBMNM54FBQ | closed | makVaeBtdwYd0Tbhd/qCuQRFK7QDsaw0ZvoXV0C7S00l+JOGL/xmRRElxehDhIH/9pSsOlUoyr6CdWixva3dNYs7tIe1pnHP1EHZ20QxGo5DHf0oEt3GhKphHIjtkmRqxRbdP6Ux1V5oQqlpHwjL5RDJEtUX5oxEUip5ra13heo= | design | 6833zypfacinqTzoxeoS0VRw+4Huv6G/mKlYHqSeBbZu+HNzFwSxDk1pw/z4LFlqMNPHhTmUVCrEcFvXnD/H0CE46aueE5GNeBTsrO3oTVRDx5hdMJKkTkoCLzKi/qX+swlE+6yNrV9ZI5moGFfoTNWkWdZ2dwRA2kvXb3XxqUc3kYWBRef0H6nwEtGRZ85cbF8h+6+qYJAlO9MzbejkZdgFPWL25j0UUHYp2sFivlzLFSMmYi+LZqN/eeOLyGtc73KVQ1pDvNVohcYnLC4n1CTQ03EecHUrJSErqBYEQncxK8B6Mh8b/EcFBDBsQLbP7puohorj/StkEPYFQYrkxgK16hZTA1RYJ0y+vsm3ufGkjCkSJTcYeBp8LsvuzROplZ+yhEtBry+mTKsUrJX0ZIvxsSjGzIElP2qkS5O85BbEzC06eal8cy0VVzn++sMD8NkF/nOeGU4v7YRB+/q9Sfoz6U4nFRaLw0SLnZSn6/iIyWbWN511IyyGHgAg/nAi38BeRC5mf2ZsE6zb0THsNwR0XuXB7coXs9f0d2FsoY4FDHhwMydZdcaF9R/wq7Uoeq2Jg03GORJD6Afz7Ij4hw== | 1.0 | makVaeBtdwYd0Tbhd/qCuQRFK7QDsaw0ZvoXV0C7S00l+JOGL/xmRRElxehDhIH/9pSsOlUoyr6CdWixva3dNYs7tIe1pnHP1EHZ20QxGo5DHf0oEt3GhKphHIjtkmRqxRbdP6Ux1V5oQqlpHwjL5RDJEtUX5oxEUip5ra13heo= - 6833zypfacinqTzoxeoS0VRw+4Huv6G/mKlYHqSeBbZu+HNzFwSxDk1pw/z4LFlqMNPHhTmUVCrEcFvXnD/H0CE46aueE5GNeBTsrO3oTVRDx5hdMJKkTkoCLzKi/qX+swlE+6yNrV9ZI5moGFfoTNWkWdZ2dwRA2kvXb3XxqUc3kYWBRef0H6nwEtGRZ85cbF8h+6+qYJAlO9MzbejkZdgFPWL25j0UUHYp2sFivlzLFSMmYi+LZqN/eeOLyGtc73KVQ1pDvNVohcYnLC4n1CTQ03EecHUrJSErqBYEQncxK8B6Mh8b/EcFBDBsQLbP7puohorj/StkEPYFQYrkxgK16hZTA1RYJ0y+vsm3ufGkjCkSJTcYeBp8LsvuzROplZ+yhEtBry+mTKsUrJX0ZIvxsSjGzIElP2qkS5O85BbEzC06eal8cy0VVzn++sMD8NkF/nOeGU4v7YRB+/q9Sfoz6U4nFRaLw0SLnZSn6/iIyWbWN511IyyGHgAg/nAi38BeRC5mf2ZsE6zb0THsNwR0XuXB7coXs9f0d2FsoY4FDHhwMydZdcaF9R/wq7Uoeq2Jg03GORJD6Afz7Ij4hw== | design | jogl xmrrelxehdhih mklyhqsebbzu qx swle lzqn yhetbry | 1 |
66,795 | 8,970,207,276 | IssuesEvent | 2019-01-29 13:02:23 | Samsung/Universum | https://api.github.com/repos/Samsung/Universum | closed | Add instructions for setting up builds in TeamCity using CI system | component: teamcity documentation | Originally created on Mon, 31 Jul 2017 16:49:55 +0900
Describe how to create a new configuration, add a meta-runner and set up project and configuration environment variables | 1.0 | Add instructions for setting up builds in TeamCity using CI system - Originally created on Mon, 31 Jul 2017 16:49:55 +0900
Describe how to create a new configuration, add a meta-runner and set up project and configuration environment variables | non_design | add instructions for setting up builds in teamcity using ci system originally created on mon jul describe how to create a new configuration add a meta runner and set up project and configuration environment variables | 0 |
152,968 | 24,047,241,356 | IssuesEvent | 2022-09-16 09:25:57 | WinterWind33/fish-and-plants | https://api.github.com/repos/WinterWind33/fish-and-plants | opened | [A.4] Add feature toogles and feature toogles groups support | Type: Enhancement Topology: Platform Type: Analysis and Design | ## Description
As many of the software features are experimental we want to enable or disable at runtime these features in order to not broke the hardware in case something goes wrong.
Analyze a way of implementing these feature toggles. | 1.0 | [A.4] Add feature toogles and feature toogles groups support - ## Description
As many of the software features are experimental we want to enable or disable at runtime these features in order to not broke the hardware in case something goes wrong.
Analyze a way of implementing these feature toggles. | design | add feature toogles and feature toogles groups support description as many of the software features are experimental we want to enable or disable at runtime these features in order to not broke the hardware in case something goes wrong analyze a way of implementing these feature toggles | 1 |
126,450 | 26,858,251,677 | IssuesEvent | 2023-02-03 16:12:33 | eclipse/che | https://api.github.com/repos/eclipse/che | closed | Adapt Che-Code to the latest VS Code upstream changes | kind/task severity/P1 area/editor/vscode | ### Is your task related to a problem? Please describe
There're [changes in VS Code upstream](https://github.com/microsoft/vscode/pull/172754) that conflicts with Che-Code build:
```
#13 358.3 [12:56:12] Error: /checode-compilation/src/vs/workbench/contrib/remote/browser/che/remote.ts(114,35): Property 'show' does not exist on type 'IDialogService'.
#13 358.3 [12:56:12] Error: /checode-compilation/src/vs/workbench/contrib/remote/browser/che/remote.ts(164,33): Property 'show' does not exist on type 'IDialogService'.
```
For more details, see the output of [the auto-rebase job](https://github.com/che-incubator/che-code/actions/runs/4078359010/jobs/7028473498).
### Describe the solution you'd like
Adaptat Che-Code to the upstream changes.
https://github.com/che-incubator/che-code#fixing-the-rebase-insiders-workflow
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | 1.0 | Adapt Che-Code to the latest VS Code upstream changes - ### Is your task related to a problem? Please describe
There're [changes in VS Code upstream](https://github.com/microsoft/vscode/pull/172754) that conflicts with Che-Code build:
```
#13 358.3 [12:56:12] Error: /checode-compilation/src/vs/workbench/contrib/remote/browser/che/remote.ts(114,35): Property 'show' does not exist on type 'IDialogService'.
#13 358.3 [12:56:12] Error: /checode-compilation/src/vs/workbench/contrib/remote/browser/che/remote.ts(164,33): Property 'show' does not exist on type 'IDialogService'.
```
For more details, see the output of [the auto-rebase job](https://github.com/che-incubator/che-code/actions/runs/4078359010/jobs/7028473498).
### Describe the solution you'd like
Adaptat Che-Code to the upstream changes.
https://github.com/che-incubator/che-code#fixing-the-rebase-insiders-workflow
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | non_design | adapt che code to the latest vs code upstream changes is your task related to a problem please describe there re that conflicts with che code build error checode compilation src vs workbench contrib remote browser che remote ts property show does not exist on type idialogservice error checode compilation src vs workbench contrib remote browser che remote ts property show does not exist on type idialogservice for more details see the output of describe the solution you d like adaptat che code to the upstream changes describe alternatives you ve considered no response additional context no response | 0 |
176,909 | 28,292,782,901 | IssuesEvent | 2023-04-09 12:27:38 | bounswe/bounswe2023group7 | https://api.github.com/repos/bounswe/bounswe2023group7 | closed | Scenario - Group | type : design priority : urgent status : need_review effort : moderate | ### Issue Description
As we talked in group meeting, scenarios is needed to prepare. I will create scenario for "group".
### Tasks
_No Response_
### Extra Comments
_No Response_
### Final Step
_No Response_
### Deadline of the Issue
10.04.2023 - Monday - 14:00
### Reviewer
@SouthAscend
### Deadline for the Review
10.04.2023 - Monday - 21:00 | 1.0 | Scenario - Group - ### Issue Description
As we talked in group meeting, scenarios is needed to prepare. I will create scenario for "group".
### Tasks
_No Response_
### Extra Comments
_No Response_
### Final Step
_No Response_
### Deadline of the Issue
10.04.2023 - Monday - 14:00
### Reviewer
@SouthAscend
### Deadline for the Review
10.04.2023 - Monday - 21:00 | design | scenario group issue description as we talked in group meeting scenarios is needed to prepare i will create scenario for group tasks no response extra comments no response final step no response deadline of the issue monday reviewer southascend deadline for the review monday | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.