Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 5
112
| repo_url
stringlengths 34
141
| action
stringclasses 3
values | title
stringlengths 1
757
| labels
stringlengths 4
664
| body
stringlengths 3
261k
| index
stringclasses 10
values | text_combine
stringlengths 96
261k
| label
stringclasses 2
values | text
stringlengths 96
232k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
35,237
| 7,669,097,400
|
IssuesEvent
|
2018-05-14 08:34:35
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
closed
|
Deadlock when loading DataType classes
|
C: Functionality P: Medium T: Defect
|
We're seeing a deadlock when two different threads load different DataType classes at the same time. It looks like loading one DataType class causes the others to be loaded as well during class initialization. But, this can cause a deadlock when multiple threads are trying to load these DataType classes because they each hold a lock on the class and end up waiting for the others to finish.
The following code reproduces the deadlock for me:
``` java
import java.io.*;
import java.net.*;
class jooqlock {
public static void main(String[] args) throws Exception {
for (int i = 0; i < 1; i++) {
doit();
}
}
private static void doit() throws Exception {
final ClassLoader loader = new URLClassLoader(new URL[] { new File("jooq-3.4.4.jar").toURI().toURL() });
Runnable oload = new Runnable() {
public void run() {
try {
Class.forName("org.jooq.util.sqlite.SQLiteDataType", true, loader);
} catch (Throwable th) {
th.printStackTrace();
}
}
};
Runnable sload = new Runnable() {
public void run() {
try {
Class.forName("org.jooq.util.postgres.PostgresDataType", true, loader);
} catch (Throwable th) {
th.printStackTrace();
}
}
};
Thread th1 = new Thread(oload);
Thread th2 = new Thread(sload);
th1.start();
th2.start();
th1.join();
th2.join();
}
}
```
Here is a stack dump from after the deadlock happens:
```
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode):
"Thread-1" prio=5 tid=0x00007fd119841800 nid=0x5303 in Object.wait() [0x000000011b619000]
java.lang.Thread.State: RUNNABLE
at org.jooq.util.postgres.PostgresDataType.<clinit>(PostgresDataType.java:76)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at jooqlock$2.run(jooqlock.java:27)
at java.lang.Thread.run(Thread.java:745)
"Thread-0" prio=5 tid=0x00007fd119841000 nid=0x5103 in Object.wait() [0x000000011b515000]
java.lang.Thread.State: RUNNABLE
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at org.jooq.impl.SQLDataType.<clinit>(SQLDataType.java:341)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at org.jooq.impl.DefaultDataType.<clinit>(DefaultDataType.java:219)
at org.jooq.util.sqlite.SQLiteDataType.<clinit>(SQLiteDataType.java:71)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at jooqlock$1.run(jooqlock.java:18)
at java.lang.Thread.run(Thread.java:745)
```
|
1.0
|
Deadlock when loading DataType classes - We're seeing a deadlock when two different threads load different DataType classes at the same time. It looks like loading one DataType class causes the others to be loaded as well during class initialization. But, this can cause a deadlock when multiple threads are trying to load these DataType classes because they each hold a lock on the class and end up waiting for the others to finish.
The following code reproduces the deadlock for me:
``` java
import java.io.*;
import java.net.*;
class jooqlock {
public static void main(String[] args) throws Exception {
for (int i = 0; i < 1; i++) {
doit();
}
}
private static void doit() throws Exception {
final ClassLoader loader = new URLClassLoader(new URL[] { new File("jooq-3.4.4.jar").toURI().toURL() });
Runnable oload = new Runnable() {
public void run() {
try {
Class.forName("org.jooq.util.sqlite.SQLiteDataType", true, loader);
} catch (Throwable th) {
th.printStackTrace();
}
}
};
Runnable sload = new Runnable() {
public void run() {
try {
Class.forName("org.jooq.util.postgres.PostgresDataType", true, loader);
} catch (Throwable th) {
th.printStackTrace();
}
}
};
Thread th1 = new Thread(oload);
Thread th2 = new Thread(sload);
th1.start();
th2.start();
th1.join();
th2.join();
}
}
```
Here is a stack dump from after the deadlock happens:
```
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode):
"Thread-1" prio=5 tid=0x00007fd119841800 nid=0x5303 in Object.wait() [0x000000011b619000]
java.lang.Thread.State: RUNNABLE
at org.jooq.util.postgres.PostgresDataType.<clinit>(PostgresDataType.java:76)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at jooqlock$2.run(jooqlock.java:27)
at java.lang.Thread.run(Thread.java:745)
"Thread-0" prio=5 tid=0x00007fd119841000 nid=0x5103 in Object.wait() [0x000000011b515000]
java.lang.Thread.State: RUNNABLE
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at org.jooq.impl.SQLDataType.<clinit>(SQLDataType.java:341)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at org.jooq.impl.DefaultDataType.<clinit>(DefaultDataType.java:219)
at org.jooq.util.sqlite.SQLiteDataType.<clinit>(SQLiteDataType.java:71)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at jooqlock$1.run(jooqlock.java:18)
at java.lang.Thread.run(Thread.java:745)
```
|
defect
|
deadlock when loading datatype classes we re seeing a deadlock when two different threads load different datatype classes at the same time it looks like loading one datatype class causes the others to be loaded as well during class initialization but this can cause a deadlock when multiple threads are trying to load these datatype classes because they each hold a lock on the class and end up waiting for the others to finish the following code reproduces the deadlock for me java import java io import java net class jooqlock public static void main string args throws exception for int i i i doit private static void doit throws exception final classloader loader new urlclassloader new url new file jooq jar touri tourl runnable oload new runnable public void run try class forname org jooq util sqlite sqlitedatatype true loader catch throwable th th printstacktrace runnable sload new runnable public void run try class forname org jooq util postgres postgresdatatype true loader catch throwable th th printstacktrace thread new thread oload thread new thread sload start start join join here is a stack dump from after the deadlock happens full thread dump java hotspot tm bit server vm mixed mode thread prio tid nid in object wait java lang thread state runnable at org jooq util postgres postgresdatatype postgresdatatype java at java lang class native method at java lang class forname class java at jooqlock run jooqlock java at java lang thread run thread java thread prio tid nid in object wait java lang thread state runnable at java lang class native method at java lang class forname class java at org jooq impl sqldatatype sqldatatype java at java lang class native method at java lang class forname class java at org jooq impl defaultdatatype defaultdatatype java at org jooq util sqlite sqlitedatatype sqlitedatatype java at java lang class native method at java lang class forname class java at jooqlock run jooqlock java at java lang thread run thread java
| 1
|
24,624
| 4,048,943,738
|
IssuesEvent
|
2016-05-23 12:27:39
|
obophenotype/developmental-stage-ontologies
|
https://api.github.com/repos/obophenotype/developmental-stage-ontologies
|
closed
|
ZFA:0007000 CAUTION wrong ID in version 25:09:2014
|
auto-migrated Priority-Medium Type-Defect
|
```
http://developmental-stage-ontologies.googlecode.com/svn/trunk/src/zfs/zfs.obo
format-version: 1.2
date: 25:09:2014 14:17
saved-by: yvonne
[Term]
id: ZFA:0007000
name: hatching
....and
[Term]
id: ZFA:0007000
name: macula saccule
```
Original issue reported on code.google.com by `niknej...@gmail.com` on 5 Nov 2014 at 8:49
|
1.0
|
ZFA:0007000 CAUTION wrong ID in version 25:09:2014 - ```
http://developmental-stage-ontologies.googlecode.com/svn/trunk/src/zfs/zfs.obo
format-version: 1.2
date: 25:09:2014 14:17
saved-by: yvonne
[Term]
id: ZFA:0007000
name: hatching
....and
[Term]
id: ZFA:0007000
name: macula saccule
```
Original issue reported on code.google.com by `niknej...@gmail.com` on 5 Nov 2014 at 8:49
|
defect
|
zfa caution wrong id in version format version date saved by yvonne id zfa name hatching and id zfa name macula saccule original issue reported on code google com by niknej gmail com on nov at
| 1
|
28,984
| 5,468,913,539
|
IssuesEvent
|
2017-03-10 08:14:33
|
gbif/ipt
|
https://api.github.com/repos/gbif/ipt
|
closed
|
A registered resource is shown as no Not registered in the Home Table (IPT 2.3.3)
|
bug Type-Defect
|
I cloned and installed the version 2.3.3 (git clone from master, and after that checkout tag 2.3.3). In this version, some resources are shown as no registered in the Home table, column Organisation, despite already have been registered, whit a link to the dataset in GBIF.
For example, in the SiB Colombia's IPT, the resource http://ipt.biodiversidad.co/sib/resource?r=cnidaria in the table is shown as No registered.
But, this resource has been registered, as is possible confirm in GBIF
http://www.gbif.org/dataset/de10d7a1-a4f7-4aa8-aa1d-72364cecc263
I downloaded the datadir to compare as the resource is shown in the IPT version 2.3.2 and IPT version 2.3.3. In the Home table for the 2.3.2, the organization is shown, but in the 2.3.3, the text "No registered" is shown.
In 2.3.2
In 2.3.3
Looking in the code, in pages/macros/resourcesTable.ftl, a validation of the state of the resource is made
In the resource's xml, the state is REGISTERED
I think, that the problem is the way the resources are reconstructed, in \ipt\src\main\java\org\gbif\ipt\action\portal\HomeAction.java
The reconstruction is made using the version published, for the mentioned case versionHistory has a status PUBLIC
|
1.0
|
A registered resource is shown as no Not registered in the Home Table (IPT 2.3.3) - I cloned and installed the version 2.3.3 (git clone from master, and after that checkout tag 2.3.3). In this version, some resources are shown as no registered in the Home table, column Organisation, despite already have been registered, whit a link to the dataset in GBIF.
For example, in the SiB Colombia's IPT, the resource http://ipt.biodiversidad.co/sib/resource?r=cnidaria in the table is shown as No registered.
But, this resource has been registered, as is possible confirm in GBIF
http://www.gbif.org/dataset/de10d7a1-a4f7-4aa8-aa1d-72364cecc263
I downloaded the datadir to compare as the resource is shown in the IPT version 2.3.2 and IPT version 2.3.3. In the Home table for the 2.3.2, the organization is shown, but in the 2.3.3, the text "No registered" is shown.
In 2.3.2
In 2.3.3
Looking in the code, in pages/macros/resourcesTable.ftl, a validation of the state of the resource is made
In the resource's xml, the state is REGISTERED
I think, that the problem is the way the resources are reconstructed, in \ipt\src\main\java\org\gbif\ipt\action\portal\HomeAction.java
The reconstruction is made using the version published, for the mentioned case versionHistory has a status PUBLIC
|
defect
|
a registered resource is shown as no not registered in the home table ipt i cloned and installed the version git clone from master and after that checkout tag in this version some resources are shown as no registered in the home table column organisation despite already have been registered whit a link to the dataset in gbif for example in the sib colombia s ipt the resource in the table is shown as no registered but this resource has been registered as is possible confirm in gbif i downloaded the datadir to compare as the resource is shown in the ipt version and ipt version in the home table for the the organization is shown but in the the text no registered is shown in in looking in the code in pages macros resourcestable ftl a validation of the state of the resource is made in the resource s xml the state is registered i think that the problem is the way the resources are reconstructed in ipt src main java org gbif ipt action portal homeaction java the reconstruction is made using the version published for the mentioned case versionhistory has a status public
| 1
|
69,701
| 22,618,436,123
|
IssuesEvent
|
2022-06-30 02:18:13
|
zed-industries/feedback
|
https://api.github.com/repos/zed-industries/feedback
|
opened
|
Single quotes shouldn't auto-close inside comment blocks
|
defect triage
|
**Before you begin**
Check the backlog of issues to reduce the chances of creating duplicates; if an issue already exists, place a `+1` (👍) on it.
**Describe the bug**
A clear and concise description of what the bug is.
**To reproduce**
Steps to reproduce the behavior:
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Environment:**
Copy & paste output of this command:
```sh
Zed 0.42.0 – /Applications/Zed.app \nmacOS 12.4 \narchitecture arm64
```
When typing comments in JavaScript or TypeScript files, the single quotes auto-complete the closing quote. It doesn't appear to do this in other languages. I also tried this in Python, Rust, and Go files and they all seem to work as expected. In JS or TS, however, typing a single-quote in a comment block inserts a closing quote. This is particularly annoying when typing words with contractions like `don't`. I think this behavior is probably correct for double quotes - those insert a second quote in all languages and that seems expected.
|
1.0
|
Single quotes shouldn't auto-close inside comment blocks - **Before you begin**
Check the backlog of issues to reduce the chances of creating duplicates; if an issue already exists, place a `+1` (👍) on it.
**Describe the bug**
A clear and concise description of what the bug is.
**To reproduce**
Steps to reproduce the behavior:
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Environment:**
Copy & paste output of this command:
```sh
Zed 0.42.0 – /Applications/Zed.app \nmacOS 12.4 \narchitecture arm64
```
When typing comments in JavaScript or TypeScript files, the single quotes auto-complete the closing quote. It doesn't appear to do this in other languages. I also tried this in Python, Rust, and Go files and they all seem to work as expected. In JS or TS, however, typing a single-quote in a comment block inserts a closing quote. This is particularly annoying when typing words with contractions like `don't`. I think this behavior is probably correct for double quotes - those insert a second quote in all languages and that seems expected.
|
defect
|
single quotes shouldn t auto close inside comment blocks before you begin check the backlog of issues to reduce the chances of creating duplicates if an issue already exists place a 👍 on it describe the bug a clear and concise description of what the bug is to reproduce steps to reproduce the behavior expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem environment copy paste output of this command sh zed – applications zed app nmacos narchitecture when typing comments in javascript or typescript files the single quotes auto complete the closing quote it doesn t appear to do this in other languages i also tried this in python rust and go files and they all seem to work as expected in js or ts however typing a single quote in a comment block inserts a closing quote this is particularly annoying when typing words with contractions like don t i think this behavior is probably correct for double quotes those insert a second quote in all languages and that seems expected
| 1
|
65,135
| 19,179,402,117
|
IssuesEvent
|
2021-12-04 05:19:55
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
opened
|
Generated jooq sources tables names are uppercase and in my docker container migration is lowercase
|
T: Defect
|
### Expected behavior
Generate jooq sources tables use same name for tables as liquibase migration generates
### Actual behavior
Generated jooq tables names in uppercase causing errors when performing queries or inserts,updates because of mismatch of table name. Message: "table doesn't exist"
### Steps to reproduce the problem
- If the problem relates to code generation, please post your code generation configuration
- If the problem relates to upgrades, please check if your RDBMS version is still supported by jOOQ: https://www.jooq.org/download/support-matrix
- A complete set of DDL statements can help re-create the setup you're having
- An MCVE can be helpful to provide a complete reproduction case: https://github.com/jOOQ/jOOQ-mcve
### Versions
- jOOQ:
- Java:
- Database (include vendor):
- OS:
- JDBC Driver (include name if inofficial driver):
|
1.0
|
Generated jooq sources tables names are uppercase and in my docker container migration is lowercase - ### Expected behavior
Generate jooq sources tables use same name for tables as liquibase migration generates
### Actual behavior
Generated jooq tables names in uppercase causing errors when performing queries or inserts,updates because of mismatch of table name. Message: "table doesn't exist"
### Steps to reproduce the problem
- If the problem relates to code generation, please post your code generation configuration
- If the problem relates to upgrades, please check if your RDBMS version is still supported by jOOQ: https://www.jooq.org/download/support-matrix
- A complete set of DDL statements can help re-create the setup you're having
- An MCVE can be helpful to provide a complete reproduction case: https://github.com/jOOQ/jOOQ-mcve
### Versions
- jOOQ:
- Java:
- Database (include vendor):
- OS:
- JDBC Driver (include name if inofficial driver):
|
defect
|
generated jooq sources tables names are uppercase and in my docker container migration is lowercase expected behavior generate jooq sources tables use same name for tables as liquibase migration generates actual behavior generated jooq tables names in uppercase causing errors when performing queries or inserts updates because of mismatch of table name message table doesn t exist steps to reproduce the problem if the problem relates to code generation please post your code generation configuration if the problem relates to upgrades please check if your rdbms version is still supported by jooq a complete set of ddl statements can help re create the setup you re having an mcve can be helpful to provide a complete reproduction case versions jooq java database include vendor os jdbc driver include name if inofficial driver
| 1
|
250,057
| 21,259,228,980
|
IssuesEvent
|
2022-04-13 00:59:44
|
RamiMustafa/WAF_Sec_Test
|
https://api.github.com/repos/RamiMustafa/WAF_Sec_Test
|
opened
|
Define security requirements for the workload
|
WARP-Import WAF_Sec_Test Security Application Design Threat Analysis
|
<a href="https://docs.microsoft.com/azure/governance/policy/concepts/azure-security-benchmark-baseline">Define security requirements for the workload</a>
<p><b>Why Consider This?</b></p>
Azure resources should be blocked if they do not meet the proper security requirements defined during service enablement, e.g., organizational security baseline.
<p><b>Context</b></p>
<p><b>Suggested Actions</b></p>
<p><span>Define security requirements for the workload.</span></p>
<p><b>Learn More</b></p>
<p><a href="https://docs.microsoft.com/en-us/azure/governance/policy/concepts/azure-security-benchmark-baseline" target="_blank"><span>https://docs.microsoft.com/en-us/azure/governance/policy/concepts/azure-security-benchmark-baseline</span></a><span /></p>
|
1.0
|
Define security requirements for the workload - <a href="https://docs.microsoft.com/azure/governance/policy/concepts/azure-security-benchmark-baseline">Define security requirements for the workload</a>
<p><b>Why Consider This?</b></p>
Azure resources should be blocked if they do not meet the proper security requirements defined during service enablement, e.g., organizational security baseline.
<p><b>Context</b></p>
<p><b>Suggested Actions</b></p>
<p><span>Define security requirements for the workload.</span></p>
<p><b>Learn More</b></p>
<p><a href="https://docs.microsoft.com/en-us/azure/governance/policy/concepts/azure-security-benchmark-baseline" target="_blank"><span>https://docs.microsoft.com/en-us/azure/governance/policy/concepts/azure-security-benchmark-baseline</span></a><span /></p>
|
non_defect
|
define security requirements for the workload why consider this azure resources should be blocked if they do not meet the proper security requirements defined during service enablement e g organizational security baseline context suggested actions define security requirements for the workload learn more
| 0
|
41,889
| 10,695,040,031
|
IssuesEvent
|
2019-10-23 12:13:40
|
mozilla-lockwise/lockwise-android
|
https://api.github.com/repos/mozilla-lockwise/lockwise-android
|
opened
|
Lockwise is stuck at launch under some specific steps(not major)
|
type: defect
|
## Steps to reproduce
1. Launch Lockwise.
2. Login with valid credentials.
3. Do anything on the app(Lockwise is working correctly)
4. Tap on the `Disconnect` button.
5. After Welcome Screen redirection where the `Get Started` button is displayed.
6. Tap on `Get Started` and input valid credentials in order to login.
7. The Welcome Screen is displayed again(wich is intended).
8. The login page is displayed again.
9. Login with valid credentials, tap on skip now.
10. On the `You're all set!` page wait and don't tap on anything.(in this case Finish) button.
11. Restart Lockwise.
### Expected behavior
When launching Lockwise again everything works as expected and lockwise is not stuck on login.
### Actual behavior
A white screen with the Lockwise logo is displayed when trying to launch the app after `step 9`.
### Device & build information
* Device: **`Google Pixel 3a XL(Android 9), Samsung Galaxy S10+(Android 9)`**
* Build version: **`3.0.1 (Build 5124)`**
### Notes
**Please note that I'm not really sure if this is a regression or not.
Also, note that this issue is not really a normal user behavior and I cannot reproduce it all the time.**
Here you can find the full log with all the actions I did. [fullog.txt](https://github.com/mozilla-lockwise/lockwise-android/files/3762271/fullog.txt)
|
1.0
|
Lockwise is stuck at launch under some specific steps(not major) - ## Steps to reproduce
1. Launch Lockwise.
2. Login with valid credentials.
3. Do anything on the app(Lockwise is working correctly)
4. Tap on the `Disconnect` button.
5. After Welcome Screen redirection where the `Get Started` button is displayed.
6. Tap on `Get Started` and input valid credentials in order to login.
7. The Welcome Screen is displayed again(wich is intended).
8. The login page is displayed again.
9. Login with valid credentials, tap on skip now.
10. On the `You're all set!` page wait and don't tap on anything.(in this case Finish) button.
11. Restart Lockwise.
### Expected behavior
When launching Lockwise again everything works as expected and lockwise is not stuck on login.
### Actual behavior
A white screen with the Lockwise logo is displayed when trying to launch the app after `step 9`.
### Device & build information
* Device: **`Google Pixel 3a XL(Android 9), Samsung Galaxy S10+(Android 9)`**
* Build version: **`3.0.1 (Build 5124)`**
### Notes
**Please note that I'm not really sure if this is a regression or not.
Also, note that this issue is not really a normal user behavior and I cannot reproduce it all the time.**
Here you can find the full log with all the actions I did. [fullog.txt](https://github.com/mozilla-lockwise/lockwise-android/files/3762271/fullog.txt)
|
defect
|
lockwise is stuck at launch under some specific steps not major steps to reproduce launch lockwise login with valid credentials do anything on the app lockwise is working correctly tap on the disconnect button after welcome screen redirection where the get started button is displayed tap on get started and input valid credentials in order to login the welcome screen is displayed again wich is intended the login page is displayed again login with valid credentials tap on skip now on the you re all set page wait and don t tap on anything in this case finish button restart lockwise expected behavior when launching lockwise again everything works as expected and lockwise is not stuck on login actual behavior a white screen with the lockwise logo is displayed when trying to launch the app after step device build information device google pixel xl android samsung galaxy android build version build notes please note that i m not really sure if this is a regression or not also note that this issue is not really a normal user behavior and i cannot reproduce it all the time here you can find the full log with all the actions i did
| 1
|
55,306
| 14,361,609,771
|
IssuesEvent
|
2020-11-30 18:31:23
|
dkfans/keeperfx
|
https://api.github.com/repos/dkfans/keeperfx
|
opened
|
Melee attacks never miss
|
Priority-High Type-Defect
|
Reported on discord, confirmed by another user:
Melee attacks always hit. They should occasionally miss based on unit stats and randomness.
To me this indicates there's either a problem with Dexterity or Defense stat.
|
1.0
|
Melee attacks never miss - Reported on discord, confirmed by another user:
Melee attacks always hit. They should occasionally miss based on unit stats and randomness.
To me this indicates there's either a problem with Dexterity or Defense stat.
|
defect
|
melee attacks never miss reported on discord confirmed by another user melee attacks always hit they should occasionally miss based on unit stats and randomness to me this indicates there s either a problem with dexterity or defense stat
| 1
|
45,885
| 13,055,816,114
|
IssuesEvent
|
2020-07-30 02:49:21
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
opened
|
I3DbDetectorStatusService::GetOMKey(const string& serial) causes segfault (Trac #201)
|
Incomplete Migration Migrated from Trac defect jeb + pnf
|
Migrated from https://code.icecube.wisc.edu/ticket/201
```json
{
"status": "closed",
"changetime": "2014-11-23T03:37:57",
"description": "I3DbDetectorStatusService::GetOMKey(const string& serial) does this (line 1138):\n\nI3OMKey2MBID& omkey2mbid = GetService<I3OMKey2MBID>() ; key = omkey2mbid.GetOMKey(mbid);\n\nThe call to GetService calls I3Module::GetService which does:\n\nconst I3Context& context = GetActiveContext(); // in I3Tray\nreturn context.template Get<T>(where);\n\nThis crashes because GetActiveContext returns 0. This is caused by the ifndef I3_JEB in line 109 of I3Module.cxx. ",
"reporter": "rfranke",
"cc": "",
"resolution": "fixed",
"_ts": "1416713877066511",
"component": "jeb + pnf",
"summary": "I3DbDetectorStatusService::GetOMKey(const string& serial) causes segfault",
"priority": "normal",
"keywords": "",
"time": "2010-03-30T15:02:48",
"milestone": "",
"owner": "tschmidt",
"type": "defect"
}
```
|
1.0
|
I3DbDetectorStatusService::GetOMKey(const string& serial) causes segfault (Trac #201) - Migrated from https://code.icecube.wisc.edu/ticket/201
```json
{
"status": "closed",
"changetime": "2014-11-23T03:37:57",
"description": "I3DbDetectorStatusService::GetOMKey(const string& serial) does this (line 1138):\n\nI3OMKey2MBID& omkey2mbid = GetService<I3OMKey2MBID>() ; key = omkey2mbid.GetOMKey(mbid);\n\nThe call to GetService calls I3Module::GetService which does:\n\nconst I3Context& context = GetActiveContext(); // in I3Tray\nreturn context.template Get<T>(where);\n\nThis crashes because GetActiveContext returns 0. This is caused by the ifndef I3_JEB in line 109 of I3Module.cxx. ",
"reporter": "rfranke",
"cc": "",
"resolution": "fixed",
"_ts": "1416713877066511",
"component": "jeb + pnf",
"summary": "I3DbDetectorStatusService::GetOMKey(const string& serial) causes segfault",
"priority": "normal",
"keywords": "",
"time": "2010-03-30T15:02:48",
"milestone": "",
"owner": "tschmidt",
"type": "defect"
}
```
|
defect
|
getomkey const string serial causes segfault trac migrated from json status closed changetime description getomkey const string serial does this line n getservice key getomkey mbid n nthe call to getservice calls getservice which does n nconst context getactivecontext in nreturn context template get where n nthis crashes because getactivecontext returns this is caused by the ifndef jeb in line of cxx reporter rfranke cc resolution fixed ts component jeb pnf summary getomkey const string serial causes segfault priority normal keywords time milestone owner tschmidt type defect
| 1
|
134,500
| 10,917,949,741
|
IssuesEvent
|
2019-11-21 16:01:34
|
phetsims/circuit-construction-kit-common
|
https://api.github.com/repos/phetsims/circuit-construction-kit-common
|
opened
|
CT various for different sims
|
type:automated-testing
|
```
circuit-construction-kit-ac : phet-io-fuzz : require.js : run
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: There should always be an entry in the baseline for each phetioID
Error: Assertion failed: There should always be an entry in the baseline for each phetioID
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574322196919:22:13)
at PhetioAPIValidation.onPhetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/phetioAPIValidation.js?bust=1574322197011:196:19)
at PhetioEngine.phetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574322197011:362:27)
at Object.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574322197011:516:51)
at Tandem.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/Tandem.js?bust=1574322197011:147:40)
at BooleanProperty.initializePhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574322197011:331:19)
at new PhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574322197011:144:12)
at new Property (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574322197011:69:7)
at new BooleanProperty (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/BooleanProperty.js?bust=1574322197011:48:7)
at PushButtonModel.ButtonModel [as constructor] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/sun/js/buttons/ButtonModel.js?bust=1574322197011:74:28)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-fuzz : require.js : run
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: There should always be an entry in the baseline for each phetioID
Error: Assertion failed: There should always be an entry in the baseline for each phetioID
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574336955137:22:13)
at PhetioAPIValidation.onPhetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/phetioAPIValidation.js?bust=1574336955218:196:19)
at PhetioEngine.phetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574336955218:362:27)
at Object.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574336955218:516:51)
at Tandem.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/Tandem.js?bust=1574336955218:147:40)
at BooleanProperty.initializePhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574336955218:331:19)
at new PhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574336955218:144:12)
at new Property (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336955218:69:7)
at new BooleanProperty (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/BooleanProperty.js?bust=1574336955218:48:7)
at PushButtonModel.ButtonModel [as constructor] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/sun/js/buttons/ButtonModel.js?bust=1574336955218:74:28)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-fuzz : require.js : run
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: reentry detected, value=null, oldValue=[object Object]
Error: Assertion failed: reentry detected, value=null, oldValue=[object Object]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574336955137:22:13)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336955218:272:17)
at Property.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336955218:176:16)
at CCKCLightBulbNode.selectCircuitElementNodeWhenNear (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitElementNode.js?bust=1574336955218:261:65)
at CCKCLightBulbNode.endDrag (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitElementNode.js?bust=1574336955218:207:25)
at end (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/FixedCircuitElementNode.js?bust=1574336955218:159:18)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/scenery/js/input/SimpleDragHandler.js?bust=1574336955218:215:26
at Action.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Action.js?bust=1574336955218:230:20)
at SimpleDragHandler.endDrag (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/scenery/js/input/SimpleDragHandler.js?bust=1574336955218:330:26)
at Object.up (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/scenery/js/input/SimpleDragHandler.js?bust=1574336955218:273:16)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-tests : assert
9 out of 9 tests passed. 0 failed.
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-tests : no-assert
9 out of 9 tests passed. 0 failed.
Approximately 11/20/2019, 11:29:23 PM
```
```circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: should not be called if disposed
Error: Assertion failed: should not be called if disposed
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574329285098:22:13)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574329285168:53:17)
at Vector2Property.notifyListenersStatic (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:290:27)
at CircuitLayerNode.translateVertexGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574329285168:699:40)
at moveVerticesInBounds (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574329285168:393:18)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574329285168:68:55)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:275:27)
at Property.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:176:16)
at CircuitLayerNode.updateTransform (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574329285168:771:58)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CCKCScreenView.js?bust=1574329285168:324:31
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: reentry detected, value=0.5875314264771545, oldValue=0.5619486787744986
Error: Assertion failed: reentry detected, value=0.5875314264771545, oldValue=0.5619486787744986
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574329285098:22:13)
at NumberProperty._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:272:17)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:176:16)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/NumberProperty.js?bust=1574329285168:134:13)
at NumberProperty.set value [as value] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:345:34)
at ZoomAnimation.zoomCallback (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574329285168:99:42)
at ZoomAnimation.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/ZoomAnimation.js?bust=1574329285168:47:14)
at BlackBoxSceneModel.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574329285168:197:45)
at BlackBoxScreenView.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-black-box-study/js/blackbox/view/BlackBoxScreenView.js?bust=1574329285168:96:77)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/joist/js/Sim.js?bust=1574329285168:250:21
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: should not be called if disposed
Error: Assertion failed: should not be called if disposed
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574337686120:22:13)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574337686192:53:17)
at Vector2Property.notifyListenersStatic (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:290:27)
at CircuitLayerNode.translateVertexGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574337686192:699:40)
at moveVerticesInBounds (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574337686192:393:18)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574337686192:68:55)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:275:27)
at Property.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:176:16)
at CircuitLayerNode.updateTransform (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574337686192:771:58)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CCKCScreenView.js?bust=1574337686192:324:31
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: reentry detected, value=0.9810974227405248, oldValue=0.882660944606414
Error: Assertion failed: reentry detected, value=0.9810974227405248, oldValue=0.882660944606414
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574337686120:22:13)
at NumberProperty._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:272:17)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:176:16)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/NumberProperty.js?bust=1574337686192:134:13)
at NumberProperty.set value [as value] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:345:34)
at ZoomAnimation.zoomCallback (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574337686192:99:42)
at ZoomAnimation.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/ZoomAnimation.js?bust=1574337686192:47:14)
at BlackBoxSceneModel.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574337686192:197:45)
at BlackBoxScreenView.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-black-box-study/js/blackbox/view/BlackBoxScreenView.js?bust=1574337686192:96:77)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/joist/js/Sim.js?bust=1574337686192:250:21
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
```
```
circuit-construction-kit-dc : xss-fuzz : run
Query: brand=phet&ea&fuzz&stringTest=xss&memoryLimit=1000
Uncaught Error: Assertion failed: tried to removeListener on something that wasn't a listener
Error: Assertion failed: tried to removeListener on something that wasn't a listener
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574336902853:22:13)
at TinyEmitter.removeListener (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574336902921:104:9)
at NumberProperty.unlink (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336902921:376:27)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitElement.js?bust=1574336902921:270:54)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Battery.js?bust=1574336902921:82:13)
at Battery.PhetioObject.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574336902921:154:22)
at PhetioGroup.disposeMember (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioGroup.js?bust=1574336902921:112:14)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574336902921:388:79
at Array.forEach (<anonymous>)
at Circuit.disposeFromGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574336902921:388:19)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
```
```circuit-construction-kit-dc-virtual-lab : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: tried to removeListener on something that wasn't a listener
Error: Assertion failed: tried to removeListener on something that wasn't a listener
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574327590878:22:13)
at TinyEmitter.removeListener (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574327590949:104:9)
at NumberProperty.unlink (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574327590949:376:27)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitElement.js?bust=1574327590949:270:54)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Battery.js?bust=1574327590949:82:13)
at Battery.PhetioObject.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574327590949:154:22)
at PhetioGroup.disposeMember (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioGroup.js?bust=1574327590949:112:14)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574327590949:388:79
at Array.forEach (<anonymous>)
at Circuit.disposeFromGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574327590949:388:19)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
```
|
1.0
|
CT various for different sims - ```
circuit-construction-kit-ac : phet-io-fuzz : require.js : run
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: There should always be an entry in the baseline for each phetioID
Error: Assertion failed: There should always be an entry in the baseline for each phetioID
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574322196919:22:13)
at PhetioAPIValidation.onPhetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/phetioAPIValidation.js?bust=1574322197011:196:19)
at PhetioEngine.phetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574322197011:362:27)
at Object.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574322197011:516:51)
at Tandem.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/Tandem.js?bust=1574322197011:147:40)
at BooleanProperty.initializePhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574322197011:331:19)
at new PhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574322197011:144:12)
at new Property (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574322197011:69:7)
at new BooleanProperty (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/BooleanProperty.js?bust=1574322197011:48:7)
at PushButtonModel.ButtonModel [as constructor] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/sun/js/buttons/ButtonModel.js?bust=1574322197011:74:28)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-fuzz : require.js : run
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: There should always be an entry in the baseline for each phetioID
Error: Assertion failed: There should always be an entry in the baseline for each phetioID
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574336955137:22:13)
at PhetioAPIValidation.onPhetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/phetioAPIValidation.js?bust=1574336955218:196:19)
at PhetioEngine.phetioObjectAdded (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574336955218:362:27)
at Object.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/phet-io/js/phetioEngine.js?bust=1574336955218:516:51)
at Tandem.addPhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/Tandem.js?bust=1574336955218:147:40)
at BooleanProperty.initializePhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574336955218:331:19)
at new PhetioObject (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574336955218:144:12)
at new Property (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336955218:69:7)
at new BooleanProperty (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/BooleanProperty.js?bust=1574336955218:48:7)
at PushButtonModel.ButtonModel [as constructor] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/sun/js/buttons/ButtonModel.js?bust=1574336955218:74:28)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-fuzz : require.js : run
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: reentry detected, value=null, oldValue=[object Object]
Error: Assertion failed: reentry detected, value=null, oldValue=[object Object]
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574336955137:22:13)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336955218:272:17)
at Property.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336955218:176:16)
at CCKCLightBulbNode.selectCircuitElementNodeWhenNear (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitElementNode.js?bust=1574336955218:261:65)
at CCKCLightBulbNode.endDrag (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitElementNode.js?bust=1574336955218:207:25)
at end (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/FixedCircuitElementNode.js?bust=1574336955218:159:18)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/scenery/js/input/SimpleDragHandler.js?bust=1574336955218:215:26
at Action.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Action.js?bust=1574336955218:230:20)
at SimpleDragHandler.endDrag (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/scenery/js/input/SimpleDragHandler.js?bust=1574336955218:330:26)
at Object.up (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/scenery/js/input/SimpleDragHandler.js?bust=1574336955218:273:16)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-tests : assert
9 out of 9 tests passed. 0 failed.
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-ac : phet-io-tests : no-assert
9 out of 9 tests passed. 0 failed.
Approximately 11/20/2019, 11:29:23 PM
```
```circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: should not be called if disposed
Error: Assertion failed: should not be called if disposed
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574329285098:22:13)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574329285168:53:17)
at Vector2Property.notifyListenersStatic (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:290:27)
at CircuitLayerNode.translateVertexGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574329285168:699:40)
at moveVerticesInBounds (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574329285168:393:18)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574329285168:68:55)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:275:27)
at Property.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:176:16)
at CircuitLayerNode.updateTransform (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574329285168:771:58)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CCKCScreenView.js?bust=1574329285168:324:31
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: reentry detected, value=0.5875314264771545, oldValue=0.5619486787744986
Error: Assertion failed: reentry detected, value=0.5875314264771545, oldValue=0.5619486787744986
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574329285098:22:13)
at NumberProperty._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:272:17)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:176:16)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/NumberProperty.js?bust=1574329285168:134:13)
at NumberProperty.set value [as value] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574329285168:345:34)
at ZoomAnimation.zoomCallback (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574329285168:99:42)
at ZoomAnimation.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/ZoomAnimation.js?bust=1574329285168:47:14)
at BlackBoxSceneModel.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574329285168:197:45)
at BlackBoxScreenView.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-black-box-study/js/blackbox/view/BlackBoxScreenView.js?bust=1574329285168:96:77)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/joist/js/Sim.js?bust=1574329285168:250:21
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: should not be called if disposed
Error: Assertion failed: should not be called if disposed
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574337686120:22:13)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574337686192:53:17)
at Vector2Property.notifyListenersStatic (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:290:27)
at CircuitLayerNode.translateVertexGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574337686192:699:40)
at moveVerticesInBounds (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574337686192:393:18)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574337686192:68:55)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:275:27)
at Property.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:176:16)
at CircuitLayerNode.updateTransform (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CircuitLayerNode.js?bust=1574337686192:771:58)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/view/CCKCScreenView.js?bust=1574337686192:324:31
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
circuit-construction-kit-black-box-study : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: reentry detected, value=0.9810974227405248, oldValue=0.882660944606414
Error: Assertion failed: reentry detected, value=0.9810974227405248, oldValue=0.882660944606414
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574337686120:22:13)
at NumberProperty._notifyListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:272:17)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:176:16)
at NumberProperty.set (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/NumberProperty.js?bust=1574337686192:134:13)
at NumberProperty.set value [as value] (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574337686192:345:34)
at ZoomAnimation.zoomCallback (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574337686192:99:42)
at ZoomAnimation.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/ZoomAnimation.js?bust=1574337686192:47:14)
at BlackBoxSceneModel.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitConstructionKitModel.js?bust=1574337686192:197:45)
at BlackBoxScreenView.step (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-black-box-study/js/blackbox/view/BlackBoxScreenView.js?bust=1574337686192:96:77)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/joist/js/Sim.js?bust=1574337686192:250:21
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
```
```
circuit-construction-kit-dc : xss-fuzz : run
Query: brand=phet&ea&fuzz&stringTest=xss&memoryLimit=1000
Uncaught Error: Assertion failed: tried to removeListener on something that wasn't a listener
Error: Assertion failed: tried to removeListener on something that wasn't a listener
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574336902853:22:13)
at TinyEmitter.removeListener (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574336902921:104:9)
at NumberProperty.unlink (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574336902921:376:27)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitElement.js?bust=1574336902921:270:54)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Battery.js?bust=1574336902921:82:13)
at Battery.PhetioObject.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574336902921:154:22)
at PhetioGroup.disposeMember (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioGroup.js?bust=1574336902921:112:14)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574336902921:388:79
at Array.forEach (<anonymous>)
at Circuit.disposeFromGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574336902921:388:19)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
```
```circuit-construction-kit-dc-virtual-lab : fuzz : require.js : run
Query: brand=phet&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: tried to removeListener on something that wasn't a listener
Error: Assertion failed: tried to removeListener on something that wasn't a listener
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/assert/js/assert.js?bust=1574327590878:22:13)
at TinyEmitter.removeListener (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/TinyEmitter.js?bust=1574327590949:104:9)
at NumberProperty.unlink (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/axon/js/Property.js?bust=1574327590949:376:27)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/CircuitElement.js?bust=1574327590949:270:54)
at Battery.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Battery.js?bust=1574327590949:82:13)
at Battery.PhetioObject.dispose (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioObject.js?bust=1574327590949:154:22)
at PhetioGroup.disposeMember (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/tandem/js/PhetioGroup.js?bust=1574327590949:112:14)
at https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574327590949:388:79
at Array.forEach (<anonymous>)
at Circuit.disposeFromGroup (https://bayes.colorado.edu/continuous-testing/snapshot-1574317763454/circuit-construction-kit-common/js/model/Circuit.js?bust=1574327590949:388:19)
id: Bayes Chrome
Approximately 11/20/2019, 11:29:23 PM
```
|
non_defect
|
ct various for different sims circuit construction kit ac phet io fuzz require js run query brand phet io phetiostandalone ea fuzz memorylimit uncaught error assertion failed there should always be an entry in the baseline for each phetioid error assertion failed there should always be an entry in the baseline for each phetioid at window assertions assertfunction at phetioapivalidation onphetioobjectadded at phetioengine phetioobjectadded at object addphetioobject at tandem addphetioobject at booleanproperty initializephetioobject at new phetioobject at new property at new booleanproperty at pushbuttonmodel buttonmodel id bayes chrome approximately pm circuit construction kit ac phet io fuzz require js run query brand phet io phetiostandalone ea fuzz memorylimit uncaught error assertion failed there should always be an entry in the baseline for each phetioid error assertion failed there should always be an entry in the baseline for each phetioid at window assertions assertfunction at phetioapivalidation onphetioobjectadded at phetioengine phetioobjectadded at object addphetioobject at tandem addphetioobject at booleanproperty initializephetioobject at new phetioobject at new property at new booleanproperty at pushbuttonmodel buttonmodel id bayes chrome approximately pm circuit construction kit ac phet io fuzz require js run query brand phet io phetiostandalone ea fuzz memorylimit uncaught error assertion failed reentry detected value null oldvalue error assertion failed reentry detected value null oldvalue at window assertions assertfunction at property notifylisteners at property set at cckclightbulbnode selectcircuitelementnodewhennear at cckclightbulbnode enddrag at end at at action execute at simpledraghandler enddrag at object up id bayes chrome approximately pm circuit construction kit ac phet io tests assert out of tests passed failed approximately pm circuit construction kit ac phet io tests no assert out of tests passed failed approximately pm circuit construction kit black box study fuzz require js run query brand phet ea fuzz memorylimit uncaught error assertion failed should not be called if disposed error assertion failed should not be called if disposed at window assertions assertfunction at tinyemitter emit at notifylistenersstatic at circuitlayernode translatevertexgroup at moveverticesinbounds at tinyemitter emit at property notifylisteners at property set at circuitlayernode updatetransform at id bayes chrome approximately pm circuit construction kit black box study fuzz require js run query brand phet ea fuzz memorylimit uncaught error assertion failed reentry detected value oldvalue error assertion failed reentry detected value oldvalue at window assertions assertfunction at numberproperty notifylisteners at numberproperty set at numberproperty set at numberproperty set value at zoomanimation zoomcallback at zoomanimation step at blackboxscenemodel step at blackboxscreenview step at id bayes chrome approximately pm circuit construction kit black box study fuzz require js run query brand phet ea fuzz memorylimit uncaught error assertion failed should not be called if disposed error assertion failed should not be called if disposed at window assertions assertfunction at tinyemitter emit at notifylistenersstatic at circuitlayernode translatevertexgroup at moveverticesinbounds at tinyemitter emit at property notifylisteners at property set at circuitlayernode updatetransform at id bayes chrome approximately pm circuit construction kit black box study fuzz require js run query brand phet ea fuzz memorylimit uncaught error assertion failed reentry detected value oldvalue error assertion failed reentry detected value oldvalue at window assertions assertfunction at numberproperty notifylisteners at numberproperty set at numberproperty set at numberproperty set value at zoomanimation zoomcallback at zoomanimation step at blackboxscenemodel step at blackboxscreenview step at id bayes chrome approximately pm circuit construction kit dc xss fuzz run query brand phet ea fuzz stringtest xss memorylimit uncaught error assertion failed tried to removelistener on something that wasn t a listener error assertion failed tried to removelistener on something that wasn t a listener at window assertions assertfunction at tinyemitter removelistener at numberproperty unlink at battery dispose at battery dispose at battery phetioobject dispose at phetiogroup disposemember at at array foreach at circuit disposefromgroup id bayes chrome approximately pm circuit construction kit dc virtual lab fuzz require js run query brand phet ea fuzz memorylimit uncaught error assertion failed tried to removelistener on something that wasn t a listener error assertion failed tried to removelistener on something that wasn t a listener at window assertions assertfunction at tinyemitter removelistener at numberproperty unlink at battery dispose at battery dispose at battery phetioobject dispose at phetiogroup disposemember at at array foreach at circuit disposefromgroup id bayes chrome approximately pm
| 0
|
31,580
| 6,551,910,851
|
IssuesEvent
|
2017-09-05 16:16:14
|
jccastillo0007/eFacturaT
|
https://api.github.com/repos/jccastillo0007/eFacturaT
|
opened
|
Web CFDi 3.3- No jaló la addenda mabe
|
bug defect
|
De hecho, subí el XML de configuración, tomado de un cliente en producción, y con datos predefinidos para no adivinarle. Hay dos problemas:
a) Al capturar la addenda, mezcló datos de ooootro archivo XML de configuración del CCE, con el archivo de configuración XML de mabe.
b) Marcó error al generar la factura.
|
1.0
|
Web CFDi 3.3- No jaló la addenda mabe - De hecho, subí el XML de configuración, tomado de un cliente en producción, y con datos predefinidos para no adivinarle. Hay dos problemas:
a) Al capturar la addenda, mezcló datos de ooootro archivo XML de configuración del CCE, con el archivo de configuración XML de mabe.
b) Marcó error al generar la factura.
|
defect
|
web cfdi no jaló la addenda mabe de hecho subí el xml de configuración tomado de un cliente en producción y con datos predefinidos para no adivinarle hay dos problemas a al capturar la addenda mezcló datos de ooootro archivo xml de configuración del cce con el archivo de configuración xml de mabe b marcó error al generar la factura
| 1
|
275,566
| 8,577,093,803
|
IssuesEvent
|
2018-11-12 22:34:53
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www3.nhk.or.jp - video or audio doesn't play
|
browser-firefox-mobile priority-important
|
<!-- @browser: Firefox Mobile 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.0.0; Mobile; rv:64.0) Gecko/64.0 Firefox/64.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www3.nhk.or.jp/nhkworld/en/vod/asiainsight/2022253/
**Browser / Version**: Firefox Mobile 64.0
**Operating System**: Android 8.0.0
**Tested Another Browser**: Yes
**Problem type**: Video or audio doesn't play
**Description**: Video is not showing nor playable
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
www3.nhk.or.jp - video or audio doesn't play - <!-- @browser: Firefox Mobile 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.0.0; Mobile; rv:64.0) Gecko/64.0 Firefox/64.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www3.nhk.or.jp/nhkworld/en/vod/asiainsight/2022253/
**Browser / Version**: Firefox Mobile 64.0
**Operating System**: Android 8.0.0
**Tested Another Browser**: Yes
**Problem type**: Video or audio doesn't play
**Description**: Video is not showing nor playable
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_defect
|
nhk or jp video or audio doesn t play url browser version firefox mobile operating system android tested another browser yes problem type video or audio doesn t play description video is not showing nor playable steps to reproduce browser configuration none from with ❤️
| 0
|
3,800
| 2,610,069,254
|
IssuesEvent
|
2015-02-26 18:20:18
|
chrsmith/jsjsj122
|
https://api.github.com/repos/chrsmith/jsjsj122
|
opened
|
台州割包茎哪个医院专业
|
auto-migrated Priority-Medium Type-Defect
|
```
台州割包茎哪个医院专业【台州五洲生殖医院】24小时健康咨
询热线:0576-88066933-(扣扣800080609)-(微信号tzwzszyy)医院地址:台州
市椒江区枫南路229号（枫南大转盘旁）乘车线路:乘坐104、108�
��118、198及椒江一金清公交车直达枫南小区，乘坐107、105、109
、112、901、 902公交车到星星广场下车，步行即可到院。
诊疗项目：阳痿，早泄，前列腺炎，前列腺增生，龟头炎，��
�精，无精。包皮包茎，精索静脉曲张，淋病等。
台州五洲生殖医院是台州最大的男科医院，权威专家在线免��
�咨询，拥有专业完善的男科检查治疗设备，严格按照国家标�
��收费。尖端医疗设备，与世界同步。权威专家，成就专业典
范。人性化服务，一切以患者为中心。
看男科就选台州五洲生殖医院，专业男科为男人。
```
-----
Original issue reported on code.google.com by `poweragr...@gmail.com` on 30 May 2014 at 9:45
|
1.0
|
台州割包茎哪个医院专业 - ```
台州割包茎哪个医院专业【台州五洲生殖医院】24小时健康咨
询热线:0576-88066933-(扣扣800080609)-(微信号tzwzszyy)医院地址:台州
市椒江区枫南路229号（枫南大转盘旁）乘车线路:乘坐104、108�
��118、198及椒江一金清公交车直达枫南小区，乘坐107、105、109
、112、901、 902公交车到星星广场下车，步行即可到院。
诊疗项目：阳痿，早泄，前列腺炎，前列腺增生，龟头炎，��
�精，无精。包皮包茎，精索静脉曲张，淋病等。
台州五洲生殖医院是台州最大的男科医院，权威专家在线免��
�咨询，拥有专业完善的男科检查治疗设备，严格按照国家标�
��收费。尖端医疗设备，与世界同步。权威专家，成就专业典
范。人性化服务，一切以患者为中心。
看男科就选台州五洲生殖医院，专业男科为男人。
```
-----
Original issue reported on code.google.com by `poweragr...@gmail.com` on 30 May 2014 at 9:45
|
defect
|
台州割包茎哪个医院专业 台州割包茎哪个医院专业【台州五洲生殖医院】 询热线 微信号tzwzszyy 医院地址 台州 （枫南大转盘旁）乘车线路 、 � �� 、 ， 、 、 、 、 、 ，步行即可到院。 诊疗项目：阳痿，早泄，前列腺炎，前列腺增生，龟头炎，�� �精，无精。包皮包茎，精索静脉曲张，淋病等。 台州五洲生殖医院是台州最大的男科医院，权威专家在线免�� �咨询，拥有专业完善的男科检查治疗设备，严格按照国家标� ��收费。尖端医疗设备，与世界同步。权威专家，成就专业典 范。人性化服务，一切以患者为中心。 看男科就选台州五洲生殖医院，专业男科为男人。 original issue reported on code google com by poweragr gmail com on may at
| 1
|
120,311
| 17,644,085,279
|
IssuesEvent
|
2021-08-20 01:39:12
|
DavidSpek/pipelines
|
https://api.github.com/repos/DavidSpek/pipelines
|
opened
|
CVE-2021-37677 (Medium) detected in tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl
|
security vulnerability
|
## CVE-2021-37677 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt</p>
<p>Path to vulnerable library: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt,pipelines/samples/core/ai_platform/training</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl** (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>
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the shape inference code for `tf.raw_ops.Dequantize` has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses `axis` to select between two different values for `minmax_rank` which is then used to retrieve tensor dimensions. However, code assumes that `axis` can be either `-1` or a value greater than `-1`, with no validation for the other values. We have patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37677>CVE-2021-37677</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-37677 (Medium) detected in tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl - ## CVE-2021-37677 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt</p>
<p>Path to vulnerable library: pipelines/contrib/components/openvino/ovms-deployer/containers/requirements.txt,pipelines/samples/core/ai_platform/training</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl** (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>
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the shape inference code for `tf.raw_ops.Dequantize` has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses `axis` to select between two different values for `minmax_rank` which is then used to retrieve tensor dimensions. However, code assumes that `axis` can be either `-1` or a value greater than `-1`, with no validation for the other values. We have patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37677>CVE-2021-37677</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qfpc-5pjr-mh26</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: tensorflow - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-cpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0, tensorflow-gpu - 2.3.4, 2.4.3, 2.5.1, 2.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_defect
|
cve medium detected in tensorflow whl cve medium severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file pipelines contrib components openvino ovms deployer containers requirements txt path to vulnerable library pipelines contrib components openvino ovms deployer containers requirements txt pipelines samples core ai platform training dependency hierarchy x tensorflow whl vulnerable library found in base branch master vulnerability details tensorflow is an end to end open source platform for machine learning in affected versions the shape inference code for tf raw ops dequantize has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments the shape inference uses axis to select between two different values for minmax rank which is then used to retrieve tensor dimensions however code assumes that axis can be either or a value greater than with no validation for the other values we have patched the issue in github commit the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow and tensorflow as these are also affected and still in supported range publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu step up your open source security game with whitesource
| 0
|
4,839
| 2,610,157,897
|
IssuesEvent
|
2015-02-26 18:50:09
|
chrsmith/republic-at-war
|
https://api.github.com/repos/chrsmith/republic-at-war
|
closed
|
Skirmish
|
auto-migrated Priority-Medium Type-Defect
|
```
Clone Platoons Land in wrong ship in Skirmish.
```
-----
Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:57
|
1.0
|
Skirmish - ```
Clone Platoons Land in wrong ship in Skirmish.
```
-----
Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:57
|
defect
|
skirmish clone platoons land in wrong ship in skirmish original issue reported on code google com by gmail com on jan at
| 1
|
410,471
| 11,992,048,081
|
IssuesEvent
|
2020-04-08 09:25:53
|
AY1920S2-CS2103T-W12-1/main
|
https://api.github.com/repos/AY1920S2-CS2103T-W12-1/main
|
closed
|
[PE-D] The Insert command example given in the UG has invalid format
|
priority.High type.Bug type.DG type.UG
|
In the second example given by table 7 is invalid due to a wrong format for the phone number. The screenshot below highlights the invalid phone number.
-------------
Labels: `severity.Medium` `type.DocumentationBug`
original: zenatrick/ped#3
|
1.0
|
[PE-D] The Insert command example given in the UG has invalid format - In the second example given by table 7 is invalid due to a wrong format for the phone number. The screenshot below highlights the invalid phone number.
-------------
Labels: `severity.Medium` `type.DocumentationBug`
original: zenatrick/ped#3
|
non_defect
|
the insert command example given in the ug has invalid format in the second example given by table is invalid due to a wrong format for the phone number the screenshot below highlights the invalid phone number labels severity medium type documentationbug original zenatrick ped
| 0
|
47,449
| 13,056,190,087
|
IssuesEvent
|
2020-07-30 03:56:13
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
closed
|
Examples docs cannot be built without an X server connection (Trac #575)
|
Migrated from Trac defect documentation
|
Running `make docs` fails with the following output, if no X server is available:
```text
...
reading sources... [ 58%] projects/dataio/serialization
reading sources... [ 60%] projects/dataio/using_muxer
reading sources... [ 61%] projects/examples/index
reading sources... [ 62%] projects/examples/modules
/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py:44: GtkWarning: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed
cursors.MOVE : gdk.Cursor(gdk.FLEUR),
Exception occurred:
File "/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/stow/python-2.6.1/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py", line 44, in <module>
cursors.MOVE : gdk.Cursor(gdk.FLEUR),
RuntimeError: could not create GdkCursor object
The full traceback has been saved in /tmp/sphinx-err-Gku2vo.log, if you want to report the issue to the author.
Please also report this if it was a user error, so that a better error message can be provided next time.
Send reports to sphinx-dev@googlegroups.com. Thanks!
make[3]: *** [cmake/meta-project-docs/CMakeFiles/html] Error 1
make[2]: *** [cmake/meta-project-docs/CMakeFiles/html.dir/all] Error 2
make[1]: *** [CMakeFiles/docs.dir/rule] Error 2
make: *** [docs] Error 2
```
I consider this a defect since it keeps me from building the icerec documentation in my nightly cron-job.
Migrated from https://code.icecube.wisc.edu/ticket/575
```json
{
"status": "closed",
"changetime": "2011-05-11T23:22:06",
"description": "Running `make docs` fails with the following output, if no X server is available:\n{{{\n ...\nreading sources... [ 58%] projects/dataio/serialization\nreading sources... [ 60%] projects/dataio/using_muxer\nreading sources... [ 61%] projects/examples/index\nreading sources... [ 62%] projects/examples/modules\n/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display\n warnings.warn(str(e), _gtk.Warning)\n/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py:44: GtkWarning: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed\n cursors.MOVE : gdk.Cursor(gdk.FLEUR),\n\nException occurred:\n File \"/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/stow/python-2.6.1/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py\", line 44, in <module>\n cursors.MOVE : gdk.Cursor(gdk.FLEUR),\nRuntimeError: could not create GdkCursor object\nThe full traceback has been saved in /tmp/sphinx-err-Gku2vo.log, if you want to report the issue to the author.\nPlease also report this if it was a user error, so that a better error message can be provided next time.\nSend reports to sphinx-dev@googlegroups.com. Thanks!\nmake[3]: *** [cmake/meta-project-docs/CMakeFiles/html] Error 1\nmake[2]: *** [cmake/meta-project-docs/CMakeFiles/html.dir/all] Error 2\nmake[1]: *** [CMakeFiles/docs.dir/rule] Error 2\nmake: *** [docs] Error 2\n}}}\n\nI consider this a defect since it keeps me from building the icerec documentation in my nightly cron-job.",
"reporter": "kislat",
"cc": "fabian.kislat@desy.de",
"resolution": "worksforme",
"_ts": "1305156126000000",
"component": "documentation",
"summary": "Examples docs cannot be built without an X server connection",
"priority": "normal",
"keywords": "",
"time": "2009-11-13T14:44:20",
"milestone": "",
"owner": "troy",
"type": "defect"
}
```
|
1.0
|
Examples docs cannot be built without an X server connection (Trac #575) - Running `make docs` fails with the following output, if no X server is available:
```text
...
reading sources... [ 58%] projects/dataio/serialization
reading sources... [ 60%] projects/dataio/using_muxer
reading sources... [ 61%] projects/examples/index
reading sources... [ 62%] projects/examples/modules
/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py:44: GtkWarning: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed
cursors.MOVE : gdk.Cursor(gdk.FLEUR),
Exception occurred:
File "/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/stow/python-2.6.1/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py", line 44, in <module>
cursors.MOVE : gdk.Cursor(gdk.FLEUR),
RuntimeError: could not create GdkCursor object
The full traceback has been saved in /tmp/sphinx-err-Gku2vo.log, if you want to report the issue to the author.
Please also report this if it was a user error, so that a better error message can be provided next time.
Send reports to sphinx-dev@googlegroups.com. Thanks!
make[3]: *** [cmake/meta-project-docs/CMakeFiles/html] Error 1
make[2]: *** [cmake/meta-project-docs/CMakeFiles/html.dir/all] Error 2
make[1]: *** [CMakeFiles/docs.dir/rule] Error 2
make: *** [docs] Error 2
```
I consider this a defect since it keeps me from building the icerec documentation in my nightly cron-job.
Migrated from https://code.icecube.wisc.edu/ticket/575
```json
{
"status": "closed",
"changetime": "2011-05-11T23:22:06",
"description": "Running `make docs` fails with the following output, if no X server is available:\n{{{\n ...\nreading sources... [ 58%] projects/dataio/serialization\nreading sources... [ 60%] projects/dataio/using_muxer\nreading sources... [ 61%] projects/examples/index\nreading sources... [ 62%] projects/examples/modules\n/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display\n warnings.warn(str(e), _gtk.Warning)\n/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py:44: GtkWarning: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed\n cursors.MOVE : gdk.Cursor(gdk.FLEUR),\n\nException occurred:\n File \"/afs/ifh.de/group/amanda/software_test/RHEL_5.0_amd64/stow/python-2.6.1/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py\", line 44, in <module>\n cursors.MOVE : gdk.Cursor(gdk.FLEUR),\nRuntimeError: could not create GdkCursor object\nThe full traceback has been saved in /tmp/sphinx-err-Gku2vo.log, if you want to report the issue to the author.\nPlease also report this if it was a user error, so that a better error message can be provided next time.\nSend reports to sphinx-dev@googlegroups.com. Thanks!\nmake[3]: *** [cmake/meta-project-docs/CMakeFiles/html] Error 1\nmake[2]: *** [cmake/meta-project-docs/CMakeFiles/html.dir/all] Error 2\nmake[1]: *** [CMakeFiles/docs.dir/rule] Error 2\nmake: *** [docs] Error 2\n}}}\n\nI consider this a defect since it keeps me from building the icerec documentation in my nightly cron-job.",
"reporter": "kislat",
"cc": "fabian.kislat@desy.de",
"resolution": "worksforme",
"_ts": "1305156126000000",
"component": "documentation",
"summary": "Examples docs cannot be built without an X server connection",
"priority": "normal",
"keywords": "",
"time": "2009-11-13T14:44:20",
"milestone": "",
"owner": "troy",
"type": "defect"
}
```
|
defect
|
examples docs cannot be built without an x server connection trac running make docs fails with the following output if no x server is available text reading sources projects dataio serialization reading sources projects dataio using muxer reading sources projects examples index reading sources projects examples modules afs ifh de group amanda software test rhel lib site packages gtk gtk init py gtkwarning could not open display warnings warn str e gtk warning afs ifh de group amanda software test rhel lib site packages matplotlib backends backend gtk py gtkwarning gdk cursor new for display assertion gdk is display display failed cursors move gdk cursor gdk fleur exception occurred file afs ifh de group amanda software test rhel stow python lib site packages matplotlib backends backend gtk py line in cursors move gdk cursor gdk fleur runtimeerror could not create gdkcursor object the full traceback has been saved in tmp sphinx err log if you want to report the issue to the author please also report this if it was a user error so that a better error message can be provided next time send reports to sphinx dev googlegroups com thanks make error make error make error make error i consider this a defect since it keeps me from building the icerec documentation in my nightly cron job migrated from json status closed changetime description running make docs fails with the following output if no x server is available n n nreading sources projects dataio serialization nreading sources projects dataio using muxer nreading sources projects examples index nreading sources projects examples modules n afs ifh de group amanda software test rhel lib site packages gtk gtk init py gtkwarning could not open display n warnings warn str e gtk warning n afs ifh de group amanda software test rhel lib site packages matplotlib backends backend gtk py gtkwarning gdk cursor new for display assertion gdk is display display failed n cursors move gdk cursor gdk fleur n nexception occurred n file afs ifh de group amanda software test rhel stow python lib site packages matplotlib backends backend gtk py line in n cursors move gdk cursor gdk fleur nruntimeerror could not create gdkcursor object nthe full traceback has been saved in tmp sphinx err log if you want to report the issue to the author nplease also report this if it was a user error so that a better error message can be provided next time nsend reports to sphinx dev googlegroups com thanks nmake error nmake error nmake error nmake error n n ni consider this a defect since it keeps me from building the icerec documentation in my nightly cron job reporter kislat cc fabian kislat desy de resolution worksforme ts component documentation summary examples docs cannot be built without an x server connection priority normal keywords time milestone owner troy type defect
| 1
|
15,734
| 2,869,004,927
|
IssuesEvent
|
2015-06-05 22:31:18
|
dart-lang/sdk
|
https://api.github.com/repos/dart-lang/sdk
|
closed
|
Specify alphabet to base64 encoding (e.g. base64url)
|
Area-Pkg Pkg-Crypto Priority-Unassigned Triaged Type-Defect
|
crypto's bytesToBase64 is great, but I'd really like to specify the alphabet; specifically base64url in which the last two characters are -_
See: http://tools.ietf.org/html/rfc4648#section-5
See: http://en.wikipedia.org/wiki/Base64
|
1.0
|
Specify alphabet to base64 encoding (e.g. base64url) - crypto's bytesToBase64 is great, but I'd really like to specify the alphabet; specifically base64url in which the last two characters are -_
See: http://tools.ietf.org/html/rfc4648#section-5
See: http://en.wikipedia.org/wiki/Base64
|
defect
|
specify alphabet to encoding e g crypto s is great but i d really like to specify the alphabet specifically in which the last two characters are see see
| 1
|
26,037
| 4,553,048,623
|
IssuesEvent
|
2016-09-13 02:17:10
|
cakephp/cakephp
|
https://api.github.com/repos/cakephp/cakephp
|
closed
|
getMockForModel uses default datasource when cacheMethods are disabled
|
Defect testing
|
When cacheMethods are disabled in CakePHP 2.7.* getMockForModel makes atleast once use of default datasource instead of test datasource.
|
1.0
|
getMockForModel uses default datasource when cacheMethods are disabled - When cacheMethods are disabled in CakePHP 2.7.* getMockForModel makes atleast once use of default datasource instead of test datasource.
|
defect
|
getmockformodel uses default datasource when cachemethods are disabled when cachemethods are disabled in cakephp getmockformodel makes atleast once use of default datasource instead of test datasource
| 1
|
92,213
| 11,615,764,541
|
IssuesEvent
|
2020-02-26 14:42:13
|
GCTC-NTGC/TalentCloud
|
https://api.github.com/repos/GCTC-NTGC/TalentCloud
|
closed
|
[Design] - Assessment Plan Tool Null States
|
Design Ask
|
# Design Goal
**Please describe the ask.**
@Jerryescandon mentioned the need for clearer null states on the assessment plan tool, particularly when the user visits the tool before completing a job poster.
**Related Features:**
- Assessment Plan Builder
|
1.0
|
[Design] - Assessment Plan Tool Null States - # Design Goal
**Please describe the ask.**
@Jerryescandon mentioned the need for clearer null states on the assessment plan tool, particularly when the user visits the tool before completing a job poster.
**Related Features:**
- Assessment Plan Builder
|
non_defect
|
assessment plan tool null states design goal please describe the ask jerryescandon mentioned the need for clearer null states on the assessment plan tool particularly when the user visits the tool before completing a job poster related features assessment plan builder
| 0
|
27,605
| 5,052,430,801
|
IssuesEvent
|
2016-12-21 02:08:09
|
jccastillo0007/eFacturaT
|
https://api.github.com/repos/jccastillo0007/eFacturaT
|
opened
|
CFDI Estándar+Nómina - No se debe reportar el atributo NumCtaPago
|
bug defect
|
Siempre te has confundido con la cuenta que se captura en los datos de la nómina.
Esa cuenta va en el nodo receptor del complemento, pero no a nivel estándar.
A nivel estándar, no aplica este atributo.
|
1.0
|
CFDI Estándar+Nómina - No se debe reportar el atributo NumCtaPago - Siempre te has confundido con la cuenta que se captura en los datos de la nómina.
Esa cuenta va en el nodo receptor del complemento, pero no a nivel estándar.
A nivel estándar, no aplica este atributo.
|
defect
|
cfdi estándar nómina no se debe reportar el atributo numctapago siempre te has confundido con la cuenta que se captura en los datos de la nómina esa cuenta va en el nodo receptor del complemento pero no a nivel estándar a nivel estándar no aplica este atributo
| 1
|
20,329
| 3,343,253,002
|
IssuesEvent
|
2015-11-15 10:17:39
|
jbgi/graphwiz
|
https://api.github.com/repos/jbgi/graphwiz
|
closed
|
asdasd
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `tede...@googlemail.com` on 22 Feb 2008 at 5:41
|
1.0
|
asdasd - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `tede...@googlemail.com` on 22 Feb 2008 at 5:41
|
defect
|
asdasd what steps will reproduce the problem what is the expected output what do you see instead what version of the product are you using on what operating system please provide any additional information below original issue reported on code google com by tede googlemail com on feb at
| 1
|
29,878
| 11,782,210,125
|
IssuesEvent
|
2020-03-17 01:05:10
|
LevyForchh/webdataconnector
|
https://api.github.com/repos/LevyForchh/webdataconnector
|
opened
|
CVE-2020-7598 (High) detected in minimist-0.0.10.tgz
|
security vulnerability
|
## CVE-2020-7598 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.10.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/webdataconnector/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/webdataconnector/node_modules/optimist/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- http-server-0.9.0.tgz (Root Library)
- optimist-0.6.1.tgz
- :x: **minimist-0.0.10.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>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.10","isTransitiveDependency":true,"dependencyTree":"http-server:0.9.0;optimist:0.6.1;minimist:0.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.2"}],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-7598 (High) detected in minimist-0.0.10.tgz - ## CVE-2020-7598 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.10.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/webdataconnector/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/webdataconnector/node_modules/optimist/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- http-server-0.9.0.tgz (Root Library)
- optimist-0.6.1.tgz
- :x: **minimist-0.0.10.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>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.10","isTransitiveDependency":true,"dependencyTree":"http-server:0.9.0;optimist:0.6.1;minimist:0.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.2"}],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_defect
|
cve high detected in minimist tgz cve high severity vulnerability vulnerable library minimist tgz parse argument options library home page a href path to dependency file tmp ws scm webdataconnector package json path to vulnerable library tmp ws scm webdataconnector node modules optimist node modules minimist package json dependency hierarchy http server tgz root library optimist tgz x minimist tgz vulnerable library vulnerability details minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution minimist isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload vulnerabilityurl
| 0
|
18,843
| 24,754,040,025
|
IssuesEvent
|
2022-10-21 15:58:29
|
aiidateam/aiida-core
|
https://api.github.com/repos/aiidateam/aiida-core
|
closed
|
Mark relevant `Process` exit codes as `invalidates_cache=True`
|
priority/important type/enhancement topic/processes
|
There are a number of exit codes defined on processes by `aiida-core` that do not specify `invalidates_cache=True` even though they should.
|
1.0
|
Mark relevant `Process` exit codes as `invalidates_cache=True` - There are a number of exit codes defined on processes by `aiida-core` that do not specify `invalidates_cache=True` even though they should.
|
non_defect
|
mark relevant process exit codes as invalidates cache true there are a number of exit codes defined on processes by aiida core that do not specify invalidates cache true even though they should
| 0
|
14,002
| 2,789,838,671
|
IssuesEvent
|
2015-05-08 21:49:37
|
google/google-visualization-api-issues
|
https://api.github.com/repos/google/google-visualization-api-issues
|
opened
|
Bug: Sytle of Annotations on annotated timeline are wrong
|
Priority-Medium Type-Defect
|
Original [issue 258](https://code.google.com/p/google-visualization-api-issues/issues/detail?id=258) created by orwant on 2010-04-14T23:06:26.000Z:
<b>What steps will reproduce the problem? Please provide a link to a</b>
<b>demonstration page if at all possible, or attach code.</b>
1. Include both annotatedtimeline and table
2. Draw the annotatedtimeline with annotations
3. View the annotations scroll buttons
<b>What component is this issue related to (PieChart, LineChart, DataTable,</b>
Query, etc)? AnnotatedTimeline and Table
<b>Are you using the test environment (version 1.1)?</b>
(If you are not sure, answer NO) No
<b>What operating system and browser are you using?</b>
Mac OS X 10.6 and Firefox
<b>*********************************************************</b>
<b>For developers viewing this issue: please click the 'star' icon to be</b>
<b>notified of future changes, and to let us know how many of you are</b>
<b>interested in seeing it resolved.</b>
<b>*********************************************************</b>
|
1.0
|
Bug: Sytle of Annotations on annotated timeline are wrong - Original [issue 258](https://code.google.com/p/google-visualization-api-issues/issues/detail?id=258) created by orwant on 2010-04-14T23:06:26.000Z:
<b>What steps will reproduce the problem? Please provide a link to a</b>
<b>demonstration page if at all possible, or attach code.</b>
1. Include both annotatedtimeline and table
2. Draw the annotatedtimeline with annotations
3. View the annotations scroll buttons
<b>What component is this issue related to (PieChart, LineChart, DataTable,</b>
Query, etc)? AnnotatedTimeline and Table
<b>Are you using the test environment (version 1.1)?</b>
(If you are not sure, answer NO) No
<b>What operating system and browser are you using?</b>
Mac OS X 10.6 and Firefox
<b>*********************************************************</b>
<b>For developers viewing this issue: please click the 'star' icon to be</b>
<b>notified of future changes, and to let us know how many of you are</b>
<b>interested in seeing it resolved.</b>
<b>*********************************************************</b>
|
defect
|
bug sytle of annotations on annotated timeline are wrong original created by orwant on what steps will reproduce the problem please provide a link to a demonstration page if at all possible or attach code include both annotatedtimeline and table draw the annotatedtimeline with annotations view the annotations scroll buttons what component is this issue related to piechart linechart datatable query etc annotatedtimeline and table are you using the test environment version if you are not sure answer no no what operating system and browser are you using mac os x and firefox for developers viewing this issue please click the star icon to be notified of future changes and to let us know how many of you are interested in seeing it resolved
| 1
|
29,280
| 5,632,363,505
|
IssuesEvent
|
2017-04-05 16:24:34
|
BOINC/boinc
|
https://api.github.com/repos/BOINC/boinc
|
closed
|
Disk usage pie chart shows projects multiple times in the mouse-over
|
C: Manager P: Minor T: Defect
|
**Reported by Ageless on 19 Oct 37956691 20:26 UTC**
I got this question from TJM through the Enigma forums.
"Hello Jord,
Take a look at these graphs:
http://plikens.no-ip.net/plikens/298x81rav/Clipboard02.png
http://plikens.no-ip.net/plikens/297xwdcgj/bug1.png
at the second screen you can see that the tooltip shows 'boincsimap' instead of hydrogen@home. Purely cosmetic, but it's still a bug. Is it a known problem ?"
I then checked the pie chart on the right in my BOINC 5.10.30 and found I have two entries for Einstein@Home, both 55.30MB big. They are the same colour as well (pink).
If I then go further down the pie chart and check what projects the mouse-over says it 'sees', I notice that it finds the projects it found first again. I have duplicates of Einstein, Alpha BOINC, Hydrogen, LHC, Leiden Classical etc.
Something weird in the mouse-over code. And difficult to explain.
Migrated-From: http://boinc.berkeley.edu/trac/ticket/517
|
1.0
|
Disk usage pie chart shows projects multiple times in the mouse-over - **Reported by Ageless on 19 Oct 37956691 20:26 UTC**
I got this question from TJM through the Enigma forums.
"Hello Jord,
Take a look at these graphs:
http://plikens.no-ip.net/plikens/298x81rav/Clipboard02.png
http://plikens.no-ip.net/plikens/297xwdcgj/bug1.png
at the second screen you can see that the tooltip shows 'boincsimap' instead of hydrogen@home. Purely cosmetic, but it's still a bug. Is it a known problem ?"
I then checked the pie chart on the right in my BOINC 5.10.30 and found I have two entries for Einstein@Home, both 55.30MB big. They are the same colour as well (pink).
If I then go further down the pie chart and check what projects the mouse-over says it 'sees', I notice that it finds the projects it found first again. I have duplicates of Einstein, Alpha BOINC, Hydrogen, LHC, Leiden Classical etc.
Something weird in the mouse-over code. And difficult to explain.
Migrated-From: http://boinc.berkeley.edu/trac/ticket/517
|
defect
|
disk usage pie chart shows projects multiple times in the mouse over reported by ageless on oct utc i got this question from tjm through the enigma forums hello jord take a look at these graphs at the second screen you can see that the tooltip shows boincsimap instead of hydrogen home purely cosmetic but it s still a bug is it a known problem i then checked the pie chart on the right in my boinc and found i have two entries for einstein home both big they are the same colour as well pink if i then go further down the pie chart and check what projects the mouse over says it sees i notice that it finds the projects it found first again i have duplicates of einstein alpha boinc hydrogen lhc leiden classical etc something weird in the mouse over code and difficult to explain migrated from
| 1
|
27,824
| 5,109,205,695
|
IssuesEvent
|
2017-01-05 20:04:19
|
cakephp/cakephp
|
https://api.github.com/repos/cakephp/cakephp
|
closed
|
ServerRequest::input() is not returning the contents of php://input
|
Defect
|
This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: 3.4.0-beta3
* Platform and Target: Vagrant Debian-8.6 and using Postman to make a POST request
### What you did
I made a POST request to my app with Postman. This POST request consists of some header information (for the Digest authentication) and two other basic headers:
```
Accept:application/json
Authorization:Digest xxx
Content-Type:application/json
```
The body contains:
```
{
"message": "test"
}
```
In my controller (in my case, in the initialize() method, just after loading the `RequestHandler` component), I try to get the input of the sent JSON by using:
```
# load other components
$this->loadComponent('RequestHandler');
debug($this->request->input('json_decode'));
exit;
```
### What happened
No data was returned, in fact, I got `NULL`.
### What you expected to happen
I expected an object, containing my JSON data.
### Research
So I did some research.
Calling `$this->request->input()` returns the string `php://input`, which is weird. (I didn't even know what this was). So I Googled it, and found that this stream should contain my data. Calling `file_get_contents('php://input')` did in fact return my raw JSON. So, I know the server is receiving my data.
Upon further inspection and a lot of debugging later, I found that within ServerRequest, the $stream is [fed by the $config](https://github.com/cakephp/cakephp/blob/3.next/src/Http/ServerRequest.php#L327)
So, `debug($config)` then, gave me 'php://input' as well. Although the [docs of `$stream->write()`](https://github.com/php-fig/http-message/blob/master/src/StreamInterface.php#L109) say:
> * Write data to the stream.
* @param string $string The string that is to be written.
So, it expects that actual data, not the name of the stream/file.
But still, didn't know what was happening. So after some more research and great help of @hmic in the IRC, I figured it all out.
[ServerRequestFactory.php#L53](https://github.com/cakephp/cakephp/blob/3.next/src/Http/ServerRequestFactory.php#L53) is hard coding the string "php://input" to the config of ServerRequest despite the fact that [ServerRequest.php#L251](https://github.com/cakephp/cakephp/blob/3.next/src/Http/ServerRequest.php#L251) clearly states:
>`input` The data that would come from php://input this is useful for simulating requests with put, patch or delete data.
### It works in
Tested it with version 3.3.11, and in that version nothing is wrong. `$this->request->input()` returns exactly what I expect.
### Suggestion
I don't know. `file_get_contents()` wrapped around it? Or, I have no idea what is best practice in this case.
Also, after the hint from hmic and Neon1024 I did some unit testing. But I didn't seem to find any tests that actually tested this. So, maybe there is a step to make there as well?
|
1.0
|
ServerRequest::input() is not returning the contents of php://input - This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: 3.4.0-beta3
* Platform and Target: Vagrant Debian-8.6 and using Postman to make a POST request
### What you did
I made a POST request to my app with Postman. This POST request consists of some header information (for the Digest authentication) and two other basic headers:
```
Accept:application/json
Authorization:Digest xxx
Content-Type:application/json
```
The body contains:
```
{
"message": "test"
}
```
In my controller (in my case, in the initialize() method, just after loading the `RequestHandler` component), I try to get the input of the sent JSON by using:
```
# load other components
$this->loadComponent('RequestHandler');
debug($this->request->input('json_decode'));
exit;
```
### What happened
No data was returned, in fact, I got `NULL`.
### What you expected to happen
I expected an object, containing my JSON data.
### Research
So I did some research.
Calling `$this->request->input()` returns the string `php://input`, which is weird. (I didn't even know what this was). So I Googled it, and found that this stream should contain my data. Calling `file_get_contents('php://input')` did in fact return my raw JSON. So, I know the server is receiving my data.
Upon further inspection and a lot of debugging later, I found that within ServerRequest, the $stream is [fed by the $config](https://github.com/cakephp/cakephp/blob/3.next/src/Http/ServerRequest.php#L327)
So, `debug($config)` then, gave me 'php://input' as well. Although the [docs of `$stream->write()`](https://github.com/php-fig/http-message/blob/master/src/StreamInterface.php#L109) say:
> * Write data to the stream.
* @param string $string The string that is to be written.
So, it expects that actual data, not the name of the stream/file.
But still, didn't know what was happening. So after some more research and great help of @hmic in the IRC, I figured it all out.
[ServerRequestFactory.php#L53](https://github.com/cakephp/cakephp/blob/3.next/src/Http/ServerRequestFactory.php#L53) is hard coding the string "php://input" to the config of ServerRequest despite the fact that [ServerRequest.php#L251](https://github.com/cakephp/cakephp/blob/3.next/src/Http/ServerRequest.php#L251) clearly states:
>`input` The data that would come from php://input this is useful for simulating requests with put, patch or delete data.
### It works in
Tested it with version 3.3.11, and in that version nothing is wrong. `$this->request->input()` returns exactly what I expect.
### Suggestion
I don't know. `file_get_contents()` wrapped around it? Or, I have no idea what is best practice in this case.
Also, after the hint from hmic and Neon1024 I did some unit testing. But I didn't seem to find any tests that actually tested this. So, maybe there is a step to make there as well?
|
defect
|
serverrequest input is not returning the contents of php input this is a multiple allowed bug enhancement feature discussion rfc cakephp version platform and target vagrant debian and using postman to make a post request what you did i made a post request to my app with postman this post request consists of some header information for the digest authentication and two other basic headers accept application json authorization digest xxx content type application json the body contains message test in my controller in my case in the initialize method just after loading the requesthandler component i try to get the input of the sent json by using load other components this loadcomponent requesthandler debug this request input json decode exit what happened no data was returned in fact i got null what you expected to happen i expected an object containing my json data research so i did some research calling this request input returns the string php input which is weird i didn t even know what this was so i googled it and found that this stream should contain my data calling file get contents php input did in fact return my raw json so i know the server is receiving my data upon further inspection and a lot of debugging later i found that within serverrequest the stream is so debug config then gave me php input as well although the say write data to the stream param string string the string that is to be written so it expects that actual data not the name of the stream file but still didn t know what was happening so after some more research and great help of hmic in the irc i figured it all out is hard coding the string php input to the config of serverrequest despite the fact that clearly states input the data that would come from php input this is useful for simulating requests with put patch or delete data it works in tested it with version and in that version nothing is wrong this request input returns exactly what i expect suggestion i don t know file get contents wrapped around it or i have no idea what is best practice in this case also after the hint from hmic and i did some unit testing but i didn t seem to find any tests that actually tested this so maybe there is a step to make there as well
| 1
|
57,889
| 16,130,424,590
|
IssuesEvent
|
2021-04-29 03:13:27
|
Project-Sustain/aperture-client
|
https://api.github.com/repos/Project-Sustain/aperture-client
|
closed
|
More responsive / faster updating charts
|
defect
|
A lot of things that don't need to take a long time take a long time (e.g. a newly created graph takes ~2 seconds to display features that already exist on the map)
|
1.0
|
More responsive / faster updating charts - A lot of things that don't need to take a long time take a long time (e.g. a newly created graph takes ~2 seconds to display features that already exist on the map)
|
defect
|
more responsive faster updating charts a lot of things that don t need to take a long time take a long time e g a newly created graph takes seconds to display features that already exist on the map
| 1
|
660,411
| 21,965,063,368
|
IssuesEvent
|
2022-05-24 19:23:56
|
dnnsoftware/Dnn.Platform
|
https://api.github.com/repos/dnnsoftware/Dnn.Platform
|
closed
|
Removal of SharpZipLib
|
Effort: Medium Priority: Medium Type: Maintenance Status: On Hold
|
## Description of problem
DNN Platform is currently using SharpZipLib for some Zip operations. The usage of this should be reviewed and replaced with standard .NET Zip functionality if possible.
## Description of solution
Remove third-party dependency
## Description of alternatives considered
Leave the third-party solution
|
1.0
|
Removal of SharpZipLib - ## Description of problem
DNN Platform is currently using SharpZipLib for some Zip operations. The usage of this should be reviewed and replaced with standard .NET Zip functionality if possible.
## Description of solution
Remove third-party dependency
## Description of alternatives considered
Leave the third-party solution
|
non_defect
|
removal of sharpziplib description of problem dnn platform is currently using sharpziplib for some zip operations the usage of this should be reviewed and replaced with standard net zip functionality if possible description of solution remove third party dependency description of alternatives considered leave the third party solution
| 0
|
19,470
| 3,207,137,646
|
IssuesEvent
|
2015-10-05 08:52:17
|
hazelcast/hazelcast
|
https://api.github.com/repos/hazelcast/hazelcast
|
opened
|
[TEST-FAILURE] ClientMapNearCacheTest.testNearCacheInvalidation_WithRandom_whenMaxSizeExceeded
|
Team: Client Team: Core Type: Defect
|
```
java.lang.AssertionError: owned entry count 100
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at com.hazelcast.client.map.ClientMapNearCacheTest$10.run(ClientMapNearCacheTest.java:620)
at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:737)
at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:751)
at com.hazelcast.client.map.ClientMapNearCacheTest.testNearCacheInvalidation_WithRandom_whenMaxSizeExceeded(ClientMapNearCacheTest.java:614)
```
https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.maintenance-OpenJDK8/com.hazelcast$hazelcast-client-new/298/testReport/junit/com.hazelcast.client.map/ClientMapNearCacheTest/testNearCacheInvalidation_WithRandom_whenMaxSizeExceeded/
|
1.0
|
[TEST-FAILURE] ClientMapNearCacheTest.testNearCacheInvalidation_WithRandom_whenMaxSizeExceeded - ```
java.lang.AssertionError: owned entry count 100
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at com.hazelcast.client.map.ClientMapNearCacheTest$10.run(ClientMapNearCacheTest.java:620)
at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:737)
at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:751)
at com.hazelcast.client.map.ClientMapNearCacheTest.testNearCacheInvalidation_WithRandom_whenMaxSizeExceeded(ClientMapNearCacheTest.java:614)
```
https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.maintenance-OpenJDK8/com.hazelcast$hazelcast-client-new/298/testReport/junit/com.hazelcast.client.map/ClientMapNearCacheTest/testNearCacheInvalidation_WithRandom_whenMaxSizeExceeded/
|
defect
|
clientmapnearcachetest testnearcacheinvalidation withrandom whenmaxsizeexceeded java lang assertionerror owned entry count at org junit assert fail assert java at org junit assert asserttrue assert java at com hazelcast client map clientmapnearcachetest run clientmapnearcachetest java at com hazelcast test hazelcasttestsupport asserttrueeventually hazelcasttestsupport java at com hazelcast test hazelcasttestsupport asserttrueeventually hazelcasttestsupport java at com hazelcast client map clientmapnearcachetest testnearcacheinvalidation withrandom whenmaxsizeexceeded clientmapnearcachetest java
| 1
|
316,973
| 23,658,447,461
|
IssuesEvent
|
2022-08-26 13:28:52
|
sinanbekar/browser-extension-react-typescript-starter
|
https://api.github.com/repos/sinanbekar/browser-extension-react-typescript-starter
|
closed
|
How can I add script.js?
|
documentation question
|
Usually in vanilla js I use `content_script.js` that will inject `script.js` to the page but I can't find any example related to that?
```js
const container = document.head || document.documentElement
const scriptTag = document.createElement('script')
scriptTag.setAttribute('async', 'false')
scriptTag.src = chrome.runtime.getURL('script.js')
container.insertBefore(scriptTag, container.children[0])
container.removeChild(scriptTag)
```
Second question is where to place that `script.ts` to trigger `script.js` build and include it in `HMR`?
|
1.0
|
How can I add script.js? - Usually in vanilla js I use `content_script.js` that will inject `script.js` to the page but I can't find any example related to that?
```js
const container = document.head || document.documentElement
const scriptTag = document.createElement('script')
scriptTag.setAttribute('async', 'false')
scriptTag.src = chrome.runtime.getURL('script.js')
container.insertBefore(scriptTag, container.children[0])
container.removeChild(scriptTag)
```
Second question is where to place that `script.ts` to trigger `script.js` build and include it in `HMR`?
|
non_defect
|
how can i add script js usually in vanilla js i use content script js that will inject script js to the page but i can t find any example related to that js const container document head document documentelement const scripttag document createelement script scripttag setattribute async false scripttag src chrome runtime geturl script js container insertbefore scripttag container children container removechild scripttag second question is where to place that script ts to trigger script js build and include it in hmr
| 0
|
41,651
| 10,556,627,215
|
IssuesEvent
|
2019-10-04 02:43:39
|
zealdocs/zeal
|
https://api.github.com/repos/zealdocs/zeal
|
reopened
|
angular docset showing white screen
|
resolution/fixed scope/misc/docsets scope/ui/webview type/defect
|
Hi,
I'am using Zeal version 0.6.1 and every document in the angular (2+) docset is just showing a white page...
Every else docset I downloaded is working properly...
Hope for a fix soon. Greetings!
|
1.0
|
angular docset showing white screen - Hi,
I'am using Zeal version 0.6.1 and every document in the angular (2+) docset is just showing a white page...
Every else docset I downloaded is working properly...
Hope for a fix soon. Greetings!
|
defect
|
angular docset showing white screen hi i am using zeal version and every document in the angular docset is just showing a white page every else docset i downloaded is working properly hope for a fix soon greetings
| 1
|
22,255
| 3,619,494,822
|
IssuesEvent
|
2016-02-08 16:14:14
|
miracle091/transmission-remote-dotnet
|
https://api.github.com/repos/miracle091/transmission-remote-dotnet
|
closed
|
Transmission Crashing
|
Priority-Medium Type-Defect
|
```
Hello
Im using Transmission for a while now
I have upgraded my windows 7 to windows 8 Pro
Before this i had no issue's
But now when i wanna check automatic start
Transmission crashes, im using the latest version
Is this a known bug?
Regards Marco
```
Original issue reported on code.google.com by `Addicted...@gmail.com` on 1 Nov 2012 at 9:01
Attachments:
* [trdcrash_20121101_204438.log](https://storage.googleapis.com/google-code-attachments/transmission-remote-dotnet/issue-455/comment-0/trdcrash_20121101_204438.log)
|
1.0
|
Transmission Crashing - ```
Hello
Im using Transmission for a while now
I have upgraded my windows 7 to windows 8 Pro
Before this i had no issue's
But now when i wanna check automatic start
Transmission crashes, im using the latest version
Is this a known bug?
Regards Marco
```
Original issue reported on code.google.com by `Addicted...@gmail.com` on 1 Nov 2012 at 9:01
Attachments:
* [trdcrash_20121101_204438.log](https://storage.googleapis.com/google-code-attachments/transmission-remote-dotnet/issue-455/comment-0/trdcrash_20121101_204438.log)
|
defect
|
transmission crashing hello im using transmission for a while now i have upgraded my windows to windows pro before this i had no issue s but now when i wanna check automatic start transmission crashes im using the latest version is this a known bug regards marco original issue reported on code google com by addicted gmail com on nov at attachments
| 1
|
1,630
| 2,603,968,592
|
IssuesEvent
|
2015-02-24 18:59:41
|
chrsmith/nishazi6
|
https://api.github.com/repos/chrsmith/nishazi6
|
opened
|
沈阳包皮有小颗粒怎么回事
|
auto-migrated Priority-Medium Type-Defect
|
```
沈阳包皮有小颗粒怎么回事〓沈陽軍區政治部醫院性病〓TEL��
�024-31023308〓成立于1946年，68年專注于性傳播疾病的研究和治�
��。位于沈陽市沈河區二緯路32號。是一所與新中國同建立共�
��煌的歷史悠久、設備精良、技術權威、專家云集，是預防、
保健、醫療、科研康復為一體的綜合性醫院。是國家首批公��
�甲等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大�
��、東南大學等知名高等院校的教學醫院。曾被中國人民解放
軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立��
�體二等功。
```
-----
Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 7:18
|
1.0
|
沈阳包皮有小颗粒怎么回事 - ```
沈阳包皮有小颗粒怎么回事〓沈陽軍區政治部醫院性病〓TEL��
�024-31023308〓成立于1946年，68年專注于性傳播疾病的研究和治�
��。位于沈陽市沈河區二緯路32號。是一所與新中國同建立共�
��煌的歷史悠久、設備精良、技術權威、專家云集，是預防、
保健、醫療、科研康復為一體的綜合性醫院。是國家首批公��
�甲等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大�
��、東南大學等知名高等院校的教學醫院。曾被中國人民解放
軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立��
�體二等功。
```
-----
Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 7:18
|
defect
|
沈阳包皮有小颗粒怎么回事 沈阳包皮有小颗粒怎么回事〓沈陽軍區政治部醫院性病〓tel�� � 〓 ， � ��。 。是一所與新中國同建立共� ��煌的歷史悠久、設備精良、技術權威、專家云集，是預防、 保健、醫療、科研康復為一體的綜合性醫院。是國家首批公�� �甲等部隊醫院、全國首批醫療規范定點單位，是第四軍醫大� ��、東南大學等知名高等院校的教學醫院。曾被中國人民解放 軍空軍后勤部衛生部評為衛生工作先進單位，先后兩次榮立�� �體二等功。 original issue reported on code google com by gmail com on jun at
| 1
|
542,650
| 15,864,193,203
|
IssuesEvent
|
2021-04-08 13:35:41
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www.omegle.com - site is not usable
|
browser-firefox engine-gecko priority-normal
|
<!-- @browser: Firefox iOS 33.0 -->
<!-- @ua_header: Mozilla/5.0 (iPhone; CPU OS 12_5_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/33.0 Mobile/15E148 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/69781 -->
**URL**: https://www.omegle.com/
**Browser / Version**: Firefox iOS 33.0
**Operating System**: iOS 12.5.2
**Tested Another Browser**: Yes Safari
**Problem type**: Site is not usable
**Description**: Problems with Captcha
**Steps to Reproduce**:
Ayaw gumana pisti. Di ko alam kung bakit
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
www.omegle.com - site is not usable - <!-- @browser: Firefox iOS 33.0 -->
<!-- @ua_header: Mozilla/5.0 (iPhone; CPU OS 12_5_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/33.0 Mobile/15E148 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/69781 -->
**URL**: https://www.omegle.com/
**Browser / Version**: Firefox iOS 33.0
**Operating System**: iOS 12.5.2
**Tested Another Browser**: Yes Safari
**Problem type**: Site is not usable
**Description**: Problems with Captcha
**Steps to Reproduce**:
Ayaw gumana pisti. Di ko alam kung bakit
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_defect
|
site is not usable url browser version firefox ios operating system ios tested another browser yes safari problem type site is not usable description problems with captcha steps to reproduce ayaw gumana pisti di ko alam kung bakit browser configuration none from with ❤️
| 0
|
581,004
| 17,271,802,523
|
IssuesEvent
|
2021-07-22 20:56:59
|
googleapis/google-cloud-go
|
https://api.github.com/repos/googleapis/google-cloud-go
|
closed
|
bigtable: TestIntegration_AdminUpdateInstanceAndSyncClusters failed
|
:rotating_light: api: bigtable flakybot: flaky flakybot: issue priority: p1 type: bug
|
Note: #4178 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 32d68ec54f418da086940b6e2f74a0fd85f29fc9
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/7ac931dc-0aa3-4ff6-a001-60d58a16a415), [Sponge](http://sponge2/7ac931dc-0aa3-4ff6-a001-60d58a16a415)
status: failed
<details><summary>Test output</summary><br><pre> integration_test.go:1919: UpdateInstanceAndSyncClusters: &{bt-it-1625684909 [{ bt-it-1625684909-cluster 0 0 } { bt-it-1625684909-cluster-2 us-east1-c 3 0 }] 0 map[]} CreateCluster {bt-it-1625684909 bt-it-1625684909-cluster-2 us-east1-c 3 0 } failed context deadline exceeded; Progress: Instance updated? false Clusters added:[] Clusters deleted:[] Clusters updated:[]</pre></details>
|
1.0
|
bigtable: TestIntegration_AdminUpdateInstanceAndSyncClusters failed - Note: #4178 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 32d68ec54f418da086940b6e2f74a0fd85f29fc9
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/7ac931dc-0aa3-4ff6-a001-60d58a16a415), [Sponge](http://sponge2/7ac931dc-0aa3-4ff6-a001-60d58a16a415)
status: failed
<details><summary>Test output</summary><br><pre> integration_test.go:1919: UpdateInstanceAndSyncClusters: &{bt-it-1625684909 [{ bt-it-1625684909-cluster 0 0 } { bt-it-1625684909-cluster-2 us-east1-c 3 0 }] 0 map[]} CreateCluster {bt-it-1625684909 bt-it-1625684909-cluster-2 us-east1-c 3 0 } failed context deadline exceeded; Progress: Instance updated? false Clusters added:[] Clusters deleted:[] Clusters updated:[]</pre></details>
|
non_defect
|
bigtable testintegration adminupdateinstanceandsyncclusters failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output integration test go updateinstanceandsyncclusters bt it map createcluster bt it bt it cluster us c failed context deadline exceeded progress instance updated false clusters added clusters deleted clusters updated
| 0
|
6,892
| 2,610,302,641
|
IssuesEvent
|
2015-02-26 19:37:16
|
chrsmith/hedgewars
|
https://api.github.com/repos/chrsmith/hedgewars
|
closed
|
Lasersight steadies SniperRifle for 1/2 of the shots
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1. Use the Lasersight utility
2. Activate the Sniper Rifle
3. Fire
What is the expected output? What do you see instead?
The Sniper Rifle should remain deadly still and not waver up and down whilst
firing on your second shot.
OR
The Sniper Rifle should waver up and down on both shots.
```
-----
Original issue reported on code.google.com by `RedGrin...@gmail.com` on 22 Jun 2011 at 2:56
|
1.0
|
Lasersight steadies SniperRifle for 1/2 of the shots - ```
What steps will reproduce the problem?
1. Use the Lasersight utility
2. Activate the Sniper Rifle
3. Fire
What is the expected output? What do you see instead?
The Sniper Rifle should remain deadly still and not waver up and down whilst
firing on your second shot.
OR
The Sniper Rifle should waver up and down on both shots.
```
-----
Original issue reported on code.google.com by `RedGrin...@gmail.com` on 22 Jun 2011 at 2:56
|
defect
|
lasersight steadies sniperrifle for of the shots what steps will reproduce the problem use the lasersight utility activate the sniper rifle fire what is the expected output what do you see instead the sniper rifle should remain deadly still and not waver up and down whilst firing on your second shot or the sniper rifle should waver up and down on both shots original issue reported on code google com by redgrin gmail com on jun at
| 1
|
73,834
| 7,359,686,941
|
IssuesEvent
|
2018-03-10 09:59:57
|
GTNewHorizons/NewHorizons
|
https://api.github.com/repos/GTNewHorizons/NewHorizons
|
closed
|
electro magic nanosuit loses pollution protection
|
FixedInDev need to be tested
|
#### Which modpack version are you using?
2.0.2.7
#
#### If in multiplayer; On which server does this happen?
Private Server
#
#### What did you try to do, and what did you expect to happen?
I upgraded my nanosuit boots and helmet into the electro-magic versions, Nanosuit Boots of the Traveler and Nanosuit Goggles of Revealing.
#
#### What happend instead? (Attach screenshots if needed)
IC2 nanosuit protects against pollution effects (slowness, mining fatigue, weakness), but when I upgraded my boots and helm to electro-magic nanosuit variants, I lost that protection.
#
#### What do you suggest instead/what changes do you propose?
I propose to keep that protection. Make it consistent with the IC2 nanosuit behavior.
|
1.0
|
electro magic nanosuit loses pollution protection - #### Which modpack version are you using?
2.0.2.7
#
#### If in multiplayer; On which server does this happen?
Private Server
#
#### What did you try to do, and what did you expect to happen?
I upgraded my nanosuit boots and helmet into the electro-magic versions, Nanosuit Boots of the Traveler and Nanosuit Goggles of Revealing.
#
#### What happend instead? (Attach screenshots if needed)
IC2 nanosuit protects against pollution effects (slowness, mining fatigue, weakness), but when I upgraded my boots and helm to electro-magic nanosuit variants, I lost that protection.
#
#### What do you suggest instead/what changes do you propose?
I propose to keep that protection. Make it consistent with the IC2 nanosuit behavior.
|
non_defect
|
electro magic nanosuit loses pollution protection which modpack version are you using if in multiplayer on which server does this happen private server what did you try to do and what did you expect to happen i upgraded my nanosuit boots and helmet into the electro magic versions nanosuit boots of the traveler and nanosuit goggles of revealing what happend instead attach screenshots if needed nanosuit protects against pollution effects slowness mining fatigue weakness but when i upgraded my boots and helm to electro magic nanosuit variants i lost that protection what do you suggest instead what changes do you propose i propose to keep that protection make it consistent with the nanosuit behavior
| 0
|
580,917
| 17,269,972,351
|
IssuesEvent
|
2021-07-22 18:24:38
|
episphere/connectApp
|
https://api.github.com/repos/episphere/connectApp
|
closed
|
[DM] A50 subsequent skip pattern missing- was not directed to A51
|
High Priority MVP Mod 1
|
Selected "TYPE 1" (0) FOR A50 [DM] "what type of diabetes did a doctor or other health professional tell you you have or had?" and was not redirected to A51 [DM2] "How old were you when a doctor or other health professional first told you that you have or had diabetes?"
Instead I was directed to A52 [GRAVES] " How old were you when a doctor or other health professional first told you that you have or had Graves’ disease?" (I did select Graves as a response for A48, so that was ok, but I think I was supposed to see the A51 diabetes age question before that)
|
1.0
|
[DM] A50 subsequent skip pattern missing- was not directed to A51 - Selected "TYPE 1" (0) FOR A50 [DM] "what type of diabetes did a doctor or other health professional tell you you have or had?" and was not redirected to A51 [DM2] "How old were you when a doctor or other health professional first told you that you have or had diabetes?"
Instead I was directed to A52 [GRAVES] " How old were you when a doctor or other health professional first told you that you have or had Graves’ disease?" (I did select Graves as a response for A48, so that was ok, but I think I was supposed to see the A51 diabetes age question before that)
|
non_defect
|
subsequent skip pattern missing was not directed to selected type for what type of diabetes did a doctor or other health professional tell you you have or had and was not redirected to how old were you when a doctor or other health professional first told you that you have or had diabetes instead i was directed to how old were you when a doctor or other health professional first told you that you have or had graves’ disease i did select graves as a response for so that was ok but i think i was supposed to see the diabetes age question before that
| 0
|
78,409
| 27,510,709,491
|
IssuesEvent
|
2023-03-06 08:35:35
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
closed
|
"Error decrypting image" bubble should be styled
|
T-Defect S-Tolerable X-Needs-Design A-Error-Message A-Message-Bubbles O-Uncommon
|
### Steps to reproduce
1. Enable bubble layout
1. Send an image file to a room
2. Reload Element offline
### Outcome
#### What did you expect?
The error message should be styled properly.
#### What happened instead?
It is displayed as below.
### Operating system
Debian
### Browser information
Firefox ESR 91
### URL for webapp
localhost
### Application version
develop branch
### Homeserver
_No response_
### Will you send logs?
No
|
1.0
|
"Error decrypting image" bubble should be styled - ### Steps to reproduce
1. Enable bubble layout
1. Send an image file to a room
2. Reload Element offline
### Outcome
#### What did you expect?
The error message should be styled properly.
#### What happened instead?
It is displayed as below.
### Operating system
Debian
### Browser information
Firefox ESR 91
### URL for webapp
localhost
### Application version
develop branch
### Homeserver
_No response_
### Will you send logs?
No
|
defect
|
error decrypting image bubble should be styled steps to reproduce enable bubble layout send an image file to a room reload element offline outcome what did you expect the error message should be styled properly what happened instead it is displayed as below operating system debian browser information firefox esr url for webapp localhost application version develop branch homeserver no response will you send logs no
| 1
|
40,526
| 10,029,381,970
|
IssuesEvent
|
2019-07-17 13:49:37
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
closed
|
DefaultRecordMapper cannot map into generic type variable in Kotlin
|
C: Functionality E: All Editions P: Medium R: Fixed T: Defect
|
### Expected behavior and actual behavior:
I have a test code like this:
```kotlin
create
.select(
DSL.one().`as`("group"),
DSL.two().`as`("count")
)
.fetchInto(GroupCountResponse::class.java)
.forEach { println(it) }
```
And there is a kotlin data class like this:
```kotlin
data class GroupCountResponse<T> (
val group: T,
val count: Long
)
```
Executing this code will cause an exception:
```
2019-04-30 11:24:33.301 INFO 20500 --- [ main] c.x.e.a.config.handler.SQLBaseListener : select
1 as "group",
2 as "count"
java.lang.IllegalArgumentException: argument type mismatch
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.jooq.impl.DefaultRecordMapper.init(DefaultRecordMapper.java:407)
at org.jooq.impl.DefaultRecordMapper.<init>(DefaultRecordMapper.java:314)
at org.jooq.impl.DefaultRecordMapper.<init>(DefaultRecordMapper.java:305)
at org.jooq.impl.DefaultRecordMapperProvider$1.call(DefaultRecordMapperProvider.java:87)
at org.jooq.impl.DefaultRecordMapperProvider$1.call(DefaultRecordMapperProvider.java:84)
at org.jooq.impl.Tools$Cache.run(Tools.java:2882)
at org.jooq.impl.DefaultRecordMapperProvider.provide(DefaultRecordMapperProvider.java:84)
at org.jooq.impl.ResultImpl.into(ResultImpl.java:1369)
at org.jooq.impl.AbstractResultQuery.fetchInto(AbstractResultQuery.java:1440)
at org.jooq.impl.SelectImpl.fetchInto(SelectImpl.java:3741)
at com.xhstormr.erp.JooqTests.test1(JooqTests.kt:28)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:675)
at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:117)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:185)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:181)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:128)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:135)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
```
As workaround, I add the @ConstructorProperties annotation:
```kotlin
data class GroupCountResponse<T> @ConstructorProperties(value = ["group", "count"]) constructor(
val group: T,
val count: Long
)
```
I passed the test:
```
2019-04-30 11:22:48.651 INFO 61728 --- [ main] c.x.e.a.config.handler.SQLBaseListener : select
1 as "group",
2 as "count"
GroupCountResponse(group=1, count=2)
```
I looked at the source code, it seems that this line of code has a bug, It seems that this code will reflect the call to the getJavaClass method in kotlin:
https://github.com/jOOQ/jOOQ/blob/master/jOOQ/src/main/java/org/jooq/impl/DefaultRecordMapper.java#L407
The kotlin version I am using is the latest 1.3.31. This version of the getJavaClass method does not require parameters, maybe the problem is here:
https://github.com/JetBrains/kotlin/blob/master/libraries/stdlib/jvm/runtime/kotlin/jvm/JvmClassMapping.kt#L27
### Steps to reproduce the problem (if possible, create an MCVE: https://github.com/jOOQ/jOOQ-mcve):
### Versions:
- jOOQ: org.jooq:jooq:3.11.10
- Java: "12.0.1"
- Database (include vendor): Postgresql 11
- OS: Windows 10
- JDBC Driver (include name if inofficial driver): org.postgresql:postgresql:42.2.5
|
1.0
|
DefaultRecordMapper cannot map into generic type variable in Kotlin - ### Expected behavior and actual behavior:
I have a test code like this:
```kotlin
create
.select(
DSL.one().`as`("group"),
DSL.two().`as`("count")
)
.fetchInto(GroupCountResponse::class.java)
.forEach { println(it) }
```
And there is a kotlin data class like this:
```kotlin
data class GroupCountResponse<T> (
val group: T,
val count: Long
)
```
Executing this code will cause an exception:
```
2019-04-30 11:24:33.301 INFO 20500 --- [ main] c.x.e.a.config.handler.SQLBaseListener : select
1 as "group",
2 as "count"
java.lang.IllegalArgumentException: argument type mismatch
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.jooq.impl.DefaultRecordMapper.init(DefaultRecordMapper.java:407)
at org.jooq.impl.DefaultRecordMapper.<init>(DefaultRecordMapper.java:314)
at org.jooq.impl.DefaultRecordMapper.<init>(DefaultRecordMapper.java:305)
at org.jooq.impl.DefaultRecordMapperProvider$1.call(DefaultRecordMapperProvider.java:87)
at org.jooq.impl.DefaultRecordMapperProvider$1.call(DefaultRecordMapperProvider.java:84)
at org.jooq.impl.Tools$Cache.run(Tools.java:2882)
at org.jooq.impl.DefaultRecordMapperProvider.provide(DefaultRecordMapperProvider.java:84)
at org.jooq.impl.ResultImpl.into(ResultImpl.java:1369)
at org.jooq.impl.AbstractResultQuery.fetchInto(AbstractResultQuery.java:1440)
at org.jooq.impl.SelectImpl.fetchInto(SelectImpl.java:3741)
at com.xhstormr.erp.JooqTests.test1(JooqTests.kt:28)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:675)
at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:117)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:185)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:181)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:128)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:135)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
```
As workaround, I add the @ConstructorProperties annotation:
```kotlin
data class GroupCountResponse<T> @ConstructorProperties(value = ["group", "count"]) constructor(
val group: T,
val count: Long
)
```
I passed the test:
```
2019-04-30 11:22:48.651 INFO 61728 --- [ main] c.x.e.a.config.handler.SQLBaseListener : select
1 as "group",
2 as "count"
GroupCountResponse(group=1, count=2)
```
I looked at the source code, it seems that this line of code has a bug, It seems that this code will reflect the call to the getJavaClass method in kotlin:
https://github.com/jOOQ/jOOQ/blob/master/jOOQ/src/main/java/org/jooq/impl/DefaultRecordMapper.java#L407
The kotlin version I am using is the latest 1.3.31. This version of the getJavaClass method does not require parameters, maybe the problem is here:
https://github.com/JetBrains/kotlin/blob/master/libraries/stdlib/jvm/runtime/kotlin/jvm/JvmClassMapping.kt#L27
### Steps to reproduce the problem (if possible, create an MCVE: https://github.com/jOOQ/jOOQ-mcve):
### Versions:
- jOOQ: org.jooq:jooq:3.11.10
- Java: "12.0.1"
- Database (include vendor): Postgresql 11
- OS: Windows 10
- JDBC Driver (include name if inofficial driver): org.postgresql:postgresql:42.2.5
|
defect
|
defaultrecordmapper cannot map into generic type variable in kotlin expected behavior and actual behavior i have a test code like this kotlin create select dsl one as group dsl two as count fetchinto groupcountresponse class java foreach println it and there is a kotlin data class like this kotlin data class groupcountresponse val group t val count long executing this code will cause an exception info c x e a config handler sqlbaselistener select as group as count java lang illegalargumentexception argument type mismatch at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org jooq impl defaultrecordmapper init defaultrecordmapper java at org jooq impl defaultrecordmapper defaultrecordmapper java at org jooq impl defaultrecordmapper defaultrecordmapper java at org jooq impl defaultrecordmapperprovider call defaultrecordmapperprovider java at org jooq impl defaultrecordmapperprovider call defaultrecordmapperprovider java at org jooq impl tools cache run tools java at org jooq impl defaultrecordmapperprovider provide defaultrecordmapperprovider java at org jooq impl resultimpl into resultimpl java at org jooq impl abstractresultquery fetchinto abstractresultquery java at org jooq impl selectimpl fetchinto selectimpl java at com xhstormr erp jooqtests jooqtests kt at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org junit platform commons util reflectionutils invokemethod reflectionutils java at org junit jupiter engine execution executableinvoker invoke executableinvoker java at org junit jupiter engine descriptor testmethodtestdescriptor lambda invoketestmethod testmethodtestdescriptor java at org junit platform engine support hierarchical throwablecollector execute throwablecollector java at org junit jupiter engine descriptor testmethodtestdescriptor invoketestmethod testmethodtestdescriptor java at org junit jupiter engine descriptor testmethodtestdescriptor execute testmethodtestdescriptor java at org junit jupiter engine descriptor testmethodtestdescriptor execute testmethodtestdescriptor java at org junit platform engine support hierarchical nodetesttask lambda executerecursively nodetesttask java at org junit platform engine support hierarchical throwablecollector execute throwablecollector java at org junit platform engine support hierarchical nodetesttask lambda executerecursively nodetesttask java at org junit platform engine support hierarchical node around node java at org junit platform engine support hierarchical nodetesttask lambda executerecursively nodetesttask java at org junit platform engine support hierarchical throwablecollector execute throwablecollector java at org junit platform engine support hierarchical nodetesttask executerecursively nodetesttask java at org junit platform engine support hierarchical nodetesttask execute nodetesttask java as workaround i add the constructorproperties annotation kotlin data class groupcountresponse constructorproperties value constructor val group t val count long i passed the test info c x e a config handler sqlbaselistener select as group as count groupcountresponse group count i looked at the source code it seems that this line of code has a bug it seems that this code will reflect the call to the getjavaclass method in kotlin the kotlin version i am using is the latest this version of the getjavaclass method does not require parameters maybe the problem is here steps to reproduce the problem if possible create an mcve versions jooq org jooq jooq java database include vendor postgresql os windows jdbc driver include name if inofficial driver org postgresql postgresql
| 1
|
153,085
| 13,493,567,952
|
IssuesEvent
|
2020-09-11 19:53:21
|
pacien/ldgallery
|
https://api.github.com/repos/pacien/ldgallery
|
closed
|
viewer: config override via URL parameters
|
class:enhancement component:viewer documentation
|
It would be nice to be able to override settings from the viewer's config.json using URL parameters.
This would allow, for instance, loading another gallery index or use another theme.
(Implementation of this may conflict with the search query parameters in the URL, but we can probably find a way around that.)
|
1.0
|
viewer: config override via URL parameters - It would be nice to be able to override settings from the viewer's config.json using URL parameters.
This would allow, for instance, loading another gallery index or use another theme.
(Implementation of this may conflict with the search query parameters in the URL, but we can probably find a way around that.)
|
non_defect
|
viewer config override via url parameters it would be nice to be able to override settings from the viewer s config json using url parameters this would allow for instance loading another gallery index or use another theme implementation of this may conflict with the search query parameters in the url but we can probably find a way around that
| 0
|
9,457
| 2,615,151,133
|
IssuesEvent
|
2015-03-01 06:28:34
|
chrsmith/reaver-wps
|
https://api.github.com/repos/chrsmith/reaver-wps
|
closed
|
Reaver is not able to keep right channel on a newest build
|
auto-migrated Priority-Triage Type-Defect
|
```
A few things to consider before submitting an issue:
There is a bug on a newest source. Reaver worked right before. But on a newest
source Reaver changes channel every time when need to try new pin.
Log:
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 11
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Trying pin 12345670
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 11
[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Sending EAPOL START request
```
Original issue reported on code.google.com by `juuso...@gmail.com` on 23 Jan 2012 at 9:25
|
1.0
|
Reaver is not able to keep right channel on a newest build - ```
A few things to consider before submitting an issue:
There is a bug on a newest source. Reaver worked right before. But on a newest
source Reaver changes channel every time when need to try new pin.
Log:
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 11
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Trying pin 12345670
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 11
[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Sending EAPOL START request
```
Original issue reported on code.google.com by `juuso...@gmail.com` on 23 Jan 2012 at 9:25
|
defect
|
reaver is not able to keep right channel on a newest build a few things to consider before submitting an issue there is a bug on a newest source reaver worked right before but on a newest source reaver changes channel every time when need to try new pin log reaver i b xx xx xx xx xx xx vv reaver wifi protected setup attack tool copyright c tactical network solutions craig heffner waiting for beacon from xx xx xx xx xx xx switching to channel switching to channel switching to channel switching to channel switching to channel switching to channel associated with xx xx xx xx xx xx essid xxxxxx trying pin switching to channel switching to channel switching to channel switching to channel switching to channel switching to channel switching to channel switching to channel warning failed to associate with xx xx xx xx xx xx essid xxxxxx sending eapol start request original issue reported on code google com by juuso gmail com on jan at
| 1
|
782,215
| 27,490,482,868
|
IssuesEvent
|
2023-03-04 15:03:53
|
wso2/api-manager
|
https://api.github.com/repos/wso2/api-manager
|
closed
|
APICTL tool is not available for Mac arm64
|
Type/Task Priority/High Component/APICTL
|
### Description
Released binaries are not available for Mac arm64. But the mac amd64 is working with my Mac m1 maybe because I have already installed Rosetta2. It is nice to have a separate binary for mac arm64.
### Affected Component
APICTL
### Version
4.1.0
### Related Issues
_No response_
### Suggested Labels
_No response_
|
1.0
|
APICTL tool is not available for Mac arm64 - ### Description
Released binaries are not available for Mac arm64. But the mac amd64 is working with my Mac m1 maybe because I have already installed Rosetta2. It is nice to have a separate binary for mac arm64.
### Affected Component
APICTL
### Version
4.1.0
### Related Issues
_No response_
### Suggested Labels
_No response_
|
non_defect
|
apictl tool is not available for mac description released binaries are not available for mac but the mac is working with my mac maybe because i have already installed it is nice to have a separate binary for mac affected component apictl version related issues no response suggested labels no response
| 0
|
507,760
| 14,680,169,966
|
IssuesEvent
|
2020-12-31 09:15:44
|
k8smeetup/website-tasks
|
https://api.github.com/repos/k8smeetup/website-tasks
|
opened
|
/docs/tutorials/kubernetes-basics/scale/scale-interactive.html
|
lang/zh priority/P0 sync/update version/master welcome
|
Source File: [/docs/tutorials/kubernetes-basics/scale/scale-interactive.html](https://github.com/kubernetes/website/blob/master/content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html)
Diff 命令参考:
```bash
# 查看原始文档与翻译文档更新差异
git diff --no-index -- content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html content/zh/docs/tutorials/kubernetes-basics/scale/scale-interactive.html
# 跨分支持查看原始文档更新差异
git diff release-1.19 master -- content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html
```
|
1.0
|
/docs/tutorials/kubernetes-basics/scale/scale-interactive.html - Source File: [/docs/tutorials/kubernetes-basics/scale/scale-interactive.html](https://github.com/kubernetes/website/blob/master/content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html)
Diff 命令参考:
```bash
# 查看原始文档与翻译文档更新差异
git diff --no-index -- content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html content/zh/docs/tutorials/kubernetes-basics/scale/scale-interactive.html
# 跨分支持查看原始文档更新差异
git diff release-1.19 master -- content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html
```
|
non_defect
|
docs tutorials kubernetes basics scale scale interactive html source file diff 命令参考 bash 查看原始文档与翻译文档更新差异 git diff no index content en docs tutorials kubernetes basics scale scale interactive html content zh docs tutorials kubernetes basics scale scale interactive html 跨分支持查看原始文档更新差异 git diff release master content en docs tutorials kubernetes basics scale scale interactive html
| 0
|
103,240
| 16,602,035,580
|
IssuesEvent
|
2021-06-01 20:57:13
|
samq-ghdemo/SEARCH-NCJIS-nibrs
|
https://api.github.com/repos/samq-ghdemo/SEARCH-NCJIS-nibrs
|
opened
|
CVE-2018-11761 (High) detected in tika-core-1.18.jar
|
security vulnerability
|
## CVE-2018-11761 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tika-core-1.18.jar</b></p></summary>
<p>This is the core Apache Tika™ toolkit library from which all other modules inherit functionality. It also
includes the core facades for the Tika API.</p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/tools/nibrs-common/pom.xml</p>
<p>Path to vulnerable library: SEARCH-NCJIS-nibrs/web/nibrs-web/target/nibrs-web/WEB-INF/lib/tika-core-1.18.jar,canner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,canner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar</p>
<p>
Dependency Hierarchy:
- :x: **tika-core-1.18.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/SEARCH-NCJIS-nibrs/commit/2643373aa9a184ff4ea81e98caf4009bf2ee8e91">2643373aa9a184ff4ea81e98caf4009bf2ee8e91</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>
In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.
<p>Publish Date: 2018-09-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11761>CVE-2018-11761</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://lists.apache.org/thread.html/5553e10bba5604117967466618f219c0cae710075819c70cfb3fb421@%3Cdev.tika.apache.org%3E">https://lists.apache.org/thread.html/5553e10bba5604117967466618f219c0cae710075819c70cfb3fb421@%3Cdev.tika.apache.org%3E</a></p>
<p>Release Date: 2018-09-19</p>
<p>Fix Resolution: 1.19</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tika","packageName":"tika-core","packageVersion":"1.18","packageFilePaths":["/tools/nibrs-common/pom.xml","/web/nibrs-web/pom.xml","/tools/nibrs-xmlfile/pom.xml","/tools/nibrs-flatfile/pom.xml","/tools/nibrs-validate-common/pom.xml","/tools/nibrs-fbi-service/pom.xml","/tools/nibrs-summary-report/pom.xml","/tools/nibrs-staging-data/pom.xml","/tools/nibrs-summary-report-common/pom.xml","/tools/nibrs-validation/pom.xml","/tools/nibrs-staging-data-common/pom.xml","/tools/nibrs-route/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.apache.tika:tika-core:1.18","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.19"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-11761","vulnerabilityDetails":"In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11761","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-11761 (High) detected in tika-core-1.18.jar - ## CVE-2018-11761 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tika-core-1.18.jar</b></p></summary>
<p>This is the core Apache Tika™ toolkit library from which all other modules inherit functionality. It also
includes the core facades for the Tika API.</p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/tools/nibrs-common/pom.xml</p>
<p>Path to vulnerable library: SEARCH-NCJIS-nibrs/web/nibrs-web/target/nibrs-web/WEB-INF/lib/tika-core-1.18.jar,canner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,canner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar,/home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.18/tika-core-1.18.jar</p>
<p>
Dependency Hierarchy:
- :x: **tika-core-1.18.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/SEARCH-NCJIS-nibrs/commit/2643373aa9a184ff4ea81e98caf4009bf2ee8e91">2643373aa9a184ff4ea81e98caf4009bf2ee8e91</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>
In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.
<p>Publish Date: 2018-09-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11761>CVE-2018-11761</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://lists.apache.org/thread.html/5553e10bba5604117967466618f219c0cae710075819c70cfb3fb421@%3Cdev.tika.apache.org%3E">https://lists.apache.org/thread.html/5553e10bba5604117967466618f219c0cae710075819c70cfb3fb421@%3Cdev.tika.apache.org%3E</a></p>
<p>Release Date: 2018-09-19</p>
<p>Fix Resolution: 1.19</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tika","packageName":"tika-core","packageVersion":"1.18","packageFilePaths":["/tools/nibrs-common/pom.xml","/web/nibrs-web/pom.xml","/tools/nibrs-xmlfile/pom.xml","/tools/nibrs-flatfile/pom.xml","/tools/nibrs-validate-common/pom.xml","/tools/nibrs-fbi-service/pom.xml","/tools/nibrs-summary-report/pom.xml","/tools/nibrs-staging-data/pom.xml","/tools/nibrs-summary-report-common/pom.xml","/tools/nibrs-validation/pom.xml","/tools/nibrs-staging-data-common/pom.xml","/tools/nibrs-route/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.apache.tika:tika-core:1.18","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.19"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-11761","vulnerabilityDetails":"In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11761","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_defect
|
cve high detected in tika core jar cve high severity vulnerability vulnerable library tika core jar this is the core apache tika™ toolkit library from which all other modules inherit functionality it also includes the core facades for the tika api path to dependency file search ncjis nibrs tools nibrs common pom xml path to vulnerable library search ncjis nibrs web nibrs web target nibrs web web inf lib tika core jar canner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar canner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar home wss scanner repository org apache tika tika core tika core jar dependency hierarchy x tika core jar vulnerable library found in head commit a href found in base branch master vulnerability details in apache tika to the xml parsers were not configured to limit entity expansion they were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org apache tika tika core isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails in apache tika to the xml parsers were not configured to limit entity expansion they were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack vulnerabilityurl
| 0
|
11,299
| 2,648,925,698
|
IssuesEvent
|
2015-03-14 12:05:53
|
jancona/android-on-freerunner
|
https://api.github.com/repos/jancona/android-on-freerunner
|
reopened
|
Problem in recording audio on Froyo
|
auto-migrated invalid Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1. Start Speech Recorder
2. Press Record Button
3. Watch the app die
What is the expected output? What do you see instead?
A message saying the application is crashed.
What version of the product are you using? On what operating system?
I'm using the build android-on-freerunner-froyo-daily-20110707.tar.gz from
ran000
Please provide any additional information below.
The same error happens with Voice Dialer also.
logcat output:
I/ActivityManager( 956): Displayed activity
com.android.speechrecorder/.SpeechRecorderActivity: 1574 ms (total 1574 ms)
D/SpeechRecorderActivity( 2207): mRecord.OnClickListener.onClick
D/SpeechRecorderActivity( 2207): setupRecording
D/SpeechRecorderActivity( 2207): going to record
/data/data/com.android.speechrecorder/app_recordings/call_adam_varro.wav
D/dalvikvm( 2207): GC_FOR_MALLOC freed 1035 objects / 71016 bytes in 111ms
D/ALSAModule( 906): open called for devices 00040000 in mode 0...
E/ALSAModule( 906): Unable to set channel count to 1: Invalid argument
I/ALSAModule( 906): Initialized ALSA CAPTURE device AndroidCapture
D/ALSAModule( 906): open called for devices 00040000 in mode 0...
E/ALSAModule( 906): Unable to set channel count to 1: Invalid argument
I/ALSAModule( 906): Initialized ALSA CAPTURE device AndroidCapture
E/AudioRecord( 2207): Could not get audio input for record source 1
E/srec_jni( 2207): initCheck error -22
D/SpeechRecorderActivity( 2207): run audio capture thread
W/dalvikvm( 2207): threadid=7: thread exiting with uncaught exception
(group=0x4001d7e8)
E/AndroidRuntime( 2207): FATAL EXCEPTION: Thread-8
E/AndroidRuntime( 2207): java.lang.NullPointerException
E/AndroidRuntime( 2207): at
com.android.speechrecorder.SpeechRecorderActivity$4.run(SpeechRecorderActivity.j
ava:192)
W/ActivityManager( 956): Force finishing activity
com.android.speechrecorder/.SpeechRecorderActivity
W/ActivityManager( 956): Activity pause timeout for HistoryRecord{43dd34a8
com.android.speechrecorder/.SpeechRecorderActivity}
I/ActivityManager( 956): Process android.process.media (pid 2024) has died.
D/SpeechRecorderActivity( 2207): stopRecording
```
Original issue reported on code.google.com by `deli...@gmail.com` on 25 Jul 2011 at 7:15
|
1.0
|
Problem in recording audio on Froyo - ```
What steps will reproduce the problem?
1. Start Speech Recorder
2. Press Record Button
3. Watch the app die
What is the expected output? What do you see instead?
A message saying the application is crashed.
What version of the product are you using? On what operating system?
I'm using the build android-on-freerunner-froyo-daily-20110707.tar.gz from
ran000
Please provide any additional information below.
The same error happens with Voice Dialer also.
logcat output:
I/ActivityManager( 956): Displayed activity
com.android.speechrecorder/.SpeechRecorderActivity: 1574 ms (total 1574 ms)
D/SpeechRecorderActivity( 2207): mRecord.OnClickListener.onClick
D/SpeechRecorderActivity( 2207): setupRecording
D/SpeechRecorderActivity( 2207): going to record
/data/data/com.android.speechrecorder/app_recordings/call_adam_varro.wav
D/dalvikvm( 2207): GC_FOR_MALLOC freed 1035 objects / 71016 bytes in 111ms
D/ALSAModule( 906): open called for devices 00040000 in mode 0...
E/ALSAModule( 906): Unable to set channel count to 1: Invalid argument
I/ALSAModule( 906): Initialized ALSA CAPTURE device AndroidCapture
D/ALSAModule( 906): open called for devices 00040000 in mode 0...
E/ALSAModule( 906): Unable to set channel count to 1: Invalid argument
I/ALSAModule( 906): Initialized ALSA CAPTURE device AndroidCapture
E/AudioRecord( 2207): Could not get audio input for record source 1
E/srec_jni( 2207): initCheck error -22
D/SpeechRecorderActivity( 2207): run audio capture thread
W/dalvikvm( 2207): threadid=7: thread exiting with uncaught exception
(group=0x4001d7e8)
E/AndroidRuntime( 2207): FATAL EXCEPTION: Thread-8
E/AndroidRuntime( 2207): java.lang.NullPointerException
E/AndroidRuntime( 2207): at
com.android.speechrecorder.SpeechRecorderActivity$4.run(SpeechRecorderActivity.j
ava:192)
W/ActivityManager( 956): Force finishing activity
com.android.speechrecorder/.SpeechRecorderActivity
W/ActivityManager( 956): Activity pause timeout for HistoryRecord{43dd34a8
com.android.speechrecorder/.SpeechRecorderActivity}
I/ActivityManager( 956): Process android.process.media (pid 2024) has died.
D/SpeechRecorderActivity( 2207): stopRecording
```
Original issue reported on code.google.com by `deli...@gmail.com` on 25 Jul 2011 at 7:15
|
defect
|
problem in recording audio on froyo what steps will reproduce the problem start speech recorder press record button watch the app die what is the expected output what do you see instead a message saying the application is crashed what version of the product are you using on what operating system i m using the build android on freerunner froyo daily tar gz from please provide any additional information below the same error happens with voice dialer also logcat output i activitymanager displayed activity com android speechrecorder speechrecorderactivity ms total ms d speechrecorderactivity mrecord onclicklistener onclick d speechrecorderactivity setuprecording d speechrecorderactivity going to record data data com android speechrecorder app recordings call adam varro wav d dalvikvm gc for malloc freed objects bytes in d alsamodule open called for devices in mode e alsamodule unable to set channel count to invalid argument i alsamodule initialized alsa capture device androidcapture d alsamodule open called for devices in mode e alsamodule unable to set channel count to invalid argument i alsamodule initialized alsa capture device androidcapture e audiorecord could not get audio input for record source e srec jni initcheck error d speechrecorderactivity run audio capture thread w dalvikvm threadid thread exiting with uncaught exception group e androidruntime fatal exception thread e androidruntime java lang nullpointerexception e androidruntime at com android speechrecorder speechrecorderactivity run speechrecorderactivity j ava w activitymanager force finishing activity com android speechrecorder speechrecorderactivity w activitymanager activity pause timeout for historyrecord com android speechrecorder speechrecorderactivity i activitymanager process android process media pid has died d speechrecorderactivity stoprecording original issue reported on code google com by deli gmail com on jul at
| 1
|
22,267
| 3,619,718,395
|
IssuesEvent
|
2016-02-08 17:02:27
|
miracle091/transmission-remote-dotnet
|
https://api.github.com/repos/miracle091/transmission-remote-dotnet
|
closed
|
Crash while in RSS dialog
|
Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
No idea - I was adding and editing RSS feeds and it crashed - I've attached the
crash log file.
What is the expected output? What do you see instead?
Shouldn't crash.
What version of the products are you using?
OS: Windows 7
Transmission: 1.91 (10268)
Remote: TRD (Release build 3.24.0.0)
```
Original issue reported on code.google.com by `richard....@gmail.com` on 25 Jan 2011 at 8:46
Attachments:
* [trdcrash_20110124_081326.log](https://storage.googleapis.com/google-code-attachments/transmission-remote-dotnet/issue-364/comment-0/trdcrash_20110124_081326.log)
|
1.0
|
Crash while in RSS dialog - ```
What steps will reproduce the problem?
No idea - I was adding and editing RSS feeds and it crashed - I've attached the
crash log file.
What is the expected output? What do you see instead?
Shouldn't crash.
What version of the products are you using?
OS: Windows 7
Transmission: 1.91 (10268)
Remote: TRD (Release build 3.24.0.0)
```
Original issue reported on code.google.com by `richard....@gmail.com` on 25 Jan 2011 at 8:46
Attachments:
* [trdcrash_20110124_081326.log](https://storage.googleapis.com/google-code-attachments/transmission-remote-dotnet/issue-364/comment-0/trdcrash_20110124_081326.log)
|
defect
|
crash while in rss dialog what steps will reproduce the problem no idea i was adding and editing rss feeds and it crashed i ve attached the crash log file what is the expected output what do you see instead shouldn t crash what version of the products are you using os windows transmission remote trd release build original issue reported on code google com by richard gmail com on jan at attachments
| 1
|
36,937
| 15,099,549,431
|
IssuesEvent
|
2021-02-08 02:55:55
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Error importing AnomalyDetectorClient
|
Pri2 anomaly-detector/subsvc cognitive-services/svc cxp product-question triaged
|
Hi guys,
import os
from azure.ai.anomalydetector import AnomalyDetectorClient
gives
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
<ipython-input-9-3011c1947004> in <module>()
1 import os
----> 2 from azure.ai.anomalydetector import AnomalyDetectorClient
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\__init__.py in <module>()
7 # --------------------------------------------------------------------------
8
----> 9 from ._anomaly_detector_client import AnomalyDetectorClient
10 from ._version import VERSION
11
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\_anomaly_detector_client.py in <module>()
19
20 from ._configuration import AnomalyDetectorClientConfiguration
---> 21 from .operations import AnomalyDetectorClientOperationsMixin
22 from . import models
23
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\operations\__init__.py in <module>()
7 # --------------------------------------------------------------------------
8
----> 9 from ._anomaly_detector_client_operations import AnomalyDetectorClientOperationsMixin
10
11 __all__ = [
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\operations\_anomaly_detector_client_operations.py in <module>()
13 from azure.core.pipeline.transport import HttpRequest, HttpResponse
14
---> 15 from .. import models
16
17 if TYPE_CHECKING:
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\models\__init__.py in <module>()
8
9 try:
---> 10 from ._models_py3 import AnomalyDetectorError
11 from ._models_py3 import ChangePointDetectRequest
12 from ._models_py3 import ChangePointDetectResponse
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\models\_models_py3.py in <module>()
13 import msrest.serialization
14
---> 15 from ._anomaly_detector_client_enums import *
16
17
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\models\_anomaly_detector_client_enums.py in <module>()
27
28
---> 29 class AnomalyDetectorErrorCodes(with_metaclass(_CaseInsensitiveEnumMeta, str, Enum)):
30 """The error code.
31 """
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\enum.py in __prepare__(metacls, cls, bases)
117 enum_dict = _EnumDict()
118 # inherit previous flags and _generate_next_value_ function
--> 119 member_type, first_enum = metacls._get_mixins_(bases)
120 if first_enum is not None:
121 enum_dict['_generate_next_value_'] = getattr(first_enum, '_generate_next_value_', None)
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\enum.py in _get_mixins_(bases)
437 # base is now the last base in bases
438 if not issubclass(base, Enum):
--> 439 raise TypeError("new enumerations must be created as "
440 "`ClassName([mixin_type,] enum_type)`")
441
TypeError: new enumerations must be created as `ClassName([mixin_type,] enum_type)`
How can this be fixed?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 884b5e88-48eb-c3ad-1995-7cd87339783b
* Version Independent ID: e06cfd58-46d0-200a-5967-c6a1a7276997
* Content: [Quickstart: Anomaly detection using the Anomaly Detector client library - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/anomaly-detector/quickstarts/client-libraries?pivots=programming-language-python&tabs=windows)
* Content Source: [articles/cognitive-services/Anomaly-Detector/quickstarts/client-libraries.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cognitive-services/Anomaly-Detector/quickstarts/client-libraries.md)
* Service: **cognitive-services**
* Sub-service: **anomaly-detector**
* GitHub Login: @mrbullwinkle
* Microsoft Alias: **mbullwin**
|
1.0
|
Error importing AnomalyDetectorClient - Hi guys,
import os
from azure.ai.anomalydetector import AnomalyDetectorClient
gives
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
<ipython-input-9-3011c1947004> in <module>()
1 import os
----> 2 from azure.ai.anomalydetector import AnomalyDetectorClient
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\__init__.py in <module>()
7 # --------------------------------------------------------------------------
8
----> 9 from ._anomaly_detector_client import AnomalyDetectorClient
10 from ._version import VERSION
11
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\_anomaly_detector_client.py in <module>()
19
20 from ._configuration import AnomalyDetectorClientConfiguration
---> 21 from .operations import AnomalyDetectorClientOperationsMixin
22 from . import models
23
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\operations\__init__.py in <module>()
7 # --------------------------------------------------------------------------
8
----> 9 from ._anomaly_detector_client_operations import AnomalyDetectorClientOperationsMixin
10
11 __all__ = [
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\operations\_anomaly_detector_client_operations.py in <module>()
13 from azure.core.pipeline.transport import HttpRequest, HttpResponse
14
---> 15 from .. import models
16
17 if TYPE_CHECKING:
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\models\__init__.py in <module>()
8
9 try:
---> 10 from ._models_py3 import AnomalyDetectorError
11 from ._models_py3 import ChangePointDetectRequest
12 from ._models_py3 import ChangePointDetectResponse
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\models\_models_py3.py in <module>()
13 import msrest.serialization
14
---> 15 from ._anomaly_detector_client_enums import *
16
17
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\site-packages\azure\ai\anomalydetector\models\_anomaly_detector_client_enums.py in <module>()
27
28
---> 29 class AnomalyDetectorErrorCodes(with_metaclass(_CaseInsensitiveEnumMeta, str, Enum)):
30 """The error code.
31 """
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\enum.py in __prepare__(metacls, cls, bases)
117 enum_dict = _EnumDict()
118 # inherit previous flags and _generate_next_value_ function
--> 119 member_type, first_enum = metacls._get_mixins_(bases)
120 if first_enum is not None:
121 enum_dict['_generate_next_value_'] = getattr(first_enum, '_generate_next_value_', None)
c:\users\vscherbinin\appdata\local\programs\python\python36-32\lib\enum.py in _get_mixins_(bases)
437 # base is now the last base in bases
438 if not issubclass(base, Enum):
--> 439 raise TypeError("new enumerations must be created as "
440 "`ClassName([mixin_type,] enum_type)`")
441
TypeError: new enumerations must be created as `ClassName([mixin_type,] enum_type)`
How can this be fixed?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 884b5e88-48eb-c3ad-1995-7cd87339783b
* Version Independent ID: e06cfd58-46d0-200a-5967-c6a1a7276997
* Content: [Quickstart: Anomaly detection using the Anomaly Detector client library - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/anomaly-detector/quickstarts/client-libraries?pivots=programming-language-python&tabs=windows)
* Content Source: [articles/cognitive-services/Anomaly-Detector/quickstarts/client-libraries.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cognitive-services/Anomaly-Detector/quickstarts/client-libraries.md)
* Service: **cognitive-services**
* Sub-service: **anomaly-detector**
* GitHub Login: @mrbullwinkle
* Microsoft Alias: **mbullwin**
|
non_defect
|
error importing anomalydetectorclient hi guys import os from azure ai anomalydetector import anomalydetectorclient gives typeerror traceback most recent call last in import os from azure ai anomalydetector import anomalydetectorclient c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector init py in from anomaly detector client import anomalydetectorclient from version import version c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector anomaly detector client py in from configuration import anomalydetectorclientconfiguration from operations import anomalydetectorclientoperationsmixin from import models c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector operations init py in from anomaly detector client operations import anomalydetectorclientoperationsmixin all c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector operations anomaly detector client operations py in from azure core pipeline transport import httprequest httpresponse from import models if type checking c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector models init py in try from models import anomalydetectorerror from models import changepointdetectrequest from models import changepointdetectresponse c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector models models py in import msrest serialization from anomaly detector client enums import c users vscherbinin appdata local programs python lib site packages azure ai anomalydetector models anomaly detector client enums py in class anomalydetectorerrorcodes with metaclass caseinsensitiveenummeta str enum the error code c users vscherbinin appdata local programs python lib enum py in prepare metacls cls bases enum dict enumdict inherit previous flags and generate next value function member type first enum metacls get mixins bases if first enum is not none enum dict getattr first enum generate next value none c users vscherbinin appdata local programs python lib enum py in get mixins bases base is now the last base in bases if not issubclass base enum raise typeerror new enumerations must be created as classname enum type typeerror new enumerations must be created as classname enum type how can this be fixed document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service cognitive services sub service anomaly detector github login mrbullwinkle microsoft alias mbullwin
| 0
|
452,147
| 13,046,707,043
|
IssuesEvent
|
2020-07-29 09:26:43
|
Blosc/cat4py
|
https://api.github.com/repos/Blosc/cat4py
|
closed
|
Expose the blosc2 metalayer functions
|
high priority
|
The use might want to use a new blosc2 metalayer for storing things like types or others, so we need to expose the [metalayer API](https://blosc-doc.readthedocs.io/en/latest/c-blosc2_api.html#metalayer-functions) to cat4py. It would be nice to add an example on adding layers and updating them directly from Python.
|
1.0
|
Expose the blosc2 metalayer functions - The use might want to use a new blosc2 metalayer for storing things like types or others, so we need to expose the [metalayer API](https://blosc-doc.readthedocs.io/en/latest/c-blosc2_api.html#metalayer-functions) to cat4py. It would be nice to add an example on adding layers and updating them directly from Python.
|
non_defect
|
expose the metalayer functions the use might want to use a new metalayer for storing things like types or others so we need to expose the to it would be nice to add an example on adding layers and updating them directly from python
| 0
|
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_defect
|
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
|
1,148
| 2,598,003,076
|
IssuesEvent
|
2015-02-22 01:39:33
|
chrsmith/bwapi
|
https://api.github.com/repos/chrsmith/bwapi
|
opened
|
the fuction onUnitComplete() works weird
|
auto-migrated Component-Logic Milestone-Release Priority-High Type-Defect Usability
|
```
What steps will reproduce the problem?
1.try to use Broodwar->printf() to test if onUnitComplete() works
2.build a debug file by visual studio c++ 2008
3.run starcraft and debugging
What is the expected output? What do you see instead?
when a new unit is complete, print out text.
the onUnitComplete() is just like onUnitCreate(), it is called when a new unit
created, but the unit complete.
What version of the product are you using? On what operating system?
BWAPI_3.7, win 7 professional
Please provide any additional information below.
I expect the function runs when a new unit complete, but it runs just like
onUnitCreate(). And I can not find further information about it on the webpage.
```
-----
Original issue reported on code.google.com by `wwzz2...@gmail.com` on 12 Jul 2012 at 3:29
|
1.0
|
the fuction onUnitComplete() works weird - ```
What steps will reproduce the problem?
1.try to use Broodwar->printf() to test if onUnitComplete() works
2.build a debug file by visual studio c++ 2008
3.run starcraft and debugging
What is the expected output? What do you see instead?
when a new unit is complete, print out text.
the onUnitComplete() is just like onUnitCreate(), it is called when a new unit
created, but the unit complete.
What version of the product are you using? On what operating system?
BWAPI_3.7, win 7 professional
Please provide any additional information below.
I expect the function runs when a new unit complete, but it runs just like
onUnitCreate(). And I can not find further information about it on the webpage.
```
-----
Original issue reported on code.google.com by `wwzz2...@gmail.com` on 12 Jul 2012 at 3:29
|
defect
|
the fuction onunitcomplete works weird what steps will reproduce the problem try to use broodwar printf to test if onunitcomplete works build a debug file by visual studio c run starcraft and debugging what is the expected output what do you see instead when a new unit is complete print out text the onunitcomplete is just like onunitcreate it is called when a new unit created but the unit complete what version of the product are you using on what operating system bwapi win professional please provide any additional information below i expect the function runs when a new unit complete but it runs just like onunitcreate and i can not find further information about it on the webpage original issue reported on code google com by gmail com on jul at
| 1
|
28,061
| 5,170,587,765
|
IssuesEvent
|
2017-01-18 07:01:55
|
TNGSB/eWallet
|
https://api.github.com/repos/TNGSB/eWallet
|
closed
|
e-Wallet_Mobile App (Reload- FPX details) 17012017 #20
|
Defect - High (Sev-2)
|
Defect Description : After successful perform FPX reload, user to view the transaction history details and verify at customer transaction in Web Admin. It displayed "code" instead of FPX.
Tested with android build 20, UAT environment.
Attached screenshot for POT.
|
1.0
|
e-Wallet_Mobile App (Reload- FPX details) 17012017 #20 - Defect Description : After successful perform FPX reload, user to view the transaction history details and verify at customer transaction in Web Admin. It displayed "code" instead of FPX.
Tested with android build 20, UAT environment.
Attached screenshot for POT.
|
defect
|
e wallet mobile app reload fpx details defect description after successful perform fpx reload user to view the transaction history details and verify at customer transaction in web admin it displayed code instead of fpx tested with android build uat environment attached screenshot for pot
| 1
|
64,015
| 18,109,204,153
|
IssuesEvent
|
2021-09-22 23:52:37
|
idaholab/moose
|
https://api.github.com/repos/idaholab/moose
|
closed
|
MooseDocs Pipe based Executioner is not stable
|
T: defect P: normal
|
## Bug Description
<!--A clear and concise description of the problem (Note: A missing feature is not a bug).-->
The following error is sporadic on the test machines:
```bash
MooseDocs/test.materialize/pipe: Working Directory: /opt/civet/build_0/moose/python/MooseDocs/test
MooseDocs/test.materialize/pipe: Running command: python moosedocs.py verify --form materialize --executioner MooseDocs.base.ParallelPipe
MooseDocs/test.materialize/pipe: python moosedocs.py build --config materialize.yml --executioner MooseDocs.base.ParallelPipe
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension init() methods...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension init() methods complete [4.9591064453125e-05 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension initPage() methods...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension initPage() methods complete [0.013221502304077148 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.build (MainProcess): Cleaning destination /opt/civet/build_0/moose/python/MooseDocs/test/output/materialize
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing preExecute methods...
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): Reading MOOSE application syntax...
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): MOOSE application syntax complete [5.848524570465088 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): Building MOOSE class database...
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): MOOSE class database complete [2.5458145141601562 sec]
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing preExecute methods complete [8.887662649154663 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Translating using 16 threads...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Reading using 16 threads...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Reading [0.08691644668579102 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Tokenizing using 16 threads...
MooseDocs/test.materialize/pipe: Process Process-25:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/katex_include.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-26:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/listing.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-27:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/materialicon.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-28:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/navigation.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-29:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/preamble.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-30:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/sqa.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-31:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/table.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-32:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/index.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Tokenizing [0.16026663780212402 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Rendering using 16 threads...
MooseDocs/test.materialize/pipe: Process Process-41:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-42:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-43:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-44:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-45:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-46:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-47:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-48:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: MooseDocs.base.renderers (Process-36):
MooseDocs/test.materialize/pipe: RENDER ERROR: 'NoneType' object has no attribute 'text'
MooseDocs/test.materialize/pipe: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/content.md:80
MooseDocs/test.materialize/pipe: ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
MooseDocs/test.materialize/pipe: 80│ │
MooseDocs/test.materialize/pipe: 81│ │
MooseDocs/test.materialize/pipe: 82│!content pagination previous=materialicon.md next=config.md use_title=True │
MooseDocs/test.materialize/pipe: └────────────────────────────────────────────────────────────────────────────────────────────────┘
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 85, in render
MooseDocs/test.materialize/pipe: el = func(parent, token, page) if func else parent
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/extensions/content.py", line 414, in createMaterialize
MooseDocs/test.materialize/pipe: link = self.createHTMLHelper(div, token, page, 'previous')
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/extensions/content.py", line 427, in createHTMLHelper
MooseDocs/test.materialize/pipe: string = heading.find_heading(node).text()
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'text'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Rendering [0.2651538848876953 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Writing using 16 threads...
MooseDocs/test.materialize/pipe: Process Process-57:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-58:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-59:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-60:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-61:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-62:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-63:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-64:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Writing [0.09599161148071289 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Translating complete [0.6114253997802734 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Copying content...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Copying Finished [0.03951835632324219 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing postExecute methods...
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing postExecute methods complete [0.0019996166229248047 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Total Time [9.541635751724243 sec.]
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "moosedocs.py", line 29, in <module>
MooseDocs/test.materialize/pipe: sys.exit(main.run())
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/main.py", line 57, in run
MooseDocs/test.materialize/pipe: errno = verify.main(options)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/commands/verify.py", line 121, in main
MooseDocs/test.materialize/pipe: subprocess.check_output(cmd, cwd=os.path.join(MooseDocs.MOOSE_DIR, 'python', 'MooseDocs', 'test'))
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/subprocess.py", line 411, in check_output
MooseDocs/test.materialize/pipe: **kwargs).stdout
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/subprocess.py", line 512, in run
MooseDocs/test.materialize/pipe: output=stdout, stderr=stderr)
MooseDocs/test.materialize/pipe: subprocess.CalledProcessError: Command '['python', 'moosedocs.py', 'build', '--config', 'materialize.yml', '--executioner', 'MooseDocs.base.ParallelPipe']' returned non-zero exit status 1.
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: ################################################################################
MooseDocs/test.materialize/pipe: Tester failed, reason: CODE 1
MooseDocs/test.materialize/pipe:
FAIL MooseDocs/test.materialize/pipe FAILED (CODE 1)
```
## Steps to Reproduce
<!--Steps to reproduce the behavior (input file, or modifications to an existing input file, etc.)-->
Login into a build machine and run the following:
```
cd ~/singularity
./start_moosebuild.sh
export PATH=/opt/civet/conda_builds/bin:$PATH
source activate /opt/civet/conda_builds/conda_envs/pr-15882
cd /opt/civet/build_0/moose/python/MooseDocs/test
export MOOSE_DIR=/opt/civet/build_0/moose
python moosedocs.py verify --form materialize --executioner MooseDocs.base.ParallelPipe
```
The final command might need to be run more than once to get the failure.
The problem is that the data map with the results is returning None, but I don't know why: https://github.com/idaholab/moose/blob/8af65214be3c18bce602149a330b30e3e37f6355/python/MooseDocs/base/executioners.py#L612
## Impact
<!--Does this prevent you from getting your work done, or is it more of an annoyance?-->
Minimal. This method for building the documentation is not the default and therefore not used. It was created in attempt to improve performance of MooseDocs and continues to exists as an alternative for future problems and/or performance improvements.
|
1.0
|
MooseDocs Pipe based Executioner is not stable - ## Bug Description
<!--A clear and concise description of the problem (Note: A missing feature is not a bug).-->
The following error is sporadic on the test machines:
```bash
MooseDocs/test.materialize/pipe: Working Directory: /opt/civet/build_0/moose/python/MooseDocs/test
MooseDocs/test.materialize/pipe: Running command: python moosedocs.py verify --form materialize --executioner MooseDocs.base.ParallelPipe
MooseDocs/test.materialize/pipe: python moosedocs.py build --config materialize.yml --executioner MooseDocs.base.ParallelPipe
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension init() methods...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension init() methods complete [4.9591064453125e-05 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension initPage() methods...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Executing extension initPage() methods complete [0.013221502304077148 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.build (MainProcess): Cleaning destination /opt/civet/build_0/moose/python/MooseDocs/test/output/materialize
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing preExecute methods...
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): Reading MOOSE application syntax...
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): MOOSE application syntax complete [5.848524570465088 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): Building MOOSE class database...
MooseDocs/test.materialize/pipe: MooseDocs.extensions.appsyntax (MainProcess): MOOSE class database complete [2.5458145141601562 sec]
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing preExecute methods complete [8.887662649154663 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Translating using 16 threads...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Reading using 16 threads...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Reading [0.08691644668579102 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Tokenizing using 16 threads...
MooseDocs/test.materialize/pipe: Process Process-25:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/katex_include.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-26:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/listing.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-27:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/materialicon.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-28:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/navigation.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-29:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/preamble.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-30:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/sqa.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-31:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/table.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: Process Process-32:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 586, in _tokenize_target
MooseDocs/test.materialize/pipe: ast = self.tokenize(node, content)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 204, in tokenize
MooseDocs/test.materialize/pipe: self.translator.reader.tokenize(ast, content, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/readers.py", line 99, in tokenize
MooseDocs/test.materialize/pipe: self.__lexer.tokenize(root, content, page, self.__lexer.grammar(group), line)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/lexers.py", line 216, in tokenize
MooseDocs/test.materialize/pipe: raise TypeError(msg)
MooseDocs/test.materialize/pipe: TypeError: EXCEPTION: /opt/civet/build_0/moose/python/MooseDocs/test/content/index.md:1
MooseDocs/test.materialize/pipe: The supplied text must be str.
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Tokenizing [0.16026663780212402 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Rendering using 16 threads...
MooseDocs/test.materialize/pipe: Process Process-41:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-42:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-43:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-44:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-45:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-46:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-47:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: Process Process-48:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 84, in render
MooseDocs/test.materialize/pipe: func = self.__getFunction(token)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 216, in __getFunction
MooseDocs/test.materialize/pipe: return self.__functions.get(token.name, None)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'name'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: During handling of the above exception, another exception occurred:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 600, in _render_target
MooseDocs/test.materialize/pipe: result = self.render(node, ast)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 216, in render
MooseDocs/test.materialize/pipe: self.translator.renderer.render(result, ast, node)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 89, in render
MooseDocs/test.materialize/pipe: if token.info is not None:
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'info'
MooseDocs/test.materialize/pipe: MooseDocs.base.renderers (Process-36):
MooseDocs/test.materialize/pipe: RENDER ERROR: 'NoneType' object has no attribute 'text'
MooseDocs/test.materialize/pipe: /opt/civet/build_0/moose/python/MooseDocs/test/content/extensions/content.md:80
MooseDocs/test.materialize/pipe: ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
MooseDocs/test.materialize/pipe: 80│ │
MooseDocs/test.materialize/pipe: 81│ │
MooseDocs/test.materialize/pipe: 82│!content pagination previous=materialicon.md next=config.md use_title=True │
MooseDocs/test.materialize/pipe: └────────────────────────────────────────────────────────────────────────────────────────────────┘
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/renderers.py", line 85, in render
MooseDocs/test.materialize/pipe: el = func(parent, token, page) if func else parent
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/extensions/content.py", line 414, in createMaterialize
MooseDocs/test.materialize/pipe: link = self.createHTMLHelper(div, token, page, 'previous')
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/extensions/content.py", line 427, in createHTMLHelper
MooseDocs/test.materialize/pipe: string = heading.find_heading(node).text()
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'text'
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Rendering [0.2651538848876953 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Writing using 16 threads...
MooseDocs/test.materialize/pipe: Process Process-57:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-58:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-59:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-60:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-61:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-62:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-63:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: Process Process-64:
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
MooseDocs/test.materialize/pipe: self.run()
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/multiprocessing/process.py", line 99, in run
MooseDocs/test.materialize/pipe: self._target(*self._args, **self._kwargs)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 614, in _write_target
MooseDocs/test.materialize/pipe: self.write(node, result)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/base/executioners.py", line 227, in write
MooseDocs/test.materialize/pipe: self.translator.renderer.write(node, result.root)
MooseDocs/test.materialize/pipe: AttributeError: 'NoneType' object has no attribute 'root'
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Finished Writing [0.09599161148071289 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Translating complete [0.6114253997802734 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Copying content...
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Copying Finished [0.03951835632324219 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing postExecute methods...
MooseDocs/test.materialize/pipe: MooseDocs.Translator (MainProcess): Executing postExecute methods complete [0.0019996166229248047 sec.]
MooseDocs/test.materialize/pipe: MooseDocs.Executioner (MainProcess): Total Time [9.541635751724243 sec.]
MooseDocs/test.materialize/pipe: Traceback (most recent call last):
MooseDocs/test.materialize/pipe: File "moosedocs.py", line 29, in <module>
MooseDocs/test.materialize/pipe: sys.exit(main.run())
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/main.py", line 57, in run
MooseDocs/test.materialize/pipe: errno = verify.main(options)
MooseDocs/test.materialize/pipe: File "/opt/civet/build_0/moose/python/MooseDocs/commands/verify.py", line 121, in main
MooseDocs/test.materialize/pipe: subprocess.check_output(cmd, cwd=os.path.join(MooseDocs.MOOSE_DIR, 'python', 'MooseDocs', 'test'))
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/subprocess.py", line 411, in check_output
MooseDocs/test.materialize/pipe: **kwargs).stdout
MooseDocs/test.materialize/pipe: File "/opt/civet/conda_builds/conda_envs/next-8af65214be/lib/python3.7/subprocess.py", line 512, in run
MooseDocs/test.materialize/pipe: output=stdout, stderr=stderr)
MooseDocs/test.materialize/pipe: subprocess.CalledProcessError: Command '['python', 'moosedocs.py', 'build', '--config', 'materialize.yml', '--executioner', 'MooseDocs.base.ParallelPipe']' returned non-zero exit status 1.
MooseDocs/test.materialize/pipe:
MooseDocs/test.materialize/pipe: ################################################################################
MooseDocs/test.materialize/pipe: Tester failed, reason: CODE 1
MooseDocs/test.materialize/pipe:
FAIL MooseDocs/test.materialize/pipe FAILED (CODE 1)
```
## Steps to Reproduce
<!--Steps to reproduce the behavior (input file, or modifications to an existing input file, etc.)-->
Login into a build machine and run the following:
```
cd ~/singularity
./start_moosebuild.sh
export PATH=/opt/civet/conda_builds/bin:$PATH
source activate /opt/civet/conda_builds/conda_envs/pr-15882
cd /opt/civet/build_0/moose/python/MooseDocs/test
export MOOSE_DIR=/opt/civet/build_0/moose
python moosedocs.py verify --form materialize --executioner MooseDocs.base.ParallelPipe
```
The final command might need to be run more than once to get the failure.
The problem is that the data map with the results is returning None, but I don't know why: https://github.com/idaholab/moose/blob/8af65214be3c18bce602149a330b30e3e37f6355/python/MooseDocs/base/executioners.py#L612
## Impact
<!--Does this prevent you from getting your work done, or is it more of an annoyance?-->
Minimal. This method for building the documentation is not the default and therefore not used. It was created in attempt to improve performance of MooseDocs and continues to exists as an alternative for future problems and/or performance improvements.
|
defect
|
moosedocs pipe based executioner is not stable bug description the following error is sporadic on the test machines bash moosedocs test materialize pipe working directory opt civet build moose python moosedocs test moosedocs test materialize pipe running command python moosedocs py verify form materialize executioner moosedocs base parallelpipe moosedocs test materialize pipe python moosedocs py build config materialize yml executioner moosedocs base parallelpipe moosedocs test materialize pipe moosedocs executioner mainprocess executing extension init methods moosedocs test materialize pipe moosedocs executioner mainprocess executing extension init methods complete moosedocs test materialize pipe moosedocs executioner mainprocess executing extension initpage methods moosedocs test materialize pipe moosedocs executioner mainprocess executing extension initpage methods complete moosedocs test materialize pipe moosedocs build mainprocess cleaning destination opt civet build moose python moosedocs test output materialize moosedocs test materialize pipe moosedocs translator mainprocess executing preexecute methods moosedocs test materialize pipe moosedocs extensions appsyntax mainprocess reading moose application syntax moosedocs test materialize pipe moosedocs extensions appsyntax mainprocess moose application syntax complete moosedocs test materialize pipe moosedocs extensions appsyntax mainprocess building moose class database moosedocs test materialize pipe moosedocs extensions appsyntax mainprocess moose class database complete moosedocs test materialize pipe moosedocs translator mainprocess executing preexecute methods complete moosedocs test materialize pipe moosedocs executioner mainprocess translating using threads moosedocs test materialize pipe moosedocs executioner mainprocess reading using threads moosedocs test materialize pipe moosedocs executioner mainprocess finished reading moosedocs test materialize pipe moosedocs executioner mainprocess tokenizing using threads moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions katex include md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions listing md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions materialicon md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions navigation md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions preamble md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions sqa md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content extensions table md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize target moosedocs test materialize pipe ast self tokenize node content moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in tokenize moosedocs test materialize pipe self translator reader tokenize ast content node moosedocs test materialize pipe file opt civet build moose python moosedocs base readers py line in tokenize moosedocs test materialize pipe self lexer tokenize root content page self lexer grammar group line moosedocs test materialize pipe file opt civet build moose python moosedocs base lexers py line in tokenize moosedocs test materialize pipe raise typeerror msg moosedocs test materialize pipe typeerror exception opt civet build moose python moosedocs test content index md moosedocs test materialize pipe the supplied text must be str moosedocs test materialize pipe moosedocs executioner mainprocess finished tokenizing moosedocs test materialize pipe moosedocs executioner mainprocess rendering using threads moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe func self getfunction token moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in getfunction moosedocs test materialize pipe return self functions get token name none moosedocs test materialize pipe attributeerror nonetype object has no attribute name moosedocs test materialize pipe moosedocs test materialize pipe during handling of the above exception another exception occurred moosedocs test materialize pipe moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render target moosedocs test materialize pipe result self render node ast moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in render moosedocs test materialize pipe self translator renderer render result ast node moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe if token info is not none moosedocs test materialize pipe attributeerror nonetype object has no attribute info moosedocs test materialize pipe moosedocs base renderers process moosedocs test materialize pipe render error nonetype object has no attribute text moosedocs test materialize pipe opt civet build moose python moosedocs test content extensions content md moosedocs test materialize pipe ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ moosedocs test materialize pipe │ │ moosedocs test materialize pipe │ │ moosedocs test materialize pipe │ content pagination previous materialicon md next config md use title true │ moosedocs test materialize pipe └────────────────────────────────────────────────────────────────────────────────────────────────┘ moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet build moose python moosedocs base renderers py line in render moosedocs test materialize pipe el func parent token page if func else parent moosedocs test materialize pipe file opt civet build moose python moosedocs extensions content py line in creatematerialize moosedocs test materialize pipe link self createhtmlhelper div token page previous moosedocs test materialize pipe file opt civet build moose python moosedocs extensions content py line in createhtmlhelper moosedocs test materialize pipe string heading find heading node text moosedocs test materialize pipe attributeerror nonetype object has no attribute text moosedocs test materialize pipe moosedocs test materialize pipe moosedocs test materialize pipe moosedocs executioner mainprocess finished rendering moosedocs test materialize pipe moosedocs executioner mainprocess writing using threads moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe process process moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in bootstrap moosedocs test materialize pipe self run moosedocs test materialize pipe file opt civet conda builds conda envs next lib multiprocessing process py line in run moosedocs test materialize pipe self target self args self kwargs moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write target moosedocs test materialize pipe self write node result moosedocs test materialize pipe file opt civet build moose python moosedocs base executioners py line in write moosedocs test materialize pipe self translator renderer write node result root moosedocs test materialize pipe attributeerror nonetype object has no attribute root moosedocs test materialize pipe moosedocs executioner mainprocess finished writing moosedocs test materialize pipe moosedocs executioner mainprocess translating complete moosedocs test materialize pipe moosedocs executioner mainprocess copying content moosedocs test materialize pipe moosedocs executioner mainprocess copying finished moosedocs test materialize pipe moosedocs translator mainprocess executing postexecute methods moosedocs test materialize pipe moosedocs translator mainprocess executing postexecute methods complete moosedocs test materialize pipe moosedocs executioner mainprocess total time moosedocs test materialize pipe traceback most recent call last moosedocs test materialize pipe file moosedocs py line in moosedocs test materialize pipe sys exit main run moosedocs test materialize pipe file opt civet build moose python moosedocs main py line in run moosedocs test materialize pipe errno verify main options moosedocs test materialize pipe file opt civet build moose python moosedocs commands verify py line in main moosedocs test materialize pipe subprocess check output cmd cwd os path join moosedocs moose dir python moosedocs test moosedocs test materialize pipe file opt civet conda builds conda envs next lib subprocess py line in check output moosedocs test materialize pipe kwargs stdout moosedocs test materialize pipe file opt civet conda builds conda envs next lib subprocess py line in run moosedocs test materialize pipe output stdout stderr stderr moosedocs test materialize pipe subprocess calledprocesserror command returned non zero exit status moosedocs test materialize pipe moosedocs test materialize pipe moosedocs test materialize pipe tester failed reason code moosedocs test materialize pipe fail moosedocs test materialize pipe failed code steps to reproduce login into a build machine and run the following cd singularity start moosebuild sh export path opt civet conda builds bin path source activate opt civet conda builds conda envs pr cd opt civet build moose python moosedocs test export moose dir opt civet build moose python moosedocs py verify form materialize executioner moosedocs base parallelpipe the final command might need to be run more than once to get the failure the problem is that the data map with the results is returning none but i don t know why impact minimal this method for building the documentation is not the default and therefore not used it was created in attempt to improve performance of moosedocs and continues to exists as an alternative for future problems and or performance improvements
| 1
|
78,033
| 15,569,911,586
|
IssuesEvent
|
2021-03-17 01:16:49
|
Killy85/game_ai_trainer
|
https://api.github.com/repos/Killy85/game_ai_trainer
|
opened
|
CVE-2020-1747 (High) detected in PyYAML-5.1.tar.gz
|
security vulnerability
|
## CVE-2020-1747 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>PyYAML-5.1.tar.gz</b></p></summary>
<p>YAML parser and emitter for Python</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/9f/2c/9417b5c774792634834e730932745bc09a7d36754ca00acf1ccd1ac2594d/PyYAML-5.1.tar.gz">https://files.pythonhosted.org/packages/9f/2c/9417b5c774792634834e730932745bc09a7d36754ca00acf1ccd1ac2594d/PyYAML-5.1.tar.gz</a></p>
<p>Path to dependency file: /game_ai_trainer/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_da03aa19-8c81-4d9c-9496-c373589d1ea2/20190506071543_44724/20190506071259_depth_0/46/PyYAML-5.1.tar/PyYAML-5.1</p>
<p>
Dependency Hierarchy:
- :x: **PyYAML-5.1.tar.gz** (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>
A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
<p>Publish Date: 2020-03-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1747>CVE-2020-1747</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1747">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1747</a></p>
<p>Release Date: 2020-03-24</p>
<p>Fix Resolution: 5.3.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-1747 (High) detected in PyYAML-5.1.tar.gz - ## CVE-2020-1747 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>PyYAML-5.1.tar.gz</b></p></summary>
<p>YAML parser and emitter for Python</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/9f/2c/9417b5c774792634834e730932745bc09a7d36754ca00acf1ccd1ac2594d/PyYAML-5.1.tar.gz">https://files.pythonhosted.org/packages/9f/2c/9417b5c774792634834e730932745bc09a7d36754ca00acf1ccd1ac2594d/PyYAML-5.1.tar.gz</a></p>
<p>Path to dependency file: /game_ai_trainer/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_da03aa19-8c81-4d9c-9496-c373589d1ea2/20190506071543_44724/20190506071259_depth_0/46/PyYAML-5.1.tar/PyYAML-5.1</p>
<p>
Dependency Hierarchy:
- :x: **PyYAML-5.1.tar.gz** (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>
A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
<p>Publish Date: 2020-03-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1747>CVE-2020-1747</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1747">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1747</a></p>
<p>Release Date: 2020-03-24</p>
<p>Fix Resolution: 5.3.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_defect
|
cve high detected in pyyaml tar gz cve high severity vulnerability vulnerable library pyyaml tar gz yaml parser and emitter for python library home page a href path to dependency file game ai trainer requirements txt path to vulnerable library tesource archiveextractor depth pyyaml tar pyyaml dependency hierarchy x pyyaml tar gz vulnerable library vulnerability details a vulnerability was discovered in the pyyaml library in versions before where it is susceptible to arbitrary code execution when it processes untrusted yaml files through the full load method or with the fullloader loader applications that use the library to process untrusted input may be vulnerable to this flaw an attacker could use this flaw to execute arbitrary code on the system by abusing the python object new constructor publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
9,326
| 11,355,635,359
|
IssuesEvent
|
2020-01-24 20:31:42
|
scireum/s3ninja
|
https://api.github.com/repos/scireum/s3ninja
|
closed
|
listObjects(), listNextBatchOfObjects() don't list objects in appropriate order; breaks markers
|
API-INCOMPATIBILITY ready 🏁
|
According to
https://docs.aws.amazon.com/AmazonS3/latest/dev/ListingKeysUsingAPIs.html
> Amazon S3 exposes a list operation that lets you enumerate the keys contained in a bucket. Keys are selected for listing by bucket and prefix. For example, consider a bucket named "dictionary" that contains a key for every English word. You might make a call to list all the keys in that bucket that start with the letter "q". List results are always returned in UTF-8 binary order.
S3Ninja, on the contrary, enumerates keys in whatever order `java.nio.file.Files.walkFileTree()` happens to encounter them.
Also, S3Ninja implements markers in such a way that it ignores keys until it encounters one that matches the marker. From then on, all keys are allowed to pass through. (See https://github.com/scireum/s3ninja/blob/master/src/main/java/ninja/ListFileTreeVisitor.java#L67)
In conjunction, this breaks the use of markers.
|
True
|
listObjects(), listNextBatchOfObjects() don't list objects in appropriate order; breaks markers - According to
https://docs.aws.amazon.com/AmazonS3/latest/dev/ListingKeysUsingAPIs.html
> Amazon S3 exposes a list operation that lets you enumerate the keys contained in a bucket. Keys are selected for listing by bucket and prefix. For example, consider a bucket named "dictionary" that contains a key for every English word. You might make a call to list all the keys in that bucket that start with the letter "q". List results are always returned in UTF-8 binary order.
S3Ninja, on the contrary, enumerates keys in whatever order `java.nio.file.Files.walkFileTree()` happens to encounter them.
Also, S3Ninja implements markers in such a way that it ignores keys until it encounters one that matches the marker. From then on, all keys are allowed to pass through. (See https://github.com/scireum/s3ninja/blob/master/src/main/java/ninja/ListFileTreeVisitor.java#L67)
In conjunction, this breaks the use of markers.
|
non_defect
|
listobjects listnextbatchofobjects don t list objects in appropriate order breaks markers according to amazon exposes a list operation that lets you enumerate the keys contained in a bucket keys are selected for listing by bucket and prefix for example consider a bucket named dictionary that contains a key for every english word you might make a call to list all the keys in that bucket that start with the letter q list results are always returned in utf binary order on the contrary enumerates keys in whatever order java nio file files walkfiletree happens to encounter them also implements markers in such a way that it ignores keys until it encounters one that matches the marker from then on all keys are allowed to pass through see in conjunction this breaks the use of markers
| 0
|
69,094
| 14,970,061,703
|
IssuesEvent
|
2021-01-27 19:03:15
|
jgeraigery/experian-java
|
https://api.github.com/repos/jgeraigery/experian-java
|
closed
|
CVE-2020-36187 (Medium) detected in jackson-databind-2.9.2.jar - autoclosed
|
security vulnerability
|
## CVE-2020-36187 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.2.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: experian-java/MavenWorkspace/bis-services-lib/bis-services-base/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.2/jackson-databind-2.9.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/experian-java/commit/e2b236143990842a0d83d97532011829192916a7">e2b236143990842a0d83d97532011829192916a7</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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36187>CVE-2020-36187</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>6.8</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.2","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.2","isMinimumFixVersionAvailable":false}],"vulnerabilityIdentifier":"CVE-2020-36187","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36187","cvss2Severity":"medium","cvss2Score":"6.8","extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-36187 (Medium) detected in jackson-databind-2.9.2.jar - autoclosed - ## CVE-2020-36187 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.2.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: experian-java/MavenWorkspace/bis-services-lib/bis-services-base/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.2/jackson-databind-2.9.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/experian-java/commit/e2b236143990842a0d83d97532011829192916a7">e2b236143990842a0d83d97532011829192916a7</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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36187>CVE-2020-36187</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>6.8</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.2","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.2","isMinimumFixVersionAvailable":false}],"vulnerabilityIdentifier":"CVE-2020-36187","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36187","cvss2Severity":"medium","cvss2Score":"6.8","extraData":{}}</REMEDIATE> -->
|
non_defect
|
cve medium detected in jackson databind jar autoclosed cve medium severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file experian java mavenworkspace bis services lib bis services base pom xml path to vulnerable library canner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache tomcat dbcp dbcp datasources sharedpooldatasource publish date url a href cvss score details base score metrics not available isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache tomcat dbcp dbcp datasources sharedpooldatasource vulnerabilityurl
| 0
|
70,806
| 3,343,741,087
|
IssuesEvent
|
2015-11-15 19:03:31
|
codenameone/CodenameOne
|
https://api.github.com/repos/codenameone/CodenameOne
|
opened
|
Support new native fonts API in JavaScript port
|
enhancement Priority-Low
|
The native: scheme recently committed to git https://github.com/codenameone/CodenameOne/commit/2634fc09aff2d3354a6c3faed02d7a05bf9615cd
Uses native: hardcoded values to provide font objects. This should map to a set of CSS font styles (or something similar) that give reasonable platform defaults.
|
1.0
|
Support new native fonts API in JavaScript port - The native: scheme recently committed to git https://github.com/codenameone/CodenameOne/commit/2634fc09aff2d3354a6c3faed02d7a05bf9615cd
Uses native: hardcoded values to provide font objects. This should map to a set of CSS font styles (or something similar) that give reasonable platform defaults.
|
non_defect
|
support new native fonts api in javascript port the native scheme recently committed to git uses native hardcoded values to provide font objects this should map to a set of css font styles or something similar that give reasonable platform defaults
| 0
|
307,306
| 26,523,558,268
|
IssuesEvent
|
2023-01-19 06:22:05
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
roachtest: change-replicas/mixed-version failed
|
C-test-failure O-robot O-roachtest branch-master release-blocker T-kv-replication
|
roachtest.change-replicas/mixed-version [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8366766?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8366766?buildTab=artifacts#/change-replicas/mixed-version) on master @ [942b55ef3f329d2e5e8142c8fc5282ed56173ea7](https://github.com/cockroachdb/cockroach/commits/942b55ef3f329d2e5e8142c8fc5282ed56173ea7):
```
test artifacts and logs in: /artifacts/change-replicas/mixed-version/run_1
(mixed_version_change_replicas.go:156).1: failed to move 1 replicas from n1 to n2 using gateway n3
(assertions.go:264).Fail:
Error Trace: /go/src/github.com/cockroachdb/cockroach/mixed_version_change_replicas.go:101
/go/src/github.com/cockroachdb/cockroach/panic.go:890
/go/src/github.com/cockroachdb/cockroach/test_impl.go:298
/go/src/github.com/cockroachdb/cockroach/mixed_version_change_replicas.go:156
/go/src/github.com/cockroachdb/cockroach/versionupgrade.go:219
/go/src/github.com/cockroachdb/cockroach/mixed_version_change_replicas.go:319
/go/src/github.com/cockroachdb/cockroach/test_runner.go:943
/go/src/github.com/cockroachdb/cockroach/asm_amd64.s:1594
Error: Received unexpected error:
context canceled
Test: change-replicas/mixed-version
(require.go:1264).NoError: FailNow called
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/replication
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*change-replicas/mixed-version.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
2.0
|
roachtest: change-replicas/mixed-version failed - roachtest.change-replicas/mixed-version [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8366766?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8366766?buildTab=artifacts#/change-replicas/mixed-version) on master @ [942b55ef3f329d2e5e8142c8fc5282ed56173ea7](https://github.com/cockroachdb/cockroach/commits/942b55ef3f329d2e5e8142c8fc5282ed56173ea7):
```
test artifacts and logs in: /artifacts/change-replicas/mixed-version/run_1
(mixed_version_change_replicas.go:156).1: failed to move 1 replicas from n1 to n2 using gateway n3
(assertions.go:264).Fail:
Error Trace: /go/src/github.com/cockroachdb/cockroach/mixed_version_change_replicas.go:101
/go/src/github.com/cockroachdb/cockroach/panic.go:890
/go/src/github.com/cockroachdb/cockroach/test_impl.go:298
/go/src/github.com/cockroachdb/cockroach/mixed_version_change_replicas.go:156
/go/src/github.com/cockroachdb/cockroach/versionupgrade.go:219
/go/src/github.com/cockroachdb/cockroach/mixed_version_change_replicas.go:319
/go/src/github.com/cockroachdb/cockroach/test_runner.go:943
/go/src/github.com/cockroachdb/cockroach/asm_amd64.s:1594
Error: Received unexpected error:
context canceled
Test: change-replicas/mixed-version
(require.go:1264).NoError: FailNow called
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/replication
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*change-replicas/mixed-version.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
non_defect
|
roachtest change replicas mixed version failed roachtest change replicas mixed version with on master test artifacts and logs in artifacts change replicas mixed version run mixed version change replicas go failed to move replicas from to using gateway assertions go fail error trace go src github com cockroachdb cockroach mixed version change replicas go go src github com cockroachdb cockroach panic go go src github com cockroachdb cockroach test impl go go src github com cockroachdb cockroach mixed version change replicas go go src github com cockroachdb cockroach versionupgrade go go src github com cockroachdb cockroach mixed version change replicas go go src github com cockroachdb cockroach test runner go go src github com cockroachdb cockroach asm s error received unexpected error context canceled test change replicas mixed version require go noerror failnow called parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see cc cockroachdb replication
| 0
|
85,561
| 3,691,614,383
|
IssuesEvent
|
2016-02-26 00:59:53
|
kubernetes/deployment-manager
|
https://api.github.com/repos/kubernetes/deployment-manager
|
opened
|
Add helm maintainers to kubernetes organization
|
area/access helm priority/P0
|
As we prepare to merge the helm repo into the deployment-manager repo, we need to make the helm maintainers members of the deployment-manager-maintainers group.
Here are their Github handles:
@adamreese
@michelleN
@sgoings
@technosophos
|
1.0
|
Add helm maintainers to kubernetes organization - As we prepare to merge the helm repo into the deployment-manager repo, we need to make the helm maintainers members of the deployment-manager-maintainers group.
Here are their Github handles:
@adamreese
@michelleN
@sgoings
@technosophos
|
non_defect
|
add helm maintainers to kubernetes organization as we prepare to merge the helm repo into the deployment manager repo we need to make the helm maintainers members of the deployment manager maintainers group here are their github handles adamreese michellen sgoings technosophos
| 0
|
35,619
| 9,633,618,584
|
IssuesEvent
|
2019-05-15 19:06:16
|
shenv/shenv
|
https://api.github.com/repos/shenv/shenv
|
closed
|
Fix or remove zsh-4.0.1 build
|
build help wanted
|
```
/tmp/shell-build.20171215153350.26110 /media/pawamoy/Data/git/shenv/shenv/plugins/shell-build/share/shell-build
/tmp/shell-build.20171215153350.26110/zsh-4.0.1 /tmp/shell-build.20171215153350.26110 /media/pawamoy/Data/git/shenv/shenv/plugins/shell-build/share/shell-build
creating cache ./config.cache
configuring for zsh 4.0.1
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler (gcc -L/home/pawamoy/.shenv/versions/zsh-4.0.1/lib ) works... yes
checking whether the C compiler (gcc -L/home/pawamoy/.shenv/versions/zsh-4.0.1/lib ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking whether large file support needs explicit enabling... no
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking for working const... yes
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for executable suffix... no
checking for gcc option to accept ANSI C...
checking whether to use prototypes... yes
checking for working alloca.h... yes
checking for alloca... yes
checking if the compiler supports union initialisation... yes
checking if signed to unsigned casting is broken... no
checking if the compiler supports variable-length arrays... yes
checking what to set MAXJOB to... 50
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for mawk... mawk
checking whether ln works... yes
checking for yodl... no
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether stat file-mode macros are broken... no
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/time.h... yes
checking for sys/times.h... yes
checking for sys/select.h... yes
checking for termcap.h... yes
checking for termio.h... yes
checking for termios.h... yes
checking for sys/param.h... yes
checking for sys/filio.h... no
checking for string.h... yes
checking for memory.h... yes
checking for limits.h... yes
checking for fcntl.h... yes
checking for libc.h... no
checking for sys/utsname.h... yes
checking for sys/resource.h... yes
checking for locale.h... yes
checking for errno.h... yes
checking for stdlib.h... yes
checking for unistd.h... yes
checking for sys/capability.h... no
checking for utmp.h... yes
checking for utmpx.h... yes
checking for sys/types.h... yes
checking for pwd.h... yes
checking for grp.h... yes
checking for poll.h... yes
checking for sys/mman.h... yes
checking for netinet/in_systm.h... yes
checking for dlfcn.h... yes
checking for dl.h... no
checking for conflicts in sys/time.h and sys/select.h... no
checking POSIX termios... yes
checking TIOCGWINSZ in termios.h... no
checking TIOCGWINSZ in sys/ioctl.h... yes
checking for sys/ptem.h... no
checking for printf in -lc... yes
checking for pow in -lm... yes
checking for library containing tgetent... -ltermcap
checking for library containing yp_all... -lnsl
checking for dlopen in -ldl... yes
checking for cap_get_proc in -lcap... no
checking for socket in -lsocket... no
checking if an include file defines ospeed... yes
checking return type of signal handlers... void
checking for pid_t... yes
checking for off_t... yes
checking for ino_t... yes
checking for mode_t... yes
checking for uid_t in sys/types.h... yes
checking for size_t... yes
checking if long is 64 bits... yes
checking for sigset_t... yes
checking for struct timezone... yes
checking for struct utmp... yes
checking for struct utmpx... yes
checking for ut_host in struct utmp... yes
checking for ut_host in struct utmpx... yes
checking for ut_xtime in struct utmpx... no
checking for ut_tv in struct utmpx... yes
checking for d_ino in struct dirent... yes
checking for d_stat in struct dirent... no
checking for d_ino in struct direct... no
checking for d_stat in struct direct... no
checking for sin6_scope_id in struct sockaddr_in6... yes
checking if we need our own h_errno... yes
checking for strftime... yes
checking for difftime... yes
checking for gettimeofday... yes
checking for select... yes
checking for poll... yes
checking for readlink... yes
checking for lstat... yes
checking for lchown... yes
checking for faccessx... no
checking for fchdir... yes
checking for ftruncate... yes
checking for fseeko... yes
checking for ftello... yes
checking for mkfifo... yes
checking for _mktemp... no
checking for waitpid... yes
checking for wait3... yes
checking for sigaction... yes
checking for sigblock... yes
checking for sighold... yes
checking for sigrelse... yes
checking for sigsetmask... yes
checking for sigprocmask... yes
checking for killpg... yes
checking for setpgid... yes
checking for setpgrp... yes
checking for tcsetpgrp... yes
checking for tcgetattr... yes
checking for nice... yes
checking for gethostname... yes
checking for gethostbyname2... yes
checking for getipnodebyname... no
checking for inet_aton... yes
checking for inet_pton... yes
checking for inet_ntop... yes
checking for getlogin... yes
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for getgrgid... yes
checking for getgrnam... yes
checking for initgroups... yes
checking for nis_list... yes
checking for setuid... yes
checking for seteuid... yes
checking for setreuid... yes
checking for setresuid... yes
checking for setsid... yes
checking for memcpy... yes
checking for memmove... yes
checking for strstr... yes
checking for strerror... yes
checking for cap_get_proc... no
checking for getrlimit... yes
checking for setlocale... yes
checking for uname... yes
checking for signgam... yes
checking for putenv... yes
checking for getenv... yes
checking for brk... yes
checking for sbrk... yes
checking for pathconf... yes
checking for sysconf... yes
checking for tgetent... yes
checking for tigetflag... yes
checking for tigetnum... yes
checking for tigetstr... yes
checking for setupterm... yes
checking for working strcoll... yes
checking if tgetent accepts NULL... yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... no
checking whether getpgrp takes no argument... yes
checking for dlopen... yes
checking for dlerror... yes
checking for dlsym... yes
checking for dlclose... yes
checking for load... no
checking for loadquery... no
checking for loadbind... no
checking for unload... no
checking for shl_load... no
checking for shl_unload... no
checking for shl_findsym... no
checking what style of signals to use... POSIX_SIGNALS
checking where signal.h is located... /usr/include/x86_64-linux-gnu/bits/signum.h
checking where the RLIMIT macros are located... configure: warning: RLIMIT MACROS NOT FOUND: please report to developers
/dev/null
checking if rlim_t is longer than a long... no
checking if the rlim_t is unsigned... yes
checking for rlim_t... yes
checking for /dev/fd filesystem... /proc/self/fd
checking for RFS superroot directory... no
checking whether we should use the native getcwd... no
checking for NIS... no
checking for NIS+... no
checking for utmp file... /var/run/utmp
checking for wtmp file... /var/log/wtmp
checking for utmpx file... no
checking for wtmpx file... no
checking for brk() prototype in <unistd.h>... yes
checking for sbrk() prototype in <unistd.h>... yes
checking for ioctl prototype in <sys/ioctl.h>... yes
checking for mknod prototype in <sys/stat.h>... yes
checking if named FIFOs work... yes
checking if echo in /bin/sh interprets escape sequences... yes
checking if link() works... yes
checking if kill(pid, 0) returns ESRCH correctly... yes
checking if POSIX sigsuspend() works... yes
checking if tcsetpgrp() actually works... yes
checking if getpwnam() is faked... no
checking if your system use ELF binaries... yes
checking if your dlsym() needs a leading underscore... no
checking if environ is available in shared libraries... yes
checking if tgetent is available in shared libraries... yes
checking if tigetstr is available in shared libraries... yes
checking if name clashes in shared objects are OK... yes
checking for working RTLD_GLOBAL... yes
checking whether symbols in the executable are available... yes
checking whether executables can be stripped... yes
checking whether libraries can be stripped... yes
creating ./config.modules
updating cache ./config.cache
creating ./config.status
creating Config/defs.mk
creating Makefile
creating Doc/Makefile
creating Etc/Makefile
creating Src/Makefile
creating Test/Makefile
creating config.h
zsh configuration
-----------------
zsh version : 4.0.1
host operating system : x86_64-unknown-linux-gnu
source code location : .
compiler : gcc
preprocessor flags : -I/home/pawamoy/.shenv/versions/zsh-4.0.1/include
executable compiler flags : -Wall -Wno-implicit -Wmissing-prototypes -O2
module compiler flags : -Wall -Wno-implicit -Wmissing-prototypes -O2 -fpic
executable linker flags : -rdynamic
module linker flags : -shared
library flags : -ldl -lnsl -ltermcap -lm -lc
installation basename : zsh
binary install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/bin
man page install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/man
info install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/info
functions install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/share/zsh/4.0.1/functions
See config.modules for installed modules and functions.
make[1]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
rm -f stamp-modobjs.tmp
cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
creating Src/Makemod.in
creating Src/Makemod
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
echo 'timestamp for *.mdd files' > ../Src/modules.stamp
creating Src/Builtins/Makefile.in
creating Src/Builtins/Makefile
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Builtins'
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Builtins'
creating Src/Modules/Makefile.in
creating Src/Modules/Makefile
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Modules'
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Modules'
creating Src/Zle/Makefile.in
creating Src/Zle/Makefile
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Zle'
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Zle'
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ./signames1.awk /usr/include/x86_64-linux-gnu/bits/signum.h >sigtmp.c
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ./signames1.awk /usr/include/x86_64-linux-gnu/bits/signum.h >sigtmp.c
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ../Src/makepro.awk builtin.c Src > builtin.syms
gcc -E sigtmp.c >sigtmp.out
gcc -E sigtmp.c >sigtmp.out
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ../Src/makepro.awk compat.c Src > compat.syms
mawk -f ../Src/makepro.awk cond.c Src > cond.syms
mawk -f ./signames2.awk sigtmp.out > signames.c
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
rm -f sigtmp.c sigtmp.out
mawk -f ../Src/makepro.awk exec.c Src > exec.syms
Updated `zsh.mdh'.
echo 'timestamp for zsh.mdh against zsh.mdd' > zsh.mdhs
mawk -f ../Src/makepro.awk glob.c Src > glob.syms
mawk -f ./signames2.awk sigtmp.out > signames.c
mawk -f ../Src/makepro.awk builtin.c Src > builtin.syms
mawk -f ../Src/makepro.awk hashtable.c Src > hashtable.syms
mawk: cannot open sigtmp.out (No such file or directory)
Makemod:519: recipe for target 'signames.c' failed
make[2]: *** [signames.c] Error 2
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
make[2]: *** Waiting for unfinished jobs....
mawk -f ../Src/makepro.awk hist.c Src > hist.syms
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
Makefile:445: recipe for target 'headers' failed
make[1]: *** [headers] Error 2
make[1]: *** Waiting for unfinished jobs....
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < builtin.syms) \
> builtin.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < compat.syms) \
> compat.epro
mawk -f ../Src/makepro.awk init.c Src > init.syms
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < compat.syms) \
> `echo compat.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < builtin.syms) \
> `echo builtin.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk input.c Src > input.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < cond.syms) \
> cond.epro
mawk -f ../Src/makepro.awk jobs.c Src > jobs.syms
`zsh.mdh' is up to date.
echo 'timestamp for zsh.mdh against zsh.mdd' > zsh.mdhs
mawk -f ../Src/makepro.awk lex.c Src > lex.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < cond.syms) \
> `echo cond.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk linklist.c Src > linklist.syms
mawk -f ../Src/makepro.awk loop.c Src > loop.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < exec.syms) \
> exec.epro
mawk -f ../Src/makepro.awk math.c Src > math.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < glob.syms) \
> glob.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < exec.syms) \
> `echo exec.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk mem.c Src > mem.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < hashtable.syms) \
> hashtable.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < glob.syms) \
> `echo glob.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < hashtable.syms) \
> `echo hashtable.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk module.c Src > module.syms
mawk -f ../Src/makepro.awk options.c Src > options.syms
mawk -f ../Src/makepro.awk params.c Src > params.syms
mawk -f ../Src/makepro.awk parse.c Src > parse.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < hist.syms) \
> hist.epro
mawk -f ../Src/makepro.awk pattern.c Src > pattern.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < hist.syms) \
> `echo hist.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < init.syms) \
> init.epro
mawk -f ../Src/makepro.awk prompt.c Src > prompt.syms
mawk -f ../Src/makepro.awk signals.c Src > signals.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < init.syms) \
> `echo init.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < input.syms) \
> input.epro
mawk -f ../Src/makepro.awk signames.c Src > signames.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < input.syms) \
> `echo input.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk string.c Src > string.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < jobs.syms) \
> jobs.epro
mawk -f ../Src/makepro.awk subst.c Src > subst.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < lex.syms) \
> lex.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < jobs.syms) \
> `echo jobs.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < linklist.syms) \
> linklist.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < lex.syms) \
> `echo lex.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk text.c Src > text.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < linklist.syms) \
> `echo linklist.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk utils.c Src > utils.syms
mawk -f ../Src/makepro.awk watch.c Src > watch.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < loop.syms) \
> loop.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < math.syms) \
> math.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < mem.syms) \
> mem.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < math.syms) \
> `echo math.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < mem.syms) \
> `echo mem.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < module.syms) \
> module.epro
( echo '#!'; cat builtin.syms compat.syms cond.syms exec.syms glob.syms hashtable.syms hist.syms init.syms input.syms jobs.syms lex.syms linklist.syms loop.syms math.syms mem.syms module.syms options.syms params.syms parse.syms pattern.syms prompt.syms signals.syms signames.syms string.syms subst.syms text.syms utils.syms watch.syms | sed -n '/^X/{s/^X//;p;}' | sort -u ) > zsh.export
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < module.syms) \
> `echo module.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < options.syms) \
> options.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < loop.syms) \
> `echo loop.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < options.syms) \
> `echo options.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < params.syms) \
> params.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < params.syms) \
> `echo params.epro | sed 's/\.epro$/.pro/'`
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < parse.syms) \
> parse.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < pattern.syms) \
> pattern.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < prompt.syms) \
> prompt.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < pattern.syms) \
> `echo pattern.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < parse.syms) \
> `echo parse.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < prompt.syms) \
> `echo prompt.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < signals.syms) \
> signals.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < signames.syms) \
> signames.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < signals.syms) \
> `echo signals.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < string.syms) \
> string.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < subst.syms) \
> subst.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < signames.syms) \
> `echo signames.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < string.syms) \
> `echo string.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < subst.syms) \
> `echo subst.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < text.syms) \
> text.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < text.syms) \
> `echo text.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < utils.syms) \
> utils.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < watch.syms) \
> watch.epro
mawk -f ../Src/makepro.awk main.c Src > main.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < watch.syms) \
> `echo watch.epro | sed 's/\.epro$/.pro/'`
grep 'define.*SIGCOUNT' signames.c > sigcount.h
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < utils.syms) \
> `echo utils.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < main.syms) \
> main.epro
Makemod:525: recipe for target 'sigcount.h' failed
make[2]: *** [sigcount.h] Error 1
make[2]: *** Waiting for unfinished jobs....
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < main.syms) \
> `echo main.epro | sed 's/\.epro$/.pro/'`
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
Makefile:445: recipe for target 'main.o' failed
make[1]: *** [main.o] Error 2
make[1]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
Makefile:169: recipe for target 'all' failed
make: *** [all] Error 1
```
|
1.0
|
Fix or remove zsh-4.0.1 build - ```
/tmp/shell-build.20171215153350.26110 /media/pawamoy/Data/git/shenv/shenv/plugins/shell-build/share/shell-build
/tmp/shell-build.20171215153350.26110/zsh-4.0.1 /tmp/shell-build.20171215153350.26110 /media/pawamoy/Data/git/shenv/shenv/plugins/shell-build/share/shell-build
creating cache ./config.cache
configuring for zsh 4.0.1
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler (gcc -L/home/pawamoy/.shenv/versions/zsh-4.0.1/lib ) works... yes
checking whether the C compiler (gcc -L/home/pawamoy/.shenv/versions/zsh-4.0.1/lib ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking whether large file support needs explicit enabling... no
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking for working const... yes
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for executable suffix... no
checking for gcc option to accept ANSI C...
checking whether to use prototypes... yes
checking for working alloca.h... yes
checking for alloca... yes
checking if the compiler supports union initialisation... yes
checking if signed to unsigned casting is broken... no
checking if the compiler supports variable-length arrays... yes
checking what to set MAXJOB to... 50
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for mawk... mawk
checking whether ln works... yes
checking for yodl... no
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether stat file-mode macros are broken... no
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/time.h... yes
checking for sys/times.h... yes
checking for sys/select.h... yes
checking for termcap.h... yes
checking for termio.h... yes
checking for termios.h... yes
checking for sys/param.h... yes
checking for sys/filio.h... no
checking for string.h... yes
checking for memory.h... yes
checking for limits.h... yes
checking for fcntl.h... yes
checking for libc.h... no
checking for sys/utsname.h... yes
checking for sys/resource.h... yes
checking for locale.h... yes
checking for errno.h... yes
checking for stdlib.h... yes
checking for unistd.h... yes
checking for sys/capability.h... no
checking for utmp.h... yes
checking for utmpx.h... yes
checking for sys/types.h... yes
checking for pwd.h... yes
checking for grp.h... yes
checking for poll.h... yes
checking for sys/mman.h... yes
checking for netinet/in_systm.h... yes
checking for dlfcn.h... yes
checking for dl.h... no
checking for conflicts in sys/time.h and sys/select.h... no
checking POSIX termios... yes
checking TIOCGWINSZ in termios.h... no
checking TIOCGWINSZ in sys/ioctl.h... yes
checking for sys/ptem.h... no
checking for printf in -lc... yes
checking for pow in -lm... yes
checking for library containing tgetent... -ltermcap
checking for library containing yp_all... -lnsl
checking for dlopen in -ldl... yes
checking for cap_get_proc in -lcap... no
checking for socket in -lsocket... no
checking if an include file defines ospeed... yes
checking return type of signal handlers... void
checking for pid_t... yes
checking for off_t... yes
checking for ino_t... yes
checking for mode_t... yes
checking for uid_t in sys/types.h... yes
checking for size_t... yes
checking if long is 64 bits... yes
checking for sigset_t... yes
checking for struct timezone... yes
checking for struct utmp... yes
checking for struct utmpx... yes
checking for ut_host in struct utmp... yes
checking for ut_host in struct utmpx... yes
checking for ut_xtime in struct utmpx... no
checking for ut_tv in struct utmpx... yes
checking for d_ino in struct dirent... yes
checking for d_stat in struct dirent... no
checking for d_ino in struct direct... no
checking for d_stat in struct direct... no
checking for sin6_scope_id in struct sockaddr_in6... yes
checking if we need our own h_errno... yes
checking for strftime... yes
checking for difftime... yes
checking for gettimeofday... yes
checking for select... yes
checking for poll... yes
checking for readlink... yes
checking for lstat... yes
checking for lchown... yes
checking for faccessx... no
checking for fchdir... yes
checking for ftruncate... yes
checking for fseeko... yes
checking for ftello... yes
checking for mkfifo... yes
checking for _mktemp... no
checking for waitpid... yes
checking for wait3... yes
checking for sigaction... yes
checking for sigblock... yes
checking for sighold... yes
checking for sigrelse... yes
checking for sigsetmask... yes
checking for sigprocmask... yes
checking for killpg... yes
checking for setpgid... yes
checking for setpgrp... yes
checking for tcsetpgrp... yes
checking for tcgetattr... yes
checking for nice... yes
checking for gethostname... yes
checking for gethostbyname2... yes
checking for getipnodebyname... no
checking for inet_aton... yes
checking for inet_pton... yes
checking for inet_ntop... yes
checking for getlogin... yes
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for getgrgid... yes
checking for getgrnam... yes
checking for initgroups... yes
checking for nis_list... yes
checking for setuid... yes
checking for seteuid... yes
checking for setreuid... yes
checking for setresuid... yes
checking for setsid... yes
checking for memcpy... yes
checking for memmove... yes
checking for strstr... yes
checking for strerror... yes
checking for cap_get_proc... no
checking for getrlimit... yes
checking for setlocale... yes
checking for uname... yes
checking for signgam... yes
checking for putenv... yes
checking for getenv... yes
checking for brk... yes
checking for sbrk... yes
checking for pathconf... yes
checking for sysconf... yes
checking for tgetent... yes
checking for tigetflag... yes
checking for tigetnum... yes
checking for tigetstr... yes
checking for setupterm... yes
checking for working strcoll... yes
checking if tgetent accepts NULL... yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... no
checking whether getpgrp takes no argument... yes
checking for dlopen... yes
checking for dlerror... yes
checking for dlsym... yes
checking for dlclose... yes
checking for load... no
checking for loadquery... no
checking for loadbind... no
checking for unload... no
checking for shl_load... no
checking for shl_unload... no
checking for shl_findsym... no
checking what style of signals to use... POSIX_SIGNALS
checking where signal.h is located... /usr/include/x86_64-linux-gnu/bits/signum.h
checking where the RLIMIT macros are located... configure: warning: RLIMIT MACROS NOT FOUND: please report to developers
/dev/null
checking if rlim_t is longer than a long... no
checking if the rlim_t is unsigned... yes
checking for rlim_t... yes
checking for /dev/fd filesystem... /proc/self/fd
checking for RFS superroot directory... no
checking whether we should use the native getcwd... no
checking for NIS... no
checking for NIS+... no
checking for utmp file... /var/run/utmp
checking for wtmp file... /var/log/wtmp
checking for utmpx file... no
checking for wtmpx file... no
checking for brk() prototype in <unistd.h>... yes
checking for sbrk() prototype in <unistd.h>... yes
checking for ioctl prototype in <sys/ioctl.h>... yes
checking for mknod prototype in <sys/stat.h>... yes
checking if named FIFOs work... yes
checking if echo in /bin/sh interprets escape sequences... yes
checking if link() works... yes
checking if kill(pid, 0) returns ESRCH correctly... yes
checking if POSIX sigsuspend() works... yes
checking if tcsetpgrp() actually works... yes
checking if getpwnam() is faked... no
checking if your system use ELF binaries... yes
checking if your dlsym() needs a leading underscore... no
checking if environ is available in shared libraries... yes
checking if tgetent is available in shared libraries... yes
checking if tigetstr is available in shared libraries... yes
checking if name clashes in shared objects are OK... yes
checking for working RTLD_GLOBAL... yes
checking whether symbols in the executable are available... yes
checking whether executables can be stripped... yes
checking whether libraries can be stripped... yes
creating ./config.modules
updating cache ./config.cache
creating ./config.status
creating Config/defs.mk
creating Makefile
creating Doc/Makefile
creating Etc/Makefile
creating Src/Makefile
creating Test/Makefile
creating config.h
zsh configuration
-----------------
zsh version : 4.0.1
host operating system : x86_64-unknown-linux-gnu
source code location : .
compiler : gcc
preprocessor flags : -I/home/pawamoy/.shenv/versions/zsh-4.0.1/include
executable compiler flags : -Wall -Wno-implicit -Wmissing-prototypes -O2
module compiler flags : -Wall -Wno-implicit -Wmissing-prototypes -O2 -fpic
executable linker flags : -rdynamic
module linker flags : -shared
library flags : -ldl -lnsl -ltermcap -lm -lc
installation basename : zsh
binary install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/bin
man page install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/man
info install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/info
functions install path : /home/pawamoy/.shenv/versions/zsh-4.0.1/share/zsh/4.0.1/functions
See config.modules for installed modules and functions.
make[1]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
rm -f stamp-modobjs.tmp
cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
creating Src/Makemod.in
creating Src/Makemod
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
echo 'timestamp for *.mdd files' > ../Src/modules.stamp
creating Src/Builtins/Makefile.in
creating Src/Builtins/Makefile
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Builtins'
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Builtins'
creating Src/Modules/Makefile.in
creating Src/Modules/Makefile
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Modules'
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Modules'
creating Src/Zle/Makefile.in
creating Src/Zle/Makefile
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Zle'
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src/Zle'
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ./signames1.awk /usr/include/x86_64-linux-gnu/bits/signum.h >sigtmp.c
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ./signames1.awk /usr/include/x86_64-linux-gnu/bits/signum.h >sigtmp.c
make[2]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ../Src/makepro.awk builtin.c Src > builtin.syms
gcc -E sigtmp.c >sigtmp.out
gcc -E sigtmp.c >sigtmp.out
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
mawk -f ../Src/makepro.awk compat.c Src > compat.syms
mawk -f ../Src/makepro.awk cond.c Src > cond.syms
mawk -f ./signames2.awk sigtmp.out > signames.c
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
rm -f sigtmp.c sigtmp.out
mawk -f ../Src/makepro.awk exec.c Src > exec.syms
Updated `zsh.mdh'.
echo 'timestamp for zsh.mdh against zsh.mdd' > zsh.mdhs
mawk -f ../Src/makepro.awk glob.c Src > glob.syms
mawk -f ./signames2.awk sigtmp.out > signames.c
mawk -f ../Src/makepro.awk builtin.c Src > builtin.syms
mawk -f ../Src/makepro.awk hashtable.c Src > hashtable.syms
mawk: cannot open sigtmp.out (No such file or directory)
Makemod:519: recipe for target 'signames.c' failed
make[2]: *** [signames.c] Error 2
make[3]: Entering directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
make[2]: *** Waiting for unfinished jobs....
mawk -f ../Src/makepro.awk hist.c Src > hist.syms
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
Makefile:445: recipe for target 'headers' failed
make[1]: *** [headers] Error 2
make[1]: *** Waiting for unfinished jobs....
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < builtin.syms) \
> builtin.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < compat.syms) \
> compat.epro
mawk -f ../Src/makepro.awk init.c Src > init.syms
make[3]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < compat.syms) \
> `echo compat.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < builtin.syms) \
> `echo builtin.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk input.c Src > input.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < cond.syms) \
> cond.epro
mawk -f ../Src/makepro.awk jobs.c Src > jobs.syms
`zsh.mdh' is up to date.
echo 'timestamp for zsh.mdh against zsh.mdd' > zsh.mdhs
mawk -f ../Src/makepro.awk lex.c Src > lex.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < cond.syms) \
> `echo cond.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk linklist.c Src > linklist.syms
mawk -f ../Src/makepro.awk loop.c Src > loop.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < exec.syms) \
> exec.epro
mawk -f ../Src/makepro.awk math.c Src > math.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < glob.syms) \
> glob.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < exec.syms) \
> `echo exec.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk mem.c Src > mem.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < hashtable.syms) \
> hashtable.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < glob.syms) \
> `echo glob.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < hashtable.syms) \
> `echo hashtable.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk module.c Src > module.syms
mawk -f ../Src/makepro.awk options.c Src > options.syms
mawk -f ../Src/makepro.awk params.c Src > params.syms
mawk -f ../Src/makepro.awk parse.c Src > parse.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < hist.syms) \
> hist.epro
mawk -f ../Src/makepro.awk pattern.c Src > pattern.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < hist.syms) \
> `echo hist.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < init.syms) \
> init.epro
mawk -f ../Src/makepro.awk prompt.c Src > prompt.syms
mawk -f ../Src/makepro.awk signals.c Src > signals.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < init.syms) \
> `echo init.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < input.syms) \
> input.epro
mawk -f ../Src/makepro.awk signames.c Src > signames.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < input.syms) \
> `echo input.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk string.c Src > string.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < jobs.syms) \
> jobs.epro
mawk -f ../Src/makepro.awk subst.c Src > subst.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < lex.syms) \
> lex.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < jobs.syms) \
> `echo jobs.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < linklist.syms) \
> linklist.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < lex.syms) \
> `echo lex.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk text.c Src > text.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < linklist.syms) \
> `echo linklist.epro | sed 's/\.epro$/.pro/'`
mawk -f ../Src/makepro.awk utils.c Src > utils.syms
mawk -f ../Src/makepro.awk watch.c Src > watch.syms
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < loop.syms) \
> loop.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < math.syms) \
> math.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < mem.syms) \
> mem.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < math.syms) \
> `echo math.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < mem.syms) \
> `echo mem.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < module.syms) \
> module.epro
( echo '#!'; cat builtin.syms compat.syms cond.syms exec.syms glob.syms hashtable.syms hist.syms init.syms input.syms jobs.syms lex.syms linklist.syms loop.syms math.syms mem.syms module.syms options.syms params.syms parse.syms pattern.syms prompt.syms signals.syms signames.syms string.syms subst.syms text.syms utils.syms watch.syms | sed -n '/^X/{s/^X//;p;}' | sort -u ) > zsh.export
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < module.syms) \
> `echo module.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < options.syms) \
> options.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < loop.syms) \
> `echo loop.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < options.syms) \
> `echo options.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < params.syms) \
> params.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < params.syms) \
> `echo params.epro | sed 's/\.epro$/.pro/'`
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < parse.syms) \
> parse.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < pattern.syms) \
> pattern.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < prompt.syms) \
> prompt.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < pattern.syms) \
> `echo pattern.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < parse.syms) \
> `echo parse.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < prompt.syms) \
> `echo prompt.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < signals.syms) \
> signals.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < signames.syms) \
> signames.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < signals.syms) \
> `echo signals.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < string.syms) \
> string.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < subst.syms) \
> subst.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < signames.syms) \
> `echo signames.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < string.syms) \
> `echo string.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < subst.syms) \
> `echo subst.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < text.syms) \
> text.epro
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < text.syms) \
> `echo text.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < utils.syms) \
> utils.epro
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < watch.syms) \
> watch.epro
mawk -f ../Src/makepro.awk main.c Src > main.syms
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < watch.syms) \
> `echo watch.epro | sed 's/\.epro$/.pro/'`
grep 'define.*SIGCOUNT' signames.c > sigcount.h
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < utils.syms) \
> `echo utils.epro | sed 's/\.epro$/.pro/'`
(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < main.syms) \
> main.epro
Makemod:525: recipe for target 'sigcount.h' failed
make[2]: *** [sigcount.h] Error 1
make[2]: *** Waiting for unfinished jobs....
(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < main.syms) \
> `echo main.epro | sed 's/\.epro$/.pro/'`
make[2]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
Makefile:445: recipe for target 'main.o' failed
make[1]: *** [main.o] Error 2
make[1]: Leaving directory '/tmp/shell-build.20171215153350.26110/zsh-4.0.1/Src'
Makefile:169: recipe for target 'all' failed
make: *** [all] Error 1
```
|
non_defect
|
fix or remove zsh build tmp shell build media pawamoy data git shenv shenv plugins shell build share shell build tmp shell build zsh tmp shell build media pawamoy data git shenv shenv plugins shell build share shell build creating cache config cache configuring for zsh checking host system type unknown linux gnu checking for gcc gcc checking whether the c compiler gcc l home pawamoy shenv versions zsh lib works yes checking whether the c compiler gcc l home pawamoy shenv versions zsh lib is a cross compiler no checking whether we are using gnu c yes checking whether gcc accepts g yes checking whether large file support needs explicit enabling no checking how to run the c preprocessor gcc e checking whether gcc needs traditional no checking for working const yes checking for cygwin environment no checking for environment no checking for executable suffix no checking for gcc option to accept ansi c checking whether to use prototypes yes checking for working alloca h yes checking for alloca yes checking if the compiler supports union initialisation yes checking if signed to unsigned casting is broken no checking if the compiler supports variable length arrays yes checking what to set maxjob to checking whether make sets make yes checking for a bsd compatible install usr bin install c checking for mawk mawk checking whether ln works yes checking for yodl no checking for dirent h that defines dir yes checking for opendir in ldir no checking for ansi c header files yes checking whether time h and sys time h may both be included yes checking whether stat file mode macros are broken no checking for sys wait h that is posix compatible yes checking for sys time h yes checking for sys times h yes checking for sys select h yes checking for termcap h yes checking for termio h yes checking for termios h yes checking for sys param h yes checking for sys filio h no checking for string h yes checking for memory h yes checking for limits h yes checking for fcntl h yes checking for libc h no checking for sys utsname h yes checking for sys resource h yes checking for locale h yes checking for errno h yes checking for stdlib h yes checking for unistd h yes checking for sys capability h no checking for utmp h yes checking for utmpx h yes checking for sys types h yes checking for pwd h yes checking for grp h yes checking for poll h yes checking for sys mman h yes checking for netinet in systm h yes checking for dlfcn h yes checking for dl h no checking for conflicts in sys time h and sys select h no checking posix termios yes checking tiocgwinsz in termios h no checking tiocgwinsz in sys ioctl h yes checking for sys ptem h no checking for printf in lc yes checking for pow in lm yes checking for library containing tgetent ltermcap checking for library containing yp all lnsl checking for dlopen in ldl yes checking for cap get proc in lcap no checking for socket in lsocket no checking if an include file defines ospeed yes checking return type of signal handlers void checking for pid t yes checking for off t yes checking for ino t yes checking for mode t yes checking for uid t in sys types h yes checking for size t yes checking if long is bits yes checking for sigset t yes checking for struct timezone yes checking for struct utmp yes checking for struct utmpx yes checking for ut host in struct utmp yes checking for ut host in struct utmpx yes checking for ut xtime in struct utmpx no checking for ut tv in struct utmpx yes checking for d ino in struct dirent yes checking for d stat in struct dirent no checking for d ino in struct direct no checking for d stat in struct direct no checking for scope id in struct sockaddr yes checking if we need our own h errno yes checking for strftime yes checking for difftime yes checking for gettimeofday yes checking for select yes checking for poll yes checking for readlink yes checking for lstat yes checking for lchown yes checking for faccessx no checking for fchdir yes checking for ftruncate yes checking for fseeko yes checking for ftello yes checking for mkfifo yes checking for mktemp no checking for waitpid yes checking for yes checking for sigaction yes checking for sigblock yes checking for sighold yes checking for sigrelse yes checking for sigsetmask yes checking for sigprocmask yes checking for killpg yes checking for setpgid yes checking for setpgrp yes checking for tcsetpgrp yes checking for tcgetattr yes checking for nice yes checking for gethostname yes checking for yes checking for getipnodebyname no checking for inet aton yes checking for inet pton yes checking for inet ntop yes checking for getlogin yes checking for getpwent yes checking for getpwnam yes checking for getpwuid yes checking for getgrgid yes checking for getgrnam yes checking for initgroups yes checking for nis list yes checking for setuid yes checking for seteuid yes checking for setreuid yes checking for setresuid yes checking for setsid yes checking for memcpy yes checking for memmove yes checking for strstr yes checking for strerror yes checking for cap get proc no checking for getrlimit yes checking for setlocale yes checking for uname yes checking for signgam yes checking for putenv yes checking for getenv yes checking for brk yes checking for sbrk yes checking for pathconf yes checking for sysconf yes checking for tgetent yes checking for tigetflag yes checking for tigetnum yes checking for tigetstr yes checking for setupterm yes checking for working strcoll yes checking if tgetent accepts null yes checking for unistd h cached yes checking for getpagesize yes checking for working mmap no checking whether getpgrp takes no argument yes checking for dlopen yes checking for dlerror yes checking for dlsym yes checking for dlclose yes checking for load no checking for loadquery no checking for loadbind no checking for unload no checking for shl load no checking for shl unload no checking for shl findsym no checking what style of signals to use posix signals checking where signal h is located usr include linux gnu bits signum h checking where the rlimit macros are located configure warning rlimit macros not found please report to developers dev null checking if rlim t is longer than a long no checking if the rlim t is unsigned yes checking for rlim t yes checking for dev fd filesystem proc self fd checking for rfs superroot directory no checking whether we should use the native getcwd no checking for nis no checking for nis no checking for utmp file var run utmp checking for wtmp file var log wtmp checking for utmpx file no checking for wtmpx file no checking for brk prototype in yes checking for sbrk prototype in yes checking for ioctl prototype in yes checking for mknod prototype in yes checking if named fifos work yes checking if echo in bin sh interprets escape sequences yes checking if link works yes checking if kill pid returns esrch correctly yes checking if posix sigsuspend works yes checking if tcsetpgrp actually works yes checking if getpwnam is faked no checking if your system use elf binaries yes checking if your dlsym needs a leading underscore no checking if environ is available in shared libraries yes checking if tgetent is available in shared libraries yes checking if tigetstr is available in shared libraries yes checking if name clashes in shared objects are ok yes checking for working rtld global yes checking whether symbols in the executable are available yes checking whether executables can be stripped yes checking whether libraries can be stripped yes creating config modules updating cache config cache creating config status creating config defs mk creating makefile creating doc makefile creating etc makefile creating src makefile creating test makefile creating config h zsh configuration zsh version host operating system unknown linux gnu source code location compiler gcc preprocessor flags i home pawamoy shenv versions zsh include executable compiler flags wall wno implicit wmissing prototypes module compiler flags wall wno implicit wmissing prototypes fpic executable linker flags rdynamic module linker flags shared library flags ldl lnsl ltermcap lm lc installation basename zsh binary install path home pawamoy shenv versions zsh bin man page install path home pawamoy shenv versions zsh man info install path home pawamoy shenv versions zsh info functions install path home pawamoy shenv versions zsh share zsh functions see config modules for installed modules and functions make entering directory tmp shell build zsh src rm f stamp modobjs tmp cd bin sh top srcdir src mkmakemod sh src makemod creating src makemod in creating src makemod make entering directory tmp shell build zsh src echo timestamp for mdd files src modules stamp creating src builtins makefile in creating src builtins makefile make entering directory tmp shell build zsh src builtins make leaving directory tmp shell build zsh src builtins creating src modules makefile in creating src modules makefile make entering directory tmp shell build zsh src modules make leaving directory tmp shell build zsh src modules creating src zle makefile in creating src zle makefile make entering directory tmp shell build zsh src zle make leaving directory tmp shell build zsh src zle make leaving directory tmp shell build zsh src make entering directory tmp shell build zsh src mawk f awk usr include linux gnu bits signum h sigtmp c make entering directory tmp shell build zsh src mawk f awk usr include linux gnu bits signum h sigtmp c make entering directory tmp shell build zsh src mawk f src makepro awk builtin c src builtin syms gcc e sigtmp c sigtmp out gcc e sigtmp c sigtmp out make entering directory tmp shell build zsh src mawk f src makepro awk compat c src compat syms mawk f src makepro awk cond c src cond syms mawk f awk sigtmp out signames c make leaving directory tmp shell build zsh src rm f sigtmp c sigtmp out mawk f src makepro awk exec c src exec syms updated zsh mdh echo timestamp for zsh mdh against zsh mdd zsh mdhs mawk f src makepro awk glob c src glob syms mawk f awk sigtmp out signames c mawk f src makepro awk builtin c src builtin syms mawk f src makepro awk hashtable c src hashtable syms mawk cannot open sigtmp out no such file or directory makemod recipe for target signames c failed make error make entering directory tmp shell build zsh src make waiting for unfinished jobs mawk f src makepro awk hist c src hist syms make leaving directory tmp shell build zsh src makefile recipe for target headers failed make error make waiting for unfinished jobs echo generated automatically sed n e s e p builtin syms builtin epro echo generated automatically sed n e s e p compat syms compat epro mawk f src makepro awk init c src init syms make leaving directory tmp shell build zsh src echo generated automatically sed n l s l p compat syms echo compat epro sed s epro pro echo generated automatically sed n l s l p builtin syms echo builtin epro sed s epro pro mawk f src makepro awk input c src input syms echo generated automatically sed n e s e p cond syms cond epro mawk f src makepro awk jobs c src jobs syms zsh mdh is up to date echo timestamp for zsh mdh against zsh mdd zsh mdhs mawk f src makepro awk lex c src lex syms echo generated automatically sed n l s l p cond syms echo cond epro sed s epro pro mawk f src makepro awk linklist c src linklist syms mawk f src makepro awk loop c src loop syms echo generated automatically sed n e s e p exec syms exec epro mawk f src makepro awk math c src math syms echo generated automatically sed n e s e p glob syms glob epro echo generated automatically sed n l s l p exec syms echo exec epro sed s epro pro mawk f src makepro awk mem c src mem syms echo generated automatically sed n e s e p hashtable syms hashtable epro echo generated automatically sed n l s l p glob syms echo glob epro sed s epro pro echo generated automatically sed n l s l p hashtable syms echo hashtable epro sed s epro pro mawk f src makepro awk module c src module syms mawk f src makepro awk options c src options syms mawk f src makepro awk params c src params syms mawk f src makepro awk parse c src parse syms echo generated automatically sed n e s e p hist syms hist epro mawk f src makepro awk pattern c src pattern syms echo generated automatically sed n l s l p hist syms echo hist epro sed s epro pro echo generated automatically sed n e s e p init syms init epro mawk f src makepro awk prompt c src prompt syms mawk f src makepro awk signals c src signals syms echo generated automatically sed n l s l p init syms echo init epro sed s epro pro echo generated automatically sed n e s e p input syms input epro mawk f src makepro awk signames c src signames syms echo generated automatically sed n l s l p input syms echo input epro sed s epro pro mawk f src makepro awk string c src string syms echo generated automatically sed n e s e p jobs syms jobs epro mawk f src makepro awk subst c src subst syms echo generated automatically sed n e s e p lex syms lex epro echo generated automatically sed n l s l p jobs syms echo jobs epro sed s epro pro echo generated automatically sed n e s e p linklist syms linklist epro echo generated automatically sed n l s l p lex syms echo lex epro sed s epro pro mawk f src makepro awk text c src text syms echo generated automatically sed n l s l p linklist syms echo linklist epro sed s epro pro mawk f src makepro awk utils c src utils syms mawk f src makepro awk watch c src watch syms echo generated automatically sed n e s e p loop syms loop epro echo generated automatically sed n e s e p math syms math epro echo generated automatically sed n e s e p mem syms mem epro echo generated automatically sed n l s l p math syms echo math epro sed s epro pro echo generated automatically sed n l s l p mem syms echo mem epro sed s epro pro echo generated automatically sed n e s e p module syms module epro echo cat builtin syms compat syms cond syms exec syms glob syms hashtable syms hist syms init syms input syms jobs syms lex syms linklist syms loop syms math syms mem syms module syms options syms params syms parse syms pattern syms prompt syms signals syms signames syms string syms subst syms text syms utils syms watch syms sed n x s x p sort u zsh export echo generated automatically sed n l s l p module syms echo module epro sed s epro pro echo generated automatically sed n e s e p options syms options epro echo generated automatically sed n l s l p loop syms echo loop epro sed s epro pro echo generated automatically sed n l s l p options syms echo options epro sed s epro pro echo generated automatically sed n e s e p params syms params epro echo generated automatically sed n l s l p params syms echo params epro sed s epro pro make leaving directory tmp shell build zsh src echo generated automatically sed n e s e p parse syms parse epro echo generated automatically sed n e s e p pattern syms pattern epro echo generated automatically sed n e s e p prompt syms prompt epro echo generated automatically sed n l s l p pattern syms echo pattern epro sed s epro pro echo generated automatically sed n l s l p parse syms echo parse epro sed s epro pro echo generated automatically sed n l s l p prompt syms echo prompt epro sed s epro pro echo generated automatically sed n e s e p signals syms signals epro echo generated automatically sed n e s e p signames syms signames epro echo generated automatically sed n l s l p signals syms echo signals epro sed s epro pro echo generated automatically sed n e s e p string syms string epro echo generated automatically sed n e s e p subst syms subst epro echo generated automatically sed n l s l p signames syms echo signames epro sed s epro pro echo generated automatically sed n l s l p string syms echo string epro sed s epro pro echo generated automatically sed n l s l p subst syms echo subst epro sed s epro pro echo generated automatically sed n e s e p text syms text epro echo generated automatically sed n l s l p text syms echo text epro sed s epro pro echo generated automatically sed n e s e p utils syms utils epro echo generated automatically sed n e s e p watch syms watch epro mawk f src makepro awk main c src main syms echo generated automatically sed n l s l p watch syms echo watch epro sed s epro pro grep define sigcount signames c sigcount h echo generated automatically sed n l s l p utils syms echo utils epro sed s epro pro echo generated automatically sed n e s e p main syms main epro makemod recipe for target sigcount h failed make error make waiting for unfinished jobs echo generated automatically sed n l s l p main syms echo main epro sed s epro pro make leaving directory tmp shell build zsh src makefile recipe for target main o failed make error make leaving directory tmp shell build zsh src makefile recipe for target all failed make error
| 0
|
5,577
| 2,610,190,821
|
IssuesEvent
|
2015-02-26 19:00:22
|
chrsmith/quchuseban
|
https://api.github.com/repos/chrsmith/quchuseban
|
opened
|
支招面部色斑怎样去除
|
auto-migrated Priority-Medium Type-Defect
|
```
《摘要》
执子之手，与子偕老。是我们对着三生石，许下的诺言。那��
�候的我们都带着一份热情，我们偏执的以为，只要我们相信�
��么奇迹就一定会出现。于是我们固执的朝着我们以为的方向
前进着。却不知道，原来我们走上的那条路，虽然不是绝路��
�但是同样的充满了荆棘与磨难。祛斑，是每个女人心中的一�
��病，怎么祛斑才是最安全的那！面部色斑怎样去除，
《客户案例》
这几年吧因为工作的关系，每天都要跟电脑打交道，而��
�每天至少都是十几个小时以上，都知道有辐射，时间长了也�
��烦，可是没办法啊，总要生活，做别的又没有什么经验，这
可不，这两年连斑点也在脸上长起来了，开始的时候还是鼻��
�两边，多是挺多的，不过不明显，稍微遮一下，也看不出来�
��我也担心过，就怕越来越多，越来越明显，也赶紧的找了一
些小方法，像什么蜂蜜面膜啊、橄榄油啊、水果面膜啊几乎��
�试过，开始皮肤变了好一点，可斑点还是很明显，连脸颊和�
��头都没能幸免，连着试了一个月，几乎是没什么效果，连带
着心情都变得特别不好，我都快郁闷死了，好好的脸怎么就��
�倒腾成这样了，这还没找男朋友呢，愁死了，我可不想顶着�
��样一张脸，我自己都别扭，就更别说别人了，我也在打听有
没有什么好的祛斑产品，好多人都说「黛芙薇尔精华液」不��
�，我也仔细的看了，也是有点小犹豫，看起来是不错，口碑�
��蛮好的，还是有点小贵啊，倒不是舍不得花钱，如果真的能
去掉，这钱我也花的心甘情愿，可万一没用，不是白忙活了��
�?其实，纠结了有蛮久，在她们反复保证如果无效会退款而且
还提供了面部照片的情况下，我还是决定买了，事实也证明��
�的选择是正确的，差不多有三个周期的时候，我的斑已经全�
��去掉了，皮肤也没那么干燥了，不过对着电脑的时候比以前
注意了很多，几个月来也没见再怎么长，想想真是美啊，心��
�舒坦多了。
阅读了面部色斑怎样去除，再看脸上容易长斑的原因：
《色斑形成原因》
内部因素
一、压力
当人受到压力时，就会分泌肾上腺素，为对付压力而做��
�备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在�
��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出
现斑，这时候出现的斑点在产后大部分会消失。可是，新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因，都会使斑加深。有时新长出的斑，产后也不会消失，所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态�
��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是
内分泌失调导致过敏体质而形成的。另外，身体状态不正常��
�时候，紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵�
��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候，人体为了保护皮肤，会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。��
�皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦�
��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的，则本人长斑的概率就很高，这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人，要注意避免引发长斑的重要因素之一——紫外
线照射，这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必�
��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑
，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显
而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新��
�客都是通过老顾客介绍而来，口碑由此而来!
2，服用黛芙薇尔美白，会伤身体吗?有副作用吗?
答：黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻�
��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技��
�，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽�
��迹，令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3，去除黄褐斑之后，会反弹吗?
答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔��
�白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话，让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来，请问�
��如果效果不好，会有客户转介绍吗?
4，你们的价格有点贵，能不能便宜一点?
答：如果您使用西药最少需要2000元，煎服的药最少需要3
000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去�
��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的��
�是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的�
��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉��
�，不但斑没去掉，还把自己的皮肤弄的越来越糟吗
5，我适合用黛芙薇尔精华液吗?
答：黛芙薇尔适用人群：
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
面部色斑怎样去除，同时为您分享祛斑小方法
1、将鲜明萝卜辟碎挤汁，取10-30毫升，每日上晚洗完脸后涂��
�，待干后，洗净。此外，每日喝一杯胡萝卜，可美白肌肤。
2.将柠檬汁搅汁，加糖水适量饮用。柠檬中含有大量维生素C��
�钙、磷、铁等。常饮柠檬汁不仅可美白肌肤，还能使黑色素�
��淀，达到祛斑的作用。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 5:01
|
1.0
|
支招面部色斑怎样去除 - ```
《摘要》
执子之手，与子偕老。是我们对着三生石，许下的诺言。那��
�候的我们都带着一份热情，我们偏执的以为，只要我们相信�
��么奇迹就一定会出现。于是我们固执的朝着我们以为的方向
前进着。却不知道，原来我们走上的那条路，虽然不是绝路��
�但是同样的充满了荆棘与磨难。祛斑，是每个女人心中的一�
��病，怎么祛斑才是最安全的那！面部色斑怎样去除，
《客户案例》
这几年吧因为工作的关系，每天都要跟电脑打交道，而��
�每天至少都是十几个小时以上，都知道有辐射，时间长了也�
��烦，可是没办法啊，总要生活，做别的又没有什么经验，这
可不，这两年连斑点也在脸上长起来了，开始的时候还是鼻��
�两边，多是挺多的，不过不明显，稍微遮一下，也看不出来�
��我也担心过，就怕越来越多，越来越明显，也赶紧的找了一
些小方法，像什么蜂蜜面膜啊、橄榄油啊、水果面膜啊几乎��
�试过，开始皮肤变了好一点，可斑点还是很明显，连脸颊和�
��头都没能幸免，连着试了一个月，几乎是没什么效果，连带
着心情都变得特别不好，我都快郁闷死了，好好的脸怎么就��
�倒腾成这样了，这还没找男朋友呢，愁死了，我可不想顶着�
��样一张脸，我自己都别扭，就更别说别人了，我也在打听有
没有什么好的祛斑产品，好多人都说「黛芙薇尔精华液」不��
�，我也仔细的看了，也是有点小犹豫，看起来是不错，口碑�
��蛮好的，还是有点小贵啊，倒不是舍不得花钱，如果真的能
去掉，这钱我也花的心甘情愿，可万一没用，不是白忙活了��
�?其实，纠结了有蛮久，在她们反复保证如果无效会退款而且
还提供了面部照片的情况下，我还是决定买了，事实也证明��
�的选择是正确的，差不多有三个周期的时候，我的斑已经全�
��去掉了，皮肤也没那么干燥了，不过对着电脑的时候比以前
注意了很多，几个月来也没见再怎么长，想想真是美啊，心��
�舒坦多了。
阅读了面部色斑怎样去除，再看脸上容易长斑的原因：
《色斑形成原因》
内部因素
一、压力
当人受到压力时，就会分泌肾上腺素，为对付压力而做��
�备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在�
��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出
现斑，这时候出现的斑点在产后大部分会消失。可是，新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因，都会使斑加深。有时新长出的斑，产后也不会消失，所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态�
��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是
内分泌失调导致过敏体质而形成的。另外，身体状态不正常��
�时候，紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵�
��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候，人体为了保护皮肤，会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。��
�皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦�
��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的，则本人长斑的概率就很高，这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人，要注意避免引发长斑的重要因素之一——紫外
线照射，这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必�
��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑
，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显
而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新��
�客都是通过老顾客介绍而来，口碑由此而来!
2，服用黛芙薇尔美白，会伤身体吗?有副作用吗?
答：黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻�
��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技��
�，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽�
��迹，令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3，去除黄褐斑之后，会反弹吗?
答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔��
�白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话，让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来，请问�
��如果效果不好，会有客户转介绍吗?
4，你们的价格有点贵，能不能便宜一点?
答：如果您使用西药最少需要2000元，煎服的药最少需要3
000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去�
��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的��
�是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的�
��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉��
�，不但斑没去掉，还把自己的皮肤弄的越来越糟吗
5，我适合用黛芙薇尔精华液吗?
答：黛芙薇尔适用人群：
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
面部色斑怎样去除，同时为您分享祛斑小方法
1、将鲜明萝卜辟碎挤汁，取10-30毫升，每日上晚洗完脸后涂��
�，待干后，洗净。此外，每日喝一杯胡萝卜，可美白肌肤。
2.将柠檬汁搅汁，加糖水适量饮用。柠檬中含有大量维生素C��
�钙、磷、铁等。常饮柠檬汁不仅可美白肌肤，还能使黑色素�
��淀，达到祛斑的作用。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 5:01
|
defect
|
支招面部色斑怎样去除 《摘要》 执子之手，与子偕老。是我们对着三生石，许下的诺言。那�� �候的我们都带着一份热情，我们偏执的以为，只要我们相信� ��么奇迹就一定会出现。于是我们固执的朝着我们以为的方向 前进着。却不知道，原来我们走上的那条路，虽然不是绝路�� �但是同样的充满了荆棘与磨难。祛斑，是每个女人心中的一� ��病，怎么祛斑才是最安全的那！面部色斑怎样去除， 《客户案例》 这几年吧因为工作的关系，每天都要跟电脑打交道，而�� �每天至少都是十几个小时以上，都知道有辐射，时间长了也� ��烦，可是没办法啊，总要生活，做别的又没有什么经验，这 可不，这两年连斑点也在脸上长起来了，开始的时候还是鼻�� �两边，多是挺多的，不过不明显，稍微遮一下，也看不出来� ��我也担心过，就怕越来越多，越来越明显，也赶紧的找了一 些小方法，像什么蜂蜜面膜啊、橄榄油啊、水果面膜啊几乎�� �试过，开始皮肤变了好一点，可斑点还是很明显，连脸颊和� ��头都没能幸免，连着试了一个月，几乎是没什么效果，连带 着心情都变得特别不好，我都快郁闷死了，好好的脸怎么就�� �倒腾成这样了，这还没找男朋友呢，愁死了，我可不想顶着� ��样一张脸，我自己都别扭，就更别说别人了，我也在打听有 没有什么好的祛斑产品，好多人都说「黛芙薇尔精华液」不�� �，我也仔细的看了，也是有点小犹豫，看起来是不错，口碑� ��蛮好的，还是有点小贵啊，倒不是舍不得花钱，如果真的能 去掉，这钱我也花的心甘情愿，可万一没用，不是白忙活了�� � 其实，纠结了有蛮久，在她们反复保证如果无效会退款而且 还提供了面部照片的情况下，我还是决定买了，事实也证明�� �的选择是正确的，差不多有三个周期的时候，我的斑已经全� ��去掉了，皮肤也没那么干燥了，不过对着电脑的时候比以前 注意了很多，几个月来也没见再怎么长，想想真是美啊，心�� �舒坦多了。 阅读了面部色斑怎样去除，再看脸上容易长斑的原因： 《色斑形成原因》 内部因素 一、压力 当人受到压力时，就会分泌肾上腺素，为对付压力而做�� �备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃 。 二、荷尔蒙分泌失调 避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� �分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕 中因女性荷尔蒙雌激素的增加， — 现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� �谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所 以需要更加注意。 三、新陈代谢缓慢 肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� �因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是 内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� �时候，紫外线的照射也会加速斑的形成。 四、错误的使用化妆品 使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� �疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的 问题。 外部因素 一、紫外线 照射紫外线的时候，人体为了保护皮肤，会在基底层产�� �很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化， 还会引起黑斑、雀斑等色素沉着的皮肤疾患。 二、不良的清洁习惯 因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� �皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的 问题。 三、遗传基因 父母中有长斑的，则本人长斑的概率就很高，这种情况�� �一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外 线照射，这是预防斑必须注意的。 《有疑问帮你解决》 黛芙薇尔精华液真的有效果吗 真的可以把脸上的黄褐�� �去掉吗 答：黛芙薇尔精华液dna精华能够有效的修复周围难以触�� �的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑 ，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� �，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显 而易见。自产品上市以来，老顾客纷纷介绍新顾客， 的新�� �客都是通过老顾客介绍而来，口碑由此而来 ，服用黛芙薇尔美白，会伤身体吗 有副作用吗 答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� �斑科技，并将“dna美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有 效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� �地的专家通力协作， �� �，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然 之美。 专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� �百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖 ，去除黄褐斑之后，会反弹吗 答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� �白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。 树立权威品牌 我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗 ，你们的价格有点贵，能不能便宜一点 答： ， ， ，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助 一分价钱，一份价值，我们现在做的�� �是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗 你还会再去花那么多冤枉�� �，不但斑没去掉，还把自己的皮肤弄的越来越糟吗 ，我适合用黛芙薇尔精华液吗 答：黛芙薇尔适用人群： 、生理紊乱引起的黄褐斑人群 、生育引起的妊娠斑人群 、年纪增长引起的老年斑人群 、化妆品色素沉积、辐射斑人群 、长期日照引起的日晒斑人群 、肌肤暗淡急需美白的人群 《祛斑小方法》 面部色斑怎样去除，同时为您分享祛斑小方法 、将鲜明萝卜辟碎挤汁， ，每日上晚洗完脸后涂�� �，待干后，洗净。此外，每日喝一杯胡萝卜，可美白肌肤。 将柠檬汁搅汁，加糖水适量饮用。柠檬中含有大量维生素c�� �钙、磷、铁等。常饮柠檬汁不仅可美白肌肤，还能使黑色素� ��淀，达到祛斑的作用。 original issue reported on code google com by additive gmail com on jul at
| 1
|
57,267
| 15,728,488,368
|
IssuesEvent
|
2021-03-29 13:52:36
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
opened
|
508-defect-0 Launchblocker: Smooth scroll should not be used with accordions
|
508-defect-0 508/Accessibility
|
# [508-defect-0 :exclamation: Launchblocker](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-0)
<!--
Enter an issue title using the format [ERROR TYPE]: Brief description of the problem
---
[SCREENREADER]: Edit buttons need aria-label for context
[KEYBOARD]: Add another user link will not receive keyboard focus
[AXE-CORE]: Heading levels should increase by one
[COGNITION]: Error messages should be more specific
[COLOR]: Blue button on blue background does not have sufficient contrast ratio
---
-->
<!-- It's okay to delete the instructions above, but leave the link to the 508 defect severity level for your issue. -->
## Feedback framework
- **❗️ Must** for if the feedback must be applied
- **⚠️ Should** if the feedback is best practice
- **✔️ Consider** for suggestions/enhancements
## Definition of done
1. Review and acknowledge feedback.
1. Fix and/or document decisions made.
1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.
## Point of Contact
<!-- If this issue is being opened by a VFS team member, please add a point of contact. Usually this is the same person who enters the issue ticket. -->
**VFS Point of Contact:** Josh
## User Story or Problem Statement
As a user with vestibular disorder, I don't want the page to unexpectedly scroll without my permission.
## Details
Smooth scrolling that hijacks control from the user may be harmful to those with vestibular disorders.
## Acceptance Criteria
- [ ] Accordions do not smooth scroll on the page
## Steps to Recreate
Homepage accordions
## Proposed Solution (if known)
- Remove smooth scroll from the accordions OR
- do not scroll at all (I think the design system accordion does not scrolljack the user) OR
- use the reduce motion CSS media query to make it conditional based on the user's settings
## WCAG or Vendor Guidance (optional)
<!--
* [Understanding Success Criterion 2.3.3: Animation from Interactions](https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html#:~:text=Some%20users%20experience%20distraction%20or,include%20dizziness%2C%20nausea%20and%20headaches.)
-->
## Screenshots or Trace Logs
https://user-images.githubusercontent.com/14154792/112846795-6cbf1400-9074-11eb-989e-e214112d25f0.mov
|
1.0
|
508-defect-0 Launchblocker: Smooth scroll should not be used with accordions - # [508-defect-0 :exclamation: Launchblocker](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-0)
<!--
Enter an issue title using the format [ERROR TYPE]: Brief description of the problem
---
[SCREENREADER]: Edit buttons need aria-label for context
[KEYBOARD]: Add another user link will not receive keyboard focus
[AXE-CORE]: Heading levels should increase by one
[COGNITION]: Error messages should be more specific
[COLOR]: Blue button on blue background does not have sufficient contrast ratio
---
-->
<!-- It's okay to delete the instructions above, but leave the link to the 508 defect severity level for your issue. -->
## Feedback framework
- **❗️ Must** for if the feedback must be applied
- **⚠️ Should** if the feedback is best practice
- **✔️ Consider** for suggestions/enhancements
## Definition of done
1. Review and acknowledge feedback.
1. Fix and/or document decisions made.
1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.
## Point of Contact
<!-- If this issue is being opened by a VFS team member, please add a point of contact. Usually this is the same person who enters the issue ticket. -->
**VFS Point of Contact:** Josh
## User Story or Problem Statement
As a user with vestibular disorder, I don't want the page to unexpectedly scroll without my permission.
## Details
Smooth scrolling that hijacks control from the user may be harmful to those with vestibular disorders.
## Acceptance Criteria
- [ ] Accordions do not smooth scroll on the page
## Steps to Recreate
Homepage accordions
## Proposed Solution (if known)
- Remove smooth scroll from the accordions OR
- do not scroll at all (I think the design system accordion does not scrolljack the user) OR
- use the reduce motion CSS media query to make it conditional based on the user's settings
## WCAG or Vendor Guidance (optional)
<!--
* [Understanding Success Criterion 2.3.3: Animation from Interactions](https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html#:~:text=Some%20users%20experience%20distraction%20or,include%20dizziness%2C%20nausea%20and%20headaches.)
-->
## Screenshots or Trace Logs
https://user-images.githubusercontent.com/14154792/112846795-6cbf1400-9074-11eb-989e-e214112d25f0.mov
|
defect
|
defect launchblocker smooth scroll should not be used with accordions enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact josh user story or problem statement as a user with vestibular disorder i don t want the page to unexpectedly scroll without my permission details smooth scrolling that hijacks control from the user may be harmful to those with vestibular disorders acceptance criteria accordions do not smooth scroll on the page steps to recreate homepage accordions proposed solution if known remove smooth scroll from the accordions or do not scroll at all i think the design system accordion does not scrolljack the user or use the reduce motion css media query to make it conditional based on the user s settings wcag or vendor guidance optional screenshots or trace logs
| 1
|
54,985
| 14,113,783,076
|
IssuesEvent
|
2020-11-07 13:01:46
|
line/armeria
|
https://api.github.com/repos/line/armeria
|
opened
|
Incorrect route decorator evaluation order
|
defect
|
Route decorators are currently evaluated in incorrect order.
For example, the decorators in the following two examples should be evaluated in different orders:
```java
// Example A:
Server.builder()
.decorator("glob:/**", decorator1)
.decorator("glob:/foo/*", decorator2);
// Example B:
Server.builder()
.decorator("glob:/foo/*", decorator3)
.decorator("glob:/**", decorator4);
```
`decorator2` and `decorator4` must be evaluated before `decorator1` and `decorator3`, but it's `decorator1` and `decorator4` that are evaluated first.
To fix this issue, we need to change how we choose route decorators, e.g. do not use a trie but evaluate all routes of route decorators sequentially. Not efficient, but it's correct.
|
1.0
|
Incorrect route decorator evaluation order - Route decorators are currently evaluated in incorrect order.
For example, the decorators in the following two examples should be evaluated in different orders:
```java
// Example A:
Server.builder()
.decorator("glob:/**", decorator1)
.decorator("glob:/foo/*", decorator2);
// Example B:
Server.builder()
.decorator("glob:/foo/*", decorator3)
.decorator("glob:/**", decorator4);
```
`decorator2` and `decorator4` must be evaluated before `decorator1` and `decorator3`, but it's `decorator1` and `decorator4` that are evaluated first.
To fix this issue, we need to change how we choose route decorators, e.g. do not use a trie but evaluate all routes of route decorators sequentially. Not efficient, but it's correct.
|
defect
|
incorrect route decorator evaluation order route decorators are currently evaluated in incorrect order for example the decorators in the following two examples should be evaluated in different orders java example a server builder decorator glob decorator glob foo example b server builder decorator glob foo decorator glob and must be evaluated before and but it s and that are evaluated first to fix this issue we need to change how we choose route decorators e g do not use a trie but evaluate all routes of route decorators sequentially not efficient but it s correct
| 1
|
62,541
| 17,035,084,268
|
IssuesEvent
|
2021-07-05 05:37:29
|
naev/naev
|
https://api.github.com/repos/naev/naev
|
closed
|
Aborting the Crimson Gauntlet should put the player back on Totoran in a normal state.
|
Priority-Low Type-Defect
|
Split off from #1849. If you start the Crimson gauntlet, open the Info dialog, and abort the mission, you wind up with an open/hidden Info dialogue. (The `i` key does nothing until you take off or re-enter the Crimson gauntlet; as soon as you do so, you'll see the dialogue already open.)
This is so surprising that even we expected it not to happen. :)
|
1.0
|
Aborting the Crimson Gauntlet should put the player back on Totoran in a normal state. - Split off from #1849. If you start the Crimson gauntlet, open the Info dialog, and abort the mission, you wind up with an open/hidden Info dialogue. (The `i` key does nothing until you take off or re-enter the Crimson gauntlet; as soon as you do so, you'll see the dialogue already open.)
This is so surprising that even we expected it not to happen. :)
|
defect
|
aborting the crimson gauntlet should put the player back on totoran in a normal state split off from if you start the crimson gauntlet open the info dialog and abort the mission you wind up with an open hidden info dialogue the i key does nothing until you take off or re enter the crimson gauntlet as soon as you do so you ll see the dialogue already open this is so surprising that even we expected it not to happen
| 1
|
29,969
| 13,190,217,958
|
IssuesEvent
|
2020-08-13 09:48:17
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Could not deploy python webapp
|
Pri2 app-service/svc cxp product-question triaged
|
I kept getting a failure on the application deployment.
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp up --resource-group learning -n lam-first-python-app
webapp lam-first-python-app doesn't exist
Creating webapp 'lam-first-python-app' ...
Configuring default logging for the app, if not already enabled
Creating zip with contents of dir C:\Users\lam\source\repos\python-docs-hello-world ...
Getting scm site credentials for zip deployment
Starting zip deployment. This operation can take a while to complete ...
Deployment endpoint responded with status code 202
Deployment status endpoint https://lam-first-python-app.scm.azurewebsites.net/api/deployments/latest returns malformed data. Retrying...
Configuring default logging for the app, if not already enabled
Zip deployment failed. {'id': '624f144a1b294c8da5b3b752c3eca0d0', 'status': 3, 'status_text': '', 'author_email': 'N/A', 'author': 'N/A', 'deployer': 'Push-Deployer', 'message': 'Created via a push deployment', 'progress': '', 'received_time': '2020-08-09T13:12:48.1989457Z', 'start_time': '2020-08-09T13:12:48.2909523Z', 'end_time': '2020-08-09T13:13:09.3821502Z', 'last_success_end_time': None, 'complete': True, 'active': False, 'is_temp': False, 'is_readonly': True, 'url': 'https://lam-first-python-app.scm.azurewebsites.net/api/deployments/latest', 'log_url': 'https://lam-first-python-app.scm.azurewebsites.net/api/deployments/latest/log', 'site_name': 'lam-first-python-app'}. Please run the command az webapp log deployment show
-n lam-first-python-app -g learning
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp lo
az webapp: 'lo' is not in the 'az webapp' command group. See 'az webapp --help'. If the command is from an extension, please make sure the corresponding extension is installed. To learn more about extensions, please visit https://docs.microsoft.com/en-us/cli/azure/azure-cli-extensions-overview
The most similar choice to 'lo' is:
log
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp log deployment show
az webapp log deployment show: error: the following arguments are required: --resource-group/-g, --name/-n
usage: az webapp log deployment show [-h] [--verbose] [--debug]
[--only-show-errors]
[--output {json,jsonc,yaml,yamlc,table,tsv,none}]
[--query JMESPATH]
[--subscription _SUBSCRIPTION]
--resource-group RESOURCE_GROUP --name
NAME [--slot SLOT]
[--deployment-id DEPLOYMENT_ID]
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp log deployment show -n lam-first-python-app -g learning
{
"active": false,
"author": "N/A",
"author_email": "N/A",
"complete": true,
"deployer": "Push-Deployer",
"end_time": "2020-08-09T13:13:09.3821502Z",
"id": "624f144a1b294c8da5b3b752c3eca0d0",
"is_readonly": true,
"is_temp": false,
"last_success_end_time": null,
"log_url": "https://lam-first-python-app.scm.azurewebsites.net/api/deployments/624f144a1b294c8da5b3b752c3eca0d0/log",
"message": "Created via a push deployment",
"progress": "",
"received_time": "2020-08-09T13:12:48.1989457Z",
"site_name": "lam-first-python-app",
"start_time": "2020-08-09T13:12:48.2909523Z",
"status": 3,
"status_text": "",
"url": "https://lam-first-python-app.scm.azurewebsites.net/api/deployments/624f144a1b294c8da5b3b752c3eca0d0"
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 0077a811-b0b7-93b1-80b0-a4d45615ef4b
* Version Independent ID: cc95198d-5560-2bf1-09ae-b8d210e45f2d
* Content: [Quickstart: Create a Linux Python app - Azure App Service](https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-python?tabs=bash)
* Content Source: [articles/app-service/containers/quickstart-python.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/app-service/containers/quickstart-python.md)
* Service: **app-service**
* GitHub Login: @cephalin
* Microsoft Alias: **cephalin**
|
1.0
|
Could not deploy python webapp - I kept getting a failure on the application deployment.
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp up --resource-group learning -n lam-first-python-app
webapp lam-first-python-app doesn't exist
Creating webapp 'lam-first-python-app' ...
Configuring default logging for the app, if not already enabled
Creating zip with contents of dir C:\Users\lam\source\repos\python-docs-hello-world ...
Getting scm site credentials for zip deployment
Starting zip deployment. This operation can take a while to complete ...
Deployment endpoint responded with status code 202
Deployment status endpoint https://lam-first-python-app.scm.azurewebsites.net/api/deployments/latest returns malformed data. Retrying...
Configuring default logging for the app, if not already enabled
Zip deployment failed. {'id': '624f144a1b294c8da5b3b752c3eca0d0', 'status': 3, 'status_text': '', 'author_email': 'N/A', 'author': 'N/A', 'deployer': 'Push-Deployer', 'message': 'Created via a push deployment', 'progress': '', 'received_time': '2020-08-09T13:12:48.1989457Z', 'start_time': '2020-08-09T13:12:48.2909523Z', 'end_time': '2020-08-09T13:13:09.3821502Z', 'last_success_end_time': None, 'complete': True, 'active': False, 'is_temp': False, 'is_readonly': True, 'url': 'https://lam-first-python-app.scm.azurewebsites.net/api/deployments/latest', 'log_url': 'https://lam-first-python-app.scm.azurewebsites.net/api/deployments/latest/log', 'site_name': 'lam-first-python-app'}. Please run the command az webapp log deployment show
-n lam-first-python-app -g learning
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp lo
az webapp: 'lo' is not in the 'az webapp' command group. See 'az webapp --help'. If the command is from an extension, please make sure the corresponding extension is installed. To learn more about extensions, please visit https://docs.microsoft.com/en-us/cli/azure/azure-cli-extensions-overview
The most similar choice to 'lo' is:
log
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp log deployment show
az webapp log deployment show: error: the following arguments are required: --resource-group/-g, --name/-n
usage: az webapp log deployment show [-h] [--verbose] [--debug]
[--only-show-errors]
[--output {json,jsonc,yaml,yamlc,table,tsv,none}]
[--query JMESPATH]
[--subscription _SUBSCRIPTION]
--resource-group RESOURCE_GROUP --name
NAME [--slot SLOT]
[--deployment-id DEPLOYMENT_ID]
(venv) lam@ivxdev-vm:/mnt/c/Users/lam/source/repos/python-docs-hello-world$ az webapp log deployment show -n lam-first-python-app -g learning
{
"active": false,
"author": "N/A",
"author_email": "N/A",
"complete": true,
"deployer": "Push-Deployer",
"end_time": "2020-08-09T13:13:09.3821502Z",
"id": "624f144a1b294c8da5b3b752c3eca0d0",
"is_readonly": true,
"is_temp": false,
"last_success_end_time": null,
"log_url": "https://lam-first-python-app.scm.azurewebsites.net/api/deployments/624f144a1b294c8da5b3b752c3eca0d0/log",
"message": "Created via a push deployment",
"progress": "",
"received_time": "2020-08-09T13:12:48.1989457Z",
"site_name": "lam-first-python-app",
"start_time": "2020-08-09T13:12:48.2909523Z",
"status": 3,
"status_text": "",
"url": "https://lam-first-python-app.scm.azurewebsites.net/api/deployments/624f144a1b294c8da5b3b752c3eca0d0"
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 0077a811-b0b7-93b1-80b0-a4d45615ef4b
* Version Independent ID: cc95198d-5560-2bf1-09ae-b8d210e45f2d
* Content: [Quickstart: Create a Linux Python app - Azure App Service](https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-python?tabs=bash)
* Content Source: [articles/app-service/containers/quickstart-python.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/app-service/containers/quickstart-python.md)
* Service: **app-service**
* GitHub Login: @cephalin
* Microsoft Alias: **cephalin**
|
non_defect
|
could not deploy python webapp i kept getting a failure on the application deployment venv lam ivxdev vm mnt c users lam source repos python docs hello world az webapp up resource group learning n lam first python app webapp lam first python app doesn t exist creating webapp lam first python app configuring default logging for the app if not already enabled creating zip with contents of dir c users lam source repos python docs hello world getting scm site credentials for zip deployment starting zip deployment this operation can take a while to complete deployment endpoint responded with status code deployment status endpoint returns malformed data retrying configuring default logging for the app if not already enabled zip deployment failed id status status text author email n a author n a deployer push deployer message created via a push deployment progress received time start time end time last success end time none complete true active false is temp false is readonly true url log url site name lam first python app please run the command az webapp log deployment show n lam first python app g learning venv lam ivxdev vm mnt c users lam source repos python docs hello world az webapp lo az webapp lo is not in the az webapp command group see az webapp help if the command is from an extension please make sure the corresponding extension is installed to learn more about extensions please visit the most similar choice to lo is log venv lam ivxdev vm mnt c users lam source repos python docs hello world az webapp log deployment show az webapp log deployment show error the following arguments are required resource group g name n usage az webapp log deployment show resource group resource group name name venv lam ivxdev vm mnt c users lam source repos python docs hello world az webapp log deployment show n lam first python app g learning active false author n a author email n a complete true deployer push deployer end time id is readonly true is temp false last success end time null log url message created via a push deployment progress received time site name lam first python app start time status status text url document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service app service github login cephalin microsoft alias cephalin
| 0
|
221,428
| 17,349,598,660
|
IssuesEvent
|
2021-07-29 06:57:05
|
Cour-de-cassation/label
|
https://api.github.com/repos/Cour-de-cassation/label
|
closed
|
[Feat] sensible website category
|
To Test Local To Test Preprod
|
## Context
Color is light Blue 700 (dark mode) or light Blue 200 (light mode)
Icon name : "web"
## Mockup
https://www.figma.com/file/bxeU6RJzyBU1ICL8jrgpva/Maquettes?node-id=1560%3A15
|
2.0
|
[Feat] sensible website category - ## Context
Color is light Blue 700 (dark mode) or light Blue 200 (light mode)
Icon name : "web"
## Mockup
https://www.figma.com/file/bxeU6RJzyBU1ICL8jrgpva/Maquettes?node-id=1560%3A15
|
non_defect
|
sensible website category context color is light blue dark mode or light blue light mode icon name web mockup
| 0
|
668,803
| 22,598,315,892
|
IssuesEvent
|
2022-06-29 06:43:22
|
orden-gg/fireball
|
https://api.github.com/repos/orden-gg/fireball
|
opened
|
Gotchi card Kinship adjustment
|
priority: high
|
`Kinship` is the most important `Gotchi` parameter right now. We need to make it more highlighted.
- [ ] move kinship to top center card part
- [ ] update kinship UI
- [ ] make dropdown alchemica visible only on altar level hover (CSS based, do not use rect states)
<img width="769" alt="Screenshot 2022-06-29 at 13 39 32" src="https://user-images.githubusercontent.com/42136738/176368672-35fb073c-3903-4ab0-b588-1f1f2c58b13b.png">
<img width="249" alt="Screenshot 2022-06-29 at 13 40 25" src="https://user-images.githubusercontent.com/42136738/176368852-0bf87835-d2e7-419a-b913-6c7d680adf64.png">
|
1.0
|
Gotchi card Kinship adjustment - `Kinship` is the most important `Gotchi` parameter right now. We need to make it more highlighted.
- [ ] move kinship to top center card part
- [ ] update kinship UI
- [ ] make dropdown alchemica visible only on altar level hover (CSS based, do not use rect states)
<img width="769" alt="Screenshot 2022-06-29 at 13 39 32" src="https://user-images.githubusercontent.com/42136738/176368672-35fb073c-3903-4ab0-b588-1f1f2c58b13b.png">
<img width="249" alt="Screenshot 2022-06-29 at 13 40 25" src="https://user-images.githubusercontent.com/42136738/176368852-0bf87835-d2e7-419a-b913-6c7d680adf64.png">
|
non_defect
|
gotchi card kinship adjustment kinship is the most important gotchi parameter right now we need to make it more highlighted move kinship to top center card part update kinship ui make dropdown alchemica visible only on altar level hover css based do not use rect states img width alt screenshot at src img width alt screenshot at src
| 0
|
42,644
| 11,195,890,945
|
IssuesEvent
|
2020-01-03 08:21:53
|
primefaces/primefaces
|
https://api.github.com/repos/primefaces/primefaces
|
closed
|
DataTable: currentPageReportTemplate {endRecord} incorrect calculation
|
defect
|
## 1) Environment
- PrimeFaces version: 8.0.RC2
- Does it work on the newest released PrimeFaces version? NO
- Does it work on the newest sources in GitHub? NO
- Application server + version: Jetty Showcase
- Affected browsers: ALL
## 2) Expected behavior
Using currentPageReportTemplate reports the correct values.
## 3) Actual behavior
It is reporting incorrect values for the {endRecord} value.
## 4) Steps to reproduce
I just updated the showcase with this PR: https://github.com/primefaces/showcase-facelift/pull/112
1. Run the showcase and navigate to the Paginator Example: http://localhost:8080/showcase/ui/data/datatable/paginator.xhtml
2. Note the starting value of the current report is "1-10 of 50 records".
3. Now page to the right it will display "11-20 of 50 records" correctly.
4. Page to the left it will display "1-10 of 50 records" correctly.
5. Now change the records per page from "10" to "15" the report will incorrectly display "1-015 of 50 records" notice the "015" instead of "15".
6. Now page to the right and it incorrectly displays "16-50 of 50 records" instead of "16-30 of 50" records.
## 5) Sample XHTML
```xml
<p:dataTable var="car" value="#{dtPaginatorView.cars}" rows="10"
paginator="true"
paginatorTemplate="{CurrentPageReport} {FirstPageLink} {PreviousPageLink} {PageLinks} {NextPageLink} {LastPageLink} {RowsPerPageDropdown}"
currentPageReportTemplate="{startRecord}-{endRecord} of {totalRecords} records"
rowsPerPageTemplate="5,10,15">
```
## 6) Sample bean
```java
@Named("dtPaginatorView")
@ViewScoped
public class PaginatorView implements Serializable {
private List<Car> cars;
@Inject
private CarService service;
@PostConstruct
public void init() {
cars = service.createCars(50);
}
public List<Car> getCars() {
return cars;
}
public void setService(CarService service) {
this.service = service;
}
}
```
|
1.0
|
DataTable: currentPageReportTemplate {endRecord} incorrect calculation - ## 1) Environment
- PrimeFaces version: 8.0.RC2
- Does it work on the newest released PrimeFaces version? NO
- Does it work on the newest sources in GitHub? NO
- Application server + version: Jetty Showcase
- Affected browsers: ALL
## 2) Expected behavior
Using currentPageReportTemplate reports the correct values.
## 3) Actual behavior
It is reporting incorrect values for the {endRecord} value.
## 4) Steps to reproduce
I just updated the showcase with this PR: https://github.com/primefaces/showcase-facelift/pull/112
1. Run the showcase and navigate to the Paginator Example: http://localhost:8080/showcase/ui/data/datatable/paginator.xhtml
2. Note the starting value of the current report is "1-10 of 50 records".
3. Now page to the right it will display "11-20 of 50 records" correctly.
4. Page to the left it will display "1-10 of 50 records" correctly.
5. Now change the records per page from "10" to "15" the report will incorrectly display "1-015 of 50 records" notice the "015" instead of "15".
6. Now page to the right and it incorrectly displays "16-50 of 50 records" instead of "16-30 of 50" records.
## 5) Sample XHTML
```xml
<p:dataTable var="car" value="#{dtPaginatorView.cars}" rows="10"
paginator="true"
paginatorTemplate="{CurrentPageReport} {FirstPageLink} {PreviousPageLink} {PageLinks} {NextPageLink} {LastPageLink} {RowsPerPageDropdown}"
currentPageReportTemplate="{startRecord}-{endRecord} of {totalRecords} records"
rowsPerPageTemplate="5,10,15">
```
## 6) Sample bean
```java
@Named("dtPaginatorView")
@ViewScoped
public class PaginatorView implements Serializable {
private List<Car> cars;
@Inject
private CarService service;
@PostConstruct
public void init() {
cars = service.createCars(50);
}
public List<Car> getCars() {
return cars;
}
public void setService(CarService service) {
this.service = service;
}
}
```
|
defect
|
datatable currentpagereporttemplate endrecord incorrect calculation environment primefaces version does it work on the newest released primefaces version no does it work on the newest sources in github no application server version jetty showcase affected browsers all expected behavior using currentpagereporttemplate reports the correct values actual behavior it is reporting incorrect values for the endrecord value steps to reproduce i just updated the showcase with this pr run the showcase and navigate to the paginator example note the starting value of the current report is of records now page to the right it will display of records correctly page to the left it will display of records correctly now change the records per page from to the report will incorrectly display of records notice the instead of now page to the right and it incorrectly displays of records instead of of records sample xhtml xml p datatable var car value dtpaginatorview cars rows paginator true paginatortemplate currentpagereport firstpagelink previouspagelink pagelinks nextpagelink lastpagelink rowsperpagedropdown currentpagereporttemplate startrecord endrecord of totalrecords records rowsperpagetemplate sample bean java named dtpaginatorview viewscoped public class paginatorview implements serializable private list cars inject private carservice service postconstruct public void init cars service createcars public list getcars return cars public void setservice carservice service this service service
| 1
|
69,909
| 22,746,601,706
|
IssuesEvent
|
2022-07-07 09:42:38
|
cakephp/cakephp
|
https://api.github.com/repos/cakephp/cakephp
|
opened
|
Folder::create: umask has no effect
|
defect
|
### Description
In Folder::create the call on `$old = umask(0);` is directly followed by `umask($old)` and therefor is directly reseted to its old value. This leads to unexpected permission set in the filesystem.
Solution: wrap the umask calls around the `mkdir` call.
### CakePHP Version
4.3.0
### PHP Version
8.1
|
1.0
|
Folder::create: umask has no effect - ### Description
In Folder::create the call on `$old = umask(0);` is directly followed by `umask($old)` and therefor is directly reseted to its old value. This leads to unexpected permission set in the filesystem.
Solution: wrap the umask calls around the `mkdir` call.
### CakePHP Version
4.3.0
### PHP Version
8.1
|
defect
|
folder create umask has no effect description in folder create the call on old umask is directly followed by umask old and therefor is directly reseted to its old value this leads to unexpected permission set in the filesystem solution wrap the umask calls around the mkdir call cakephp version php version
| 1
|
133,374
| 18,297,375,676
|
IssuesEvent
|
2021-10-05 21:54:21
|
vipinsun/blockchain-carbon-accounting
|
https://api.github.com/repos/vipinsun/blockchain-carbon-accounting
|
closed
|
CVE-2020-28852 (High) detected in github.com/golang/text-v0.3.2 - autoclosed
|
security vulnerability
|
## CVE-2020-28852 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/golang/text-v0.3.2</b></p></summary>
<p>[mirror] Go text processing support</p>
<p>
Dependency Hierarchy:
- github.com/hyperledger/fabric-protos-go-d7d9b8e1fcde4eb6a4b44ec9003bfb90eee3301c (Root Library)
- github.com/grpc/grpc-go-v1.27.0
- github.com/golang/net-16171245cfb220d5317888b716d69c1fb4e7992b
- :x: **github.com/golang/text-v0.3.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vipinsun/blockchain-carbon-accounting/commit/d388e16464e00b9ce84df0d247029f534a429b90">d388e16464e00b9ce84df0d247029f534a429b90</a></p>
<p>Found in base branch: <b>main</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>
In x/text in Go before v0.3.5, a "slice bounds out of range" panic occurs in language.ParseAcceptLanguage while processing a BCP 47 tag. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.)
<p>Publish Date: 2021-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28852>CVE-2020-28852</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: Change files</p>
<p>Origin: <a href="https://github.com/golang/text/commit/4482a914f52311356f6f4b7a695d4075ca22c0c6">https://github.com/golang/text/commit/4482a914f52311356f6f4b7a695d4075ca22c0c6</a></p>
<p>Release Date: 2020-11-18</p>
<p>Fix Resolution: Replace or update the following files: parse.go, parse_test.go</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-28852 (High) detected in github.com/golang/text-v0.3.2 - autoclosed - ## CVE-2020-28852 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/golang/text-v0.3.2</b></p></summary>
<p>[mirror] Go text processing support</p>
<p>
Dependency Hierarchy:
- github.com/hyperledger/fabric-protos-go-d7d9b8e1fcde4eb6a4b44ec9003bfb90eee3301c (Root Library)
- github.com/grpc/grpc-go-v1.27.0
- github.com/golang/net-16171245cfb220d5317888b716d69c1fb4e7992b
- :x: **github.com/golang/text-v0.3.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vipinsun/blockchain-carbon-accounting/commit/d388e16464e00b9ce84df0d247029f534a429b90">d388e16464e00b9ce84df0d247029f534a429b90</a></p>
<p>Found in base branch: <b>main</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>
In x/text in Go before v0.3.5, a "slice bounds out of range" panic occurs in language.ParseAcceptLanguage while processing a BCP 47 tag. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.)
<p>Publish Date: 2021-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28852>CVE-2020-28852</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: Change files</p>
<p>Origin: <a href="https://github.com/golang/text/commit/4482a914f52311356f6f4b7a695d4075ca22c0c6">https://github.com/golang/text/commit/4482a914f52311356f6f4b7a695d4075ca22c0c6</a></p>
<p>Release Date: 2020-11-18</p>
<p>Fix Resolution: Replace or update the following files: parse.go, parse_test.go</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_defect
|
cve high detected in github com golang text autoclosed cve high severity vulnerability vulnerable library github com golang text go text processing support dependency hierarchy github com hyperledger fabric protos go root library github com grpc grpc go github com golang net x github com golang text vulnerable library found in head commit a href found in base branch main vulnerability details in x text in go before a slice bounds out of range panic occurs in language parseacceptlanguage while processing a bcp tag x text language is supposed to be able to parse an http accept language header 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 change files origin a href release date fix resolution replace or update the following files parse go parse test go step up your open source security game with whitesource
| 0
|
272,475
| 20,747,000,395
|
IssuesEvent
|
2022-03-15 00:50:04
|
SE701-T5/Frontend
|
https://api.github.com/repos/SE701-T5/Frontend
|
closed
|
Add CONTRIBUTING.md
|
documentation
|
Add the contribution guideline as a markdown file named CONTRIBUTING.md in /.github directory for GitHub to link to (refer to the bottom right of Issues when creating them).
This issue and subsequent Pull Request are intended for the team to review and approve the contribution guidelines before @christopher-alba merges them, and also as an example on how to make and use an Issue and Pull Request using a GitHub Kanban project board.
|
1.0
|
Add CONTRIBUTING.md - Add the contribution guideline as a markdown file named CONTRIBUTING.md in /.github directory for GitHub to link to (refer to the bottom right of Issues when creating them).
This issue and subsequent Pull Request are intended for the team to review and approve the contribution guidelines before @christopher-alba merges them, and also as an example on how to make and use an Issue and Pull Request using a GitHub Kanban project board.
|
non_defect
|
add contributing md add the contribution guideline as a markdown file named contributing md in github directory for github to link to refer to the bottom right of issues when creating them this issue and subsequent pull request are intended for the team to review and approve the contribution guidelines before christopher alba merges them and also as an example on how to make and use an issue and pull request using a github kanban project board
| 0
|
14,604
| 2,829,610,106
|
IssuesEvent
|
2015-05-23 02:06:28
|
awesomebing1/fuzzdb
|
https://api.github.com/repos/awesomebing1/fuzzdb
|
closed
|
http://www.hidesertstar.com/calendar/event_7b6c28c8-6cd4-11e4-9752-cb6a3e4f46f4.html
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What
dohttp://www.hidesertstar.com/calendar/event_7b6c28c8-6cd4-11e4-9752-cb6a3e4f46f
4.html
http://www.hidesertstar.com/calendar/event_7b6c28c8-6cd4-11e4-9752-cb6a3e4f46f4.
html you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `sabujhos...@gmail.com` on 15 Nov 2014 at 2:44
|
1.0
|
http://www.hidesertstar.com/calendar/event_7b6c28c8-6cd4-11e4-9752-cb6a3e4f46f4.html - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What
dohttp://www.hidesertstar.com/calendar/event_7b6c28c8-6cd4-11e4-9752-cb6a3e4f46f
4.html
http://www.hidesertstar.com/calendar/event_7b6c28c8-6cd4-11e4-9752-cb6a3e4f46f4.
html you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `sabujhos...@gmail.com` on 15 Nov 2014 at 2:44
|
defect
|
what steps will reproduce the problem what is the expected output what do html html you see instead what version of the product are you using on what operating system please provide any additional information below original issue reported on code google com by sabujhos gmail com on nov at
| 1
|
35,293
| 7,928,902,847
|
IssuesEvent
|
2018-07-06 13:23:43
|
PowerShell/vscode-powershell
|
https://api.github.com/repos/PowerShell/vscode-powershell
|
closed
|
Clicking on an element of Outline does not work
|
Area-CodeLens Issue-Enhancement
|
## Issue Description ##
I am experiencing a problem with the Outline feature in the Explorer view. When I click on an element of the Outline, the active editor closes or nothing happens.
## Attached Logs ##
[1530008985-8037a55e-b901-4ff8-8ef1-6281b0ce2cb61530008980459.zip](https://github.com/PowerShell/vscode-powershell/files/2136762/1530008985-8037a55e-b901-4ff8-8ef1-6281b0ce2cb61530008980459.zip)
## Environment Information ##
### Visual Studio Code ###
| Name | Version |
| --- | --- |
| Operating System | Windows_NT x64 6.1.7601 |
| VSCode | 1.24.1|
| PowerShell Extension Version | 1.7.0 |
### PowerShell Information ###
|Name|Value|
|---|---|
|PSVersion|5.1.14409.1012|
|PSEdition|Desktop|
|PSCompatibleVersions|1.0 2.0 3.0 4.0 5.0 5.1.14409.1012|
|BuildVersion|10.0.14409.1012|
|CLRVersion|4.0.30319.42000|
|WSManStackVersion|3.0|
|PSRemotingProtocolVersion|2.3|
|SerializationVersion|1.1.0.1|
### Visual Studio Code Extensions ###
<details><summary>Visual Studio Code Extensions(Click to Expand)</summary>
|Extension|Author|Version|
|---|---|---|
|PowerShell|ms-vscode|1.7.0|;
</details>
|
1.0
|
Clicking on an element of Outline does not work - ## Issue Description ##
I am experiencing a problem with the Outline feature in the Explorer view. When I click on an element of the Outline, the active editor closes or nothing happens.
## Attached Logs ##
[1530008985-8037a55e-b901-4ff8-8ef1-6281b0ce2cb61530008980459.zip](https://github.com/PowerShell/vscode-powershell/files/2136762/1530008985-8037a55e-b901-4ff8-8ef1-6281b0ce2cb61530008980459.zip)
## Environment Information ##
### Visual Studio Code ###
| Name | Version |
| --- | --- |
| Operating System | Windows_NT x64 6.1.7601 |
| VSCode | 1.24.1|
| PowerShell Extension Version | 1.7.0 |
### PowerShell Information ###
|Name|Value|
|---|---|
|PSVersion|5.1.14409.1012|
|PSEdition|Desktop|
|PSCompatibleVersions|1.0 2.0 3.0 4.0 5.0 5.1.14409.1012|
|BuildVersion|10.0.14409.1012|
|CLRVersion|4.0.30319.42000|
|WSManStackVersion|3.0|
|PSRemotingProtocolVersion|2.3|
|SerializationVersion|1.1.0.1|
### Visual Studio Code Extensions ###
<details><summary>Visual Studio Code Extensions(Click to Expand)</summary>
|Extension|Author|Version|
|---|---|---|
|PowerShell|ms-vscode|1.7.0|;
</details>
|
non_defect
|
clicking on an element of outline does not work issue description i am experiencing a problem with the outline feature in the explorer view when i click on an element of the outline the active editor closes or nothing happens attached logs environment information visual studio code name version operating system windows nt vscode powershell extension version powershell information name value psversion psedition desktop pscompatibleversions buildversion clrversion wsmanstackversion psremotingprotocolversion serializationversion visual studio code extensions visual studio code extensions click to expand extension author version powershell ms vscode
| 0
|
63,547
| 12,338,448,854
|
IssuesEvent
|
2020-05-14 16:28:13
|
imjakedaniels/raptors_animation
|
https://api.github.com/repos/imjakedaniels/raptors_animation
|
closed
|
Add segment_geom to signify score disparity
|
code enhancement
|
**WHAT IS IT?**
A new feature that is a `geom_segment` to signify which team is winning!
**WHY AM I DOING IT?**
Better user experience (they don't need to see the actual score.
**WHEN IS IT DONE?**
When I merge a PR with a fix into master.
**TASKS**
- [x] Build a geom_segment under the running score
**FUTURE NOTES**
- This solution could be disturbed when the width of the file is increased.
|
1.0
|
Add segment_geom to signify score disparity - **WHAT IS IT?**
A new feature that is a `geom_segment` to signify which team is winning!
**WHY AM I DOING IT?**
Better user experience (they don't need to see the actual score.
**WHEN IS IT DONE?**
When I merge a PR with a fix into master.
**TASKS**
- [x] Build a geom_segment under the running score
**FUTURE NOTES**
- This solution could be disturbed when the width of the file is increased.
|
non_defect
|
add segment geom to signify score disparity what is it a new feature that is a geom segment to signify which team is winning why am i doing it better user experience they don t need to see the actual score when is it done when i merge a pr with a fix into master tasks build a geom segment under the running score future notes this solution could be disturbed when the width of the file is increased
| 0
|
292,295
| 8,956,037,914
|
IssuesEvent
|
2019-01-26 14:07:32
|
FRC-Team-1710/FRC1710-2019
|
https://api.github.com/repos/FRC-Team-1710/FRC1710-2019
|
closed
|
Claw actuation
|
Easy low priority
|
Create pistons to go in and out using a button press. Pistons are pretty easy to use, I can help explain them but the past code has good examples
|
1.0
|
Claw actuation - Create pistons to go in and out using a button press. Pistons are pretty easy to use, I can help explain them but the past code has good examples
|
non_defect
|
claw actuation create pistons to go in and out using a button press pistons are pretty easy to use i can help explain them but the past code has good examples
| 0
|
72,193
| 23,982,177,988
|
IssuesEvent
|
2022-09-13 15:51:54
|
cf-convention/discuss
|
https://api.github.com/repos/cf-convention/discuss
|
closed
|
CF-1.10 - schedule for release
|
defect announcement
|
Hello,
The CF Conventions committee has set out a timeline for the release of the next version of conventions, CF-1.10.
CF-1.10 will be released **during the week starting on Monday 29 August 2022**.
The new version will include all of the enhancement proposals that have already been merged since CF-1.9, plus any existing or new proposals that are concluded and merged before 29 August 2022.
The key dates to note for getting a new or not-yet-concluded enhancement into CF-1.10 are
* _07 August 2022_
The last date by which the proposal must be agreed, initiating the three week gestation period.
* _28 August 2022_
The last date by which the proposal's gestation period must be completed.
Note that if any substantive questions arise during the gestation period, then the three weeks starts again when the questions are resolved. Non-substantive items arising in this period (such as identification of a trivial formatting issue or spelling mistake) would not cause the clock to reset.
Many thanks,
David,
On behalf of the Conventions Committee and Standard Names Committee
|
1.0
|
CF-1.10 - schedule for release - Hello,
The CF Conventions committee has set out a timeline for the release of the next version of conventions, CF-1.10.
CF-1.10 will be released **during the week starting on Monday 29 August 2022**.
The new version will include all of the enhancement proposals that have already been merged since CF-1.9, plus any existing or new proposals that are concluded and merged before 29 August 2022.
The key dates to note for getting a new or not-yet-concluded enhancement into CF-1.10 are
* _07 August 2022_
The last date by which the proposal must be agreed, initiating the three week gestation period.
* _28 August 2022_
The last date by which the proposal's gestation period must be completed.
Note that if any substantive questions arise during the gestation period, then the three weeks starts again when the questions are resolved. Non-substantive items arising in this period (such as identification of a trivial formatting issue or spelling mistake) would not cause the clock to reset.
Many thanks,
David,
On behalf of the Conventions Committee and Standard Names Committee
|
defect
|
cf schedule for release hello the cf conventions committee has set out a timeline for the release of the next version of conventions cf cf will be released during the week starting on monday august the new version will include all of the enhancement proposals that have already been merged since cf plus any existing or new proposals that are concluded and merged before august the key dates to note for getting a new or not yet concluded enhancement into cf are august the last date by which the proposal must be agreed initiating the three week gestation period august the last date by which the proposal s gestation period must be completed note that if any substantive questions arise during the gestation period then the three weeks starts again when the questions are resolved non substantive items arising in this period such as identification of a trivial formatting issue or spelling mistake would not cause the clock to reset many thanks david on behalf of the conventions committee and standard names committee
| 1
|
253,580
| 21,690,050,447
|
IssuesEvent
|
2022-05-09 14:38:24
|
damccorm/test-migration-target
|
https://api.github.com/repos/damccorm/test-migration-target
|
opened
|
Replace *-gcp/*-aws tox suites with *-cloud suites to run unit tests for both
|
bug P3 testing
|
Currently there are `py37-gcp`, py37-aws test suites. Let's consolidate all of them into py37-cloud, along with other py35-gcp, py27-gcp, etc.
Imported from Jira [BEAM-9533](https://issues.apache.org/jira/browse/BEAM-9533). Original Jira may contain additional context.
Reported by: pabloem.
|
1.0
|
Replace *-gcp/*-aws tox suites with *-cloud suites to run unit tests for both - Currently there are `py37-gcp`, py37-aws test suites. Let's consolidate all of them into py37-cloud, along with other py35-gcp, py27-gcp, etc.
Imported from Jira [BEAM-9533](https://issues.apache.org/jira/browse/BEAM-9533). Original Jira may contain additional context.
Reported by: pabloem.
|
non_defect
|
replace gcp aws tox suites with cloud suites to run unit tests for both currently there are gcp aws test suites let s consolidate all of them into cloud along with other gcp gcp etc imported from jira original jira may contain additional context reported by pabloem
| 0
|
75,023
| 25,488,148,624
|
IssuesEvent
|
2022-11-26 17:46:30
|
BOINC/boinc
|
https://api.github.com/repos/BOINC/boinc
|
closed
|
If insufficient RAM for tasks in queue, doesn't download tasks from another project to fill CPU
|
C: Client - Scheduler Policy R: duplicate T: Defect
|
**Describe the bug**
I am running two projects on a 24 thread computer with 32GB RAM. Yoyo doing only "ecm p2" tasks (which use about 7GB RAM each) and NFS (which uses about half a GB each). Yoyo has higher weight. Boinc has downloaded a huge queue of Yoyo tasks and can only fit a few of them into RAM. Then it just sits there with the CPU mostly idle instead of getting NFS work.
**Steps To Reproduce**
1. Attach to Yoyo and NFS only.
2. Set Yoyo to ecm P2 work only on the server.
3. Set yoyo to weight 100, and NFS to weight 0.
**Expected behaviour**
Fill the CPU threads so it's busy with something, even if it's not my first choice of project.
**System Information**
- OS: Windows 11
- BOINC Version: 7.20.2
|
1.0
|
If insufficient RAM for tasks in queue, doesn't download tasks from another project to fill CPU - **Describe the bug**
I am running two projects on a 24 thread computer with 32GB RAM. Yoyo doing only "ecm p2" tasks (which use about 7GB RAM each) and NFS (which uses about half a GB each). Yoyo has higher weight. Boinc has downloaded a huge queue of Yoyo tasks and can only fit a few of them into RAM. Then it just sits there with the CPU mostly idle instead of getting NFS work.
**Steps To Reproduce**
1. Attach to Yoyo and NFS only.
2. Set Yoyo to ecm P2 work only on the server.
3. Set yoyo to weight 100, and NFS to weight 0.
**Expected behaviour**
Fill the CPU threads so it's busy with something, even if it's not my first choice of project.
**System Information**
- OS: Windows 11
- BOINC Version: 7.20.2
|
defect
|
if insufficient ram for tasks in queue doesn t download tasks from another project to fill cpu describe the bug i am running two projects on a thread computer with ram yoyo doing only ecm tasks which use about ram each and nfs which uses about half a gb each yoyo has higher weight boinc has downloaded a huge queue of yoyo tasks and can only fit a few of them into ram then it just sits there with the cpu mostly idle instead of getting nfs work steps to reproduce attach to yoyo and nfs only set yoyo to ecm work only on the server set yoyo to weight and nfs to weight expected behaviour fill the cpu threads so it s busy with something even if it s not my first choice of project system information os windows boinc version
| 1
|
276,677
| 30,514,527,387
|
IssuesEvent
|
2023-07-19 01:01:45
|
amaybaum-dev/log4shell-demo2
|
https://api.github.com/repos/amaybaum-dev/log4shell-demo2
|
opened
|
spring-boot-starter-log4j2-2.6.1.jar: 2 vulnerabilities (highest severity is: 10.0) reachable
|
Mend: dependency security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-boot-starter-log4j2-2.6.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (spring-boot-starter-log4j2 version) | Remediation Available | Reachability |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- |
| [CVE-2021-44228](https://www.mend.io/vulnerability-database/CVE-2021-44228) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 10.0 | log4j-core-2.14.1.jar | Transitive | 2.6.2 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-45046](https://www.mend.io/vulnerability-database/CVE-2021-45046) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.0 | log4j-core-2.14.1.jar | Transitive | 2.6.2 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-44228</summary>
### Vulnerable Library - <b>log4j-core-2.14.1.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-log4j2-2.6.1.jar (Root Library)
- :x: **log4j-core-2.14.1.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.impl.Log4jProvider (Extension)
-> org.apache.logging.log4j.core.impl.Log4jContextFactory (Extension)
-> org.apache.logging.log4j.core.config.ConfigurationSource (Extension)
-> ❌ org.apache.logging.log4j.core.Logger (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
<p>Publish Date: 2021-12-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44228>CVE-2021-44228</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>10.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-jfh8-c2jp-5v3q">https://github.com/advisories/GHSA-jfh8-c2jp-5v3q</a></p>
<p>Release Date: 2021-12-10</p>
<p>Fix Resolution (org.apache.logging.log4j:log4j-core): 2.16.0</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-log4j2): 2.6.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2021-45046</summary>
### Vulnerable Library - <b>log4j-core-2.14.1.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-log4j2-2.6.1.jar (Root Library)
- :x: **log4j-core-2.14.1.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45046>CVE-2021-45046</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution (org.apache.logging.log4j:log4j-core): 2.16.0</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-log4j2): 2.6.2</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
|
spring-boot-starter-log4j2-2.6.1.jar: 2 vulnerabilities (highest severity is: 10.0) reachable - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-boot-starter-log4j2-2.6.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (spring-boot-starter-log4j2 version) | Remediation Available | Reachability |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- |
| [CVE-2021-44228](https://www.mend.io/vulnerability-database/CVE-2021-44228) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 10.0 | log4j-core-2.14.1.jar | Transitive | 2.6.2 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-45046](https://www.mend.io/vulnerability-database/CVE-2021-45046) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.0 | log4j-core-2.14.1.jar | Transitive | 2.6.2 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-44228</summary>
### Vulnerable Library - <b>log4j-core-2.14.1.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-log4j2-2.6.1.jar (Root Library)
- :x: **log4j-core-2.14.1.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.impl.Log4jProvider (Extension)
-> org.apache.logging.log4j.core.impl.Log4jContextFactory (Extension)
-> org.apache.logging.log4j.core.config.ConfigurationSource (Extension)
-> ❌ org.apache.logging.log4j.core.Logger (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
<p>Publish Date: 2021-12-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44228>CVE-2021-44228</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>10.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-jfh8-c2jp-5v3q">https://github.com/advisories/GHSA-jfh8-c2jp-5v3q</a></p>
<p>Release Date: 2021-12-10</p>
<p>Fix Resolution (org.apache.logging.log4j:log4j-core): 2.16.0</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-log4j2): 2.6.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2021-45046</summary>
### Vulnerable Library - <b>log4j-core-2.14.1.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-log4j2-2.6.1.jar (Root Library)
- :x: **log4j-core-2.14.1.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-45046>CVE-2021-45046</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution (org.apache.logging.log4j:log4j-core): 2.16.0</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-log4j2): 2.6.2</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_defect
|
spring boot starter jar vulnerabilities highest severity is reachable vulnerable library spring boot starter jar path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org apache logging core core jar vulnerabilities cve severity cvss dependency type fixed in spring boot starter version remediation available reachability critical core jar transitive the vulnerability is likely to be reachable critical core jar transitive the vulnerability is non reachable details cve vulnerable library core jar the apache implementation library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org apache logging core core jar dependency hierarchy spring boot starter jar root library x core jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp maincontroller application org apache logging logmanager extension org apache logging core impl extension org apache logging core impl extension org apache logging core config configurationsource extension ❌ org apache logging core logger vulnerable component vulnerability details apache through excluding security releases and jndi features used in configuration log messages and parameters do not protect against attacker controlled ldap and other jndi related endpoints an attacker who can control log messages or log message parameters can execute arbitrary code loaded from ldap servers when message lookup substitution is enabled from this behavior has been disabled by default from version along with and this functionality has been completely removed note that this vulnerability is specific to core and does not affect or other apache logging services projects 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 changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache logging core direct dependency fix resolution org springframework boot spring boot starter rescue worker helmet automatic remediation is available for this issue cve vulnerable library core jar the apache implementation library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org apache logging core core jar dependency hierarchy spring boot starter jar root library x core jar vulnerable library found in base branch main reachability analysis the vulnerable code is not reachable vulnerability details it was found that the fix to address cve in apache was incomplete in certain non default configurations this could allows attackers with control over thread context map mdc input data when the logging configuration uses a non default pattern layout with either a context lookup for example ctx loginid or a thread context map pattern x mdc or mdc to craft malicious input data using a jndi lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments java and java fix this issue by removing support for message lookup patterns and disabling jndi functionality by default 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 changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache logging core direct dependency fix resolution org springframework boot spring boot starter rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue
| 0
|
47,778
| 13,066,220,904
|
IssuesEvent
|
2020-07-30 21:14:32
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
closed
|
[cscd-llh] missing documentation (Trac #1167)
|
Migrated from Trac combo reconstruction defect
|
the project has no sphinx documentation, so it does not show up here: http://software.icecube.wisc.edu/icerec_trunk/
minimal documentation should contain the release notes converted to .rst format and a link to the existing doxygen documentation. Converting the RELEASE_NOTES is comparably easy, other projects which have been converted recently may serve as a reference.
Bonus points can be achieved by converting the documentation in resources/docs/index.dox into .rst format.
the scripts in resources/scripts/ need a doc string each that explains what they do and how they should be called.
Migrated from https://code.icecube.wisc.edu/ticket/1167
```json
{
"status": "closed",
"changetime": "2019-02-13T14:11:57",
"description": "the project has no sphinx documentation, so it does not show up here: http://software.icecube.wisc.edu/icerec_trunk/\n\nminimal documentation should contain the release notes converted to .rst format and a link to the existing doxygen documentation. Converting the RELEASE_NOTES is comparably easy, other projects which have been converted recently may serve as a reference.\n\nBonus points can be achieved by converting the documentation in resources/docs/index.dox into .rst format.\n\nthe scripts in resources/scripts/ need a doc string each that explains what they do and how they should be called.",
"reporter": "hdembinski",
"cc": "",
"resolution": "fixed",
"_ts": "1550067117911749",
"component": "combo reconstruction",
"summary": "[cscd-llh] missing documentation",
"priority": "blocker",
"keywords": "",
"time": "2015-08-18T20:24:23",
"milestone": "",
"owner": "tpalczewski",
"type": "defect"
}
```
|
1.0
|
[cscd-llh] missing documentation (Trac #1167) - the project has no sphinx documentation, so it does not show up here: http://software.icecube.wisc.edu/icerec_trunk/
minimal documentation should contain the release notes converted to .rst format and a link to the existing doxygen documentation. Converting the RELEASE_NOTES is comparably easy, other projects which have been converted recently may serve as a reference.
Bonus points can be achieved by converting the documentation in resources/docs/index.dox into .rst format.
the scripts in resources/scripts/ need a doc string each that explains what they do and how they should be called.
Migrated from https://code.icecube.wisc.edu/ticket/1167
```json
{
"status": "closed",
"changetime": "2019-02-13T14:11:57",
"description": "the project has no sphinx documentation, so it does not show up here: http://software.icecube.wisc.edu/icerec_trunk/\n\nminimal documentation should contain the release notes converted to .rst format and a link to the existing doxygen documentation. Converting the RELEASE_NOTES is comparably easy, other projects which have been converted recently may serve as a reference.\n\nBonus points can be achieved by converting the documentation in resources/docs/index.dox into .rst format.\n\nthe scripts in resources/scripts/ need a doc string each that explains what they do and how they should be called.",
"reporter": "hdembinski",
"cc": "",
"resolution": "fixed",
"_ts": "1550067117911749",
"component": "combo reconstruction",
"summary": "[cscd-llh] missing documentation",
"priority": "blocker",
"keywords": "",
"time": "2015-08-18T20:24:23",
"milestone": "",
"owner": "tpalczewski",
"type": "defect"
}
```
|
defect
|
missing documentation trac the project has no sphinx documentation so it does not show up here minimal documentation should contain the release notes converted to rst format and a link to the existing doxygen documentation converting the release notes is comparably easy other projects which have been converted recently may serve as a reference bonus points can be achieved by converting the documentation in resources docs index dox into rst format the scripts in resources scripts need a doc string each that explains what they do and how they should be called migrated from json status closed changetime description the project has no sphinx documentation so it does not show up here documentation should contain the release notes converted to rst format and a link to the existing doxygen documentation converting the release notes is comparably easy other projects which have been converted recently may serve as a reference n nbonus points can be achieved by converting the documentation in resources docs index dox into rst format n nthe scripts in resources scripts need a doc string each that explains what they do and how they should be called reporter hdembinski cc resolution fixed ts component combo reconstruction summary missing documentation priority blocker keywords time milestone owner tpalczewski type defect
| 1
|
64,978
| 18,989,739,591
|
IssuesEvent
|
2021-11-22 04:59:50
|
vector-im/element-android
|
https://api.github.com/repos/vector-im/element-android
|
opened
|
Joining a Jitsi audio-only conference uses camera
|
T-Defect
|
### Steps to reproduce
1. Join a multi-user room
2. With Element Web, click the telephone icon in the top-right to start a Jitsi conference call
3. See that the Jitsi widget creation event set `"data": {"isAudioOnly": true}`
4. Join the conference with Element Web, and notice that only your microphone input is used
5. Join the room with Element Android, then join the Jitsi conference
### Outcome
#### What did you expect?
When joining the Jitsi conference from Element Android, only microphone input should be used, as the conference is audio-only.
#### What happened instead?
Camera input gets used in addition to micrphone input. The camera can be turned off manually, but only after having joined after having sent a few moments of camera footage to the conference.
### Your phone model
Samsung Galaxy S8
### Operating system version
Android 9
### Application version and app store
1.3.7 from Google Play
### Homeserver
Personal homeserver
### Will you send logs?
No
|
1.0
|
Joining a Jitsi audio-only conference uses camera - ### Steps to reproduce
1. Join a multi-user room
2. With Element Web, click the telephone icon in the top-right to start a Jitsi conference call
3. See that the Jitsi widget creation event set `"data": {"isAudioOnly": true}`
4. Join the conference with Element Web, and notice that only your microphone input is used
5. Join the room with Element Android, then join the Jitsi conference
### Outcome
#### What did you expect?
When joining the Jitsi conference from Element Android, only microphone input should be used, as the conference is audio-only.
#### What happened instead?
Camera input gets used in addition to micrphone input. The camera can be turned off manually, but only after having joined after having sent a few moments of camera footage to the conference.
### Your phone model
Samsung Galaxy S8
### Operating system version
Android 9
### Application version and app store
1.3.7 from Google Play
### Homeserver
Personal homeserver
### Will you send logs?
No
|
defect
|
joining a jitsi audio only conference uses camera steps to reproduce join a multi user room with element web click the telephone icon in the top right to start a jitsi conference call see that the jitsi widget creation event set data isaudioonly true join the conference with element web and notice that only your microphone input is used join the room with element android then join the jitsi conference outcome what did you expect when joining the jitsi conference from element android only microphone input should be used as the conference is audio only what happened instead camera input gets used in addition to micrphone input the camera can be turned off manually but only after having joined after having sent a few moments of camera footage to the conference your phone model samsung galaxy operating system version android application version and app store from google play homeserver personal homeserver will you send logs no
| 1
|
77,609
| 9,602,550,677
|
IssuesEvent
|
2019-05-10 14:50:23
|
Yoast/wordpress-seo
|
https://api.github.com/repos/Yoast/wordpress-seo
|
closed
|
[Feature Request] Add some placeholder text when the default SEO template variables are shown
|
Feature request UX component: metabox needs-design support
|
**When a user goes to edit the SEO title, they see the default template variables.**
**A user may not know they need to click on the SEO Title Field and then start entering text. We should therefore add a word like "placeholder text" in the field or the word "click to enter" next to the SEO Title.**
**USE CASE**
It may not be intuitive that a user needs to click to enter text to replace the default variables. Adding some instructions may help to clarify that action.
|
1.0
|
[Feature Request] Add some placeholder text when the default SEO template variables are shown - **When a user goes to edit the SEO title, they see the default template variables.**
**A user may not know they need to click on the SEO Title Field and then start entering text. We should therefore add a word like "placeholder text" in the field or the word "click to enter" next to the SEO Title.**
**USE CASE**
It may not be intuitive that a user needs to click to enter text to replace the default variables. Adding some instructions may help to clarify that action.
|
non_defect
|
add some placeholder text when the default seo template variables are shown when a user goes to edit the seo title they see the default template variables a user may not know they need to click on the seo title field and then start entering text we should therefore add a word like placeholder text in the field or the word click to enter next to the seo title use case it may not be intuitive that a user needs to click to enter text to replace the default variables adding some instructions may help to clarify that action
| 0
|
74,457
| 25,134,190,957
|
IssuesEvent
|
2022-11-09 17:14:40
|
department-of-veterans-affairs/va.gov-cms
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms
|
opened
|
Table audit displays tables that no longer exist on the current node
|
Defect Needs refining
|
## Describe the defect
When reviewing the new table audit with Randi and she pointed out a couple examples of pages that were appearing in the audit but no longer had tables. I looked and she's correct - I also can't figure out what might be happening - our only guess is that maybe the audit is pulling previous revisions?
Example 1:
https://www.va.gov/resources/helpful-va-phone-numbers/
https://prod.cms.va.gov/resources/helpful-va-phone-numbers
https://prod.cms.va.gov/admin/content/audit/tables?page=29
Example 2:
https://www.va.gov/resources/choosing-a-decision-review-option/
https://prod.cms.va.gov/resources/choosing-a-decision-review-option
https://prod.cms.va.gov/admin/content/audit/tables?page=42
## AC / Expected behavior
- [ ] Update table audit to only display tables in the currently published version of the node
### CMS Team
Please check the team(s) that will do this work.
- [ ] `Program`
- [ ] `Platform CMS Team`
- [ ] `Sitewide Crew`
- [ ] `⭐️ Sitewide CMS`
- [ ] `⭐️ Public Websites`
- [ ] `⭐️ Facilities`
- [ ] `⭐️ User support`
|
1.0
|
Table audit displays tables that no longer exist on the current node - ## Describe the defect
When reviewing the new table audit with Randi and she pointed out a couple examples of pages that were appearing in the audit but no longer had tables. I looked and she's correct - I also can't figure out what might be happening - our only guess is that maybe the audit is pulling previous revisions?
Example 1:
https://www.va.gov/resources/helpful-va-phone-numbers/
https://prod.cms.va.gov/resources/helpful-va-phone-numbers
https://prod.cms.va.gov/admin/content/audit/tables?page=29
Example 2:
https://www.va.gov/resources/choosing-a-decision-review-option/
https://prod.cms.va.gov/resources/choosing-a-decision-review-option
https://prod.cms.va.gov/admin/content/audit/tables?page=42
## AC / Expected behavior
- [ ] Update table audit to only display tables in the currently published version of the node
### CMS Team
Please check the team(s) that will do this work.
- [ ] `Program`
- [ ] `Platform CMS Team`
- [ ] `Sitewide Crew`
- [ ] `⭐️ Sitewide CMS`
- [ ] `⭐️ Public Websites`
- [ ] `⭐️ Facilities`
- [ ] `⭐️ User support`
|
defect
|
table audit displays tables that no longer exist on the current node describe the defect when reviewing the new table audit with randi and she pointed out a couple examples of pages that were appearing in the audit but no longer had tables i looked and she s correct i also can t figure out what might be happening our only guess is that maybe the audit is pulling previous revisions example example ac expected behavior update table audit to only display tables in the currently published version of the node cms team please check the team s that will do this work program platform cms team sitewide crew ⭐️ sitewide cms ⭐️ public websites ⭐️ facilities ⭐️ user support
| 1
|
40,204
| 9,906,542,403
|
IssuesEvent
|
2019-06-27 14:03:58
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
closed
|
DDL statements on MySQL create CHAR column instead of VARCHAR column on unknown lengths
|
C: DB: MySQL C: Functionality E: All Editions P: High R: Fixed T: Defect
|
When running DDL statements on MySQL, e.g.
```java
public void testCreateTableWithUnknownLengthStringColumn() throws Exception {
Table<?> t = table(name("t"));
Field<String> s = field(name("s"), String.class);
try {
create().createTable(t).columns(s).execute();
assertEquals(1, create().insertInto(t, s).values((String) null).execute());
assertEquals(1, create().insertInto(t, s).values("a").execute());
assertEquals(1, create().insertInto(t, s).values("abc").execute());
assertEquals(1, create().insertInto(t, s).values("abcdefghijklmnopqrstuvwxyz").execute());
List<String> list = create().select(s).from(t).orderBy(s.asc().nullsFirst()).fetch(s);
assertEquals(asList(null, "a", "abc", "abcdefghijklmnopqrstuvwxyz"), list);
}
finally {
ignoreThrows(create().dropTable(t)::execute);
}
}
```
Then, a `char` column is created instead of a `varchar` column:
```sql
create table `t`(
`s` char null
)
```
This is because the cast data type is used for DDL, not the actual data type.
The problem even persists when specifying:
```java
Field<String> s = field(name("s"), SQLDataType.VARCHAR);
```
But not when specifying:
```java
Field<String> s = field(name("s"), SQLDataType.VARCHAR(30));
```
The difficulty will be to pick a reasonable default length for DDL as MySQL has a maximum row size of 65535: https://stackoverflow.com/a/13506920/521799
A reasonable solution would be to generate
```sql
create table `t`(
`s` text null
)
```
----
See also:
- https://groups.google.com/forum/#!topic/jooq-user/i0MswJr_N_M
- https://groups.google.com/forum/#!topic/jooq-user/61qU8PbFBNM
|
1.0
|
DDL statements on MySQL create CHAR column instead of VARCHAR column on unknown lengths - When running DDL statements on MySQL, e.g.
```java
public void testCreateTableWithUnknownLengthStringColumn() throws Exception {
Table<?> t = table(name("t"));
Field<String> s = field(name("s"), String.class);
try {
create().createTable(t).columns(s).execute();
assertEquals(1, create().insertInto(t, s).values((String) null).execute());
assertEquals(1, create().insertInto(t, s).values("a").execute());
assertEquals(1, create().insertInto(t, s).values("abc").execute());
assertEquals(1, create().insertInto(t, s).values("abcdefghijklmnopqrstuvwxyz").execute());
List<String> list = create().select(s).from(t).orderBy(s.asc().nullsFirst()).fetch(s);
assertEquals(asList(null, "a", "abc", "abcdefghijklmnopqrstuvwxyz"), list);
}
finally {
ignoreThrows(create().dropTable(t)::execute);
}
}
```
Then, a `char` column is created instead of a `varchar` column:
```sql
create table `t`(
`s` char null
)
```
This is because the cast data type is used for DDL, not the actual data type.
The problem even persists when specifying:
```java
Field<String> s = field(name("s"), SQLDataType.VARCHAR);
```
But not when specifying:
```java
Field<String> s = field(name("s"), SQLDataType.VARCHAR(30));
```
The difficulty will be to pick a reasonable default length for DDL as MySQL has a maximum row size of 65535: https://stackoverflow.com/a/13506920/521799
A reasonable solution would be to generate
```sql
create table `t`(
`s` text null
)
```
----
See also:
- https://groups.google.com/forum/#!topic/jooq-user/i0MswJr_N_M
- https://groups.google.com/forum/#!topic/jooq-user/61qU8PbFBNM
|
defect
|
ddl statements on mysql create char column instead of varchar column on unknown lengths when running ddl statements on mysql e g java public void testcreatetablewithunknownlengthstringcolumn throws exception table t table name t field s field name s string class try create createtable t columns s execute assertequals create insertinto t s values string null execute assertequals create insertinto t s values a execute assertequals create insertinto t s values abc execute assertequals create insertinto t s values abcdefghijklmnopqrstuvwxyz execute list list create select s from t orderby s asc nullsfirst fetch s assertequals aslist null a abc abcdefghijklmnopqrstuvwxyz list finally ignorethrows create droptable t execute then a char column is created instead of a varchar column sql create table t s char null this is because the cast data type is used for ddl not the actual data type the problem even persists when specifying java field s field name s sqldatatype varchar but not when specifying java field s field name s sqldatatype varchar the difficulty will be to pick a reasonable default length for ddl as mysql has a maximum row size of a reasonable solution would be to generate sql create table t s text null see also
| 1
|
18,295
| 3,041,328,375
|
IssuesEvent
|
2015-08-07 20:37:14
|
dart-lang/sdk
|
https://api.github.com/repos/dart-lang/sdk
|
closed
|
Need better control of Observatory output
|
Area-Observatory Priority-Unassigned Triaged Type-Defect
|
**[user feedback]**
Username: kasperl
When running command line apps from within the editor, I find it somewhat annoying that the Observatory always prints a line to the console. It feels distracting that it interferes with the output of my app -- and that I have no reasonable way of making it stop (apart from disabling the observatory functionality).
Maybe the editor could surface this information differently? Maybe the VM could write the information somewhere else -- or only do it on demand when the VM process is sent a specific signal?
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.6.0.dev_09_06 (2014-08-21)
OS: Mac OS X - x86_64 (10.9.2)
JVM: 1.6.0_65
# projects: 3
# open dart files: 3
auto-run pub: true
localhost resolves to: 127.0.0.1
mem max/total/free: 1996 / 254 / 77 MB
thread count: 44
index: [574904 locations, 300 sources, 36024 elements]
SDK installed: true
Dartium installed: true
______
**Attachment:**
[screenshot.png](https://storage.googleapis.com/google-code-attachments/dart/issue-20664/comment-0/screenshot.png) (151.70 KB)
|
1.0
|
Need better control of Observatory output - **[user feedback]**
Username: kasperl
When running command line apps from within the editor, I find it somewhat annoying that the Observatory always prints a line to the console. It feels distracting that it interferes with the output of my app -- and that I have no reasonable way of making it stop (apart from disabling the observatory functionality).
Maybe the editor could surface this information differently? Maybe the VM could write the information somewhere else -- or only do it on demand when the VM process is sent a specific signal?
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.6.0.dev_09_06 (2014-08-21)
OS: Mac OS X - x86_64 (10.9.2)
JVM: 1.6.0_65
# projects: 3
# open dart files: 3
auto-run pub: true
localhost resolves to: 127.0.0.1
mem max/total/free: 1996 / 254 / 77 MB
thread count: 44
index: [574904 locations, 300 sources, 36024 elements]
SDK installed: true
Dartium installed: true
______
**Attachment:**
[screenshot.png](https://storage.googleapis.com/google-code-attachments/dart/issue-20664/comment-0/screenshot.png) (151.70 KB)
|
defect
|
need better control of observatory output username kasperl when running command line apps from within the editor i find it somewhat annoying that the observatory always prints a line to the console it feels distracting that it interferes with the output of my app and that i have no reasonable way of making it stop apart from disabling the observatory functionality maybe the editor could surface this information differently maybe the vm could write the information somewhere else or only do it on demand when the vm process is sent a specific signal editor dev os mac os x jvm projects open dart files auto run pub true localhost resolves to mem max total free mb thread count index sdk installed true dartium installed true attachment kb
| 1
|
98,618
| 30,019,000,983
|
IssuesEvent
|
2023-06-26 21:12:31
|
project-chip/connectedhomeip
|
https://api.github.com/repos/project-chip/connectedhomeip
|
closed
|
[Build] OpenIOT builds failing occasionally
|
bug build issue
|
### Build issue(s)
https://github.com/project-chip/connectedhomeip/actions/runs/5343701328/jobs/9687147953
I noticed a couple builds failing like this
### Platform
other
### Anything else?
_No response_
|
1.0
|
[Build] OpenIOT builds failing occasionally - ### Build issue(s)
https://github.com/project-chip/connectedhomeip/actions/runs/5343701328/jobs/9687147953
I noticed a couple builds failing like this
### Platform
other
### Anything else?
_No response_
|
non_defect
|
openiot builds failing occasionally build issue s i noticed a couple builds failing like this platform other anything else no response
| 0
|
332,032
| 29,179,436,259
|
IssuesEvent
|
2023-05-19 10:36:02
|
kernitus/BukkitOldCombatMechanics
|
https://api.github.com/repos/kernitus/BukkitOldCombatMechanics
|
closed
|
Fishing rod knockback PvP
|
incompatibility awaiting testing
|
Thank you very much for updating the plugin, now the new beta version works great.
But I would like to suggest a few things if possible.
When the fishing rod knockback and the other corresponding modules are activated. Players are able to bump each other and pull each other in areas where pvp is disabled by the world guard plugin (I solve by deactive this modules).
And there is another bug also with the knockback of the players and the mcmmo plugin, if the players go to areas with pvp off (protected by the world guard) and they keep hitting themselves, they go up a lot of acrobatic skills, I imagine because the pvp is offline, but Still something happens that I don't know what it is.
In both bugs no error appears in the console.
Thanks again for updating the plugin and fixing the bugs.
|
1.0
|
Fishing rod knockback PvP - Thank you very much for updating the plugin, now the new beta version works great.
But I would like to suggest a few things if possible.
When the fishing rod knockback and the other corresponding modules are activated. Players are able to bump each other and pull each other in areas where pvp is disabled by the world guard plugin (I solve by deactive this modules).
And there is another bug also with the knockback of the players and the mcmmo plugin, if the players go to areas with pvp off (protected by the world guard) and they keep hitting themselves, they go up a lot of acrobatic skills, I imagine because the pvp is offline, but Still something happens that I don't know what it is.
In both bugs no error appears in the console.
Thanks again for updating the plugin and fixing the bugs.
|
non_defect
|
fishing rod knockback pvp thank you very much for updating the plugin now the new beta version works great but i would like to suggest a few things if possible when the fishing rod knockback and the other corresponding modules are activated players are able to bump each other and pull each other in areas where pvp is disabled by the world guard plugin i solve by deactive this modules and there is another bug also with the knockback of the players and the mcmmo plugin if the players go to areas with pvp off protected by the world guard and they keep hitting themselves they go up a lot of acrobatic skills i imagine because the pvp is offline but still something happens that i don t know what it is in both bugs no error appears in the console thanks again for updating the plugin and fixing the bugs
| 0
|
58,660
| 14,446,133,189
|
IssuesEvent
|
2020-12-08 00:32:02
|
Azure/acr
|
https://api.github.com/repos/Azure/acr
|
closed
|
Base image update of ubuntu:18.04 on Docker Hub did not trigger my ACR task
|
bug build tasks
|
**Describe the bug**
I have setup an ACR task, which builds an image from a Dockerfile that relies on `ubuntu 18.04`.
I have followed the setup described in [Automate OS and framework patching](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-tasks-overview#automate-os-and-framework-patching) and have build the task once to let "ACR Tasks discover(...) the base image dependencies".
This setup was running fine a few weeks ago: a change on Docker Hub to `ubuntu:18.04` triggedd my task correctly, resulting in a acr task run and new image.
I have now discovered that six days ago, there was an update on Docker Hub for [`ubuntu:18.04`](https://hub.docker.com/_/ubuntu/?tab=tags&name=18.04&page=1) and the corresponding task was **not** triggered
The documentation tells:
> For image builds from a Dockerfile, an ACR task detects dependencies on base images in the following locations:
>
> * The same Azure container registry where the task runs
> * Another Azure container registry in the same region
> * A public repo in Docker Hub
> * A public repo in Microsoft Container Registry
>
> If the base image specified in the FROM statement resides in one of these locations, the ACR task adds a hook to ensure the image is rebuilt any time its base is updated.
* Where is this _hook_ added?
* How can I investigate if this hook is correctly added?
* Can you detail what the ACR task does in the background or if applicable which other services is involved here?
* How can I **reliably** tell/check that the base-image update trigger works for my ACR tasks?
(Please note, if I run my task manually, the triggering of tasks that depend on image as a base image works fine, though.)
**To Reproduce**
I am not able to reproduce the error, as I have no control over the ubuntu Docker Hub.
**Expected behavior**
An update of the base image ubuntu:18.04 on Docker Hub should reliably trigger my ACR task.
Thanks for you help
Benjamin
|
1.0
|
Base image update of ubuntu:18.04 on Docker Hub did not trigger my ACR task - **Describe the bug**
I have setup an ACR task, which builds an image from a Dockerfile that relies on `ubuntu 18.04`.
I have followed the setup described in [Automate OS and framework patching](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-tasks-overview#automate-os-and-framework-patching) and have build the task once to let "ACR Tasks discover(...) the base image dependencies".
This setup was running fine a few weeks ago: a change on Docker Hub to `ubuntu:18.04` triggedd my task correctly, resulting in a acr task run and new image.
I have now discovered that six days ago, there was an update on Docker Hub for [`ubuntu:18.04`](https://hub.docker.com/_/ubuntu/?tab=tags&name=18.04&page=1) and the corresponding task was **not** triggered
The documentation tells:
> For image builds from a Dockerfile, an ACR task detects dependencies on base images in the following locations:
>
> * The same Azure container registry where the task runs
> * Another Azure container registry in the same region
> * A public repo in Docker Hub
> * A public repo in Microsoft Container Registry
>
> If the base image specified in the FROM statement resides in one of these locations, the ACR task adds a hook to ensure the image is rebuilt any time its base is updated.
* Where is this _hook_ added?
* How can I investigate if this hook is correctly added?
* Can you detail what the ACR task does in the background or if applicable which other services is involved here?
* How can I **reliably** tell/check that the base-image update trigger works for my ACR tasks?
(Please note, if I run my task manually, the triggering of tasks that depend on image as a base image works fine, though.)
**To Reproduce**
I am not able to reproduce the error, as I have no control over the ubuntu Docker Hub.
**Expected behavior**
An update of the base image ubuntu:18.04 on Docker Hub should reliably trigger my ACR task.
Thanks for you help
Benjamin
|
non_defect
|
base image update of ubuntu on docker hub did not trigger my acr task describe the bug i have setup an acr task which builds an image from a dockerfile that relies on ubuntu i have followed the setup described in and have build the task once to let acr tasks discover the base image dependencies this setup was running fine a few weeks ago a change on docker hub to ubuntu triggedd my task correctly resulting in a acr task run and new image i have now discovered that six days ago there was an update on docker hub for and the corresponding task was not triggered the documentation tells for image builds from a dockerfile an acr task detects dependencies on base images in the following locations the same azure container registry where the task runs another azure container registry in the same region a public repo in docker hub a public repo in microsoft container registry if the base image specified in the from statement resides in one of these locations the acr task adds a hook to ensure the image is rebuilt any time its base is updated where is this hook added how can i investigate if this hook is correctly added can you detail what the acr task does in the background or if applicable which other services is involved here how can i reliably tell check that the base image update trigger works for my acr tasks please note if i run my task manually the triggering of tasks that depend on image as a base image works fine though to reproduce i am not able to reproduce the error as i have no control over the ubuntu docker hub expected behavior an update of the base image ubuntu on docker hub should reliably trigger my acr task thanks for you help benjamin
| 0
|
50,273
| 13,187,416,225
|
IssuesEvent
|
2020-08-13 03:20:42
|
icecube-trac/tix3
|
https://api.github.com/repos/icecube-trac/tix3
|
closed
|
Minor typo in I3Time.cxx (Trac #434)
|
Migrated from Trac dataclasses defect
|
This line: http://code.icecube.wisc.edu/projects/icecube/browser/projects/dataclasses/trunk/private/dataclasses/I3Time.cxx#L120
Should read
```text
if (ns <0 || ns >= I3Units::second )
```
instead of
```text
if (ns <0 || sec >= I3Units::second )
```
<details>
<summary>_Migrated from https://code.icecube.wisc.edu/ticket/434
, reported by kislat and owned by blaufuss_</summary>
<p>
```json
{
"status": "closed",
"changetime": "2012-07-27T21:34:03",
"description": "This line: http://code.icecube.wisc.edu/projects/icecube/browser/projects/dataclasses/trunk/private/dataclasses/I3Time.cxx#L120\n\nShould read\n\n{{{\nif (ns <0 || ns >= I3Units::second )\n}}}\n\ninstead of\n\n{{{\nif (ns <0 || sec >= I3Units::second )\n}}}",
"reporter": "kislat",
"cc": "",
"resolution": "fixed",
"_ts": "1343424843000000",
"component": "dataclasses",
"summary": "Minor typo in I3Time.cxx",
"priority": "trivial",
"keywords": "",
"time": "2012-07-19T22:56:16",
"milestone": "",
"owner": "blaufuss",
"type": "defect"
}
```
</p>
</details>
|
1.0
|
Minor typo in I3Time.cxx (Trac #434) - This line: http://code.icecube.wisc.edu/projects/icecube/browser/projects/dataclasses/trunk/private/dataclasses/I3Time.cxx#L120
Should read
```text
if (ns <0 || ns >= I3Units::second )
```
instead of
```text
if (ns <0 || sec >= I3Units::second )
```
<details>
<summary>_Migrated from https://code.icecube.wisc.edu/ticket/434
, reported by kislat and owned by blaufuss_</summary>
<p>
```json
{
"status": "closed",
"changetime": "2012-07-27T21:34:03",
"description": "This line: http://code.icecube.wisc.edu/projects/icecube/browser/projects/dataclasses/trunk/private/dataclasses/I3Time.cxx#L120\n\nShould read\n\n{{{\nif (ns <0 || ns >= I3Units::second )\n}}}\n\ninstead of\n\n{{{\nif (ns <0 || sec >= I3Units::second )\n}}}",
"reporter": "kislat",
"cc": "",
"resolution": "fixed",
"_ts": "1343424843000000",
"component": "dataclasses",
"summary": "Minor typo in I3Time.cxx",
"priority": "trivial",
"keywords": "",
"time": "2012-07-19T22:56:16",
"milestone": "",
"owner": "blaufuss",
"type": "defect"
}
```
</p>
</details>
|
defect
|
minor typo in cxx trac this line should read text if ns second instead of text if ns second migrated from reported by kislat and owned by blaufuss json status closed changetime description this line read n n nif ns second n n ninstead of n n nif ns second n reporter kislat cc resolution fixed ts component dataclasses summary minor typo in cxx priority trivial keywords time milestone owner blaufuss type defect
| 1
|
19,278
| 3,175,887,798
|
IssuesEvent
|
2015-09-24 04:08:39
|
RRUZ/delphi-dev-shell-tools
|
https://api.github.com/repos/RRUZ/delphi-dev-shell-tools
|
closed
|
Manage IDE paths for multiple IDE versions
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1. Install every possible IDE version
2. Try to run one
3. Kaboom!
What is the expected output? What do you see instead?
I get dialog box saying my path is too long. I know - all the IDEs are in
there, plus a few other apps that want to be on the path too. I only run one
IDE version at a time though.
How about adding a small database of path info for each IDE. If I use DDST to
launch the IDE, then check the IDE version I asked for, remove all other IDE
paths, set up the paths for the current version and then launch it.
What version of the product are you using? On what operating system?
v0.1.51.3
Please provide any additional information below.
Love your product! I do tech support for a Delphi/CB add-on company and have
to switch IDE versions many times a day.
```
Original issue reported on code.google.com by `googlegr...@idk-inc.com` on 26 Dec 2013 at 1:35
|
1.0
|
Manage IDE paths for multiple IDE versions - ```
What steps will reproduce the problem?
1. Install every possible IDE version
2. Try to run one
3. Kaboom!
What is the expected output? What do you see instead?
I get dialog box saying my path is too long. I know - all the IDEs are in
there, plus a few other apps that want to be on the path too. I only run one
IDE version at a time though.
How about adding a small database of path info for each IDE. If I use DDST to
launch the IDE, then check the IDE version I asked for, remove all other IDE
paths, set up the paths for the current version and then launch it.
What version of the product are you using? On what operating system?
v0.1.51.3
Please provide any additional information below.
Love your product! I do tech support for a Delphi/CB add-on company and have
to switch IDE versions many times a day.
```
Original issue reported on code.google.com by `googlegr...@idk-inc.com` on 26 Dec 2013 at 1:35
|
defect
|
manage ide paths for multiple ide versions what steps will reproduce the problem install every possible ide version try to run one kaboom what is the expected output what do you see instead i get dialog box saying my path is too long i know all the ides are in there plus a few other apps that want to be on the path too i only run one ide version at a time though how about adding a small database of path info for each ide if i use ddst to launch the ide then check the ide version i asked for remove all other ide paths set up the paths for the current version and then launch it what version of the product are you using on what operating system please provide any additional information below love your product i do tech support for a delphi cb add on company and have to switch ide versions many times a day original issue reported on code google com by googlegr idk inc com on dec at
| 1
|
41,291
| 10,368,831,941
|
IssuesEvent
|
2019-09-07 20:16:14
|
cakephp/bake
|
https://api.github.com/repos/cakephp/bake
|
closed
|
bake all --everything fails with non-default connection
|
Defect
|
There is a problem with the order of operations for "bake all --everything --connection xxx". In cakephp/bake/src/Shell/Task/ModelTask.php function bake() (around line 109), we bake the table, entity, fixture, and test.
The problem is that when baking the test, we go off looking for associations. The associations can be for models which have not yet been baked. Therefore at
cakephp/cakephp/src/ORM/Locator/TableLocator.php line 210:
`$connectionName = $className::defaultConnectionName();`
returns the default connection, because that model class ($className) has not yet been baked.
I can work around the issue by not baking tests/fixtures on the non-default connection. In ModelTask::bake(), between bakeEntity() and bakeFixture() (line 116), I can insert the following workaround:
```
if (array_key_exists('connection', $this->params) && ($this->params['connection'] !== 'default')) {
// Associated models may not yet be baked so their default connection will be unknown
return;
}
```
This is related to #250 but it's not the same issue. I suggest disallowing automatic generation of tests for "bake all everything" on the non-default connection. It's an edge case not worth taking up a lot of time. To do that, insert something like the above code but adding a check for "everything"; add a notice to BakeShell::all() near line 253 that tests/fixtures will not be generated; update documentation for bake all everything.
|
1.0
|
bake all --everything fails with non-default connection - There is a problem with the order of operations for "bake all --everything --connection xxx". In cakephp/bake/src/Shell/Task/ModelTask.php function bake() (around line 109), we bake the table, entity, fixture, and test.
The problem is that when baking the test, we go off looking for associations. The associations can be for models which have not yet been baked. Therefore at
cakephp/cakephp/src/ORM/Locator/TableLocator.php line 210:
`$connectionName = $className::defaultConnectionName();`
returns the default connection, because that model class ($className) has not yet been baked.
I can work around the issue by not baking tests/fixtures on the non-default connection. In ModelTask::bake(), between bakeEntity() and bakeFixture() (line 116), I can insert the following workaround:
```
if (array_key_exists('connection', $this->params) && ($this->params['connection'] !== 'default')) {
// Associated models may not yet be baked so their default connection will be unknown
return;
}
```
This is related to #250 but it's not the same issue. I suggest disallowing automatic generation of tests for "bake all everything" on the non-default connection. It's an edge case not worth taking up a lot of time. To do that, insert something like the above code but adding a check for "everything"; add a notice to BakeShell::all() near line 253 that tests/fixtures will not be generated; update documentation for bake all everything.
|
defect
|
bake all everything fails with non default connection there is a problem with the order of operations for bake all everything connection xxx in cakephp bake src shell task modeltask php function bake around line we bake the table entity fixture and test the problem is that when baking the test we go off looking for associations the associations can be for models which have not yet been baked therefore at cakephp cakephp src orm locator tablelocator php line connectionname classname defaultconnectionname returns the default connection because that model class classname has not yet been baked i can work around the issue by not baking tests fixtures on the non default connection in modeltask bake between bakeentity and bakefixture line i can insert the following workaround if array key exists connection this params this params default associated models may not yet be baked so their default connection will be unknown return this is related to but it s not the same issue i suggest disallowing automatic generation of tests for bake all everything on the non default connection it s an edge case not worth taking up a lot of time to do that insert something like the above code but adding a check for everything add a notice to bakeshell all near line that tests fixtures will not be generated update documentation for bake all everything
| 1
|
47,392
| 13,056,160,846
|
IssuesEvent
|
2020-07-30 03:50:43
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
closed
|
I3ParticleVector pybindings missing bases (Trac #479)
|
Migrated from Trac dataclasses defect
|
I3ParticleVector pybindings are missing the I3FrameObject base, and maybe other things.
We also have a similar pybinding by the name of I3VectorI3Particle that does work. Let's resolve this naming duplication.
Also examine other I3Vector classes for similar problems. I3RecoPulseSeries was noted.
Migrated from https://code.icecube.wisc.edu/ticket/479
```json
{
"status": "closed",
"changetime": "2015-02-12T06:52:34",
"description": "I3ParticleVector pybindings are missing the I3FrameObject base, and maybe other things.\n\nWe also have a similar pybinding by the name of I3VectorI3Particle that does work. Let's resolve this naming duplication.\n\nAlso examine other I3Vector classes for similar problems. I3RecoPulseSeries was noted.",
"reporter": "david.schultz",
"cc": "",
"resolution": "fixed",
"_ts": "1423723954189338",
"component": "dataclasses",
"summary": "I3ParticleVector pybindings missing bases",
"priority": "normal",
"keywords": "",
"time": "2014-01-22T03:15:57",
"milestone": "",
"owner": "olivas",
"type": "defect"
}
```
|
1.0
|
I3ParticleVector pybindings missing bases (Trac #479) - I3ParticleVector pybindings are missing the I3FrameObject base, and maybe other things.
We also have a similar pybinding by the name of I3VectorI3Particle that does work. Let's resolve this naming duplication.
Also examine other I3Vector classes for similar problems. I3RecoPulseSeries was noted.
Migrated from https://code.icecube.wisc.edu/ticket/479
```json
{
"status": "closed",
"changetime": "2015-02-12T06:52:34",
"description": "I3ParticleVector pybindings are missing the I3FrameObject base, and maybe other things.\n\nWe also have a similar pybinding by the name of I3VectorI3Particle that does work. Let's resolve this naming duplication.\n\nAlso examine other I3Vector classes for similar problems. I3RecoPulseSeries was noted.",
"reporter": "david.schultz",
"cc": "",
"resolution": "fixed",
"_ts": "1423723954189338",
"component": "dataclasses",
"summary": "I3ParticleVector pybindings missing bases",
"priority": "normal",
"keywords": "",
"time": "2014-01-22T03:15:57",
"milestone": "",
"owner": "olivas",
"type": "defect"
}
```
|
defect
|
pybindings missing bases trac pybindings are missing the base and maybe other things we also have a similar pybinding by the name of that does work let s resolve this naming duplication also examine other classes for similar problems was noted migrated from json status closed changetime description pybindings are missing the base and maybe other things n nwe also have a similar pybinding by the name of that does work let s resolve this naming duplication n nalso examine other classes for similar problems was noted reporter david schultz cc resolution fixed ts component dataclasses summary pybindings missing bases priority normal keywords time milestone owner olivas type defect
| 1
|
64,150
| 18,247,633,048
|
IssuesEvent
|
2021-10-01 20:51:58
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
closed
|
[FE] Profile: 508-defect-2 [Screen Readers, Cognition]: Focus is lost on error messages
|
508/Accessibility vsa-authenticated-exp profile 508-defect-2 planned-work
|
# [508-defect-2](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-2)
Issue Title: 508 Defect 2, Screen Readers, Cognition, focus gets lost on error messages.
Point of Contact: Angela Fowler
**VFS Point of Contact:** _First name only: Angela
## User Story or Problem Statement:
As a screen reader user, I expect to be able to easily dispatch error messages.
## Details
When editing contact information, in the event that the information can't be updated, an error message will be triggered. Currently, focus is not managed so the user has to navigate through several buttons to find "Close notification." Once the notification is closed, the user cannot proceed until the "update" function is canceled, but once again focus is placed at the top of the page resulting in more tedious navigation.
## Acceptance Criteria
Focus is properly managed throughout the process of dismissing error message.
## Proposed Solution (if known)
Focus should be placed on the "Close notification" button. Once that button is selected, either the "Update" function should be canceled or focus should be placed on the "Cancel" button.
|
1.0
|
[FE] Profile: 508-defect-2 [Screen Readers, Cognition]: Focus is lost on error messages - # [508-defect-2](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-2)
Issue Title: 508 Defect 2, Screen Readers, Cognition, focus gets lost on error messages.
Point of Contact: Angela Fowler
**VFS Point of Contact:** _First name only: Angela
## User Story or Problem Statement:
As a screen reader user, I expect to be able to easily dispatch error messages.
## Details
When editing contact information, in the event that the information can't be updated, an error message will be triggered. Currently, focus is not managed so the user has to navigate through several buttons to find "Close notification." Once the notification is closed, the user cannot proceed until the "update" function is canceled, but once again focus is placed at the top of the page resulting in more tedious navigation.
## Acceptance Criteria
Focus is properly managed throughout the process of dismissing error message.
## Proposed Solution (if known)
Focus should be placed on the "Close notification" button. Once that button is selected, either the "Update" function should be canceled or focus should be placed on the "Cancel" button.
|
defect
|
profile defect focus is lost on error messages issue title defect screen readers cognition focus gets lost on error messages point of contact angela fowler vfs point of contact first name only angela user story or problem statement as a screen reader user i expect to be able to easily dispatch error messages details when editing contact information in the event that the information can t be updated an error message will be triggered currently focus is not managed so the user has to navigate through several buttons to find close notification once the notification is closed the user cannot proceed until the update function is canceled but once again focus is placed at the top of the page resulting in more tedious navigation acceptance criteria focus is properly managed throughout the process of dismissing error message proposed solution if known focus should be placed on the close notification button once that button is selected either the update function should be canceled or focus should be placed on the cancel button
| 1
|
40,031
| 5,266,892,964
|
IssuesEvent
|
2017-02-04 17:19:11
|
benashford/rs-es
|
https://api.github.com/repos/benashford/rs-es
|
opened
|
Coveralls statistics are incomplete
|
bug test coverage
|
I need to revisit the Travis config, I haven't looked at it for a while.
Builds are built and tests are tested, but the coverage statistics haven't been working for a while.
|
1.0
|
Coveralls statistics are incomplete - I need to revisit the Travis config, I haven't looked at it for a while.
Builds are built and tests are tested, but the coverage statistics haven't been working for a while.
|
non_defect
|
coveralls statistics are incomplete i need to revisit the travis config i haven t looked at it for a while builds are built and tests are tested but the coverage statistics haven t been working for a while
| 0
|
7,634
| 2,610,408,192
|
IssuesEvent
|
2015-02-26 20:12:37
|
chrsmith/republic-at-war
|
https://api.github.com/repos/chrsmith/republic-at-war
|
opened
|
Code request
|
auto-migrated Priority-Medium Type-Defect
|
```
Change the scale of GAR HQ building as its to small
```
-----
Original issue reported on code.google.com by `Ana...@gmx-topmail.de` on 6 May 2012 at 5:11
|
1.0
|
Code request - ```
Change the scale of GAR HQ building as its to small
```
-----
Original issue reported on code.google.com by `Ana...@gmx-topmail.de` on 6 May 2012 at 5:11
|
defect
|
code request change the scale of gar hq building as its to small original issue reported on code google com by ana gmx topmail de on may at
| 1
|
650,868
| 21,419,981,144
|
IssuesEvent
|
2022-04-22 14:42:37
|
vdjagilev/nmap-formatter
|
https://api.github.com/repos/vdjagilev/nmap-formatter
|
opened
|
Add option to read xml content from stdin
|
priority/medium tech/go type/feature
|
Add a possibility to read XML content from stdin. This would allow much easier piping.
```bash
nmap -A -T4 -oX - 10.10.10.100 | nmap-formatter json
```
TODO
* [ ] Implement support for stdin read
* [ ] Update documentation examples
* [ ] Change places for file & format arguments?
|
1.0
|
Add option to read xml content from stdin - Add a possibility to read XML content from stdin. This would allow much easier piping.
```bash
nmap -A -T4 -oX - 10.10.10.100 | nmap-formatter json
```
TODO
* [ ] Implement support for stdin read
* [ ] Update documentation examples
* [ ] Change places for file & format arguments?
|
non_defect
|
add option to read xml content from stdin add a possibility to read xml content from stdin this would allow much easier piping bash nmap a ox nmap formatter json todo implement support for stdin read update documentation examples change places for file format arguments
| 0
|
11,465
| 2,651,960,627
|
IssuesEvent
|
2015-03-16 14:55:12
|
adampolak/kuini
|
https://api.github.com/repos/adampolak/kuini
|
closed
|
http://orangstres76.wordpress.com/
|
auto-migrated Priority-Medium Type-Defect
|
```
http://orangstres76.wordpress.com/
```
Original issue reported on code.google.com by `orang...@gmail.com` on 25 Aug 2013 at 7:27
|
1.0
|
http://orangstres76.wordpress.com/ - ```
http://orangstres76.wordpress.com/
```
Original issue reported on code.google.com by `orang...@gmail.com` on 25 Aug 2013 at 7:27
|
defect
|
original issue reported on code google com by orang gmail com on aug at
| 1
|
41,019
| 10,266,482,194
|
IssuesEvent
|
2019-08-22 21:34:46
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
opened
|
[SCREENREADER]: GIBCT® VETTEC - Can we move the Learn more buttons out of the label tags?
|
508-defect-2 508/Accessibility BAH
|
## Description
<!-- This is a detailed description of the issue. It should include a restatement of the title, and provide more background information. -->
The first page of GIBCT® has several `Learn more` buttons that open modals to help users learn more about the benefit in question. These buttons are wrapped inside the `<label>` tag, which is causing some issue with screen readers like NVDA. Users normally can press `ENTER` when the label has virtual cursor focus and move into the related input in forms mode, but the way these are coded, the modals are opening instead. Screenshot attached.
## Point of Contact
<!-- If this issue is being opened by a VFS team member, please add a point of contact. Usually this is the same person who enters the issue ticket.
-->
**VFS Point of Contact:** _Trevor_
## Acceptance Criteria
<!-- As a keyboard user, I want to open the Level of Coverage widget by pressing Spacebar or pressing Enter. These keypress actions should not interfere with the mouse click event also opening the widget. -->
* As a screen reader (NVDA) user, I want to be able to press `ENTER` on the label and have focus set on the related input.
* As this user, I want to be able to focus the `Learn more` button as a separate element, and press `ENTER` or `SPACE` to open the modal window.
## Environment
* Windows 10
* Firefox latest
* NVDA
* https://staging.va.gov/gi-bill-comparison-tool/
## WCAG or Vendor Guidance (optional)
* [Info and Relationships: Understanding SC 1.3.1](https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html)
## Screenshots or Trace Logs
<!-- Drop any screenshots or error logs that might be useful for debugging -->
|
1.0
|
[SCREENREADER]: GIBCT® VETTEC - Can we move the Learn more buttons out of the label tags? - ## Description
<!-- This is a detailed description of the issue. It should include a restatement of the title, and provide more background information. -->
The first page of GIBCT® has several `Learn more` buttons that open modals to help users learn more about the benefit in question. These buttons are wrapped inside the `<label>` tag, which is causing some issue with screen readers like NVDA. Users normally can press `ENTER` when the label has virtual cursor focus and move into the related input in forms mode, but the way these are coded, the modals are opening instead. Screenshot attached.
## Point of Contact
<!-- If this issue is being opened by a VFS team member, please add a point of contact. Usually this is the same person who enters the issue ticket.
-->
**VFS Point of Contact:** _Trevor_
## Acceptance Criteria
<!-- As a keyboard user, I want to open the Level of Coverage widget by pressing Spacebar or pressing Enter. These keypress actions should not interfere with the mouse click event also opening the widget. -->
* As a screen reader (NVDA) user, I want to be able to press `ENTER` on the label and have focus set on the related input.
* As this user, I want to be able to focus the `Learn more` button as a separate element, and press `ENTER` or `SPACE` to open the modal window.
## Environment
* Windows 10
* Firefox latest
* NVDA
* https://staging.va.gov/gi-bill-comparison-tool/
## WCAG or Vendor Guidance (optional)
* [Info and Relationships: Understanding SC 1.3.1](https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html)
## Screenshots or Trace Logs
<!-- Drop any screenshots or error logs that might be useful for debugging -->
|
defect
|
gibct® vettec can we move the learn more buttons out of the label tags description the first page of gibct® has several learn more buttons that open modals to help users learn more about the benefit in question these buttons are wrapped inside the tag which is causing some issue with screen readers like nvda users normally can press enter when the label has virtual cursor focus and move into the related input in forms mode but the way these are coded the modals are opening instead screenshot attached point of contact if this issue is being opened by a vfs team member please add a point of contact usually this is the same person who enters the issue ticket vfs point of contact trevor acceptance criteria as a screen reader nvda user i want to be able to press enter on the label and have focus set on the related input as this user i want to be able to focus the learn more button as a separate element and press enter or space to open the modal window environment windows firefox latest nvda wcag or vendor guidance optional screenshots or trace logs
| 1
|
322,412
| 27,598,671,988
|
IssuesEvent
|
2023-03-09 08:33:47
|
raphaelvallat/pingouin
|
https://api.github.com/repos/raphaelvallat/pingouin
|
closed
|
Variablename "C" leads to a crash in pg.plot_rm_corr
|
invalid :triangular_flag_on_post: docs/testing:book:
|
The following code crashes with a not understandable error message:
```python
import pandas as pd
import pingouin as pg
df_test = pd.DataFrame({"C":[1,2,3,4,5,6], "X":[1,2,3,4,5,6], "VP":[1,1,2,2,3,3]})
pg.plot_rm_corr(df_test, x="C", y="X", subject="VP")
```
Trace
```
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
File /opt/conda/lib/python3.10/site-packages/patsy/compat.py:36, in call_and_wrap_exc(msg, origin, f, *args, **kwargs)
35 try:
---> 36 return f(*args, **kwargs)
37 except Exception as e:
File /opt/conda/lib/python3.10/site-packages/patsy/eval.py:169, in EvalEnvironment.eval(self, expr, source_name, inner_namespace)
168 code = compile(expr, source_name, "eval", self.flags, False)
--> 169 return eval(code, {}, VarLookupDict([inner_namespace]
170 + self._namespaces))
File <string>:1, in <module>
TypeError: 'Series' object is not callable
The above exception was the direct cause of the following exception:
PatsyError Traceback (most recent call last)
Input In [124], in <cell line: 2>()
1 df_test = pd.DataFrame({"C":[1,2,3,4,5,6], "X":[1,2,3,4,5,6], "VP":[1,1,2,2,3,3]})
----> 2 pg.plot_rm_corr(df_test, x="C", y="X", subject="VP")
File /opt/conda/lib/python3.10/site-packages/pingouin/plotting.py:1005, in plot_rm_corr(data, x, y, subject, legend, kwargs_facetgrid, kwargs_line, kwargs_scatter)
996 # Calculate rm_corr
997 # rmc = pg.rm_corr(data=data, x=x, y=y, subject=subject)
998
(...)
1002 # Q allows to quote variable that do not meet Python variable name rule
1003 # e.g. if variable is "weight.in.kg" or "2A"
1004 formula = "Q('%s') ~ C(Q('%s')) + Q('%s')" % (y, subject, x)
-> 1005 model = ols(formula, data=data).fit()
1007 # Fitted values
1008 data["pred"] = model.fittedvalues
File /opt/conda/lib/python3.10/site-packages/statsmodels/base/model.py:200, in Model.from_formula(cls, formula, data, subset, drop_cols, *args, **kwargs)
197 if missing == 'none': # with patsy it's drop or raise. let's raise.
198 missing = 'raise'
--> 200 tmp = handle_formula_data(data, None, formula, depth=eval_env,
201 missing=missing)
202 ((endog, exog), missing_idx, design_info) = tmp
203 max_endog = cls._formula_max_endog
File /opt/conda/lib/python3.10/site-packages/statsmodels/formula/formulatools.py:63, in handle_formula_data(Y, X, formula, depth, missing)
61 else:
62 if data_util._is_using_pandas(Y, None):
---> 63 result = dmatrices(formula, Y, depth, return_type='dataframe',
64 NA_action=na_action)
65 else:
66 result = dmatrices(formula, Y, depth, return_type='dataframe',
67 NA_action=na_action)
File /opt/conda/lib/python3.10/site-packages/patsy/highlevel.py:309, in dmatrices(formula_like, data, eval_env, NA_action, return_type)
299 """Construct two design matrices given a formula_like and data.
300
301 This function is identical to :func:`dmatrix`, except that it requires
(...)
306 See :func:`dmatrix` for details.
307 """
308 eval_env = EvalEnvironment.capture(eval_env, reference=1)
--> 309 (lhs, rhs) = _do_highlevel_design(formula_like, data, eval_env,
310 NA_action, return_type)
311 if lhs.shape[1] == 0:
312 raise PatsyError("model is missing required outcome variables")
File /opt/conda/lib/python3.10/site-packages/patsy/highlevel.py:164, in _do_highlevel_design(formula_like, data, eval_env, NA_action, return_type)
162 def data_iter_maker():
163 return iter([data])
--> 164 design_infos = _try_incr_builders(formula_like, data_iter_maker, eval_env,
165 NA_action)
166 if design_infos is not None:
167 return build_design_matrices(design_infos, data,
168 NA_action=NA_action,
169 return_type=return_type)
File /opt/conda/lib/python3.10/site-packages/patsy/highlevel.py:66, in _try_incr_builders(formula_like, data_iter_maker, eval_env, NA_action)
64 if isinstance(formula_like, ModelDesc):
65 assert isinstance(eval_env, EvalEnvironment)
---> 66 return design_matrix_builders([formula_like.lhs_termlist,
67 formula_like.rhs_termlist],
68 data_iter_maker,
69 eval_env,
70 NA_action)
71 else:
72 return None
File /opt/conda/lib/python3.10/site-packages/patsy/build.py:693, in design_matrix_builders(termlists, data_iter_maker, eval_env, NA_action)
689 factor_states = _factors_memorize(all_factors, data_iter_maker, eval_env)
690 # Now all the factors have working eval methods, so we can evaluate them
691 # on some data to find out what type of data they return.
692 (num_column_counts,
--> 693 cat_levels_contrasts) = _examine_factor_types(all_factors,
694 factor_states,
695 data_iter_maker,
696 NA_action)
697 # Now we need the factor infos, which encapsulate the knowledge of
698 # how to turn any given factor into a chunk of data:
699 factor_infos = {}
File /opt/conda/lib/python3.10/site-packages/patsy/build.py:443, in _examine_factor_types(factors, factor_states, data_iter_maker, NA_action)
441 for data in data_iter_maker():
442 for factor in list(examine_needed):
--> 443 value = factor.eval(factor_states[factor], data)
444 if factor in cat_sniffers or guess_categorical(value):
445 if factor not in cat_sniffers:
File /opt/conda/lib/python3.10/site-packages/patsy/eval.py:568, in EvalFactor.eval(self, memorize_state, data)
567 def eval(self, memorize_state, data):
--> 568 return self._eval(memorize_state["eval_code"],
569 memorize_state,
570 data)
File /opt/conda/lib/python3.10/site-packages/patsy/eval.py:551, in EvalFactor._eval(self, code, memorize_state, data)
549 def _eval(self, code, memorize_state, data):
550 inner_namespace = VarLookupDict([data, memorize_state["transforms"]])
--> 551 return call_and_wrap_exc("Error evaluating factor",
552 self,
553 memorize_state["eval_env"].eval,
554 code,
555 inner_namespace=inner_namespace)
File /opt/conda/lib/python3.10/site-packages/patsy/compat.py:43, in call_and_wrap_exc(msg, origin, f, *args, **kwargs)
39 new_exc = PatsyError("%s: %s: %s"
40 % (msg, e.__class__.__name__, e),
41 origin)
42 # Use 'exec' to hide this syntax from the Python 2 parser:
---> 43 exec("raise new_exc from e")
44 else:
45 # In python 2, we just let the original exception escape -- better
46 # than destroying the traceback. But if it's a PatsyError, we can
47 # at least set the origin properly.
48 if isinstance(e, PatsyError):
File <string>:1, in <module>
PatsyError: Error evaluating factor: TypeError: 'Series' object is not callable
Q('X') ~ C(Q('VP')) + Q('C')
^^^^^^^^^^
```
It seems like the error is caused by the usage of the variablename "C" in the dataframe which can be traced back to patsy
(https://github.com/pydata/patsy/issues/174). Also when the error is caused by patsy it would be nice if the user can be warned to not use C as a variable name.
|
1.0
|
Variablename "C" leads to a crash in pg.plot_rm_corr - The following code crashes with a not understandable error message:
```python
import pandas as pd
import pingouin as pg
df_test = pd.DataFrame({"C":[1,2,3,4,5,6], "X":[1,2,3,4,5,6], "VP":[1,1,2,2,3,3]})
pg.plot_rm_corr(df_test, x="C", y="X", subject="VP")
```
Trace
```
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
File /opt/conda/lib/python3.10/site-packages/patsy/compat.py:36, in call_and_wrap_exc(msg, origin, f, *args, **kwargs)
35 try:
---> 36 return f(*args, **kwargs)
37 except Exception as e:
File /opt/conda/lib/python3.10/site-packages/patsy/eval.py:169, in EvalEnvironment.eval(self, expr, source_name, inner_namespace)
168 code = compile(expr, source_name, "eval", self.flags, False)
--> 169 return eval(code, {}, VarLookupDict([inner_namespace]
170 + self._namespaces))
File <string>:1, in <module>
TypeError: 'Series' object is not callable
The above exception was the direct cause of the following exception:
PatsyError Traceback (most recent call last)
Input In [124], in <cell line: 2>()
1 df_test = pd.DataFrame({"C":[1,2,3,4,5,6], "X":[1,2,3,4,5,6], "VP":[1,1,2,2,3,3]})
----> 2 pg.plot_rm_corr(df_test, x="C", y="X", subject="VP")
File /opt/conda/lib/python3.10/site-packages/pingouin/plotting.py:1005, in plot_rm_corr(data, x, y, subject, legend, kwargs_facetgrid, kwargs_line, kwargs_scatter)
996 # Calculate rm_corr
997 # rmc = pg.rm_corr(data=data, x=x, y=y, subject=subject)
998
(...)
1002 # Q allows to quote variable that do not meet Python variable name rule
1003 # e.g. if variable is "weight.in.kg" or "2A"
1004 formula = "Q('%s') ~ C(Q('%s')) + Q('%s')" % (y, subject, x)
-> 1005 model = ols(formula, data=data).fit()
1007 # Fitted values
1008 data["pred"] = model.fittedvalues
File /opt/conda/lib/python3.10/site-packages/statsmodels/base/model.py:200, in Model.from_formula(cls, formula, data, subset, drop_cols, *args, **kwargs)
197 if missing == 'none': # with patsy it's drop or raise. let's raise.
198 missing = 'raise'
--> 200 tmp = handle_formula_data(data, None, formula, depth=eval_env,
201 missing=missing)
202 ((endog, exog), missing_idx, design_info) = tmp
203 max_endog = cls._formula_max_endog
File /opt/conda/lib/python3.10/site-packages/statsmodels/formula/formulatools.py:63, in handle_formula_data(Y, X, formula, depth, missing)
61 else:
62 if data_util._is_using_pandas(Y, None):
---> 63 result = dmatrices(formula, Y, depth, return_type='dataframe',
64 NA_action=na_action)
65 else:
66 result = dmatrices(formula, Y, depth, return_type='dataframe',
67 NA_action=na_action)
File /opt/conda/lib/python3.10/site-packages/patsy/highlevel.py:309, in dmatrices(formula_like, data, eval_env, NA_action, return_type)
299 """Construct two design matrices given a formula_like and data.
300
301 This function is identical to :func:`dmatrix`, except that it requires
(...)
306 See :func:`dmatrix` for details.
307 """
308 eval_env = EvalEnvironment.capture(eval_env, reference=1)
--> 309 (lhs, rhs) = _do_highlevel_design(formula_like, data, eval_env,
310 NA_action, return_type)
311 if lhs.shape[1] == 0:
312 raise PatsyError("model is missing required outcome variables")
File /opt/conda/lib/python3.10/site-packages/patsy/highlevel.py:164, in _do_highlevel_design(formula_like, data, eval_env, NA_action, return_type)
162 def data_iter_maker():
163 return iter([data])
--> 164 design_infos = _try_incr_builders(formula_like, data_iter_maker, eval_env,
165 NA_action)
166 if design_infos is not None:
167 return build_design_matrices(design_infos, data,
168 NA_action=NA_action,
169 return_type=return_type)
File /opt/conda/lib/python3.10/site-packages/patsy/highlevel.py:66, in _try_incr_builders(formula_like, data_iter_maker, eval_env, NA_action)
64 if isinstance(formula_like, ModelDesc):
65 assert isinstance(eval_env, EvalEnvironment)
---> 66 return design_matrix_builders([formula_like.lhs_termlist,
67 formula_like.rhs_termlist],
68 data_iter_maker,
69 eval_env,
70 NA_action)
71 else:
72 return None
File /opt/conda/lib/python3.10/site-packages/patsy/build.py:693, in design_matrix_builders(termlists, data_iter_maker, eval_env, NA_action)
689 factor_states = _factors_memorize(all_factors, data_iter_maker, eval_env)
690 # Now all the factors have working eval methods, so we can evaluate them
691 # on some data to find out what type of data they return.
692 (num_column_counts,
--> 693 cat_levels_contrasts) = _examine_factor_types(all_factors,
694 factor_states,
695 data_iter_maker,
696 NA_action)
697 # Now we need the factor infos, which encapsulate the knowledge of
698 # how to turn any given factor into a chunk of data:
699 factor_infos = {}
File /opt/conda/lib/python3.10/site-packages/patsy/build.py:443, in _examine_factor_types(factors, factor_states, data_iter_maker, NA_action)
441 for data in data_iter_maker():
442 for factor in list(examine_needed):
--> 443 value = factor.eval(factor_states[factor], data)
444 if factor in cat_sniffers or guess_categorical(value):
445 if factor not in cat_sniffers:
File /opt/conda/lib/python3.10/site-packages/patsy/eval.py:568, in EvalFactor.eval(self, memorize_state, data)
567 def eval(self, memorize_state, data):
--> 568 return self._eval(memorize_state["eval_code"],
569 memorize_state,
570 data)
File /opt/conda/lib/python3.10/site-packages/patsy/eval.py:551, in EvalFactor._eval(self, code, memorize_state, data)
549 def _eval(self, code, memorize_state, data):
550 inner_namespace = VarLookupDict([data, memorize_state["transforms"]])
--> 551 return call_and_wrap_exc("Error evaluating factor",
552 self,
553 memorize_state["eval_env"].eval,
554 code,
555 inner_namespace=inner_namespace)
File /opt/conda/lib/python3.10/site-packages/patsy/compat.py:43, in call_and_wrap_exc(msg, origin, f, *args, **kwargs)
39 new_exc = PatsyError("%s: %s: %s"
40 % (msg, e.__class__.__name__, e),
41 origin)
42 # Use 'exec' to hide this syntax from the Python 2 parser:
---> 43 exec("raise new_exc from e")
44 else:
45 # In python 2, we just let the original exception escape -- better
46 # than destroying the traceback. But if it's a PatsyError, we can
47 # at least set the origin properly.
48 if isinstance(e, PatsyError):
File <string>:1, in <module>
PatsyError: Error evaluating factor: TypeError: 'Series' object is not callable
Q('X') ~ C(Q('VP')) + Q('C')
^^^^^^^^^^
```
It seems like the error is caused by the usage of the variablename "C" in the dataframe which can be traced back to patsy
(https://github.com/pydata/patsy/issues/174). Also when the error is caused by patsy it would be nice if the user can be warned to not use C as a variable name.
|
non_defect
|
variablename c leads to a crash in pg plot rm corr the following code crashes with a not understandable error message python import pandas as pd import pingouin as pg df test pd dataframe c x vp pg plot rm corr df test x c y x subject vp trace typeerror traceback most recent call last file opt conda lib site packages patsy compat py in call and wrap exc msg origin f args kwargs try return f args kwargs except exception as e file opt conda lib site packages patsy eval py in evalenvironment eval self expr source name inner namespace code compile expr source name eval self flags false return eval code varlookupdict self namespaces file in typeerror series object is not callable the above exception was the direct cause of the following exception patsyerror traceback most recent call last input in in df test pd dataframe c x vp pg plot rm corr df test x c y x subject vp file opt conda lib site packages pingouin plotting py in plot rm corr data x y subject legend kwargs facetgrid kwargs line kwargs scatter calculate rm corr rmc pg rm corr data data x x y y subject subject q allows to quote variable that do not meet python variable name rule e g if variable is weight in kg or formula q s c q s q s y subject x model ols formula data data fit fitted values data model fittedvalues file opt conda lib site packages statsmodels base model py in model from formula cls formula data subset drop cols args kwargs if missing none with patsy it s drop or raise let s raise missing raise tmp handle formula data data none formula depth eval env missing missing endog exog missing idx design info tmp max endog cls formula max endog file opt conda lib site packages statsmodels formula formulatools py in handle formula data y x formula depth missing else if data util is using pandas y none result dmatrices formula y depth return type dataframe na action na action else result dmatrices formula y depth return type dataframe na action na action file opt conda lib site packages patsy highlevel py in dmatrices formula like data eval env na action return type construct two design matrices given a formula like and data this function is identical to func dmatrix except that it requires see func dmatrix for details eval env evalenvironment capture eval env reference lhs rhs do highlevel design formula like data eval env na action return type if lhs shape raise patsyerror model is missing required outcome variables file opt conda lib site packages patsy highlevel py in do highlevel design formula like data eval env na action return type def data iter maker return iter design infos try incr builders formula like data iter maker eval env na action if design infos is not none return build design matrices design infos data na action na action return type return type file opt conda lib site packages patsy highlevel py in try incr builders formula like data iter maker eval env na action if isinstance formula like modeldesc assert isinstance eval env evalenvironment return design matrix builders formula like lhs termlist formula like rhs termlist data iter maker eval env na action else return none file opt conda lib site packages patsy build py in design matrix builders termlists data iter maker eval env na action factor states factors memorize all factors data iter maker eval env now all the factors have working eval methods so we can evaluate them on some data to find out what type of data they return num column counts cat levels contrasts examine factor types all factors factor states data iter maker na action now we need the factor infos which encapsulate the knowledge of how to turn any given factor into a chunk of data factor infos file opt conda lib site packages patsy build py in examine factor types factors factor states data iter maker na action for data in data iter maker for factor in list examine needed value factor eval factor states data if factor in cat sniffers or guess categorical value if factor not in cat sniffers file opt conda lib site packages patsy eval py in evalfactor eval self memorize state data def eval self memorize state data return self eval memorize state memorize state data file opt conda lib site packages patsy eval py in evalfactor eval self code memorize state data def eval self code memorize state data inner namespace varlookupdict return call and wrap exc error evaluating factor self memorize state eval code inner namespace inner namespace file opt conda lib site packages patsy compat py in call and wrap exc msg origin f args kwargs new exc patsyerror s s s msg e class name e origin use exec to hide this syntax from the python parser exec raise new exc from e else in python we just let the original exception escape better than destroying the traceback but if it s a patsyerror we can at least set the origin properly if isinstance e patsyerror file in patsyerror error evaluating factor typeerror series object is not callable q x c q vp q c it seems like the error is caused by the usage of the variablename c in the dataframe which can be traced back to patsy also when the error is caused by patsy it would be nice if the user can be warned to not use c as a variable name
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.